[Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx>]

Attendees (present in bold):

Kenji Kazumura - Fujitsu, Michael DeNicola

Dan Bandera - IBM, Kevin Sutter, Alasdair Nottingham

Bill Shannon - Oracle, Ed Bratt, Dmitry Kornilov

Steve Millidge - Payara, Arjan Tijms

Scott Stark - Red Hat, Mark Little

David Blevins - Tomitribe, Richard Monson-Haefel

Ivar Grimstad - PMC Representative

Alex Theedom - Participant Member

Werner Keil - Committer Member

1. Past business / action items (10 minutes)

• Approval of the August 15, 2018 minutes as distributed on August 22nd.

• Approval of last week's minutes will be deferred to our next call.

• Moved by Dan Bandera, seconded by Ivar Grimstad. Unanimously approved.

• Vote to adopt 'jakarta' as the package name for Jakarta EE Specifications. (Note that it was agreed on last week's call that we would vote this week.)

• "Resolved, that the Java namespace to be used by Jakarta EE Specifications will be jakarta."

• Moved by David Blevins, seconded by Dan Bandera. Unanimously approved.

2. Discuss outline of the Specification Process. (20 minutes)

• Based on Bill Shannon's email from August 27th. In particular looking at whether this list of topics will suffice as a starting point:

• how a spec enters the process

• what steps a spec must take as it moves through the process

• how a final spec is approved

• the role of the Specification Committee in the above

• who votes when and how on the above items and how votes are counted

• what happens when a vote fails

• how to transfer leadership of a spec/implementation/TCK

• how the spec process itself evolves

• Notes from meeting discussion:

• Bill provided an overview of the above.

• General consensus that this list was useful.

• Discussion on how JCP-centric the new process should be.

1. OASIS is a model of a code-first approach that we could also emulate.

2. The OASIS CLA provides an example of how to help construct a code-first approach.

• How do we map this to the Eclipse Development Process? Wayne’s document below is based on the assumption that the EDP is the starting point and is augmented by the specification process.

• Mike D. informed the committee that he has been drafting a major revision to the JCP process to facilitate to iterative development. He suggested that we start from that version. He will ask Don Deutsch of Oracle for permission to share this draft with the Jakarta EE Spec Committee.

• Review of early draft document to be distributed by Wayne Beaton this evening.

• Notes from meeting discussion:

• General review of the document, Agreement that much work is required.

• Everyone is requested to suggest edits and add comments in between meetings to make our meeting times more productive.

3. Create a plan to deliver a draft Specification Process for CodeOne/EclipseCon (30 minutes)

• Notes from meeting discussion:

• The group discussed what our deliverable should be for this timeframe. The general consensus was:

1. Provide a draft specification process for community feedback by CodeOne/EclipseCon. The goal is to use the events to communicate with community members and maximize community awareness and feedback.

2. Recruit our first candidate spec willing to announce their interest in using the Jakarta EE spec process. Eclipse JNoSQL was discussed as one potential.

• Mike Milinkovich took the action item to provide a draft plan for discussion prior to our next meeting.

--
Mike Milinkovich
mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx
(m) +1.613.220.3223

---

This email has been checked for viruses by Avast antivirus software. www.avast.com