Jakarta
EE Spec Committee - October 4th, 2023
Attendees
(present in bold):
Kenji
Kazumura - Fujitsu
Emily
Jiang - IBM -
Tom Watson
Ed
Bratt - Oracle -
Dmitry Kornilov
Andrew
Pielage - Payara -
Petr Aubrecht
David
Blevins - Tomitribe - Jean-Louis Monteiro, Cesar
Hernandez
Ivar
Grimstad - PMC Representative
Marcelo
Ancelmo - Participant Member - Abraham
Marin-Perez
Werner
Keil - Committer Member
Scott
Stark - Red Hat - Scott Marlow Enterprise
Member
Zhai
Luchao - Shandong Cvicse Middleware Co.
- Enterprise Member
Guests
- Jakarta EE 11 co-release coordinators: Ed Burns, Arjan Tijms
Eclipse
Foundation: Tanja Obradovic,
Wayne Beaton, Paul Buck
(chair)
Past
business / action items:
Agenda:
See the spreadsheet for updates.
Notes from 09/05 call:
-
Scott to notify the EMO to provide guidance on question of is an new ballot required for the proposed
refactoring of the CDI specification to break out the integration elements
-
Question/discussion with regards to where “integration” specifications should live? Web Profile?
What about the related TCK artifacts (which when passed bind IP)? Scott to follow up on this one.
[10/04] Check in on where this one is at
Scott to follow-up with the EMO regarding a restructuring review.
Need to determine where best to link this revised
process which is wider in scope, suggestion is to put it on https://jakarta.ee/committees/specification/,
also then send an email to the Spec Discussions mailing list.
[10/04] The Steering Committee has been informed,
the document can be posted to https://jakarta.ee/committees/specification/,
is there a volunteer? Andrew to create a PR and Eclipse WebDev can approve [https://github.com/jakartaee/jakarta.ee/tree/src/content/committees/specification]
Ideas to communicate:
Send an email to the public spec discussion mailing
list to let spec leaders know
Q&A or FAQ to accompany the process
A presentation at JakartaOne Livestream in December?
Audience of the document is mainly the spec projects. Could be a good one to add to an existing talk or segment? Explain implications to application developers.