Selected OSS Technical Writers for AsyncAPI GSoD 2022

[quetzalliwrites]

🥳 Selected Technical Writers (TW) for AsyncAPI GSoD 2022

It's been my dream to have the "power" to give people of color, women, and diverse minorities tech opportunities that provide mentorship, fun, and immersive learning. It's humbling to finally have the opportunity to do just that via AsynAPI's GSoD 2022 program. 😃

Today, I'm thrilled to announce the selected AsyncAPI's GSoD 2022 candidates (from a pool of 200+ applicants!).

Please join me in congratulating (alphabetical order):

• 🧕🏾 Anisat Akinbani (Nigeria 🇳🇬): Information Architecture, parent GSoD project.
• 💁🏾‍♀️ Florence Njeri (Kenya 🇰🇪): Generator Tool & Tools Docs, child GSoD project.
• 👩🏽‍💻 Karuna (India 🇮🇳): Information Architecture, parent GSoD project.
• 👨🏿‍💻 Nelson Michael (Nigeria 🇳🇬): Information Architecture, parent GSoD project.
• 💁🏾‍♂️ Pratik (India 🇮🇳): Generator Tool & Tools Docs, child GSoD project.
• 👩🏿‍💻 Thulie (Cape Town 🇿🇦): Information Architecture, parent GSoD project.

Congratulations on your accomplishment; you deserve to feel proud and excited! Out of 200+ applicants, you made a great impression. We are humbled and ready to support you in working with us this year.

🏃🏻‍♀️ Next steps for AsyncAPI GSoD 2022 TWs

I will create and assign GSoD Docs GH issues during the rest of this month and set up 1:1 onboarding calls with our new OSS TW mentees. (Lukasz will follow up with the 2 Generator Tool TWs independently, but if you already have Generator Tool questions for him, don't feel shy to send him a slack DM.) I will also share different TW templates with each TW for their assigned content bucket content.

As I assign new issues, I will also DM the assigned TW to share tips on getting started. We'll all work closely and asynchronously, meaning everyone will work and reply at their best convenience within their timezone. As OSS contributors worldwide, we must exhibit patience and grace for other contributors to get back to each query. Plan for at least a full one business day response time from other contributors since we all work at different times and each contributor has unique, varied responsibilities.

⚠️ Remember: We handle ALL AsyncAPI and OSS Docs contribution communication via the AsyncAPI slack workspace. Stay tuned to the #13_docs slack channel for all future instructions, interactions, and communication. The #temp-gsod-2022 channel will be removed by May 20th since the selection process is complete, and now you'll be moving over to our regular channels, such as #13_docs.

Whenever you need 1:1 help, Lukasz and I are your GSoD mentors, always available via DM and zoom calls. (Keep in mind that we're onboarding 6 new people in this program, so please allow for longer response times to DMs and PRs/issue comments.)

💰 How/When will AsyncAPI GSoD TWs receive payment?

In December, we're waiting till EOY when Google sends us the full $10,000 GSoD grant amount to divide and pay it equally amongst our 6 TWs.

When the time comes, all you'll have to do is submit an expense to the AsyncAPI Open Collective:
https://opencollective.com/asyncapi/expenses/new

Submit Open Collective expense:

Submit Open Collective invoice:

👩🏻‍🏫 Mentorship for regular AsyncAPI OSS contributors

/DOCS STUFF

The selection process was not easy to make, as there were far more than 6 amazing people from the 200+ applicant list! I did my best to make a fair and unbiased selection, but I still wish I could have chosen more than 6 people. If you feel discouraged not to get selected this year for GSoD, remember that you can still become a regular Docs contributor! ❤️

I will openly share any knowledge share sessions or content I create to mentor our GSoD TWs and make it available to the entire community. While you won't get assigned GSoD tasks, there is plenty of other work needed to get done for Docs, so I will be able to identify a cool documentation task for you. Or, you can go ahead and propose a new written contribution yourself and tag me in your PR.

To get started as a first-time Docs contributor, go ahead and follow the directions outlined here:
https://www.asyncapi.com/blog/google-season-of-docs-2022#get-started-contributing-to-asyncapi-docs-today

/CODING STUFF

If you are not specifically interested in written docs contributions and want to do some coding project, remember that AsyncAPI has 60 repositories! There is always something to code around here. 😉

For folks who want to get involved (are involved), you will want to get involved and comment right away on this AsyncAPI mentorship GH Discussion that @derberg (Lukasz) wants to offer here: #284

See you in our Slack!
A.Q.

[quetzalliwrites]

Organizations must hire a technical writer and complete the Proof of Technical Writer Hiring Form linked below by May 16, 2022 at 18:00 UTC.

AsyncAPI's is done as you can see here:

[lewikeezy]

@alequetzalli oh yes, please I will like to contribute outside the GSoD, I just want the experience and eager to improve and grow my skills so I look forward to any where hands are needed to contribute in documentation. I look forward to a positive engagement.
Thanks