Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Restructuring Review

I agree it would be good to have a definitive list.  We could probably add that to the plan that Ed created.

The javadocs need to be updated for two reasons:
  • Any reference to spec names will need to be updated when the spec names change.
  • The spec license will need to be updated to use the Eclipse Foundation Specification License.

Scott Stark wrote on 5/23/19 8:33 AM:
Good info, but I’m talking about what needs to be updated for the actual Jakarta EE 8 release in a spec project. I have been through the following:

Proposed Jakarta EE 8 Delivery Plan Slides
Jakarta EE 8 Delivery Proposal
Java EE Spec Renaming V2
Jakarta EE 8 release and Jakarta EE 9 planning sign up document

and I only see tasks related to updating spec text. I seem to recall the spec committee discussing the javadoc needing to be updated as well, but I don’t see this captured anywhere, so I’m looking for a definitive list of context that need to be dealt with for the Jakarta EE 8 release so the process guide can list the requirements for spec projects to follow.


On May 23, 2019, at 7:58 AM, Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:

At this point, we're proposing the creation of a new Eclipse Project to provide a home for work related to a specification. The proposal document is intended to describe the nature of the new Eclipse project that we'll create. As part of the proposal, you will need to include references to existing repositories that you intend to move to the Eclipse Project. Note that in this context, we're referring to the creation of a new Eclipse Project (as that term is defined by the Eclipse Development Process).
 
- Project name needs to change

I may be splitting hairs, but the Eclipse project does not exist, so there is no project name to change. As far as the process is concerned it's a new project with a new project name. I think that I'd heard "Jakarta Contexts" suggested.
 
- Javadoc needs to change?
- Any other guides in spec/api repository need to change?

I assume that you mean with regard to the namespace issue. I don't think that this needs to be addressed directly in the proposal. You might, however, for the purposes of the project proposal, you might include something in the "Legal Issues" or "Initial Contribution" section to describe that existing use of a javax namespace (assuming that this is true) will be retained for the Jakarta EE 8 release. You may also include some discussion in the "Future Work" section.
 
- Other project related websites (http://cdi-spec.org/) need to change?

The Eclipse Foundation will take ownership of the project name and claim trademark (though "Jakarta Contexts" would likely difficult/impossible to register as a trademark). Any use of that project name would be subject to the trademark usage guidelines. The Eclipse Foundation typically takes ownership of domain names that use our trademarks (I'm not sure if this applies for "cdi-spec.org").

Any content that is considered "core" to the project must be moved to an EF-managed site or resource. Documentation is considered core. As part of the project creation, the webmaster will provision space on www.eclipse.org for the project. We do have a notion of "community portals" that may apply to some of the content.
 
And whether this applies to the initial Jakarta EE 8 release or later.

The Eclipse Project will persist beyond any particular release. That is, the Jakarta Contexts project will be responsible for initially creating a release for Jakarta EE 8 and then for every subsequent release of the specification and related artifacts thereafter. The project scope should reflect this. 

HTH,

Wayne

On Wed, May 22, 2019 at 4:12 PM Scott Stark <sstark@xxxxxxxxxx> wrote:
Wayne,

I have the handbook on how to create a project now, but although we seemed to have talk about the requirements for renaming projects and their use of the Java EE related trademarks, I’m not finding a definitive guide that is addressing:
- Project name needs to change
- Javadoc needs to change?
- Any other guides in spec/api repository need to change?
- Other project related websites (http://cdi-spec.org/) need to change?

And whether this applies to the initial Jakarta EE 8 release or later.
_______________________________________________
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-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


Back to the top