Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakarta.ee-wg] Minutes from Jakarta EE Working Group Steering Committee Meeting on April 24, 2018

Minutes from Jakarta EE Working Group Steering Committee Meeting on April 24, 2018

Meeting at 12:30 PM EDT

https://eclipse.zoom.us/j/140846579

1) Attendees/roll call of Steering Committee members:

Steering Committee members:
Dan Bandera and Kevin Sutter - IBM
Will Lyons - Oracle
Steve Millidge - Payara
Kenji Kazumura - Fujitsu
David Blevins - Tomitribe

Eclipse Foundation:
Mike Milinkovich - Eclipse Foundation


2) Review of minutes from prior meeting

The April 10 meeting minutes were reviewed and approved for distribution to the Jakarta EE Working Group (jakarta.ee-wg@xxxxxxxxxxx) where they will be archived and publicly accessible.

3) Launch update:
https://jakarta.ee/

There have been 5,000 unique visitors since the site went live.  Good coverage from multiple press outlets.

Mike reports his session room packed at JAX. Requests for more technical vision.

No immediate follow-up was required of the steering committee. The following was discussed and agreed:
  • The marketing committee will have responsibility over routine Jakarta EE website updates.  
  • If there are any significant new multi-week projects/initiatives or programs, the Steering Committee requests updates on these activities.   Silent response implies approval. 
  • The following are requested of the marketing committee
  • A messaging document
  • A rolling two quarter marketing plan
4) Election process and schedule for Jakarta EE working group committees
a) Election process
Waiting on nominations.   Two Enterprise Committee seats are open.

Please reach out to qualified people you would recommend.
b) Specification Committee
This committee must begin meeting to start defining a specification process.   From my perspective this is the primary open issue to establishing a forward looking process and community.
The Specification Committee has been formed.  Doodle poll in process for meeting next week.

A first request to the Spec Committee is to define requirements for the specification process, in addition to defining the process itself.
c) New Working Group members - Acmite, Microsoft, Vaadin, Genuitec, IncQuery Labs, Useopen Middleware, DocDoku, SAP.
We encourage the marketing committee to consider how to leverage this participation and engage new members and the community.

Paul mentioned that we should be scheduling calls on the technology. Should be considered by the marketing committee.  May be run by PMC, SC, Spec committee, etc.

c) Item from last time - Technical Direction
See below discussion on technical direction.  A working definition of "technical direction" is given below.
Technical direction:

A technical direction describes the high level evolution of technologies over time.   
  • It is "technical" in that it focuses on specific characteristics of technology that are relevant to functional properties, direct user experience, integration with other technologies, architecture and design, and development/implementation and testing processes. "Technical" directions may be influenced by, and may influence, business priorities, marketing requirements and positioning, and legal issues, but these are secondary in focus to the technical considerations described.
  • It is "directional" and "high level" in that it informs a community of users, developers and other interested parties of the major areas of future development over time, how they relate to each other and to other technologies, and the goals of future development.   A "direction" does not attempt to provide an exhaustive technical description.
It was agreed that the PMC and Platform Project Committers propose a technical direction to the Steering Committee for review and adoption, with the understanding that this is subject to change, pending definition of the spec process, and is dependent on community driven initiatives of individual projects.   

This decision, and others, is subject to course correction over time, per the Charter doc.

5) Status of Oracle Contributions
https://www.eclipse.org/ee4j/status.php
There were no significant updates from the April 17 meeting.

6) Recruitment of Enterprise members, updating messaging.
No Enterprise members signed up to date.

EF ask is for vendors to re-engage with Enterprise customer prospects.

EF will share a flyer (one-pager re: WG) and update/rebrand the starting pitch.

Expect an update from Paul by end of week.

7) Conferences
EclipseCon Europe
From Mike:  Please talk to Paul about your interest in sponsorship, speaking, and participation in ECE 2018.

Note: CFP going out May 15.
JakartaOne
Discussed, but no specific plans at this time.
8) Legal Documents
Refer to Mike's mail attached.

Mike requested more sustained attention from Oracle support to close these issues.   Oracle agreed to formalize a request with Mike offline.

--- Begin Message ---

All,

I wanted to capture all of the various documents and agreements that we need to get in place over the coming months in order to be able to ship an Eclipse Glassfish release branded as Jakarta EE 8 compatible. It's a scary list, with 10 entirely new agreements required, 6 of which we haven't even started.

If people think this is helpful I can share the Google Doc.

Revisions to Existing Agreements

Topic

Description

Current Status

Eclipse Contributor Agreement Individual Committer Agreement Member Committer Agreement Terms of Use

  • Amend to capture copyright IP flows to allow the creation of specifications from code contributions to projects.

  • Approved by the EMO, working with the IP Advisory Committee

Amendments have been proposed to the IP Advisory Committee. Have been waiting for one month for Oracle Legal to provide feedback.


Action:Oracle to provide feedback on the definition of “specifications”

Eclipse Development Process

  • No or minimal changes required

  • Approval for any changes would be required by the Eclipse Foundation Board of Directors

Not started

