|
The following meeting minutes were approved at the 5/15 meeting
of the Jakarta EE Steering Committee.
-------- Forwarded Message
--------
Draft Minutes of Jakarta EE Working Group Steering Committee
Meeting on May 8, 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 - IBM
Will Lyons - Oracle
Steve Millidge - Payara
Mike D - Fujitsu
Mark Little - Red Hat
David Blevins - Tomitribe
Eclipse Foundation:
Mike Milinkovich - Eclipse Foundation
2) Review of minutes from prior meeting
Minutes of the 4/24 meeting were approved.
Minutes of the 5/1 meeting were approved.
3) Marketing Update
Reviewed the draft of the Marketing Committee 5/3
meeting minutes:
The following were the most important updates:
• Intending to come up with a Marketing Plan with
cost estimates for the steering committee to hopefully work on
a budget/modifications/input into what we can do.
• Looking for a volunteer to draft a vision/mission for the
marekting committee itself.
• Will be creating an events spreadsheet.
• Will be creating a messaging plan.
The next Eclipse newsletter is focused on Jakarta EE and will be
published towards end of May.
Mark Little of Red Hat informed the group that he did a
DevNation Live webinar last week about Jakarta EE. There were
1000 registered attendees and 700 turned up. Lots of interest
and lots of good comments.
4) Spec Committee update
The first meeting of the Spec Committee was held.
The Spec Committee will work (first) on requirements for the
spec process and will focus on the spec process vs, the
"roadmap".
There have been very active community discussions on spec
related topics (e.g. profiles).
The Steering Committee reviewed a request for guidance from Bill
Shannon on three options for versioning of Jakarta EE:
i. Continue the Java EE version numbering approach with
Jakarta EE
X being based on Java SE X, for all values of X. With
the new
rapid release cycles of Java SE, that might mean skipping
some
version numbers to allow Jakarta EE to stay in sync with
Java SE.
ii. Start with Jakarta EE 8 and increment the version number
for
each release, making a separate and explicit decision as
to what
version of Java SE to base each release on.
iii. Start over with Jakarta EE 1, incrementing the version
number
for each release.
The Steering Committee's guidance is that we will pursue option
ii. The first version of Jakarta EE will be Jakarta EE 8. We
will increment the version number for each release, making a
separate and explicit decision as to what version of Java SE to
base each release on.
The Steering Committee reviewed the following sequence of
activities leading up to Eclipse GlassFish Jakarta EE 8
certification:
i) Ship Eclipse GlassFish Java EE 8 certified
- Requires source and TCK contributions
- TCK license
ii) In parallel, build the spec process (mid-summer)
- Requires agreement to use the javax namespace and Java names
in the specs
- Requires agreement on approach for licensing specifications
Mike Milinkovich suggested a target date of Sept 15 for a
defined Jakarta EE specification process. The gating factor
to this is likely to be obtaining Legal agreements.
Creation of the Jakarta EE 8 specs (exactly
compatible with Java EE 8) may require an additional 30 days
after completion of the spec process. Would like to release
Eclipse GlassFish as Jakarte EE certified by EclipseCon/Code
One. This creates date pressure on Sept 15. David Blevins
requested guidance from the legal process and the Spec
Committee as soon as possible for what would be required to
create a Jakarta EE 8 spec.
We will review this schedule next week.
We will look at scheduling a review of Bill's prior document on
the Java Trademark Agreement.
5) Technical Vision update
A technical direction document has been started:
https://docs.google.com/document/d/1-HL8KPW4RgRW1TwV_fduHHQ-SPM5nTWysSqebcJHOhk/edit
The plan is to supplement this document with plans from
individual projects. Expect to review a template for such
project plans in the next PMC meeting in two weeks.
6) Status of Oracle contributions
https://www.eclipse.org/ee4j/status.php
(No change in this report from last meeting)
34 projects at or past project review (unchanged from last week)
20 projects with committers and resources provisioned (unchanged
from last week)
15 projects with initial contributions provided (unchanged from
last week)
13 projects with initial contributions pushed to Git (unchanged
from last week)
Wayne provided an update on project creation review. A
significant number of projects will be advanced to the
“committers and resources provisioned” state by next Wednesday.
Update on batch 4 proposals from Dmitry (for the PMC meeting).
Dmitry created the following projects for submission for
creation review:
Eclipse Project for JPA
Eclipse ORB
Eclipse implementation of JAXB
Eclipse Metro
Eclipse Jakarta EE Platform
These projects are ready for community review this week (waiting
on go ahead from Dmitry).
There are a number of projects referenced in last meeting’s
minutes which will likely require non-default licensing.
Oracle is not yet ready to make the request for approval for
this non-default licensing from the Eclipse BOD as of May 8.
The next BOD meeting is June 11, so approval must wait until
then.
7) Recruitment of Enterprise members and Elections
Election update information will be sent out Thursday.
The following proposal from Paul White was reviewed:
The Foundation is proposing to change the name of
the “Influencer" Member class of membership to “Enterprise"
Member. We’d like to add this to the agenda for the steering
committee.
As background for all, we chose the Influencer name as a means
to better reflect the role we believe the Enterprise members
would hold. In hindsight, while the name is more accurate, it
has added unnecessary confusion when explaining memberships to
Enterprises. In short, it’s just not worth the distraction.
There are still no members of this class of membership in the
working group, so there is no impact to the existing members.
This change requires a change to the working group charter,
which requires approval by the steering committee. I’ve
attached a draft with the proposed changes.
Once approved by the steering committee, the steering
committee then asks the Eclipse Foundation Executive Director
for final approval.
The proposal above is specifically intended to change the name
used in the Working Group. This proposal was approved by the
Steering Committee.
Paul also distributed a new deck and flyer for member
recruitment.
8) 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. When the CFP goes live, early
submissions would be helpful.
9) Legal Documents
The Oracle team is working internally to move the
process forward, focusing on Java EE TCK, Trademark Agreement,
and Specification related issues.
|
