Re: [ee4j-pmc] Specification project scope statements

[Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>]

Fair enough. I agree that there is a difference between the scope of the project and scope of the specification. As you may have seen from elsewhere in the thread, I've wrestled with this.

What we actually need is the scope of the specifications. The scope of the project really does just boil down to "develop and maintain the specification". 

Wayne

On Thu, Apr 4, 2019 at 1:35 AM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

 

All that says is: "Eclipse Proeject for JMS provides the API and TCK for Java™ Message Service (JMS) API, starting from the specification defined by JSR-343."

 

> This is actually a bad example that needs to be changed. It makes no attempt to actually define the scope of JMS. It's basically self-referential.

 

Actually it is not self-referential. The project "Eclipse Project for JMS" is a different thing than "Java Message Service API" itself. One is a group of committers, the other is a technology they work on. The cause of this "self-referenceis that "somebody" decided that all projects for Java EE technology are named "Eclipse Project for X". It would be more clear if the sentence would read like "Eclipse Hermes provides the API and TCK for JMS, the official standard for MOM drivers on the Java platform.".

 

So what do you actually want to have, a description of the project or a description of the technology?

_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.