Google Summer of Code 2022 at AsyncAPI

[derberg]

The intention of this post is to list all information that explains how AsyncAPI Initiative participates in Google Summer of Code (GSoC) in 2022.

A bit of history

AsyncAPI already participated in GSoC in 2021. We were not accepted as organization, but it was also a time when we were not yet part of the Linux Foundation. Therefore some of AsyncAPI maintainers pushed their ideas through Postman (that was accepted for GSoC) because they were Postman employees working on AsyncAPI. So far so good?

We mentored 5 mentees. All of them successfully completed GSoC. As a result, all of them became members of our Technical Steering Committee and also presented their solutions at AsyncAPI Conference 2021:

• GSoC: Writing the spec document without knowing the specification - Elegbede Azeez W., Individual C.
• GSoC: Visualise your defined EDA using Cupid - Arjun Garg, Individual Contributor
• GSoC: Make your AsyncAPI document shorter with Optimizer - Khuda Dad Nomani, Individual Contributor
• GSoC: Generating diffs using AsyncAPI Diff - Aayush Sahu, Individual Contributor
• Nektarios that created https://github.com/asyncapi/simulator could not, unfortunately, join the conference

We want to repeat history on an even larger scale in 2022

What about 2022?

We already shared some of the details in our live stream dedicated to contributors.

We already counted about 8 mentors (AsyncAPI maintainers) that want to join in this GSoC edition and help. The number will grow for sure.

How we work on proposals

All on GitHub

AsyncAPI Initiative is a community-driven organization that puts radical transparency at the core of its values.

This means all the work on proposals should take place in GitHub and be fully transparent.

Another good reason for this approach is that it is easy to identify duplicates and proposals that have more than one candidate. We do not want to reject candidates just because there are too many for one proposal. Let us discover it sooner and make sure we can enable as many people as possible.

Proposals processing

Proposals can be submitted either as GitHub Discussion or GitHub Issue in AsyncAPI GitHub organization.

We label proposals with gsoc label in order to make them easy to discover in the following dashboard: GitHub GSoC Issues. In case you do not have a GitHub account and cannot access the list, try here

Proposal suggestions can be created by anyone. There is no specific template to follow, only common sense. Describe in a detailed way what is it about, what are the requirements and desired outcome. If the proposal suggestion misses some details - do not worry, we will follow up with request for more clarification.

We will make sure there are mentors for each proposal.

How to connect with us

• Join our Slack workspace. Just make sure to follow our Slack etiquette and the code of conduct.
• Join the dedicated GSoC channel #temp-gsoc-2022 that we will use to coordinate the application process until coding starts. All mentees and mentors are there.

Q&A

This GSoC information page is published as a GitHub Discussion to enable you to ask questions 👇🏼 in case something is not clear and we will follow up by updating this post with more clarification.

Happy coding ☮️

[derberg]

Dear "potential" Mentors

• we need to provide GSoC proposals with our official application
• I will submit our official application on 20.02 - a day before the deadline. So you have 1 week to provide proposals
• we need to know the final number of mentors - so if you want to be a mentor, please reply to this comment so I can easily collect all details
• from the main post ☝🏼 you will learn how to submit proposals
• from the main post ☝🏼 you will learn what proposals we had last year, but there will already be some proposals from other mentors
• proposal doesn't have to be perfectly defined before 20.02. Before this deadline, you need to at least outline the scope and technologies. Then just update it in the next few days.
• proposals should be non-trivial issues that will learn mentee many different aspects of working on code in open source. They will have time to work on it between June-September-November. Watch this live stream to learn more
• 1 issue/discussion per mentee. If you have a proposal and there are 2 people interested and you can extend a proposal to 2 mentees, you need to split work into 2 issues/discussion
• to be a mentor you do not have to provide proposals, you can be a mentor in a proposal submitted by someone else. Last year we had proposals that had more than one mentor.
• some official guidelines for mentors -> - https://google.github.io/gsocguides/mentor/

Feel free to ask if something is not clear 🙏🏼

@asyncapi/tsc_members Please have a look at ☝🏼 topic. I think it would be amazing if we would have at least 10 mentors from our side. I'm opened for a chat if you need more explanation

[derberg]

@hkaur008 so far we have like 2 official proposals but until 20.02 more will come, so watch #temp-gsoc-2022 channel when people will post their proposals. Also look on dashboards that list all ideas, that I mentioned in main post.

@mcturco please keep in mind that GSoC is mainly for coding. So design is fine if it is combined with coding. It is not allowed to have only "design" focused proposals. So split, sure, but into 2 proposals that both have coding and design. Also remember about the length of the event and adjust complexity accordingly

[pankajk07]

@derberg Would like to mentor again 🙂

[magicmatatjahu]

@derberg @mcturco no problem :) We can be Missy mentors together in one proposal.

As for me, I have one task on the Studio side, which will be a typical frontend task and I have an idea for a task that will touch many repos (something in the DevOps area). I just have to create those tasks and describe them in details :)

[KhudaDad414]

Would like to be a mentor this year. I have opened an issue for an idea here: asyncapi/.github#136. feel free to check it out and leave your feedback. :)

[fmvilas]

Would love to be a mentor this year 🙌

Regarding projects, I'll start creating issues/ideas for Glee.

[fmvilas]

So, once again, we have been rejected from Google Summer of Code. The pity is that this year Postman has also been rejected and therefore we can't run the program through them. Is it a problem? I don't think so. I think it's an opportunity: #284 💪