Contribute Java JMS Template to AsyncAPI

[lewis-relph]

Hi 👋

I work in the IBM MQ development team and we would like to contribute the AsyncAPI template for Java JMS that we developed as part of the AsyncAPI hackathon under Apache 2.0 license. Our template enables the generation of standalone Java/Java JMS applications from an input AsyncAPI document and compliments the existing Java Spring template. The template includes samples for IBM MQ and Kafka but can be used more generally and we’re keen that other’s in the AsyncAPI community can benefit from this work. Following guidance from Lukasz, I’ve opened this discussion item to engage with the wider community and work towards making this available in the appropriate template repo e.g., asyncapi/java-jms-template

Initial Codeowners:

• Akshaya Gurlhosur - IBM - https://github.com/AGurlhosur
• Dale Lane - IBM - https://github.com/dalelane
• Dan Raper - IBM - https://github.com/dan-r
• Kieran Murphy - IBM - https://github.com/KieranM1999
• Lewis Relph - IBM - https://github.com/lewis-relph
• Tom Jefferson - IBM - https://github.com/JEFFLUFC

[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

@lewis-relph and his team from IBM want to donate a code generator to AsyncAPI Initiative. From now on it should always be TSC decision to accept/reject projects.

More info:

• Code generator for Java was submitted for AsyncAPI Hackathon and received 3/10 votes from folks judging submissions -> AsyncAPI Template for Java #122
• so far we have 2 java code generators (templates) in our AsyncAPI organization. One is based on Java Spring Cloud Stream, and the other is based on Java Spring. Donated project is not using Spring at all. This is not a competition to existing projects but an alternative.
• only one of the project codeowners is AsyncAPI contributor that is already part of the Technical Steering Committee (Dale Lane). This means that all other 5 codeowners would be enabled to become TSC members (of course if CHARTER-described limits would allow it as there are already 2 members from IBM)

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.

[quetzalliwrites]

Yes 🙌🏽... go java!!

[arjungarg07]

YES

[smoya]

YES

[Souvikns]

Yes

[jotamusik]

Yes!

[damaru-inc]

YES

…

On Dec 16, 2021, at 11:19 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 @lewis-relph and his team from IBM want to donate a code generator to AsyncAPI Initiative. From now on it should always be TSC decision to accept/reject projects. More info: • Code generator for Java was submitted for AsyncAPI Hackathon and received 3/10 votes from folks judging submissions -> #122 • so far we have 2 java code generators (templates) in our AsyncAPI organization. One is based on Java Spring Cloud Stream, and the other is based on Java Spring. Donated project is not using Spring at all. This is not a competition to existing projects but an alternative. • only one of the project codeowners is AsyncAPI contributor that is already part of the Technical Steering Committee (Dale Lane). This means that all other 5 codeowners would be enabled to become TSC members (of course if CHARTER-described limits would allow it as there are already 2 members from IBM) 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.

[KhudaDad414]

YES

[Pakisan]

Yes

[derberg]

@lewis-relph I see no objections here, welcome aboard. Now I'm thinking about how to do the transfer. Can you folks make me an admin in ibm-messaging so I can do the transfer? Other solution would be us creating new repo under AsyncAPI and then I would make you and admin of this repo so you can make initial push, that preserves entire project history

[dalelane]

I think making an empty repo ( https://github.com/asyncapi/java-template ? ) would be best - then it's easy enough for one of us to push to it as a new remote.

[derberg]

@dalelane created https://github.com/asyncapi/java-template. You are its admin for now. Please push the code there and lemme know once you are done, I will make sure to setup all the settings in the repo correctly. Then please open a separate PR with CODEOWNERS file

[dalelane]

@derberg Thanks! I've quickly added the code there, but I'm sure there are bits that will need tweaking in the new year. (I've added a few issues to remind us)

[derberg]

lgtm! just please switch to master branch for now otherwise automation will not function as expected. We are not ready to support main yet -> asyncapi/.github#98

ping me once you have CODEOWNERS-related PR opened so I can do all necessary invites. And then, after merge, if new folks want to support AsyncAPI Initiative more than just in Java template, advise them to open PR against https://github.com/asyncapi/community/blob/master/TSC_MEMBERS.json

[dalelane]

Renamed the branch and put a CODEOWNERS PR at asyncapi/java-template#4