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 January 30th, 2018

Hi All,

please review for approval on the next call

Spec Committee Meeting Minutes January 30th, 2018

Attendees (present in bold):

Kenji Kazumura - Fujitsu, Michael DeNicola

Dan Bandera - IBM, Kevin Sutter, Alasdair Nottingham

Bill Shannon - Oracle, Ed Bratt, Dmitry Kornilov, Jim Wright, Will Lyons

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

Antoine Sabot-Durand - Red Hat (CDI spec Lead)


Eclipse Foundation: Wayne Beaton, Tanja Obradovic, Paul Buck, Mike Milinkovich


  • Past business / action items

    • David moved, Dan second, no objections - Jan 23rd minutes approved

  • Jakarta EE Town Hall call for the community

    • Next time more questions from audience; shorter on PPT and allow more time for questions

    • 57 participants

  • Java EE Specification Documents contribution from Oracle

    • Oracle will transfer Oracle's rights in the documents for the Java EE specifications they lead to the Eclipse Foundation, pending approval by the JCP EC. Oracle will lead the discussion with JCP EC and will communicate via Steering Committee.

    • The Eclipse Foundation will need to acquire the rights that others may have in the specification documents before they can be used for Jakarta EE.

    • The Eclipse Foundation will prepare a legal agreement to acquire these rights and send it to other potential contributors to the Java EE specifications.

    • Oracle will provide a list of specification contributors for Java EE specification developed under the JCP and previously, the to the Eclipse Foundation

  • Jakarta EE 8 release

    • Please refer the document summarizing activities related to Jakarta EE 8 release

      • Approval of the document received at the Steering Committee

      • EF will be further working on identifying the work on the projects that can be done at this point

  • TCK process - David Blevins leading the effort

Things we immediately agree on:

  • A spec cannot require proprietary tools to consume (not exactly correct, but there is board resolution regarding the use of proprietary tools)

  • We want a text format for the specification

    • One month goal: we back off after one month if not attainable

    • Which formats: open discussion point

      • Asciidoc

      • Docbook

      • Markdown?

      • SVG

      • Anything github supports?

    • We agree there can be a no-new specs set of rules:

      • No new specs can have binary specification sources

  • We need a common denominator process for

    • How assertions in spec and tck relate

  • CDI TCK process dock will be the starting point

TODO:

  • Dan: gather information on Oasis FrameMaker to text conversion

  • David: send to list asciidoctor-pdf reference for Bill and others

  • Ed: to send to list conversion so far

  • David: grap CDI TCK process document and convert to google doc for review

Specification Document

  • Must it be normative or can it be a mix of javadoc and other sources

    • Javadoc is part of the specification

    • Java EE Security spec used a lot of Javadoc for assertions and asciidoc was very light

  • Should a PDF be required that can be under the Specification License

    • There are two specifications that are javadoc only

      • How this was handled by the JCP process has not yet been discussed/clarified.

  • Should an HTML version be available online

Many thanks!

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