Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakarta.ee-spec.committee] Minutes 7-Nov-2018 Meeting of the Jakarta EE Specification Committee

Agenda

  1. Approve the minutes of our Oct. 17th meeting (pasted below).
  2. Approve the Eclipse Foundation Specification Process v1.0 (PDF also attached).
  3. Discuss any modifications that this committee wants to make before adopting the Jakarta EE Specification Process v1.0. One option could be to simply adopt the EF Spec Process as is, and then make modifications as necessary going forward.
  4. Decide if we still need the extra call scheduled for tomorrow.

Minutes

Agenda topic #1: The minutes of the Oct. 17th meeting were unanimously approved.

Agenda topic #2: Approve the Eclipse Foundation Specification Process v1.0.

David Blevins raised the point that there is no process in place to revise the EFSP once it is approved. Under the JCP, for example, the spec process itself is used to modify the spec process. Bill Shannon pointed out that this required some specific allowances in the JCP process since the spec process does not have a reference implementation or TCK. Mike Milinkovich suggested that a process could be put into place which uses an Eclipse project to modify the process, where the team for such a project would be comprised of the union of the various working group specification committee members. As a result of the ensuing discussion, a resolution was drafted as follows:

Resolved, That the Jakarta EE Specification Committee will approve its Specification Process as follows:

  1. Modifications to the Eclipse Foundation Specification Process will be captured in a single document, denoted as the Jakarta EE Specification Process.
  2. The Jakarta EE Specification Process will be approved by a super-majority of the Jakarta EE Specification Committee and then referred to the Jakarta EE Steering Committee for approval.
  3. Any further modifications to the Jakarta EE Specification Process will follow this process.

Bill Shannon pointed out that Oracle has a requirement for a veto over changes to specifications which use the Java trademarks, and that this requirement for a veto extends to the approval of the process itself. Therefore, point #2 above should be revised to require a unanimous vote, or perhaps a super-majority vote that also included unanimity of the strategic members. Bill also noted that there may be additional requirements on the spec process which will arise from the Java trademark agreement between Oracle and the Eclipse Foundation. Dan Bandera asserted that requiring unanimity was not something IBM would support. Mike Milinkovich stated that providing any party to a veto when approving the Eclipse Foundation Specification Process, or future revisions thereof was not acceptable, which Mike DeNicola agreed with. Mike Milinkovich noted that he has a delegation from the Board of Directors to approve the Specification Process, and was hoping to have agreement from this Committee that the process document was adequate for a version 1.0. Bill reiterated that it was the position of Oracle that a revision process must be defined before the process itself should be approved.

The meeting was adjourned as the one hour time allocation ended, and the committee will reconvene on Thursday, November 8th.
--

Mike Milinkovich

Executive Director | Eclipse Foundation, Inc.

mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx

@mmilinkov

+1.613.220.3223 (m)



Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


Back to the top