Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakarta.ee-wg] Minutes of Jakarta EE Steering Committe Meeting on June 26

Minutes of Jakarta EE Steering Committe Meeting on June 26. 


Attendees:
Fujitsu: Kenji Kazamura
IBM: Dan Bandera
Oracle: Will Lyons
Payara: (sent regrets)
Red Hat: Scott Stark
Tomitribe: David Blevins

Eclipse: Mike Milinkovich
Review of Minutes from Prior Meeting
Review of minutes from the June 19 Steering Committee meeting.  Members requested that the details be edited, and some of the links are private.   We will revise/resend the minutes per the feedback.
Budget for 2019
The Eclipse Foundation is requesting commitment to a multi-year budget by Sept 15.  Feedback from participants is requested.

Per comments from last week, this item is the first item on the agenda. 

Marketing committee is targeting have a recommended budget by July 5. 

For the headcount budget, EF's goal is to ramp up hiring in Q1.    So the full year headcount budget is what is being proposed.  Members should consider a three-year commitment, perhaps implemented via a Working Group Participation Agreement, possibly renewable on an annual basis.  CNCF provides a good model to review.

We will come back to this topic next meeting.

Marketing Committee Update
See above budget discussion.   Will requested update on marketing calendar, will follow up separately.

Spec Committee Update
Mike M requested approval to post the spec process requirements document.  The Steering Committee voted as follows.
    •    Fujitsu: +1

    •    IBM: awaiting response from Dan

    •    Oracle: +1
    •    Payara: awaiting response from Steve

    •    Red Hat: +1 

    •    Tomitribe: +1
Mike has Steering Committee approval to publish this document, and will reach out to Steve and Dan prior to publishing.  Dan will weigh in (hopefully this week).

Implementations requirements discussion. 
Mike sent an email on the value of compatible implementations and asked Oracle, Payara and Fujitsu whether they intend to contribute to EE4J and Eclipse Glassfish, beyond Eclipse GlassFish 5.1, to keep it relevant as a Compatible Implementation of the Jakarta EE Platform.   The request for comment was made to Oracle, Payara and Fujitsu.  To summarize some of the replies in email:
  • Oracle: Oracle intends to continue to contribute to the EE4J projects.  Ideally, each of the Strategic Members would contribute equally to making EE4J and Jakarta EE successful.

  • Payara: If we have sufficient resources to contribute to EE4J, and GlassFish to keep it relevant as a Compatible Implementation of the Jakarta EE Platform then we will do so. Whether we have sufficient resources will depend on a lot of business factors and is not a given.

  • Fujitsu:  Agreed with Payara.  If the vision of Eclipse Foundation is 'the collaboration on commercially-friendly open source',  then the Eclipse Foundation should provide a commercial-ready quality implementation.  It is Eclipse GlassFish today, but can be another one.
Comment was requested from  Red Hat, IBM and Tomitribe.
All agree there must be a compatible implementation before a spec and TCK can be released, including a compatible implementation of the platform.

Red Hat, IBM and Tomitribe believe that implementations, including the platform implementation may exist outside of EE4J.  There is general consensus for a model where one vendor is the first to provide a compliant platform implementation, and that is sufficient to meet the compliant implementation requirement. 
From an Eclipse perspective, there is a requirement that a preponderance of specifications must have compatible implementations at Eclipse.

This topic will require further discussion by the spec committee regarding the evolutions of specs, TCKs and compatible implementations.   The spec committee needs to define a test/challenge process.

Technical Vision Update/PMC (no time for discussion)

Status of Oracle Contributions (no time for discussion)
EE4J Project Bootstrapping:  https://www.eclipse.org/ee4j/status.php
The high-level status of EE4J projects (as of midday 6/18) was as follows 

    •    39 project proposals have been created 

    •    30 project committers and resources have been provisioned 

    •    26 of these projects have initial contributions provided to the Eclipse IP team 

    •    21 of these projects have the initial contribution pushed to the Git Repository 


The high-level status of EE4J projects (as of midday 6/26) was as follows
    •        39 project proposals have been created (no change)

    •        30 project committers and resources have been provisioned (no change)

    •        26 of these projects have initial contributions provided to the Eclipse IP team (no change)

    •        21 of these projects have the initial contribution pushed to the Git Repository (no change)

Recruitment of new members; Elections (no time for discussion)
Elections underway.
Legal Documents (no time for discussion)
  No significant updates from the last meeting
Other Business
Steering Committee minutes publicly at the Jakarta EE Working Group web site 


 Reminder - The July 3 (two weeks) Steering Committee meeting is cancelled.   Meetings rescheduled starting July 10.


Back to the top