From: Stephen Gregoratto <dev@sgregoratto.me>
To: discuss@mandoc.bsd.lv
Subject: Google Season of Docs
Date: Wed, 17 Apr 2019 09:31:20 +1000 [thread overview]
Message-ID: <20190416233120.xpejittxfbt743o7@BlackBox> (raw)
Much like the Summer of Code, Google is now sponsoring a Season of
Docs[1] to improve Open Source documentation. There's still time for
organisations to submit applications for entry (until April 23 20:00
UTC).
The application details for projects are available here[2], but the gist
is as follows:
- Get at least two "administrators" to oversee your projects
- Create a list of writing projects and then assign at least two
mentors for each of them. There's a couple of project ideas that
Google suggest here[3], but I'm sure you have your own.
- When you have finalised your list, publish them online.
- Submit your application and sign up your admins, mentors before the
23rd.
After this, technical writers apply and get in contact with orgs.
There's too much info here for me to summarise, so I'll just link the
timeline[4]. Note that the actual writing period is Sep 2-Nov 22.
Since I'm singing up I thought I'd let you'd know, seems like something
you might be interested in.
[1] https://developers.google.com/season-of-docs/docs/
[2] https://developers.google.com/season-of-docs/docs/admin-guide
[3] https://developers.google.com/season-of-docs/docs/project-ideas
[4] https://developers.google.com/season-of-docs/docs/timeline
--
Stephen Gregoratto
PGP: 3FC6 3D0E 2801 C348 1C44 2D34 A80C 0F8E 8BAB EC8B
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next reply other threads:[~2019-04-16 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 23:31 Stephen Gregoratto [this message]
2019-04-17 0:01 ` Ingo Schwarze
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190416233120.xpejittxfbt743o7@BlackBox \
--to=dev@sgregoratto.me \
--cc=discuss@mandoc.bsd.lv \
/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.
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 NNTP newsgroup(s).