ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: TeXLive <tex-live@tug.org>, TUG office <office@tug.org>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Fwd: Announcing Season of Docs 2019
Date: Tue, 2 Apr 2019 22:47:12 +0200	[thread overview]
Message-ID: <CALBOmsbk2fbRqZi--HKbP1Bgfc-RwKC0f2P4BXX0r5Q01g8s8w@mail.gmail.com> (raw)
In-Reply-To: <563595bc-e36d-411e-9868-71a5f75742a4@googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 2940 bytes --]

Hi,

This is just to let you know that Google started accepting applications for
organisations that want to participate in "Google season of docs", offering
stipends to technical writers to work full time on improving documentation
of open source projects.

See also a list of sample ideas:
    https://developers.google.com/season-of-docs/docs/project-ideas
(but maybe some improvement of the writing tools could also count, I don't
know).

Participation is not limited to students this time.

Is any of the TeX user groups interested in participating?

Mojca


---------- Forwarded message ---------
From: 'sttaylor' via Google Summer of Code Mentors List
Date: Mon, 11 Mar 2019 at 23:32

We’re delighted to announce the inaugural year of Season of Docs, a Google
program that fosters collaboration between open source projects and
technical writers. Season of Docs is similar to Summer of Code, but with a
focus on open source documentation and technical writers. Details are on
our website: g.co/seasonofdocs
<https://developers.google.com/season-of-docs/>.

Would you like to take part as an open source mentor in the inaugural year
of Season of Docs? Open source organizations can start thinking now about
the projects you’d like a technical writer to work on. Take a look at
the examples
of project ideas
<https://developers.google.com/season-of-docs/docs/project-ideas>. Reach
out to your community members to see who’d like to be a mentor for Season
of Docs. As a mentor, you don’t need technical writing skills. Instead,
you're a member of the open source organization who knows the value of good
documentation and who is experienced in open source processes and tools.
See the guidelines on working with a technical writer
<https://developers.google.com/season-of-docs/docs/tech-writer-collaboration>.
Organization applications open on April 2, 2019. See the full timeline
<https://developers.google.com/season-of-docs/docs/timeline> on the Season
of Docs website.

>From April 30, Technical writers can explore the list of participating open
source organizations and their project ideas. Technical writers bring their
skills in designing and developing documentation to the open source
organization. Technical writer applications open on April 30. The list of
accepted technical writing projects is announced on July 30.

Please do tweet and blog about Season of Docs if you’d like to share the
news. We want as many people to know about it as possible. We’ve provided
logos that you can download and some example content on the press page
<https://developers.google.com/season-of-docs/docs/press>.

We’re looking forward to an exciting pilot of the Season of Docs program!

If you have any questions about the program, please email us at
season-of-docs-support@googlegroups.com.

Best regards

Sarah Maddox, Andrew Chen and the Season of Docs team

[-- Attachment #2: Type: text/html, Size: 7585 bytes --]

       reply	other threads:[~2019-04-02 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <563595bc-e36d-411e-9868-71a5f75742a4@googlegroups.com>
2019-04-02 20:47 ` Mojca Miklavec [this message]
2019-04-03  9:17   ` Henning Hraban Ramm
2019-04-03 11:40     ` juh

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=CALBOmsbk2fbRqZi--HKbP1Bgfc-RwKC0f2P4BXX0r5Q01g8s8w@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=office@tug.org \
    --cc=tex-live@tug.org \
    /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).