|
Draft Meeting Minutes of Jakarta EE Steering Committee Meeting
on September 4
Attendees:
Fujitsu: Kenji Kazumura, Mike Denicola
IBM: Dan Bandera
Oracle: Will Lyons
Payara: Steve Millidge
Red Hat: Mark Little
Tomitribe: Richard Monson-Hafael
Martijn Verburg
Ivar Grimstad: not present
Eclipse: Mike Milinkovich
Review of Minutes from Prior Meeting
August 21 meeting minutes were approved. Will add
Richard and Mike D to the attendee list.
Minutes of August 28 meeting have been distributed and will be
reviewed next meeting.
Budget Update
1) Per the minutes of the Budget meeting August 22,
next steps on the budget are as follows:
a) Update from IBM and Red Hat to obtain the
requested funding commitments.
IBM stated in the August 28 Steering Committee
meeting it believes it will be able to support $300K/year
for 3 years depending on the language, particularly the
contingency on enabling evolution of the javax namespace
discussed on August 22.
September 4 update from Red Hat: Mark Little expects to
send email with an update this week, or by the next Steering
Committee meeting at the latest.
b) Assuming funding commitments are obtained, we would draft,
review and vote on a Steering Committee resolution with the
required funding levels.
c) The Eclipse Foundation would draft a participation
agreement based on the agreed funding levels, with the
contingency statement referenced above.
Paul White updated the group on the appropriate
procedures for doing this. He has drafted a set of
resolutions for review next week sent in email today. These
cover:
- Fees for strategic members
- Fees for enterprise and solution members
The above include the agreed contingency on evolution of the
javax namespace. Please review and comment prior to next
week's meeting.
A budget resolution would come next, following the
resolutions above.
The Steering Committee approved publication of above to the
Jakarta EE Working Group contingent on no objections by a SC
member by 1PM EDT Sept 6.
2) In the August 28 Steering Committee meeting, Tomitribe and
the Eclipse Foundation agreed to work offline the specific case
of Apache TomEE, ability to use the Jakarta EE brand and
membership fees.
David Blevins has provided details of the case in
question in email to the Steering Committee. The Eclipse
Foundation has follow up questions. Mike Milinkovich will
reply to David's email.
Updates on Oracle contributions
The following contributions/submissions were made to
Eclipse in the past week:
• JAF
• JavaMail
• gmbal (GlassFish MBean Annotation Library)
• GlassFish Corba (on 8/23)
The following submissions were pushed to Eclipse repositories in
the past week:
• Fighterfish
• HK2
The GlassFIsh project was submitted for review this week.
Oracle has obtained internal approval to submit the TCK sources
(correction following the meeting - the Oracle Jakarta EE team
has been told this will be approved internally).
Mike Milinkovich noted that the Eclipse Foundation has signed
the TCK License Agreement and is expecting Oracle's signature
shortly.
Oracle continues to work on GlassFish contribution and
contributions to be made under EDL licensing terms.
Discuss Email re: Building Momentum for Jakarta EE discussed in
the last Steering Committee meeting (email content in italics)
We propose the following to build momentum for
Jakarta EE, and would like to discuss these topics in the next
Steering Committee meeting below.
1. Release Eclipse GlassFish and certify it as Java EE 8
compatible by Oracle CodeOne / EclipseCon Europe.
This effort will provide an implementation of Java EE and
Jakarta EE that the Jakarta EE community can evolve. Oracle
has invested a substantial amount of effort in this, and
continues to do so, in order to achieve a shared goal we have
discussed and agreed to as a group. This is an important
milestone and Oracle remains committed to deliver it.
However, contributions to this effort from other Working Group
members would accelerate delivery, improve community
collaboration, and facilitate transfer of technology
ownership.
Each of the EE4J projects have project leads
identified. Each of the EE4J projects needs to be released
and a task in the project’s issue tracker has been opened to
track this activity. For example, see: https://github.com/eclipse-ee4j/servlet-api/issues/195
We would welcome project leads, or other committers, to
take the initiative to:
• Review the release documents and prepare to release
these projects, or recruit and encourage other community
members to do so, and..
• Update the appropriate Jira issues reflecting your
plans
• Let Ed and Dmitry know if you will take on
responsibility for releasing the project in question
There has been some response on this recently and we'd
like to continue the momentum. Dmitry has created a Google
spreadsheet for tracking progress:
https://docs.google.com/spreadsheets/d/1e8inaprMOjnq04hU2o76egHhC8AF3-vNvqjRq6GR0eM/edit#gid=0
Dmitry noted to the PMC he has seen no progress in
this area.
At the last PMC meeting it was agreed that the project lead
for the project would identify and populate the "responsible
person" field.
This person would be expected to update the GitHub task
regarding creating a CI/CD pipeline and releasing the project.
It was requested that we host a webinar to walk through an
example of how this can be done. Dmitry will explore doing
this and will get back to us on this topic. Look for an
email scheduling this week (for delivery at a future time).
Dmitry created links to two how-to wiki pages related to this
topic in each GitHub task:
The Spec Committee will address the decision on Maven groupId
to be used for all specifications to be published by Jakarta
EE.
2. Create a roadmap for definition of a specification process
by the end of the year
One requirement for completing definition of a spec process
is execution of legal agreements between Oracle and the
Eclipse Foundation. With support of our executive
management, we are requesting acceleration of this process.
We are asking our Legal team to set a target for delivery of a
draft Trademark License Agreement. We will also request that
once a draft is available that our counsels meet face to face
regularly to resolve issues with agreements more quickly.
However, most of the spec process can be defined
independently of the above agreements. Bill Shannon will be
sending a separate document detailing work items that we
should address now, independent of the legal agreements.
Ideally we define public milestones some of which are
achievable by Code One / EclipseCon Europe. Please look for
a note from Bill.
Four meetings of the Spec Committee have been
scheduled over the next couple of weeks with this goal in
mind.
3. Announce commitment to Working Group funding
Assuming we collectively commit to a funding model, we
should communicate this externally. We expect to make
progress on this topic in the next Steering Committee meeting.
This topic is tied to the Budget Discussion above.
4. Demonstrate successful execution of the contributed TCKs
Java EE 8 certification of Eclipse GlassFish will be
based on existing Oracle TCK binaries.
We have stated that a next step following Java EE 8
certification of Eclipse GlassFish would be Jakarta EE 8
certification of Eclipse GlassFish. This step depends on
definition of a Jakarta EE 8 specification (discussed in #2
above), and successful execution of the contributed TCKs,
which we intend to become the Jakarta EE 8 TCKs, on Eclipse
GlassFish.
We would like affirmation from this group that Jakarta EE
8 certification of Eclipse GlassFish, including demonstration
of successful execution of the contributed TCKs, remains a
shared goal. Oracle will drive this overall effort, but
requests that project leads, with contribution from other
Working Group members and other community members, take
ownership for driving successful execution of the contributed
TCKs in their area.
This remains a shared goal of this group.
5. Define distributed ownership of Jakarta EE technology
areas and directions
Oracle regards ownership of technology areas as a shared
responsibility going forward, not as an Oracle driven activity
as in Java EE. We would like to drive a process where we
move from the Oracle-driven project leadership model that we
have today to a model where project leadership is more
distributed across the Working Group and the community, and
where project leads define directions for individual projects.
We propose scheduling a meeting in September to review
the project list and more clearly demonstrate distributed
project ownership and project direction, with the intent to
publish for the community by Code One. As part of this effort
recommend identifying those technologies that we expect to
invest in and evolve, and those we do not plan to invest in.
This is related to item #1.
6. Commit to Code One/ECE messaging
Oracle proposed the following Code One messaging. We
believe that the above can be used to augment the messaging
below. We request your support to these messages or some
other set of messages.
Announcing Eclipse GlassFish.
GlassFish contributions to Jakarta EE are complete and
Eclipse GlassFish is certified as Java EE 8 compatible [adjust
statement based on actual level of completion]. We expect
Eclipse GlassFish sources will become the basis for
implementations of Jakarta EE specifications.
[Feedback on the preceding paragraph was received
prior to the meeting from Richard Monson-Hafael and endorsed
by Martijn Verburg and Mark Little.] "The last sentence
troubles me because, in my mind, it implies that GlassFish has
some special official status compared to other
implementations. I would change the sentence "We expect
Eclipse GlassFish sources will become the basis for
implementations of Jakarta EE specifications." to read "We
expect Eclipse GlassFish sources will become the basis for an
implementation of Jakarta EE specifications." Notice that I
added "an" and removed the plural from implementation."
Java EE TCKs are open sourced.
The Java EE 8 Technology Compatibility Kits have been
contributed and are available in Open Source. We expect
these to be the basis for Jakarta EE 8 compatibility tests for
branding of multiple independent implementations of Jakarta EE
specifications.
The statement above should include "...and hosted at the
Eclipse Foundation".
We [Oracle and other WG members] are committed to Jakarta
EE.
We [Oracle and other WG members] remain committed to
enabling evolution of the Java EE 8 technologies, including
evolution of the javax namespace, in Jakarta EE specifications
for cloud native Java. [Hope to identify specific
milestone]. We [Oracle and other WG members] have committed
to funding this effort at the Eclipse foundation.
We [Oracle and other WG members] will leverage Jakarta EE.
We [Oracle and other WG members] intend to leverage
Jakarta EE technologies and cloud native Java in its product
and service offerings. [Each WG member may have its own
announcement that will...] leverage Jakarta EE and/or Eclipse
GlassFish technology, and/or will support Java EE 8, Jakarta
EE 8 and evolution of Jakarta EE.
I will send an email with a point to a Google doc
with existing edits to these messages.
Steering Committee members should review these messages,
comment on them, and be prepared to discuss at SC next week.
Need an answer to a FAQ: "Will GF be certified on JDK 11?"
The proposed response is that "GF and Java EE 8 depend on Java
SE 8 as the minimum JDK version". (I will begin a FAQ in
the messaging document).
We will also need to discuss press release vs. blog, etc.
Legal Documents
We expect the TCK License Agreement will be signed
today. Contribution of TCK sources is approved. (Correction
following the meeting - the Oracle Jakarta EE team has been told
this will be approved internally).
Oracle Legal is picking up the TM license agreement. We are
requesting a date for a draft.
Eclipse Foundation would like to discuss JakartaOne at next
meeting. Target May/June 2019 timeframe.
Marketing Committee Update (not discussed)
PMC Update (See discussion above regarding project
releases)
Recruitment of new members; Elections (no time for discussion
during the meeting)
Open issue - will there be an additional PMC
representative on the Steering Committee.
Planned Jakarta EE certifications (no time for discussion
during the meeting)
What other app servers, besides GlassFish can we
expect on Jakarta EE 8 - get input from Steering Committee.
Wildfly - name clarification needed from RedHat ?
IBM Liberty
Fujitsu
Payara - ?
Weblogic - ?
TomiTribe - ?
|
