Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jakarta.ee-spec.committee] Review for approval Spec Committee Meeting Minutes Dec 19th, 2018

Hi All,

please review for approval on our next call January 9th, 2019.

Spec Committee Meeting Minutes Dec 19th, 2018

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

  • Past business / action items

    • Meeting min Dec 12th - approved for publishing

    • Kevin Sutter moved , Bill Shannon second, no objections

  • Extending meeting invite to 2019Q1

    • Keeping the same time slot

    • Extend to weekly for now, and decide end of Jan for later

  • Adopting the “JESP” when referring to Jakarta EE Specification Process

    • As Doodle poll presented JESP is by far the favorite choice and we will go with that

  • Since Scope (and staying within the Scope) is considered an important aspect of the specification process, we need well-defined Scopes. The Scope (and descriptions) for the Specifications are not well-defined.

  • TCK process - as David Blevins is not present this was not discussed, Kevin briefly presented TCK for MicroProfile; topic will be discussed at the next call

    • Refer to email “Understanding the Current Specification Process” and Understanding Java EE TCK Process

    • Understanding MicroProfile TCK Process - Kevin Sutter, please review for discussion in the New Year

    • Completion of the TCK process no later than Jan 30th 2019

    • The topic of distribution of TCK via Maven Central was discussed

      • Compiled ZIP files can also be distributed via EF downloads server.

      • Some of these TCKs are quite large and are produced several times a year, so Sonatype may not be happy with us.

      • May consider using EF hosted Nexus instance

      • Do we need consumers to explicitly agree to any terms to get access to the TCK for a Ratified Final Specification? (e.g. some sort of click through)

        • “We gotta have an audit trail” - Dan Bandera

  • Jakarta EE road map - on hold till all agreements are in place

  • Java EE Specification Documents contribution from Oracle -> this is still being discussed, however for now the answer is NO

    • No news are expected in next little while  

    • Bill Shannon reported that the best case scenario is ⅓ specs will be contributed and ⅔ will not be (EJB and Servlet will not be contributed); criteria for deciding what specification can be contributed is not clear yet

  • Jakarta EE Spec process and Jakarta EE NoSQL project

    • based on EFSP v1.0, but not necessarily the same

    • We will use  Jakarta EE NoSQL to test  EF Spec Process and do customization if necessary to create Jakarta EE Spec Process.By going through the process with Jakarta EE NoSQL, we will capture notes and evolve a draft of the Jakarta EE Specification Process.

    • Jakarta EE NoSQL provisioning is next step; we are waiting on :

      • Board approval of the new IP policy (DONE)

      • Agreements need to be in place (MCCA and WGPA) for project lead/primary committer (Tomitribe)

      • Agreements for other committers (being pursued by the EF Membership Team via separate channels).

      • Werner - no update on Jakarta EE NoSQL, as we’re waiting on agreements to be signed

    • JCP maintenance review - please refer to Maintenance Reviews email thread.

    • “Dials and knobs” that details how a Working Group might extend the EFSP, link to share.

  • Jakarta EE Working Group calls - next call Jan 30th

Wishing you all Great Holidays and Hally New Year!

Regards,
Tanja
--

Tanja Obradovic

Jakarta EE Program Manager | Eclipse Foundation, Inc.

Twitter: @TanjaEclipse

Eclipse Foundation: The Platform for Open Innovation and Collaboration



Avast logo

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


Back to the top