Attendees:
Fujitsu:
Kenji Kazumura, Mike Denicola
IBM: Kevin Sutter, Dan Bandera
Oracle: Will Lyons
Payara: not present
Red Hat: not present
Tomitribe: Richard Monson-Hafael
Martijn Verburg:
Ivar Grimstad:
Eclipse: Mike Milinkovich
Review of Minutes from Prior Meeting
Sept 18
minutes approved pending request from Paul White to remove
budget data.
Budget Update
EF plans
to send out participation agreement to SC members in the next
few days.
Working Group Calls
Created
this Doodle poll to select the
best time for most of us. Please respond and let me know what
time slot would work for you. I have extended the poll with
day / times suggested by Amelia. Note: we are trying to get
your input on the day / time in a week, please do not focus on
the poll dates.
Weds @11 AM Eastern time is looking like the best
time.
EclipseCon Europe
Paul
requests we reach out to community members to let them know
about it and encourage attendance
Regarding Steering Committee meeting calendars
generally there is no SC meeting during ECE or during
Thanksgiving week.
Mike reiterated request to encourage attendance. Please
reinforce blogs from other Jakarta EE members.
Updates
on Oracle contributions
https://www.eclipse.org/ee4j/status.php
Schedule discussed last week:
Sep 21 -- All code required for GF build contributed.
Sep 23 — Eclipse GlassFish builds.
Oct 1 -- Java EE 8 CTS testing. We are able to run CTS
tests on Eclipse GlassFish.
Oct 22 — CI/CD release pipelines completed.
Oct 22 -- Eclipse GlassFish 5.1-RC1 milestone release.
Nov 5 — Dependencies updated. All projects are
released to OSSRH and have dependencies to Eclipse version of
other components.
Nov 30 -- Release Review completed.
Dec 14 -- Eclipse GlassFish 5.1 release. All CTS tests
are passed.
Change of Maven groupid went well.
CI/CD pipelines - progress since last week. 23 tasks are
closed. 84 in progress. 12 to do.
Some contributions remain to be published.
Oracle
still needs to blog on this topic.
Will do and encourage attendance at the
conferences and reference other blogs.
Tanja
would like input on which milestones to "make noise" about.
Dmitry will evaluate the feasibility of producing
downloads of nightly builds and provide a target date for
doing so (or having it done) next week.
This does not change the goal to create an RC1 milestone
release on Oct 22.
The next major milestone would be the Dec 14 release date.
Do a full PR push on this milestone.
Discuss Building Momentum for Jakarta EE
discussed in the last Steering Committee meeting (excerpts
from email content in italics)
1.
Release Eclipse GlassFish and certify it as Java EE 8
compatible.
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
Dmitry has created a Google spreadsheet for tracking
progress:
https://docs.google.com/spreadsheets/d/1e8inaprMOjnq04hU2o76egHhC8AF3-vNvqjRq6GR0eM/edit#gid=0
Last week
the activity being tracked above is less than 10% complete.
Seeing progress but there is not enough
progress. Dmitry requested status from project leads today.
2.
Create a roadmap for definition of a specification process
by the end of the year
Ideally we will define public milestones some of which
are achievable by Code One / EclipseCon Europe.
Are we still tracking to have a draft process ready for
community review by ECE/OC1.
Draft process distributed and is under review by Spec
Committee. Still tracking to ECE/OC1 goal.
Still on track.
Making good progress. Thank you Wayne and Tanja!
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.
Mike
blogged on this last week (thanks Mike).
4.
Demonstrate successful execution of the contributed TCKs
Progress on this is possible by Code One/ECE but not likely.
Our messaging should not rely on this.
5.
Define distributed ownership of Jakarta EE technology areas
and directions
This is related to
item #1.
6.
Commit to Code One/ECE messaging
https://docs.google.com/document/d/1_Bgh5rP1qKJdATlQ5ZC-ceJ9AFvHq8lq8_xFrarnlH0/edit
I will update to align with Mike's blog on funding/blogging.
Assuming the specification process is still on track, I will
update this document to reflect that.
Regarding setting technical direction, David initiated a
community discussion on Jakarta EE technology directions,
starting with jakarta.ee-wg@xxxxxxxxxxx,
and the PMC list, and leads (David requested list of lead
names) and report back at next Steering Committee meeting.
David had several responses to his mail. Have another 10
days for further replies. We should discuss this week.
Will discuss next week. Will ask David to be
prepared to discuss next week.
Code
One/ECE presence
Mark has a
panel discussion scheduled. Should capture details of who
will participate next week.
Adding Weds evening BOF session at ECE.
Create a summary of Code One sessions related to Jakarta EE to
use for blogging.
Tanja will do similar a similar calendar for ECE.
Legal Documents
Oracle
Legal is working on the TM license agreement. We have
requested a date for a draft.
JakartaOne
Not enough
time to plan/execute for mtg next year. Will target for
Spring 2020 for a physical event. Will target 1-2 virtual
events for 2019.
Marketing Committee Update
We will create a social media kit for ECE this
week and distribute to members.
Standardization of project pages. Marketing committee would
like to create a standard template - will ask if PMC wants
such a template for (optional/recommended) use by individual
projects. PMC believes this is a good idea, and we should
encourage individual projects to use it. Target delivery
probably after ECE.
Bill is ready to use such a template for a first project
(JavaMail). David (TT) has created a template for MP, David
(or someone from TT) volunteered to create a Jakarta EE
template based on this MP template.
PMC Update
No Update