Eclipse Foundation Intellectual Property Policy

  • Amend to include Essential Claims language and tie to the Eclipse Specification Process.

  • Approval for any changes would be required by the Eclipse Foundation Board of Directors

Not started

New Documents or Agreements In Process

Topic

Description

Current Status

Java Trademark License

Oracle must provide the Eclipse Foundation a license to use specification names such as JMS and Java Message Service, as well as the related javax namespaces. This is to enable future versions of the specifications to be created under the same names.

DIscussions happened in January 2018 based on a document prepared by Bill Shannon. Seemed like good progress was made and we were close to a consensus, but no visible progress since.


Action:Oracle to provide Eclipse with a draft agreement

License to Existing Specifications

Oracle asserts that they cannot provide the Eclipse Foundation with a license to the specification documents. As a result, new versions of the specifications cannot be based on the existing specification document. This is despite the fact that JSPA Section 5.A. says "Subject to each contributor’s underlying rights in its own Contributions, the Spec Lead(s) for a particular JSR at the time of the final release of the Specification shall own the copyright to the final Spec generated pursuant to that JSR under United States copyright law."


Cannot license existing Java EE specifications under an open source license because:

– A specification likely includes materials contributed by third parties years ago

– Contributions may have been made under license terms that are not open source compatible

– Matching a contributor to a specific, included contribution, or getting consent from all possible

contributors is not practical

No visible progress on this for months.



Action:Oracle to provide Eclipse with a separate submission of all JavaDocs under the EDL.

TCK License

In order to ship a Java EE 8 compliant release release of Eclipse Glassfish, the Eclipse Foundation must license all of the existing EE8 TCKs from Oracle.


This will also include a Java EE trademark license

Almost done.

Eclipse Specification Process

  • New document that is modeled after the EDP describing process of creating specifications, TCKs and RIs

  • Approved by the Eclipse Foundation Board of Directors

  • Adopted by the Jakarta EE Working Group Specification Committee


Additional notes betlow.


The Eclipse Foundation is tasked with creating a new specification process to guide future development of Java EE specs, and the creation and inclusion of new ones. This will involve:

  • The creation of a new certification mark (brand)

  • The creation of a new certification process that will allow organizations to use the certification mark to denote compatibility.

  • The creation of a new specification license.

  • The creation of a new expert group process that will define how specifications are created and evolved.

  • Develop rules for licensing patents related to specification

(Each of these could be there own separate issue.)

Not started

Documentation License

Oracle has a large amount of non-specification documentation that they plan to contribute.  We need to know what license to use for all of that documentation. Some of the documentation is not specific to our

implementations (e.g., the Java EE tutorial), so we wouldn't want the license to interfere with the ability of other implementations to use that documentation.

Resolved: Text will be provided at Oracle's discretion under either the EDL 1.0 (aka BSD-3 Clause) or the EE4J code license EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0.

Code examples will be provided under the EDL 1.0 (aka BSD-3 Clause)


Action:Oracle to submit documentation.

Jakarta EE Participation Agreement

  • Agreement that binds Member companies to the IP rules (especially patents) related to contributions to specifications

  • Every person involved in a specification project must be covered by a JPA

  • Approved by the EMO, working with the IP Advisory Committee

  • Adopted by the Jakarta EE Working Group Steering Committee

Not started

Eclipse Specification License

  • Terms allowing independent implementations of specifications

  • Approved by the EMO, working with the IP Advisory Committee

  • Adopted by the Jakarta EE Working Group Steering Committee

Not started

Eclipse TCK License

  • Terms allowing access to TCKs

  • Approved by the EMO, working with the IP Advisory Committee

  • Adopted by the Jakarta EE Working Group Steering Committee

Not started

Jakarta EE Trademark License

  • Terms allowing use of the Jakarta EE logo by compatible implementations

  • Approved by the EMO, working with the IP Advisory Committee

  • Adopted by the Jakarta EE Working Group Steering Committee

Not started

Patent licenses contributed under the existing JCP

As a transition-related issue, one might note that consideration should be given to the extent to which patent licenses for specifications developed in the JCP (under the JSPA) will be carried forward to updated versions of those specifications. When succeeding versions were, like the earlier versions, were created subject to the JSPA, there was not a dramatic loss of patent commitments when a spec was updated to a new version. However, when moving from the JSPA to a new regime, this is not so simple; this is complicated topic.

Not started



Completed


Topic

Description

Current Status

Trademark Assignment

Oracle needs to assign to the Eclipse Foundation the names of the projects it wishes to move to the EF.


E.g. Glassfish, Grizzly, etc.

Eclipse Foundation has provided Oracle with an editable version of our standard trademark assignment agreement.


Have received a redline from Oracle, and are working on a response.


Resolution: Agreement concluded.

Eclipse Contributor Agreement

Oracle Legal has indicated that they would like to modify the Eclipse Foundation’s standard Eclipse Contributor Agreement, which embeds the Linux Foundation’s Developer Certificate of Origin.

Resolution: Agreement concluded.

 



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

--- End Message ---

Back to the top