Review of Minutes from Prior Meeting
The Minutes of the 5/22 meeting were approved.
Marketing Committee Update
The Marketing Committee mission statement will be
distributed this week.
Targeting finalizing Social Media Policy this week.
The Marketing Committee is beginning the process of
creating a messaging editorial calendar. As part of this
effort, the marketing committee requested guidance and
input from the Steering Committee for topics that are key
to focus on. The following topics/milestones were
suggested by the Steering Committee:
- All EE4J (i.e all projects) source contributions
published
- Eclipse GlassFish build
- Java EE 8 certification of Eclipse GlassFish
- Jakarta EE 8 certification of Eclipse GlassFish
- Requirements document for the spec process published
for community input
- TCK contributions published
- Evolve sources that have been contributed (probably
dependent Java EE TM license agreement and spec
process)
- Planned sessions at relevant events (Eclipse Con
Europe and Code One)
- Technical Vision document from the PMC
- JakartaOne (physical and virtual)
- Formation of Jakarta champions(?)
Spec Committee Update
There is active discussion on the Eclipse
Foundation Specification Process: Goals and Requirements v2
document. Will continue with the process, intent is to
publish this document for public feedback.
Technical Vision Update/PMC
The PMC intends to publish a proposed Technical
Mission/Vision document, for Jakarta EE as a whole, on 5/30,
for community feedback.
PMC Minutes are posted at https://www.eclipse.org/ee4j/minutes/
Status of Oracle Contributions
EE4J Project Bootstrapping: https://www.eclipse.org/ee4j/status.php
Here was the high-level status of EE4J projects
(as of midday 5/22) according to the link above:
- 39 project proposals have been created
- 26 project committers and resources have been
provisioned
- 18 of these projects have initial contributions
provided to the Eclipse IP team
- 15 of these projects have the initial contribution
pushed to the Git Repository
The high-level status of EE4J projects (as of
midday 5/29) is as follows (with progress in parentheses)
- 39 project proposals have been created
- 29 project committers and resources have been
provisioned (+3)
- 24 of these projects have initial contributions
provided to the Eclipse IP team (+6)
- 18 of these projects have the initial contribution
pushed to the Git Repository (+3)
There was discussion of separating API projects as
a group. It was agreed we would revisit this after Eclipse
GlassFish is built and Java EE 8 and Jakarta EE 8
certification is obtained.
The Eclipse Foundation requested that Oracle consider
submitting a request for (non-standard) EDL licensing, "in
the event it is required" for the next Eclipse BOD meeting.
Oracle will respond this week.
Recruitment of new members; Elections
No updates
Legal Documents
No significant updates from the last meeting
Oracle and Eclipse Foundation have a meeting scheduled
next week
Budget for 2019
A strawman/proposed budget distributed in mail
for 2019 was discussed. The Eclipse Foundation is looking
to have a commitment to a multi-year budget by Sept 15.
Feedback from participants is requested at the next SC
meeting.
Build Process
The Eclipse Foundation uses CloudBees/Jenkins
Enterprise. Changing from this to something currently used
internally by Oracle would be a problem. A briefing/update
on this topic was requested from Oracle. Will be discussed
in the build meeting 5/30.
Other Business
Mike Milinkovich did a JCP EC update on Jakarta EE on May
24.
The process for posting Steering Committee minutes
publicly at the Jakarta EE Working Group web site is being
put in place.
The June 12 and July 3 Steering Committee meetings are
cancelled.
