Building a long term vision around converter

[jonaslagoni]

Reason/Context

The sole purpose of the current converter is converting AsyncAPI versions from one version to the next.

However, it does not really create a strong community around it nor enable further development of the tool because it is so narrowly focused on one specific area.

So I want to propose that we open up the tool to encompass convert to AsyncAPI meaning that we can have an implementation that converts from OpenAPI, Protobuf, CloudEvents, Postman collections, etc, into AsyncAPI documents. This way we open up a bunch of integration options for people who already use existing standards to switch over or try AsyncAPI.

Each of these implementations can have its own subset of code owners, in a similar fashion as we have achieved with Modelina: https://github.com/asyncapi/modelina/blob/master/CODEOWNERS

How does that idea sound @derberg (even though you leaving 😆), @fmvilas, @magicmatatjahu?

[fmvilas]

I like the idea. It may be a good way to push the interest of this package. Plus, converting from OpenAPI, Postman collections, etc. should help increase adoption too.

[derberg]

definitely makes sense to extend the scope of the library