Hi, Google Season of Docs is starting soon. It is similar to GSoC, but the aim is improving the docs of open source projects. There are also some differences. For example, experienced technical writers are expected, instead of students.
Do you think we (DebianEdu, with the help of Debian Outreach Team) can participate? The project goals might be: - Migrating the DebianEdu documentation from wiki to a text based documentation system that can be managed with Git and GitHub/GitLab. See also Documentation as Code: https://docs-as-co.de/. - Reorganizing the docs into Installation, Usage, and Development guides. Right now everything is in the same manual, but the information about development is almost nonexistent, and the usage information is very lacking. For example there are no details about how to use Veyon, or squidguard, etc. So, this would also require adding some more details to the docs, that are already missing. I do have some experience with technical writing, so I can be a possible candidate for the technical writer. But other candidates may be considered as well. Regards, Dashamir ---------- Forwarded message --------- From: Season of Docs - Announce <season-of-docs-annou...@googlegroups.com> Date: Wed, Jan 18, 2023 at 8:01 PM Subject: [Season of Docs - Announcements] Announcing Google Season of Docs 2023 To: Season of Docs - Announce <season-of-docs-annou...@googlegroups.com> Google Open Source is delighted to announce Google Season of Docs <http://developers.google.com/season-of-docs> 2023! The Google Season of Docs program supports better documentation in open source and provides opportunities for skilled technical writers to gain open source experience. Participating projects receive funds to create, improve, or expand their documentation, while contributing to our knowledge of effective metrics for evaluating open source documentation through their shared case studies <https://developers.google.com/season-of-docs/docs/2022/participants>. About the program Google Season of Docs allows open source organizations to apply for a grant based on their documentation needs. If selected, the open source organizations use their grant to hire a technical writer directly to complete their documentation project. Organizations have up to six months to complete their documentation project. Participating organizations help broaden our understanding of effective documentation practices and metrics in open source by submitting a final case study upon completion of the program. The case study should outline the problem the documentation project was intended to solve, what metrics were used to judge the effectiveness of the documentation, and what the organization learned for the future. All project case studies will be published on the Google Season of Docs site at the end of the program. Organizations: start your exploration engines 2023 Google Season of Docs applications open February 15, 2023. We strongly suggest that organizations take the time to complete the steps in the exploration phase <https://developers.google.com/season-of-docs/docs/admin-guide#exploration_phase> before the application process begins, including: - Creating a project page to gauge community and technical writer interest in participating (see our project ideas page <https://developers.google.com/season-of-docs/docs/project-ideas> for examples) - Publicizing your interest in participating in Season of Docs through your project channels and adding your project to our list of interested projects on GitHub <https://github.com/google/season-of-docs> - Lining up community members who are interested in mentoring or helping to onboard technical writers to your project - Brainstorming requirements for technical writers to work on your project (Will they need to be able to test code? Work with video? Have prior experience with your project or related technologies?) On your mark, get set, project page! Every Google Season of Docs project begins with a project page. Your project page serves as an overview of your documentation project, and it should be publicly visible. A good project page includes: - A statement of the problem your project needs to solve (“users on Windows don’t have clear guidance of how to install our project”) - The documentation that might solve this problem (“We want to create a quickstart doc and installation guide for Windows users”) - How you’ll measure the success of your documentation (“With a good quickstart, we expect to see 50% fewer issues opened about Windows installation problems.”) - What skills your technical writer would need (break down into “must have” and “nice to have” categories. “Must have: access Windows machine to test instructions”) - What volunteer help is needed from community members (“need help onboarding technical writer to our discussion groups”) and links to where the community can discuss the proposal - Most importantly, include a way for interested technical writers to reach you and ask questions! Technical writers: express your interest Technical writers interested in working with accepted open source organizations can share their contact information via the Google Season of Docs GitHub repository <https://github.com/google/season-of-docs>; or they may submit proposals directly to the organizations using the contact information shared on the organization project page. Technical writers do not submit a formal application through Season of Docs. Join us! Explore the Google Season of Docs website at g.co/seasonofdocs to learn more about participating in the program. Use our logo and other promotional resources to spread the word <https://developers.google.com/season-of-docs/docs/press>. Check out the timeline <https://developers.google.com/season-of-docs/docs/timeline> and FAQ <https://developers.google.com/season-of-docs/docs/faq>, and get ready to apply! If you have any questions about the program, please email us at season-of-d...@google.com. We’re looking forward to another productive year of the Google Season of Docs program! Best regards, Romina Vicente, Erin McKean, and the Season of Docs team -- You received this message because you are subscribed to the Google Groups "Season of Docs - Announce" group. To unsubscribe from this group and stop receiving emails from it, send an email to season-of-docs-announce+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/season-of-docs-announce/14ff57ee-9819-4eb4-a556-0bb6a3296eedn%40googlegroups.com <https://groups.google.com/d/msgid/season-of-docs-announce/14ff57ee-9819-4eb4-a556-0bb6a3296eedn%40googlegroups.com?utm_medium=email&utm_source=footer> .
