AsyncAPI Mentorship - Ideas Voting

[derberg]

Context

• AsyncAPI Mentorship Program
• AsyncAPI Mentorship Schedule

Notice

To make the process of collecting votes easier, please refrain from making comments or voting if you are not the TSC member

Voting process

• @asyncapi/tsc_members add a comment to this discussion and indicate 10 projects (by number) that should be sponsored through AsyncAPI Mentorship. In other words, add comment with comma-separated list of numbers pointing to 10 different ideas
• @asyncapi/tsc_members that are either mentor for some ideas, or would also like to be mentees (implement the idea), should not vote
• we wait until 5th of June for your votes and on 6th we announce selected ideas, the mentor of the given idea selects who will work on it.

we have 7 mentors from TSC and I think 2 mentees from TSC which gives us 23 remaining TSC members that can vote.

Ideas list

Number	Idea	Area	Lead mentor	Why should it be picked?
1	Add support for HTTP servers and clients	Glee	@Souvikns	With creating HTTP servers to connecting to webhooks from a AsyncAPI definition, Glee will be able to achieve so much more with the HTTP protocol support.
2	Add support for AMQP 1.0	Glee	@fmvilas	AMQP 1.0 is the one of the most used protocols in big corporations (e.g., banks, retail, etc.). This will give us the opportunity to stress test Glee in production.
3	Add support for AMQP 0-9-1	Glee	@fmvilas	AMQP 0-9-1 is one of the most popular protocols because it's the one powering RabbitMQ by default. This will give us the opportunity to grow Glee's user base and test it in production.
4	Add support for Kafka	Glee	@fmvilas	Kafka is the most popular broker and protocol nowadays. This will give us the opportunity to grow Glee's user base and test it in production.
5	Making testing easier with Glee	Glee	@fmvilas	Glee has to manage a bunch of protocols, schema formats, examples, and even support for other programming languages in the future. To release a new version, we should always be confident that we're not breaking anything. This issue is about that, developers' calm of mind 😄
6	Library for easier integration testing of code generators	Generator	@derberg	AsyncAPI Generator is in a shape where writing a template is easy, but testing it not so. We have guides on how to write unit tests for components and snapshot testing for generation result. There is no easy way to say how to do integration tests for generated apps. We need a library that you can just plug into your template, configure, provide AsyncAPI files to test against and as a result you get basic testing environment for specified broken. In the end, you do not have to manually check each change in the template for each supported protocol.
7	Rewrite this template and NodeJS WS template to new react rendering engine	NodeJS Template and NodeJS WS Template	@derberg	AsyncAPI Generator supports React templating, and goal is to get rid of Nunjucks. All new templates that are created follow React. We need to rewrite existing Nunjucks Nodejs templates to React, so we finally can do React a default engine, and add more features to these templates.
8	Drag&drop AsyncAPI block builder	Studio	@magicmatatjahu	drag&drop - We are missing a tool in our ecosystem that would allow us to build AsyncAPI specifications using drag&drop blocks and combine them creating channel -> operation -> message relations etc. This can be compared to event storming but based on AsyncAPI. The project itself should allow to build AsyncAPI documentation from scratch, update the existing one or just visualize the specification with blocks.
9	Website UI Kit design/dev project	Design System	@mcturco	The idea for the Website UI kit was to streamline contributions/changes to the website, providing a pre-set list of React components that are ready for content (similar to how Tailwind UI components are). Imagine if we could have a set of components that match the brand and take the guesswork out of creating new pages and whether a section is accessible, usable, and functional. It would be great to have a component set in which you can create new pages with, instead of contributors asking for a design mock-up. Even if we still needed to provide a mock-up, these components could be saved into a Figma library, and a designer could go ahead and lay out the idea for the page using the already-developed components. Cuts contribution time in half! Plus, we could continue to scale this UI kit over time if we feel like we need to make additions/adjustments.
10	An interface/project for describing errors/problems in tools in our organization	New library	@magicmatatjahu	An interface/project for describing errors/problems in tools in our organization - We have many tools in our organization. Some of them have their own error/problem handling system, others don't have it at all and only throw exceptions from the main function. I think we should standardize this and propose a system based on an interface called problem (more about it in https://lakitna.medium.com/understanding-problem-json-adf68e5cf1f8 among others), but tailored to the tools and not to the API (we should use our problem system for that too). The result of the project will be a @asyncapi/problem library which we can easily use in our other projects and in the integration tools (Studio, CLI, ServerAPI) we can easily consume and handle the error messages thrown from our tools like generator, parser etc.
11	Modelina website	Modelina	@jonaslagoni	Modelina has so many different use-cases and specifics that need to be documented and explained in different formats, that having one single page on the official page is not enough. This idea lay the foundation for how not only Modelina, but any other tool we have, can create a dedicated website.
12	Improvements to Modelina playground	Modelina	@jonaslagoni	With so many different inputs (AsyncAPI, OpenAPI, JSON Schema, TypeScript, and more to come) and specific outputs (TypeScript, C#, Go, Java, JS, and more to come) a playground that shows the full force of the tool is beyond desired. It makes the tool more discoverable, and shareable and enables you to deep dive into what the tool is capable of within minutes.
13	Build a React app to visualize GitHub Actions across the organization	AsyncAPI CI/CD	@KhudaDad414	We are an automation-driven community and we use GitHub Actions to automate lots of things in the organization. GitHub actions aren't unlimited and we need to have a clear picture of what workflows are using what amount of resources and how we can get the most out of GitHub Actions. GitHub currently doesn't provide such a tool to monitor and see the statistics about workflows across the organization.
14	MVP integration of extensions catalog with AsyncAPI tools to make extension catalog useful	Extension Catalog	@derberg	- We need to finally have some simple integration of extensions into existing tools to promote the concept more and show that it is useful to share extensions with the community, as shared extensions will always be supported. - It is also super critical for the work on new specification features, as it is always better to first add extension, check it on production and then turn it into a feature.
15	Make it easier to create templates and glee projects	CLI	@fmvilas	We're doing a great job at Glee and Generator and it's about the get even better. However, we need it to be easy for users to create their own templates and Glee projects. And even more important, it needs to be easy for them to discover these projects actually exist. CLI should be the place where people can find and use these technologies.
16	Create New page for /tools/	Website	@derberg	Current list of community tools depends on tools owners to open up a PR. It is extra effort that is hard even for us, AsyncAPI maintainers, and therefore many AsyncAPI tools are not properly promoted on AsyncAPI Website. Goal here is to improve discoverability of AsyncAPI tools, make it easier to add new ones to the list, without PR, and also have more sophisticated navigation/filtering
17	Add support for an HTTP/FaaS runtime	Glee	@fmvilas	There's a growing list of people and companies doing serverless or Fuction-as-a-Service (FaaS). Making Glee integrate with serverless providers will allow users to code and manage their functions in their favorite language and platform while still leveraging the power of Glee.
18	Add support for retries, backpressure, and at-most-once, at-least-once, and exactly-once semantics	Glee	@fmvilas	This is probably the most complicated issue in difficulty. If we want people to adopt Glee in production, it needs to be prodution-ready, and that means being able to handle huge loads, network failures, and avoid losing messages (when the protocol allows it).
19	Automate listing of members of technical steering committee	Project governance	@derberg	There is a lot of work done already for handling TSC related processes on GitHub. But there are still few more things to do in org like ours: - we need to be able to automatically discover changes in CODEOWNERS and update them in a list of TSC members - we need to communicate changes in automated way, twitter/email, as there is no one who can do it all the time

[dalelane]

6, 7, 10, 14, 16, 19, 4, 9, 18, 2

[derberg]

@asyncapi/tsc_members kind reminder that just a week left for voting and so far we got votes only from Dale. Even if you feel that recently you were not super active in the initiative and think that you should not vote -> please change your mind. You are part of TSC because you know what AsyncAPI is about and we count on your vote ❤️

@derberg @jonaslagoni @KhudaDad414 @Souvikns @fmvilas @mcturco @magicmatatjahu are the only ones that should not vote as they own some of the ideas

[M3lkior]

here is @derberg ; sorry for the delay 👇

[derberg]

no worries, I was just afraid that all votes come last-minute on Sunday 😅

[BOLT04]

@derberg also sorry for the delay, for some reason I thought only mentors could vote 😅
My answer is below 😃

[M3lkior]

4, 6, 7, 8, 9, 10, 12, 14, 16, 18

[arjungarg07]

1, 2, 6, 8, 9, 10, 11, 13, 15, 18

[aayushmau5]

1, 5, 7, 8, 9, 10, 13, 16, 18, 19

[BOLT04]

1, 2, 4, 7, 8, 9, 10, 12, 14, 18

[damaru-inc]

1, 2, 3,4, 6, 8, 13, 14, 17, 18

[quetzalliwrites]

9, 13, 15, 16, 8, 17, 18, 19, 1, 4

[lbroudoux]

4, 3, 18, 2, 8, 14, 17, 19, 11, 10

[CameronRushton]

1, 2, 4, 6, 7, 8, 14, 17, 18, 19

[AceTheCreator]

1,4,6,8,9,11,13,15,16,17

[Tenischev]

4,6,7,8,9,10,11,13,16,19

[derberg]

Thanks to all TSC members that took time and participated in voting 🍻

Summary:

7 ideas got enough votes that made it clear they should be selected
6 ideas got 6 points and only 3 spots were left in the program. This means we could choose only 3

I used the rule that we agreed for this year's program:

If we have some ideas that have the same amount of votes, we pick the one that was created first to promote people that did not create ideas for GSoC last minute

Thus:

• Add support for AMQP 1.0 glee#258 went out as it was added to the list latest
• Build a React app to visualize GitHub Actions across the organization .github#136 and MVP integration of extensions catalog with AsyncAPI tools to make extension catalog useful extensions-catalog#78 got in as they were created by mentors earliest

The problem appeared with asyncapi/nodejs-template#133, asyncapi/.github#47 and asyncapi/website#383 that were added to the GSoC list on the same day. So to have as fair selection process as possible I used https://www.random.org/lists/ to choose which idea should go through

Recording of the draw: https://youtu.be/3gtiOAo5Zyw

asyncapi/website#383 won the draw and was the last one that got accepted for mentorship

---

Final List

ordered by the largest amount of votes

Number	Idea	Area	Lead mentor	Votes	Mentee?
8	Drag&drop AsyncAPI block builder	Studio	@magicmatatjahu	10	@wh0sumit
4	Add support for Kafka	Glee	@fmvilas	9	@Ruchip16
18	Add support for retries, backpressure, and at-most-once, at-least-once, and exactly-once semantics	Glee	@fmvilas	9	@sudoshreyansh
9	Website UI Kit design/dev project	Design System	@mcturco	8	@yashsehgal @Mayaleeeee
1	Add support for HTTP servers and clients	Glee	@Souvikns	7	@ritik307
6	Library for easier integration testing of code generators	Generator	@derberg	7	#376 (comment)
10	An interface/project for describing errors/problems in tools in our organization	New library	@magicmatatjahu	7	@imabp
13	Build a React app to visualize GitHub Actions across the organization	AsyncAPI CI/CD	@KhudaDad414	6	@Samridhi-98
14	MVP integration of extensions catalog with AsyncAPI tools to make extension catalog useful	Extension Catalog	@derberg	6	@Sihamtahi
16	Create New page for /tools/	Website	@derberg	6	@akshatnema

Now @magicmatatjahu @fmvilas @mcturco @Souvikns @KhudaDad414 @derberg should comment in reply information on who is the mentee for given ideas. Some ideas just had one candidate, some more than one. It is up to the mentor to pick the right person. The best is if this is someone that already contributed to the project. As suggested in mentorship definition

Some ideas already have volunteers, but I bet that some people also applied for GSoC and might be they get selected there and therefore will not be interested with AsyncAPI Mentorship. In other words, we need to clarify who is still interested in the given idea. My strong suggestion, folks that already contributed to AsyncAPI to get familiar with our community, have priority and in addition we have rule "first gets it"

---

AsyncAPI Mentorship 2023

This year was super spontaneous. Let's start collecting feedback and ideas for 2023.
What is that you did not like and what is that you liked with current setup of the program -> #388

[wh0sumit]

Mentee for 8 project is @wh0sumit Congrats! 🚀

Thank you @magicmatatjahu, I am excited to be part of this program and I am looking forward to learning more things throughout the program 😍💜

I would also like to congratulate all the other mentees 🥳

[fmvilas]

Mentee for #18 is @sudoshreyansh and for #4 is @Ruchip16 (although I haven't been able to reach out to her, hoping she gets this notification 😄)

[Ruchip16]

haha @fmvilas I did receive your notification and I am up for it

[sudoshreyansh]

Thanks @fmvilas! Really excited to be a part of the program.

[derberg]

ok, almost all set, just waiting for @KhudaDad414 and his idea, he had many folks volunteering there, some are already picked for other ideas. Let's see 💪🏼

[Souvikns]

and, here is our second mentee -> asyncapi/glee#260 (comment) 👏🏼

@ritik307 congrats, looking forward to collaborating with you.

[ritik307]

@Souvikns looking forward to with you too 😊

[ayushpaharia]

congratulations @ritik307

[BOLT04]

congrats @ritik307 🙂

[ritik307]

Thanks! 😊 @BOLT04

[derberg]

small update on idea 6 -> asyncapi/generator#752 (comment)

People that volunteered there on time are selected for other ideas. As a mentor of this idea, I resign from having it on the list for the current Mentorship Program in favor of asyncapi-archived-repos/design-system#4 that is a big topic and has 2 solid mentees that already contributed to AsyncAPI. This way we can equally sponsor them with the same amount as other mentees 💪🏼

So we end up with 9, not 10 ideas, but still 10 mentees 🚀

[InfoSec812]

@derberg @fmvilas @KhudaDad414 @mcturco @magicmatatjahu @Souvikns Please feel free to tag me if you want any assistance. Some skills I bring and can help mentor around:

• Design Thinking
• Prototyping (using tools like Figma)
• Java, JavaScript, Typescript, Python
• APIs
• DevSecOps
• CI/CD
• Domain Driven Design

I do a lot of work in enterprise integration and Quarkus/Vert.x/AMQP/Kafka/Apache Camel

[derberg]

Here is recording of the latest Q&A -> https://youtu.be/rLJSj99oQBE

Most important info @AceTheCreator is taking over as a coordinator. He will be your contact, he will regularly check on you, collect feedback and formalize the program for next years. Go go Ace 🚀

Dear mentors/mentees -> if you did not start yet, it is a good time to get in touch with each other

Cc: @akshatnema @Sihamtahi @imabp @magicmatatjahu @ritik307 @Souvikns @yashsehgal @naman-tiwari @mcturco @sudoshreyansh @fmvilas @Ruchip16 @wh0sumit @KhudaDad414