Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Agenda for the January 12th Jakarta EE Specification Committee call

This is awesome.  Thanks for digging this up, Paul.


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852

On Jan 12, 2022, at 6:55 AM, Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx> wrote:


Agenda item added to the call today. Namespace references for the topic: 

1. See the Eclipse Foundation Trademark Usage Policy which says
    • Proper Usage of Eclipse Foundation Trademarks
      • “4. Only Eclipse Projects are authorized to develop or maintain software packages that use Eclipse Foundation namespaces such as 'org.eclipse' in their namespace. An important use of an Eclipse Trademark is the 'org.eclipse' string used on all namespaces for Eclipse Projects. This naming convention is used to identify code that has been developed as part of an Eclipse Project.”
    • Proper Usage of Eclipse WG Trademarks
      • "Use of any namespaces created by a WG including but not limited to ‘jakarta’, 'org.locationtech' or 'org.polarsys' is not permitted by this Policy unless authorized in advance in writing by Eclipse."
2. Also see the EF TCK License which says 
    • "4.c. comply with any requirements stated in the Specification with regard to subsetting, supersetting, modifying or extending the Specification in any Product claimed to be compatible with the Specification." 
3. Also see the (Jakarta) Compatibility Trademark License Agreement which says
    • “1.11 “Specification-Compatible Implementation” shall mean an implementation that: … (ii) does not modify, subset, superset or otherwise extend the Eclipse Name Space, or include any public or protected packages, classes, interfaces, fields, methods or constructors within the Eclipse Name Space, other than as required or authorized by the Ratified Specification.”

On Tue, Jan 11, 2022 at 5:51 PM Scott Stark <sstark@xxxxxxxxxx> wrote:
I created this issues in the platform project for this as well:

On Tue, Jan 11, 2022 at 4:46 PM David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
I completely forgot I have a conflict tomorrow.  I'm happy if people want to bring this up and resolve it.  I'd be on board with any sort of confirmation that developers should not be creating their own code in the jakarta namespace.

On Jan 11, 2022, at 12:40 PM, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:

Can we add to the agenda for tomorrow a discussion/action item about explicitly disallowing people from creating or modifying classes under the jakarta.* namespace.  I.e. can someone decide to write an application inside say jakarta.myapp.* or someone create and publish thier own original code or API in jakarta.* without going through the JESP.

There is an explicit statement in the Java Language spec that explicitly says this is forbidden for java.* and javax.*.  When we migrated to the jakarta.* namespace, we did not explicitly create a similar statement.

The discussions on the Platform dev list would benefit from swift clarification here.  The action item I recommend is we update the required boilerplate each spec must include so it has an explicit statement forbidding it.

Here are a couple versions of text we can kick around:

"The packages java, javax, and jakarta are reserved and trademarked.  Applications should not create or modify classes under these packages.  Applications that do so have unspecified behavior and may not deploy, function properly at runtime, or be portable."

Or target jakarta.* specifically -- likely legally safer to avoid commenting on java and javax and let that get enforced elsewhere.

"The jakarta.* package is reserved and trademarked by the Eclipse Foundation.   It is forbidden to modify, subset, superset or otherwise extend this package without explicit permission from the Eclipse Foundation through the established Jakarta EE Specification Process.  Applications that modify, subset, superset or otherwise extend this package have unspecified behavior and may not deploy, function properly at runtime, or be portable."



On Jan 11, 2022, at 12:09 PM, Paul Buck <paul.buck@xxxxxxxxxxxxxxxxxxxxxx> wrote:


The agenda for our committee call on Wednesday at 17:00 UTC is here. Please add any other business items as required. 


Password: SpecCmte

Thanks ... Paul
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To 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 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 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 unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee


Back to the top