Re: [ee4j-pmc] Specification project scope statements

[Ivar Grimstad <ivar.grimstad@xxxxxxxxx>]

I have started creating issues for each project to update their scope statement to allow tracking of progress. 

The tracking board can be found here: https://github.com/orgs/eclipse-ee4j/projects/10 

There will almost certainly be alternative statements during the discussion, so it must be super-clear which of them the project proposes for approval by the Jakarta EE Specification Committee.

I suggest that the final agreed-upon proposed scope statement by the project is put as the last comment on the issue.

Ivar

On Thu, Apr 4, 2019 at 8:33 AM Ivar Grimstad <ivar.grimstad@xxxxxxxxx> wrote:

Hi,

I think what we need is a scope statement for the project. The current suggestion is that when the transition to Jakarta EE Specification projects is done, the project name and the specification name will be equal. For example:

- The project "Eclipse Project for JMS" will be named "Jakarta Message Service"

- The specification "Java Message Service 2.0" will be named "Jakarta Message Service"

I am not sure if this ambiguity will cause some confusion or clarification...

The scope of the specification project is suggested to be the specification Document, API and TCK. 

There are some discussions going on whether the TCK should be within the scope of the specification project or not. Conceptually, and practically, it should be within the scope of the project, but not under the same license. Not sure if that is possible...

If the TCK should be in its own project, it does not make sense to include it in the scope of a specification project.

Ivar

On Thu, Apr 4, 2019 at 7:36 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