Pipeline/backlog of tasks to do to make community and contributors happy

[derberg]

This issue is a list of topics, ordered roadmap of things I want to push/drive on in the coming weeks/months aside from everyday tasks. So these are items that are not trivial and need at least one week of work.

I share the list with you to:

• Be transparent with you on what I do, what I focus on to help out the AsyncAPI community
• Enable you to influence the list and its order. You see something is missing or more important than other topics, then just let me know in the comments.

You can find here tasks that are important for different community members. Addressing issues I see regularly or hear about from community members.

💪🏼 - DONE
🏃‍♂️ - IN PROGRESS
🚽 - CANCELED

Topic	Details	Status	Comment
Automate dependencies bump	Work on GitHub Action that will automate for us versions bumping across AsyncAPI organization. In other words, we release parser, and it should be bumped in all other projects where it is used, and these should also be released if needed. More details here	💪🏼	Done with this issue and this GH Action.
2020 Summary	Summarize 2020 from AsyncAPI community growth perspective. Get numbers from Slack, Google Analytics, Twitter, LinkedIn, SEO and see growth level. Analyze and present it in the form of a blog post	💪🏼	Post published
Open governance model	Research on what would be the most optimal open governance model for AsyncAPI. Most important to treat equally individuals and vendors. No "I pay so I have a seat". Make a proposal.	💪🏼	Worked with @fmvilas on it. Blog post about it is here and PR with charter almost merged
Websockets and AsyncaPI	Work on increasing knowledge of AsyncAPI with Websockets. Prepare examples, docs, blog posts, and others if needed. See this for more details	💪🏼	1. Blog WebSocket, Shrek, and AsyncAPI - An Opinionated Intro released 2. Blog Creating AsyncAPI for WebSocket API - Step by Step released 3. Blog From API-First to Code Generation - A WebSocket Use Case released 4. Official example provided here 5. Live stream here 6. EDA Conference presentation here - available as onDemand
Conference/Hackathon	Start planning for another AsyncAPI event. It could be a conference or maybe rather a hackathon (month-long for example). Big question here is, is it still remote?	💪🏼	conference.asyncapi.com
Slack workspace structure	Analyze how we use slack, propose a structure of channels, prepare a survey to ask the community and execute/cleanup and also set proper new welcome message to new joiners. Maybe we will see by this time that Slack acquisition by Salesforce causes people to run away from it, and we should find better solution 🤷‍♂️	💪🏼	Proposal opened here
AsyncAPI GitHub organization security	Cleanup AsyncAPI organization membership and make all members have just read/triage access. Use GitHub Actions to automate the process of merging PRs (labels based), so basically, no one needs write access to the organization.	💪🏼	A bit modified requirement, add details in PR

Below moved to asyncapi/community#240 or canceled

Topic	Details	Status	Comment
Measure spec adoption	Focus on request to add $schema support as this is the only possible way we could measure AsyncAPI adoption with real numbers. Design how it would work and drive to execution.	🏃🏼‍♂️
Clear contribution guide	Make it easier for anyone to contribute. Explain what are the steps (best in a visual way on the asyncapi website). Get some kind of list of first good issues that people can see in one location. See of the initial work done here can be used.	🏃🏼‍♂️	Research in progress. We have already 6 live streams for contributors, to talk to than and understand what they struggle with
Building wider event-driven community	Work on the concept of building a wider community than just AsyncAPI, to bring all together in one place, like eventdriven.club. Take further interest from the community that was shared here. Instead of reddit, host something like https://www.forem.com/. Talk to different parties about what they think about it and propose how it would work.	🚽	I cancel my plans here. Luckily other community members have similar idea on building wider EDA community. Of course will help whenever I'm needed, but not lead.
Interactive tutorials	Get Katacoda in place to enable work on interactive tutorials on AsyncAPI, or have another look at alternatives like this new kid on the block
Generator docs pro-level	Cleanup Generator overall docs + write an interactive tutorial on how to create your own template step by step (using the template for templates). Must be combined with getting them published in asyncapi.com, so the cleanup is driven by the structure of docs in AsyncAPI website
Offer paid tasks to community	Give it a try to IssueHunter and check how we could use it to sponsor work of AsyncAPI contributors on special tasks
Improve the way we work with stale and keep-open issues	Come up with a process/mechanism that automatically pics up long-living keep-open issues and stale issues that were "unstaled" for too many times. How do respond to the community about those. How do we prioritize those

The idea is that I do not create issues for these topics upfront. I create separate issue only when needed.

[derberg]

• added new item to the list -> Improve the way we work with stale and keep-open issues
• moved open governance model to the first place now, before websockets as this is the most important topic at the moment, looking on our engagement with finding a proper foundation for the project

[derberg]

added Clear contribution guide to the list basing on the discussion from last public meeting -> asyncapi/spec#480

[derberg]

Moved up contribution guide up as people ask for it more often + moved conference topic up too

[derberg]

Changed priorities a bit, at the moment there are more important topics than the contribution guide:

• Hackathon
• Slack community is growing, we need reorg
• 2.1 spec release is close, I want to check if maybe we can get $schema in it

[derberg]

Updated status a bit for all in-progress initiatives

[derberg]

Closing in favor of asyncapi/community#240