Announcing 3.0 work has started

[jonaslagoni]

Post description

During the 3.0 meeting, @derberg suggested that we should do some kind of announcement publically, that work on 3.0 has started. To welcome enable contributions and to make some noise.

It should be a short blog post highlighting the process, where to find information, and how to participate.

[HarshCasper]

Hi @jonaslagoni 👋

I would like to contribute to this!

[magicmatatjahu]

@HarshCasper Yeah, sure, but please write about your approach (that same as you wrote in Slack) :)

[derberg]

@jonaslagoni could you provide links to all important resources that the community needs to know about. Researching these if you are not close to the subject can be really hard. I mean point out what should community know about, meetings, issues, how we work, what is target, etc.

[jonaslagoni]

The issue that tracks all related issues to the 3.0 release and who is championing them: asyncapi/spec#691

A milestone that tracks all issues that need to be considered before a 3.0 release can happen: https://github.com/asyncapi/spec/milestone/18

A release journal that tracks all relevant events that have happened: asyncapi/community#163

All previous and upcoming meetings regarding 3.0 can be found here: https://github.com/asyncapi/community/issues?q=is%3Aissue+%22Spec+3.0+Meeting%22+is%3Aopen

Youtube playlist to watch previous meetings: https://www.youtube.com/watch?v=CLNgLB4-UnA&list=PLbi1gRlP7pihClJY-kXuTRRJ8n1awb0VV

All changes being made all follow the standard contribution guidelines with RFC's: https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md

Before all of this started, we had a discussion here: asyncapi/community#157 on how we should do it.

How are the major version released? Same as always, we follow the release process: https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md

Current meeting format: Once every two weeks, where we discuss related topics to the 3.0 release, give updates, etc.

When will the release happen? Once we are done 🤷 😆 If I personally had to give an estimate, definitely this year 😄

How can you contribute and help out? There are many ways, if you are unsure how you should, feel free to reach out in the slack channel, and some kind people will help you get started! Regardless of how you start, it is just a matter of grabbing something you find interesting and drive the change!

Ask away if you have any questions or want something clarified @HarshCasper

[HarshCasper]

Hi @derberg @jonaslagoni

I am almost done with this. I will raise a PR by tomorrow :)

[jonaslagoni]

hey @HarshCasper, anything you need from us? 🙂

[HarshCasper]

Hi @jonaslagoni

I had some difficulty in setting up the AsyncAPI Website on the local machine which has been solved by using a downgraded Node version. Rest apart, a PR has been raised right now. Looking forward to your reviews 😄

[magicmatatjahu]

@HarshCasper Did you use v16, v17 or which version? I'm using v16 (on MacOS) and everything works as expected. Could you raise new issue with problems? :)

[HarshCasper]

@HarshCasper Did you use v16, v17 or which version? I'm using v16 (on MacOS) and everything works as expected. Could you raise new issue with problems? :)

I have used Node v16. I will raise an issue with the screenshots and possible fixes :)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[derberg]

solved with #611