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.
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. 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. Organization applications open on April 2, 2019. See the full 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.
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
You received this message because you are subscribed to the Google Groups "Google Summer of Code Mentors List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
.
.
.
.