Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jms-dev] Please help with converting the specification document

I agree with Werner that we can use the old names (like JMS) when referring to old versions because they didn't change their name. Only the versions under JakartaEE changed the name. When you refer to the current version, I'm afraid we need to use the full name Jakarta Messaging instead of JMS. There's no official Jakarta acronym for Jakarta Messaging.

Ondro

Dňa st 25. 3. 2020, 16:15 Werner Keil <werner.keil@xxxxxxxxx> napísal(a):
I would also not rewrite history, so 1.0 or 1.1 and even 2.0 you should rather keep the acronym JMS as it also does not have as much legal side-effects as e.g. the term "Java" in "Java Messaging Service", that I would consider changing in most cases, the acronym for current versions and explanations.

Werner



On Wed, Mar 25, 2020 at 3:19 PM Leandro Coutinho <lescoutinhovr@xxxxxxxxx> wrote:
Hi,

Should the initial "JMS" be replaced for "Jakarta Messaging" everywhere in the spec?

I think in some places it doesn't make much sense, eg:
Jakarta Messaging was initially developed to provide ...
... the design of Jakarta Messaging has always

Also when referring to previous versions, eg:
Jakarta Messaging 1.0 defined two domain-specific APIs
Jakarta Messaging 1.1 introduced a new unified API

The changes so far are in this branch:

Thank you.

On Wed, Mar 25, 2020 at 6:21 AM Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx> wrote:
Hi all, especially people experienced with Jakarta and legal aspects of specifications (maybe David B., Kevin S. or Dmitry K. ?)

I helped Leandro to get started working on converting spec document and he now seeks for some advice, especially on legal stuff like copyright headers. 

Can you please have a look at his questions in https://github.com/eclipse-ee4j/jms-api/issues/266 ?

Kind regards,

Ondrej Mihályi

Senior Payara Service Engineer
Payara-Tech LDA - Open Source Enterprise Software & Support
E: ondrej.mihalyi@xxxxxxxxxxx | T: +1 415 523 0175 | M: +421 902 079 891

----------------------------------------------------------------------------------------------------------------------

Payara-Tech LDA, Registered Office: Rua Nova de São Pedro no. 54, 2nd floor, room “D”, 9000 048 Funchal, Ilha da Madeira, Portugal

VAT: PT 515158674 | www.payara.fish | info@xxxxxxxxxxx | @Payara_Fish



From: Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx>
Sent: 23 March 2020 12:43
To: jms developer discussions <jms-dev@xxxxxxxxxxx>
Subject: Re: [jms-dev] I would like to help with JMS project
 
Hi Leandro,

Welcome here and thank you for offering help!

Recently I was investigating how I could contribute myself and one of the things I considered is converting the Java EE spec document to a Jakarta EE document. It shouldn't require more than one person to do and then a few people to review. So I would welcome if you had a look at it and so I could focus on other issues for now.

I've just created a new Github issue https://github.com/eclipse-ee4j/jms-api/issues/266 for converting the spec documents and filled it with all the details I could find. I hope that it helps get you started quickly.

Feel free to fork the jms-api github repo and get your hands dirty. If you have something, feel free to create a pull request and let us know in the mailing list. Of course, if in any doubts or trouble, don't hesitate to reach me directly.


Kind regards,

Ondrej Mihályi

Senior Payara Service Engineer
Payara-Tech LDA - Open Source Enterprise Software & Support
E: ondrej.mihalyi@xxxxxxxxxxx | T: +1 415 523 0175 | M: +421 902 079 891

----------------------------------------------------------------------------------------------------------------------

Payara-Tech LDA, Registered Office: Rua Nova de São Pedro no. 54, 2nd floor, room “D”, 9000 048 Funchal, Ilha da Madeira, Portugal

VAT: PT 515158674 | www.payara.fish | info@xxxxxxxxxxx | @Payara_Fish


From: jms-dev-bounces@xxxxxxxxxxx <jms-dev-bounces@xxxxxxxxxxx> on behalf of Reza Rahman <reza_rahman@xxxxxxxxx>
Sent: 17 March 2020 22:27
To: jms developer discussions <jms-dev@xxxxxxxxxxx>
Subject: Re: [jms-dev] I would like to help with JMS project
 

Yes, Leandro's paperwork is all squared away. If you or anyone else can help him on board with some suitable work, that will be awesome.

Reza Rahman
Jakarta EE Ambassador, Author, Speaker, Blogger

Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.

On 3/17/2020 4:53 PM, Werner Keil wrote:
Nice to  hear. 
Have you already signed the Eclipse Contributor Agreement?

That's usually the first step allowing you to propose PRs here: https://github.com/eclipse-ee4j/jms-api/pulls
Even before signing it, did you have a look at the open issues: https://github.com/eclipse-ee4j/jms-api/issues

Werner 




On Tue, Mar 17, 2020 at 9:12 PM Leandro Coutinho <lescoutinhovr@xxxxxxxxx> wrote:
Hi folks,

I would like to help with the JMS project.

How can I help?

Regards,
Leandro.
_______________________________________________
jms-dev mailing list
jms-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jms-dev

_______________________________________________
jms-dev mailing list
jms-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jms-dev


_______________________________________________
jms-dev mailing list
jms-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jms-dev
_______________________________________________
jms-dev mailing list
jms-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jms-dev
_______________________________________________
jms-dev mailing list
jms-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jms-dev

Back to the top