I would like to bring AsyncAPI bundler into the ORG

[Souvikns]

In this AsyncAPI Hackathon, I built AsyncAPI Bundler and now I would love to transfer the project to AsyncAPI ORG and maintain it further. I am opening this discussion to talk know the complete process.

[derberg]

What about the doubts that you had, that you are not sure if it should be part of parser-js or not? Can you clarify?

[Souvikns]

Yeah, as @magicmatatjahu was talking here, instead of having a separate package for bundler parser could support this feature, Since parser is using @apidevtools/json-schema-ref-parser to resolve references so implementing bundler would be very natural.

But then again parser would be doing two things, and I guess in the future when we have more use cases bundler will grow and evolve so having a separate module would also make sense.

[magicmatatjahu]

Fact, I wrote to Souvik about my idea to combine this together with the parser, because besides resolving references as well as concatenating several documents will the bundler support something else? E.g. solutions like json-schema-ref-parser or openapi-cli have bundler in one project next to parser. A separate project is ok too, but perhaps unnecessary 🤷🏼

[derberg]

json-schema-ref-parser is 151kB large 😄

bundler now handles 2 separate not related functionalities, resolving refs and merging. I haven't seen the code much, but maybe this should be split then? maybe parsing refs should be in the parser, and bundling aka concatenating should be separate?

I'm personally a fan of having independent libraries that are easy to use by anyone in their tools, and we can also easily plug them in to the CLI and Studio

[magicmatatjahu]

If we agree to go with a separate package for me it's ok :P

[derberg]

so what? bundling of single file parser, and bundling of several files standalone?

[Souvikns]

I also think we should have a different package for bundler, but at some point, people might need to use bundler as a library to create their own custom logic for bundling spec files, so the question is that should we have a cli in bundler or integrate it with the CLI, then users have to install two separate things for their use cases. If they want to use bundler as a CLI tool then they install @asyncapi/cli and install @asyncapi/bundler to use it as a library.

[magicmatatjahu]

We have this same convention also with other libraries, one package with library and then integration with cli and also (in the meantime) with studio :)

[smoya]

Does this mean parser-js will start using this new bundler for resolving references as well? Any plan?

[Souvikns]

Then shall I transfer the repo to AsyncAPI org? Would be nice if anyone guides me through the process.

[derberg]

Hi folks @asyncapi/tsc_members, we need TSC voting here.

We did not do voting on a Discussions level yet, so let's see how it will work, so we get some input (experience) for this issue asyncapi/.github#102

@Souvikns won AsyncAPI Hackathon this year with his library that one of the main features is the ability to bundle multiple AsyncAPI files into one file -> #128

@Souvikns wants to donate a library to AsyncAPI Initiative. From now on it should always be TSC decision to accept/reject projects

More info:

• we do not have such a library in our AsyncAPI organization yet
• @Souvikns is our contributor that is already part of the Technical Steering Committee (maintainer of CLI)

Please vote by writing a comment YES or NO, and if you want to vote NO, please explain why you think it should not be accepted in the org.

Voting ends next Friday 24.12, end of day Pacific Time.

[jonaslagoni]

YES

[quetzalliwrites]

YES 🙌🏽

[smoya]

YES

[KhudaDad414]

YES

[jotamusik]

Yes!

[damaru-inc]

YES

…

On Dec 16, 2021, at 11:07 AM, Lukasz Gornicki ***@***.***> wrote: Hi folks @asyncapi/tsc_members, we need TSC voting here. We did not do voting on a Discussions level yet, so let's see how it will work, so we get some input (experience) for this issue asyncapi/.github#102 @Souvikns won AsyncAPI Hackathon this year with his library that one of the main features is the ability to bundle multiple AsyncAPI files into one file -> #128 @Souvikns wants to donate a library to AsyncAPI Initiative. From now on it should always be TSC decision to accept/reject projects More info: • we do not have such a library in our AsyncAPI organization yet • @Souvikns is our contributor that is already part of the Technical Steering Committee (maintainer of CLI) Please vote by writing a comment YES or NO, and if you want to vote NO, please explain why you think it should not be accepted in the org. Voting ends next Friday 24.12, end of day Pacific Time. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you are on a team that was mentioned.

[Pakisan]

Yes

…

On 16 Dec 2021, at 19:07, Lukasz Gornicki ***@***.***> wrote: Hi folks @asyncapi/tsc_members <https://github.com/orgs/asyncapi/teams/tsc_members>, we need TSC voting here. We did not do voting on a Discussions level yet, so let's see how it will work, so we get some input (experience) for this issue asyncapi/.github#102 <asyncapi/.github#102> @Souvikns <https://github.com/Souvikns> won AsyncAPI Hackathon this year with his library that one of the main features is the ability to bundle multiple AsyncAPI files into one file -> #128 <#128> @Souvikns <https://github.com/Souvikns> wants to donate a library to AsyncAPI Initiative. From now on it should always be TSC decision to accept/reject projects More info: we do not have such a library in our AsyncAPI organization yet @Souvikns <https://github.com/Souvikns> is our contributor that is already part of the Technical Steering Committee (maintainer of CLI) Please vote by writing a comment YES or NO, and if you want to vote NO, please explain why you think it should not be accepted in the org. Voting ends next Friday 24.12, end of day Pacific Time. — Reply to this email directly, view it on GitHub <#174 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZ3H7SOO7ND23RE7L4AAPTURIFFVANCNFSM5ISYQAFQ>. You are receiving this because you are on a team that was mentioned.

[derberg]

@Souvikns congrats! I see only YESes. Please make me an admin in your repo and I will do the transfer to AsyncAPI org

[Souvikns]

Nice,
@derberg I have sent you an invite

[derberg]

Welcome BUNDLER -> https://github.com/asyncapi/bundler