git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philip Oakley <philipoakley@iee.org>
To: Thomas Gummerer <t.gummerer@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Google "Season of Docs"
Date: Mon, 1 Apr 2019 10:05:47 +0100	[thread overview]
Message-ID: <4eefb159-c219-0936-12de-e0c5844c3815@iee.org> (raw)
In-Reply-To: <20190331214900.GX32487@hank.intra.tgummerer.com>

Hi Thomas

On 31/03/2019 22:49, Thomas Gummerer wrote:
> On 03/30, Philip Oakley wrote:
>> We mentor Summer of Code projects.
>> Perhaps we should be doing something similar for docs.  Now Google are:
> One thing that I think is worth highlighting, that I don't think is
> clear from the blog post or this email, is that in contrast to Google
> Summer of Code, Season of Docs targets experienced technical writers,
> rather than students.  Just leaving this here for anyone that's just
> reading this email and/or the blog post.
I had noticed that they were including experienced technical writers, 
hence my hope that maybe we could learn something from them. It's all to 
easy for devs to say that users never read the documentation without 
appreciating that it may not be readable nor understandable from the 
user perspective, an inverse impostor syndrome effect. Perhaps [1] says 
it all ;-)

Philip

[1] https://git-man-page-generator.lokaltog.net/



      reply	other threads:[~2019-04-01  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8bb78ce0-9b32-7c49-e4aa-ce9f31662627@thingbag.net>
2019-03-30 17:17 ` Google "Season of Docs" Philip Oakley
2019-03-31  6:41   ` Kapil Jain
2019-03-31 22:19     ` Philip Oakley
2019-03-31 21:49   ` Thomas Gummerer
2019-04-01  9:05     ` Philip Oakley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4eefb159-c219-0936-12de-e0c5844c3815@iee.org \
    --to=philipoakley@iee.org \
    --cc=git@vger.kernel.org \
    --cc=t.gummerer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).