As an Open-Source (OSS) contributor, I volunteer to write periodic updates about the AsyncAPI Docs ecosystem every 2 weeks.
I want to note that this is not an official AsyncAPI Initiative update, but a personal summary I'm volunteering to write up for the OSS community. The goal is to let you know what's going on in the Docs area and how the Docs area has been teaming with other areas within the AsyncAPI Initiative. 😀👍🏽
I was quite sick last week and Monday Feb 21st was a holiday here in USA.
In addition, the whole Ukraine 🇺🇦 humanitarian crisis really troubles me so I ended up spending a little time also starting the first steps to help raise funds for this by starting to plan/research here.
As some of you may remember from my Gist Docs update for 31 Jan - 11 Feb 2022, I noted that GSoD 2022 was coming up and that AsyncAPI wanted to participate in the application process once it opened on February 23, 2022.
I have already begun our application to GSoD 2022, but keep in mind that it entails a very detailed process with several steps. One of the main components is a specific project proposal template that Google requires all orgs fill out.
You can see what the project proposal looks like so far in my Draft PR here.
Don't forget that we have an AsyncAPI Slack channel named #temp-gsod-2022 that you can join here. This slack channel is a temporary channel to coordinate GSoC 2022 setup. I'll publish regular updates on where we are in the application process, so stay tuned as the applicate date grows closer. 🙂
Join the #temp-gsod-2022 slack channel for:
- mentees identification
- mentors identification
- ideas identification
- mentees and ideas and mentors matching
We're tackling the writing for /website issue #350.
Here's that scintillating Draft PR that can be followed for updates: asyncapi/website#601. The goal is to have preview links to help community members better visualize current proposed changes in progress.
I ran into an issue this week because I couldn't figure out why the new changes don't seem to render in my local. I'm going to have to bug Lukasz or someone else next week to figure out what I did wrong. 😄✌🏽
A BIG thank you 🤗 to all of our OSS contributors; without you, there would be no OSS initiative! 😄🎉
For this biweekly update Gist, let's give a round of applause to:
- @barbanio
- @imabp (among many things, he's excited about CLI Docs!)
- @jonaslagoni
- @magicmatatjahu
- @dalelane
There is always something to do for OSS Docs, and it's no different for us! 😄
We could really use contributors for the following Docs issues:
- Development work for ✨NEW✨ Docs
feedback card#453 - Technical Writing for defining
serverin spec #587 - Development work for ✨NEW✨ Docs homepage, based on new design components created in #503
That's it for now. See you in 2 weeks! -A.Q. 👩🏻💻 y Canela 🐕🦺
Thank you for the mention @alequetzalli
Will be helping out to come up with
AsyncAPI/CLIDocumentation underreferences😄