Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] [jakarta.ee-steering] Continuing the use of existing project short names in URLs, repo names, etc.
>  Do you anticipate that this will expire at any point in the future? i.e., do you anticipate that encouraging projects to change short names will change to requiring that project change short names and their use in repository names, etc.?

I would hope not.  I think we need the "final" acronym usage rules.  Otherwise, we lose credibility.  


---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:        Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
To:        Will Lyons <will.lyons@xxxxxxxxxx>
Cc:        Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>, Jakarta EE Steering Committee <jakarta.ee-steering@xxxxxxxxxxx>
Date:        06/17/2019 12:26 PM
Subject:        [EXTERNAL] [jakarta.ee-steering] Continuing the use of existing project short names in URLs, repo names, etc.
Sent by:        jakarta.ee-steering-bounces@xxxxxxxxxxx



Regarding continuing the use of existing project ids and short names...

Can I safely assume that this applies to our existing mailing lists as well? e.g. "ejb-dev@xxxxxxxxxxx"

Can I mention this decision on public channels now? I've already engaged several project teams based on an understanding that we were required to change these names; I'm going to have to tell folks something when I change direction on that.

Can we publish this and the forthcoming more general guidance on a public channel?

Do you anticipate that this will expire at any point in the future? i.e., do you anticipate that encouragingprojects to change short names will change to requiring that project change short names and their use in repository names, etc.?

Based on this, my intention is to only change names and ids when we are specifically asked to do so. That is, I'll put an onus on the individual projects to engage with the Eclipse Webmaster to change their id, repository names, etc.. (note that no formal review is required to make these sorts of changes). Does this work?

The restructuring review that I scheduled for this first round of changes is due to complete on Wednesday, and I intend to implement the changes as quickly as possible thereafter. 

Wayne

On Wed, Jun 12, 2019 at 11:46 AM <will.lyons@xxxxxxxxxx> wrote:
To Jakarta EE Steering Committee and Specification Committee:
Oracle has voted to approve the restructuring review proposal below, and by voting to approve, we are indicating we approve the names used by these specifications, and the scope statements.  Note that use of current Oracle/JCP acronyms is not included in the names of the specifications or in the scope statements.
The current short names (or id) for these projects are sometimes derived from Oracle/JCP acronyms (specifically jaxrs-api, jaf and jpa-api).   For repositories created for these projects, use of the current short names for these projects, within the following Github organization names, continues to be acceptable:For projects created at Eclipse, use of the current short names for these projects in URLs with the following form continues to be acceptable:
eclipse.org/projects/[currentshort name] 
For maximum flexibility and clarity, we encourage projects to change their short names to more closely correspond to the new specification names and avoid the Oracle/JCP acronyms where possible.
Our intent is to have more general guidance to cover more use cases in this area by next Tuesday.   We hope this guidance allows the process to proceed smoothly for these projects.
Thanks

Will
On 6/11/19 4:14 PM, Bill Shannon wrote:
+1

Wayne Beaton wrote on 6/10/19 9:01 PM:
Greetings Specification Committee...

Here is the first round of conversions from regular Eclipse Projects into Specification Projects. I've grouped five projects into this first Restructuring Review. 

The purpose of a Restructuring Review is to change the nature of a project. Since the Eclipse Foundation Specification Process (EFSP) does not specifically deal with the notion of restructuring, I'm following the Eclipse Development Process (EDP). While we are not strictly creating a new project, we are in a manner of thinking, creating new Specification Projects from the existing ones. With this in mind, I am treating this as a Creation Review from the perspective of the Specification Committee approval requirement. 

I have created a Restructuring Review record that provides the high level details of the intention. I've pasted it below for your quick review and for posterity. In all cases, I've included the scope statement for the specification itself; the specification project's scope will be to "provide the specification document and supporting technical artifacts" for the corresponding specification.

The review documentation includes links to GitHub Issues that provide more details regarding what will change. In the case of "Eclipse Project for JAX-RS", for example, we are compelled to change the project id and the name of the GitHub repository to avoid names that Oracle lays claim to.

Here is the project list:

Eclipse Project for JAX-RS will be renamed to "Jakarta RESTful Web Services" with the following specification scope: 
Jakarta RESTful Web Services defines a standard for development of web services following the Representational State Transfer (REST) architectural pattern.
Eclipse Project for JSON Processing will be renamed "Jakarta JSON Processing" with the following specification scope:
Jakarta JSON Processing defines a Java(R) based framework for parsing, generating, transforming, and querying JSON documents.
Eclipse Project for JAF will be renamed "Jakarta Activation" with the following specification scope:
Jakarta Activation defines a set of standard services to: determine the MIME type of an arbitrary piece of data; encapsulate access to it; discover the operations available on it; and instantiate the appropriate bean to perform the operation(s).
Eclipse Project for JPA will be renamed "Jakarta Persistence" with the following specification scope:
Jakarta Persistence defines a standard for management of persistence and object/relational mapping in Java(R) environments. 
Eclipse Project for WebSocket will be renamed "Jakarta WebSocket" with the following scope:
Jakarta WebSocket defines how Jakarta based applications create and manage WebSocket Clients and Servers.

I hereby request that the Specification Committee vote to approve the conversion as described above of these existing projects into Specification Projects under the supervision of the Jakarta EE Working Group.

Please respond to this note with:
+1 to approve;
-1 to reject; or
0 to abstain.

If you do choose to reject or abstain, I would appreciate a short (one or two sentence) explanation.

I will interpret a single vote as applying to all of the listed projects. You may also vote for each project individually (if, for example, you'd like to register different votes for each projects).

I will document the results of this vote on a per-project basis.

Thanks,

Wayne
--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.



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




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




--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc._______________________________________________
jakarta.ee-steering mailing list
jakarta.ee-steering@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-steering


Back to the top