-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #5471 from iArchitSharma/gsod
GSOD 2024 page added
- Loading branch information
Showing
2 changed files
with
200 additions
and
0 deletions.
There are no files selected for viewing
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,200 @@ | ||
| --- | ||
| title: "Google Season of Docs 2024" | ||
| thumbnail: ./gsod.webp | ||
| permalink: "gsod/2024" | ||
| published: true | ||
| program: "Google Season of Docs" | ||
| programSlug: "gsod" | ||
| redirect_from: | ||
| - /gsod/2024/ | ||
| --- | ||
|
|
||
| import { ProgramsWrapper } from "../Programs.style.js"; | ||
| import gsod_logo from "./gsod.webp"; | ||
|
|
||
| <ProgramsWrapper> | ||
|
|
||
| ## Layer5 | ||
|
|
||
| [Layer5.io](http://layer5.io) is applying to participate in [Google Season of Docs 2024](https://developers.google.com/season-of-docs). | ||
|
|
||
| [Google Season of Docs](https://g.co/seasonofdocs) provides support for open-source projects to improve their documentation and allows professional technical writers to gain experience in open source. The technical writer will collaborate with other engineers and core mentors. | ||
|
|
||
| Together we raise awareness of open source, of docs, and of technical writing. The GSoD 2024 grants range from $5,000 to $15,000 depending on the project's budget. | ||
|
|
||
| ## Summary | ||
|
|
||
| 1. About Layer5 and its projects | ||
| 2. About Meshery | ||
| 3. About our community | ||
| 4. How to apply | ||
| 5. Project Idea: Meshery’s users facing doc audit and update | ||
| 6. Timeline | ||
| 7. Budget | ||
| 8. Additional information | ||
|
|
||
| ### About Layer5 and its projects | ||
| The Layer5 community represents the largest collection of cloud native projects and their maintainers in the world. Our inclusive and diverse community stewards projects to provide learning environments, create and implement cloud native industry standards, deployment and operational best practices, benchmarks and abstractions, and more. Our pay-it-forward mentality with every contributor (mentee or not) is a shared commitment by all maintainers (and MeshMates - contributor onboarding buddies) to the open source spirit that pushes Layer5 projects like Meshery forward. New members are always welcome. | ||
|
|
||
| ### About Meshery | ||
| A self-service engineering platform, Meshery, is the open source, cloud native manager that enables the design and management of all Kubernetes-based infrastructure and applications (multi-cloud). Among other features, As an extensible platform, Meshery offers visual and collaborative GitOps, freeing you from the chains of YAML while managing Kubernetes multi-cluster deployments. | ||
|
|
||
| Additionally, Meshery boasts an impressive growth trajectory, ranking as the 10th fastest growing project under the Cloud Native Computing Foundation (CNCF) with 4900+ GitHub stars, 430+ total releases and 1500+ GitHub forks. | ||
|
|
||
| ### About our Community | ||
| Layer5 is all about [its community](https://layer5.io/community) of [contributors](https://layer5.io/community/members). We have designed an onboarding program customized to [meet newcomers](https://layer5.io/community/newcomers) where they’re at and developed an onboarding buddy program, [MeshMates](https://layer5.io/community/meshmates) with individuals dedicated to assisting contributors. Layer5 and Meshery have been around for 4+ years and have a healthy, growing community of 5000+ community members. The layer5.io website itself is open source and created by 521+ of our contributors. | ||
|
|
||
| ## How to Apply | ||
|
|
||
| We interact daily over [Slack](https://slack.layer5.io/) | ||
|
|
||
| Interested writers please contact us through #documenation Layer5 slack channel, or mail us at [email protected] | ||
|
|
||
| If you have further question on participating or how to get started, please ask them in any public Layer5 slack channel so that others can also learn from answers to your questions, please visit Layer5 Discuss Forum for previous questions asked by other contributors. | ||
|
|
||
| Visit official technical writer guide for more information | ||
| ## Project Ideas | ||
|
|
||
| ### Meshery’s users facing doc audit and update | ||
|
|
||
| #### The problem: | ||
| Meshery is a open source cloud-native management platform with over 200+ integrations and experiencing significant growth in contributions over the past few years, Meshery has continuously evolved to enhance the user experience. New features have been introduced, and Meshery's internal architecture has been improved to meet the demands of its user base. | ||
|
|
||
| However, with this rapid development, we have identified many new contributors and Meshery’s users post questions on project best practices, tutorials with various integrations and contributions in Meshery which lead some of them to give up contributing or using Meshery due to lack of documentation in certain areas. | ||
|
|
||
| Meshery’s documentation - https://docs.meshery.io/ | ||
|
|
||
| ### Project Scope | ||
|
|
||
| 1. Check and analyze Meshery’s documentation to identify areas for improvement. Gather data from GitHub issues and the Layer5 #documentation Slack channel. | ||
| 2. Explore Meshery’s existing architecture and UI at playground.meshery.io to pinpoint areas not covered in the current documentation or areas needing improvement. | ||
| 3. Meshery integrates with numerous technologies. Select your area of proficiency and technology, then create a new learning path for it. Refer to GitHub issue #9832 for more information. | ||
| 4. Identify outdated information and update it with the latest features and functionalities. | ||
| 5. Enhance Meshery’s troubleshooting pages by incorporating the most common scenarios reported by Meshery’s users and contributors. | ||
| 6. Update Meshery’s README with the latest functionalities and visuals. | ||
| 7. Restructure the documentation layout to better align with the needs and interests of users. | ||
|
|
||
| ### How We Would Measure Success | ||
|
|
||
| 1. Increase in the number of closed issues tagged with “area/docs.” | ||
| 2. Feedback from users on how intuitive the documentation is (qualitative - tracked through user polls) | ||
| 3. Increased number of learning paths. | ||
| 4. Increased coverage on addressing common challenges experienced by contributors and users. | ||
|
|
||
| ### Required Skills for a Technical Writer | ||
|
|
||
| **Must-Have:** | ||
| - Technical writing experience. | ||
| - Familiarity with GitHub. | ||
| - Strong organizational skills. | ||
| - Ability and willingness to seek feedback from the target audience, and use this feedback to improve the documentation. | ||
|
|
||
| ***Nice to Have - *** | ||
| - Basic knowledge of Kubernetes. | ||
| - Familiarity with Jekyll and JavaScript. | ||
|
|
||
| ### Volunteers | ||
|
|
||
| [Uzair Shaikh](mailto:[email protected]), [Aabid Sofi](mailto:[email protected]), [Yash Sharma](mailto:[email protected]), can help with answering questions about Meshery | ||
|
|
||
| [Vivek Vishal](mailto:[email protected]), [Archit Sharma]([email protected]), happy to review docs pull requests | ||
|
|
||
| [Ritik Saxena](mailto:[email protected]) can help with creating visuals/GIFs | ||
|
|
||
| We will bring support from the Meshery CI WG, provide a full-time visual and user experience designer and well as three dedicated core maintainers of Meshery. We have one strong technical writing candidate for this project. We will support this technical writer and prioritize any dependencies on the project or community that they may have. | ||
|
|
||
| ## Project budget | ||
| <br /> | ||
| <div class="gsod-table-container"> | ||
| <table class="tutorials-table"> | ||
| <thead> | ||
| <tr> | ||
| <th>Budget Item</th> | ||
| <th>Amount</th> | ||
| <th>Running Total</th> | ||
| <th>Notes</th> | ||
| </tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td>Technical Writer stipend</td> | ||
| <td>$7,000</td> | ||
| <td>$7,000</td> | ||
| <td>Technical writer is expected to learn much and be diligent with their efforts. They should be well rewarded.</td> | ||
| <td></td> | ||
| </tr> | ||
| <tr> | ||
| <td>Mentor volunteer stipend</td> | ||
| <td>$500</td> | ||
| <td>$7,500</td> | ||
| <td>This volunteer mentor will be put much time into the project and into the success of the technical writer; should be rewarded.</td> | ||
| <td></td> | ||
| </tr> | ||
| <tr> | ||
| <td>Microphone for Technical Writer for remote collaboration</td> | ||
| <td>$150</td> | ||
| <td>$7,650</td> | ||
| <td>Clear communication is key to successful, remote collaboration. This is meant to facilitate collaboration, be a reward for participating, and be useful long-term for the technical writer.</td> | ||
| <td></td> | ||
| </tr> | ||
| <tr style="font-weight:bold;"> | ||
| <td>Total:</td> | ||
| <td></td> | ||
| <td>$7,650</td> | ||
| <td></td> | ||
| <td></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| </div> | ||
| <br /> | ||
|
|
||
| ## Timeline | ||
|
|
||
| The project is expected to last around six months. Below is an estimated timeline of the deliverables. | ||
|
|
||
| <br /> | ||
| <div class="gsod-table-container"> | ||
| <table class="tutorials-table"> | ||
| <thead> | ||
| <tr> | ||
| <th>Date</th> | ||
| <th>Action</th> | ||
| </tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td>May</td> | ||
| <td>Technical writer orientation</td> | ||
| </tr> | ||
| <tr> | ||
| <td>June</td> | ||
| <td>Drafting areas of improvement, Feedback, Refine</td> | ||
| </tr> | ||
| <tr> | ||
| <td>July - October</td> | ||
| <td>Writing documentation</td> | ||
| </tr> | ||
| <tr style="font-weight:bold;"> | ||
| <td>November</td> | ||
| <td>Feedback and adjustments</td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| </div> | ||
| <br /> | ||
|
|
||
| ## List of Org Admins | ||
|
|
||
| - [Lee Calcote](mailto:[email protected]) | ||
|
|
||
| ## Additional information | ||
| We will create a new set of interactive documentation for Meshery users to both learn how to use Meshery. We have a number of community volunteers lined up and committed to collaboration on the enhancement of existing documentation. The technical writer will collaborate with other engineers, working with Jekyll and Docusaurus. | ||
| ### Previous experience with technical writers or documentation | ||
| Our mentors have managed teams of technical writers working on documenting enterprise-grade software at large technology companies (Cisco, Seagate, SolarWinds). During the span of time, he has worked with technical writers in DITA and post-DITA environments (from Word to FrameMaker, structured writing, online help, various CMSes, git). Our mentors have worked with technical writers on documentation strategy, creating document sets, covering the full spectrum of reader personas. | ||
| ### Previous participation in Season of Docs, Google Summer of Code or others: | ||
| Layer5 and its mentors have participated as mentors in MLH, LFX, FOSSASIA, GSoD 2020, GSoC 2019, 2020, 2021, 2022 and are in 2024 under CNCF. Mentoring and seeing others learn and grow is what Layer5 is all about - it’s a platform for mentees to hoist themselves up on and leapfrog from. We’re a platform for shared success. | ||
|
|
||
| We interact daily over Slack, and have an open source project [meeting everyday](https://layer5.io/community/calendar), which are posted to the community [YouTube channel](https://www.youtube.com/channel/UCFL1af7_wdnhHXL1InzaMvA). | ||
|
|
||
| </ProgramsWrapper> |