generated/minutes/2019-01-15.html - www.eclipse.org/ee4j - Git at Google

 <!DOCTYPE html>
 <html lang="en">
 <head>
 <meta charset="UTF-8">
 <!--[if IE]><meta http-equiv="X-UA-Compatible" content="IE=edge"><![endif]-->
 <meta name="viewport" content="width=device-width, initial-scale=1.0">
 <meta name="generator" content="Asciidoctor 1.5.6.1">
 <title>EE4J PMC Meeting #2019-01</title>
 <style>

 </style>
 <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.6.3/css/font-awesome.min.css">
 </head>
 <body class="article toc2 toc-left">
 <div id="header">
 <h1>EE4J PMC Meeting #2019-01</h1>
 <div id="toc" class="toc2">
 <div id="toctitle">Table of Contents</div>
 <ul class="sectlevel1">
 <li><a href="#general">General</a></li>
 <li><a href="#action-items">Action Items</a></li>
 <li><a href="#eclipse-glassfish-5-1-status">Eclipse GlassFish 5.1 status</a></li>
 <li><a href="#ee4j-representative-on-the-security-team">EE4J Representative on the Security Team</a></li>
 <li><a href="#split-ee4j">Split EE4J?</a></li>
 <li><a href="#jakarta-ee-roadmap">Jakarta EE Roadmap</a></li>
 <li><a href="#jakarta-ee-8-release">Jakarta EE 8 Release</a></li>
 <li><a href="#jakarta-ee-town-hall-meeting">Jakarta EE Town Hall Meeting</a></li>
 <li><a href="#how-to-engage-contributors">How to engage contributors</a></li>
 <li><a href="#next-meeting">Next Meeting</a></li>
 </ul>
 </div>
 </div>
 <div id="content">
 <div class="sect1">
 <h2 id="general"><a class="anchor" href="#general"></a><a class="link" href="#general">General</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Date: 2019-01-15</p>
 </div>
 <div class="paragraph">
 <p>Present:</p>
 </div>
 <div class="ulist">
 <ul>
 <li>
 <p>Tanja</p>
 </li>
 <li>
 <p>Wayne</p>
 </li>
 <li>
 <p>Dmitry</p>
 </li>
 <li>
 <p>Kevin</p>
 </li>
 <li>
 <p>David</p>
 </li>
 <li>
 <p>Ivar</p>
 </li>
 </ul>
 </div>
 <div class="paragraph">
 <p><strong>NOTE That we now have a shared calendar.</strong></p>
 </div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="action-items"><a class="anchor" href="#action-items"></a><a class="link" href="#action-items">Action Items</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Reviewed, discussed and updated the GitHub Issues, <a href="https://github.com/eclipse-ee4j/ee4j/issues" class="bare">https://github.com/eclipse-ee4j/ee4j/issues</a>.</p>
 </div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="eclipse-glassfish-5-1-status"><a class="anchor" href="#eclipse-glassfish-5-1-status"></a><a class="link" href="#eclipse-glassfish-5-1-status">Eclipse GlassFish 5.1 status</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Dmitry covered the status.
 We have a <strong>green</strong> CTS build!
 Thanks to everybody that helped to get this done!</p>
 </div>
 <div class="paragraph">
 <p><strong>TODOs:</strong></p>
 </div>
 <div class="ulist">
 <ul>
 <li>
 <p>Release public components to Maven central</p>
 </li>
 <li>
 <p>Release Glassfish components that depend on the above</p>
 </li>
 <li>
 <p>Re-run the CTS on the new build</p>
 </li>
 <li>
 <p>4 CQs pending</p>
 </li>
 </ul>
 </div>
 <div class="paragraph">
 <p>A bug has been created for switching from OSSRH to Nexus Pro to support GF builds better in the future.</p>
 </div>
 <div class="paragraph">
 <p>Discussed that there should be a build of the TCK made available as soon as possible.
 An open source build (not officially licensed).</p>
 </div>
 <div class="paragraph">
 <p><strong>Action: David creates a github issue to track this.</strong></p>
 </div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="ee4j-representative-on-the-security-team"><a class="anchor" href="#ee4j-representative-on-the-security-team"></a><a class="link" href="#ee4j-representative-on-the-security-team">EE4J Representative on the Security Team</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Email: <a href="mailto:security@eclipse.org">security@eclipse.org</a></p>
 </div>
 <div class="paragraph">
 <p>The security team should have a rep from the EE4J PMC to ensure that messages related to EE4J projects are handled.
 There is a private bugzilla component where vulnerability reports are stored.
 The team create/identify issues in this bugzilla component and includes the project lead.</p>
 </div>
 <div class="paragraph">
 <p>More information at <a href="https://eclipse.org/security" class="bare">https://eclipse.org/security</a></p>
 </div>
 <div class="paragraph">
 <p><strong>ACTION: Select a rep on the next meeting.</strong></p>
 </div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="split-ee4j"><a class="anchor" href="#split-ee4j"></a><a class="link" href="#split-ee4j">Split EE4J?</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Followed up on the discussion regarding splitting up EE4J (and with that the PMC as well).
 The split would in practice be to split out the implementation projects to a GlassFish top level project with its own PMC and rename the EE4J project to Jakarta (or Jakarta EE?).
 Minor updates would be needed to the EE4J charter and a new charter for the GlassFish project would need to be written.</p>
 </div>
 <div class="paragraph">
 <p>The PMC discussed that we possibly could split EE4J into GlassFish and Jakarta sometime after the 5.1 release.</p>
 </div>
 <div class="paragraph">
 <p>The reason for this is that we don’t know the timeline for GlassFish 5.2 and don’t want this split to cause any further delays.</p>
 </div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="jakarta-ee-roadmap"><a class="anchor" href="#jakarta-ee-roadmap"></a><a class="link" href="#jakarta-ee-roadmap">Jakarta EE Roadmap</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>The PMC encourages the Jakarta EE Platform Specification project to start the work with creating a roadmap for Jakarta EE.</p>
 </div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="jakarta-ee-8-release"><a class="anchor" href="#jakarta-ee-8-release"></a><a class="link" href="#jakarta-ee-8-release">Jakarta EE 8 Release</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p><strong>Assumption: Jakarta EE 8 == Java EE 8 ie. no additional specifications, API, behavioral changes or new profiles.</strong></p>
 </div>
 <div class="paragraph">
 <p><strong>Jakarta EE 8 release</strong></p>
 </div>
 <div class="paragraph">
 <p>Will consist of the following:</p>
 </div>
 <div class="ulist">
 <ul>
 <li>
 <p>Specification (documents and APIs) for the full platform including full and web profiles</p>
 </li>
 <li>
 <p>TCKs (source and binaries); part of the TCKs are documents on how to use TCKs
 the Jakarta EE 8 will not attempt refactoring of the current monolith of the Java EE 8 TCK</p>
 </li>
 <li>
 <p>Specifications that already have a separate TCK will remain as is</p>
 </li>
 <li>
 <p>A Compatible Implementation of the full and web profiles, at least one,  available under open source license;</p>
 </li>
 </ul>
 </div>
 <div class="paragraph">
 <p>Required for the release:</p>
 </div>
 <div class="ulist">
 <ul>
 <li>
 <p>Jakarta EE Specification Process  needs to be completed</p>
 </li>
 <li>
 <p>Jakarta EE TCK process needs to be defined</p>
 </li>
 <li>
 <p>Means to publish Final Specifications and related TCKs</p>
 </li>
 <li>
 <p>Branding process and logo usage guidelines</p>
 </li>
 </ul>
 </div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="jakarta-ee-town-hall-meeting"><a class="anchor" href="#jakarta-ee-town-hall-meeting"></a><a class="link" href="#jakarta-ee-town-hall-meeting">Jakarta EE Town Hall Meeting</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p><strong>January 30th 11AM EST.</strong></p>
 </div>
 <div class="paragraph">
 <p>Open for everyone!
 The PMC will participate in the panel.</p>
 </div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="how-to-engage-contributors"><a class="anchor" href="#how-to-engage-contributors"></a><a class="link" href="#how-to-engage-contributors">How to engage contributors</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>This is a topic for the Town Hall.
 Tanja will create a strawman for the message.</p>
 </div>
 </div>
 </div>
 <div class="sect1">
 <h2 id="next-meeting"><a class="anchor" href="#next-meeting"></a><a class="link" href="#next-meeting">Next Meeting</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Tuesday, Jan 29 at 17:00 CET</p>
 </div>
 </div>
 </div>
 </div>
 </body>
 </html>
	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<!--[if IE]><meta http-equiv="X-UA-Compatible" content="IE=edge"><![endif]-->
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<meta name="generator" content="Asciidoctor 1.5.6.1">
	<title>EE4J PMC Meeting #2019-01</title>
	<style>

	</style>
	<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.6.3/css/font-awesome.min.css">
	</head>
	<body class="article toc2 toc-left">
	<div id="header">
	<h1>EE4J PMC Meeting #2019-01</h1>
	<div id="toc" class="toc2">
	<div id="toctitle">Table of Contents</div>
	<ul class="sectlevel1">
	<li><a href="#general">General</a></li>
	<li><a href="#action-items">Action Items</a></li>
	<li><a href="#eclipse-glassfish-5-1-status">Eclipse GlassFish 5.1 status</a></li>
	<li><a href="#ee4j-representative-on-the-security-team">EE4J Representative on the Security Team</a></li>
	<li><a href="#split-ee4j">Split EE4J?</a></li>
	<li><a href="#jakarta-ee-roadmap">Jakarta EE Roadmap</a></li>
	<li><a href="#jakarta-ee-8-release">Jakarta EE 8 Release</a></li>
	<li><a href="#jakarta-ee-town-hall-meeting">Jakarta EE Town Hall Meeting</a></li>
	<li><a href="#how-to-engage-contributors">How to engage contributors</a></li>
	<li><a href="#next-meeting">Next Meeting</a></li>
	</ul>
	</div>
	</div>
	<div id="content">
	<div class="sect1">
	<h2 id="general"><a class="anchor" href="#general"></a><a class="link" href="#general">General</a></h2>
	<div class="sectionbody">
	<div class="paragraph">
	<p>Date: 2019-01-15</p>
	</div>
	<div class="paragraph">
	<p>Present:</p>
	</div>
	<div class="ulist">
	<ul>
	<li>
	<p>Tanja</p>
	</li>
	<li>
	<p>Wayne</p>
	</li>
	<li>
	<p>Dmitry</p>
	</li>
	<li>
	<p>Kevin</p>
	</li>
	<li>
	<p>David</p>
	</li>
	<li>
	<p>Ivar</p>
	</li>
	</ul>
	</div>
	<div class="paragraph">
	<p><strong>NOTE That we now have a shared calendar.</strong></p>
	</div>
	</div>
	</div>
	<div class="sect1">
	<h2 id="action-items"><a class="anchor" href="#action-items"></a><a class="link" href="#action-items">Action Items</a></h2>
	<div class="sectionbody">
	<div class="paragraph">
	<p>Reviewed, discussed and updated the GitHub Issues, <a href="https://github.com/eclipse-ee4j/ee4j/issues" class="bare">https://github.com/eclipse-ee4j/ee4j/issues</a>.</p>
	</div>
	</div>
	</div>
	<div class="sect1">
	<h2 id="eclipse-glassfish-5-1-status"><a class="anchor" href="#eclipse-glassfish-5-1-status"></a><a class="link" href="#eclipse-glassfish-5-1-status">Eclipse GlassFish 5.1 status</a></h2>
	<div class="sectionbody">
	<div class="paragraph">
	<p>Dmitry covered the status.
	We have a <strong>green</strong> CTS build!
	Thanks to everybody that helped to get this done!</p>
	</div>
	<div class="paragraph">
	<p><strong>TODOs:</strong></p>
	</div>
	<div class="ulist">
	<ul>
	<li>
	<p>Release public components to Maven central</p>
	</li>
	<li>
	<p>Release Glassfish components that depend on the above</p>
	</li>
	<li>
	<p>Re-run the CTS on the new build</p>
	</li>
	<li>
	<p>4 CQs pending</p>
	</li>
	</ul>
	</div>
	<div class="paragraph">
	<p>A bug has been created for switching from OSSRH to Nexus Pro to support GF builds better in the future.</p>
	</div>
	<div class="paragraph">
	<p>Discussed that there should be a build of the TCK made available as soon as possible.
	An open source build (not officially licensed).</p>
	</div>
	<div class="paragraph">
	<p><strong>Action: David creates a github issue to track this.</strong></p>
	</div>
	</div>
	</div>
	<div class="sect1">
	<h2 id="ee4j-representative-on-the-security-team"><a class="anchor" href="#ee4j-representative-on-the-security-team"></a><a class="link" href="#ee4j-representative-on-the-security-team">EE4J Representative on the Security Team</a></h2>
	<div class="sectionbody">
	<div class="paragraph">
	<p>Email: <a href="mailto:security@eclipse.org">security@eclipse.org</a></p>
	</div>
	<div class="paragraph">
	<p>The security team should have a rep from the EE4J PMC to ensure that messages related to EE4J projects are handled.
	There is a private bugzilla component where vulnerability reports are stored.
	The team create/identify issues in this bugzilla component and includes the project lead.</p>
	</div>
	<div class="paragraph">
	<p>More information at <a href="https://eclipse.org/security" class="bare">https://eclipse.org/security</a></p>
	</div>
	<div class="paragraph">
	<p><strong>ACTION: Select a rep on the next meeting.</strong></p>
	</div>
	</div>
	</div>
	<div class="sect1">
	<h2 id="split-ee4j"><a class="anchor" href="#split-ee4j"></a><a class="link" href="#split-ee4j">Split EE4J?</a></h2>
	<div class="sectionbody">
	<div class="paragraph">
	<p>Followed up on the discussion regarding splitting up EE4J (and with that the PMC as well).
	The split would in practice be to split out the implementation projects to a GlassFish top level project with its own PMC and rename the EE4J project to Jakarta (or Jakarta EE?).
	Minor updates would be needed to the EE4J charter and a new charter for the GlassFish project would need to be written.</p>
	</div>
	<div class="paragraph">
	<p>The PMC discussed that we possibly could split EE4J into GlassFish and Jakarta sometime after the 5.1 release.</p>
	</div>
	<div class="paragraph">
	<p>The reason for this is that we don’t know the timeline for GlassFish 5.2 and don’t want this split to cause any further delays.</p>
	</div>
	</div>
	</div>
	<div class="sect1">
	<h2 id="jakarta-ee-roadmap"><a class="anchor" href="#jakarta-ee-roadmap"></a><a class="link" href="#jakarta-ee-roadmap">Jakarta EE Roadmap</a></h2>
	<div class="sectionbody">
	<div class="paragraph">
	<p>The PMC encourages the Jakarta EE Platform Specification project to start the work with creating a roadmap for Jakarta EE.</p>
	</div>
	</div>
	</div>
	<div class="sect1">
	<h2 id="jakarta-ee-8-release"><a class="anchor" href="#jakarta-ee-8-release"></a><a class="link" href="#jakarta-ee-8-release">Jakarta EE 8 Release</a></h2>
	<div class="sectionbody">
	<div class="paragraph">
	<p><strong>Assumption: Jakarta EE 8 == Java EE 8 ie. no additional specifications, API, behavioral changes or new profiles.</strong></p>
	</div>
	<div class="paragraph">
	<p><strong>Jakarta EE 8 release</strong></p>
	</div>
	<div class="paragraph">
	<p>Will consist of the following:</p>
	</div>
	<div class="ulist">
	<ul>
	<li>
	<p>Specification (documents and APIs) for the full platform including full and web profiles</p>
	</li>
	<li>
	<p>TCKs (source and binaries); part of the TCKs are documents on how to use TCKs
	the Jakarta EE 8 will not attempt refactoring of the current monolith of the Java EE 8 TCK</p>
	</li>
	<li>
	<p>Specifications that already have a separate TCK will remain as is</p>
	</li>
	<li>
	<p>A Compatible Implementation of the full and web profiles, at least one, available under open source license;</p>
	</li>
	</ul>
	</div>
	<div class="paragraph">
	<p>Required for the release:</p>
	</div>
	<div class="ulist">
	<ul>
	<li>
	<p>Jakarta EE Specification Process needs to be completed</p>
	</li>
	<li>
	<p>Jakarta EE TCK process needs to be defined</p>
	</li>
	<li>
	<p>Means to publish Final Specifications and related TCKs</p>
	</li>
	<li>
	<p>Branding process and logo usage guidelines</p>
	</li>
	</ul>
	</div>
	</div>
	</div>
	<div class="sect1">
	<h2 id="jakarta-ee-town-hall-meeting"><a class="anchor" href="#jakarta-ee-town-hall-meeting"></a><a class="link" href="#jakarta-ee-town-hall-meeting">Jakarta EE Town Hall Meeting</a></h2>
	<div class="sectionbody">
	<div class="paragraph">
	<p><strong>January 30th 11AM EST.</strong></p>
	</div>
	<div class="paragraph">
	<p>Open for everyone!
	The PMC will participate in the panel.</p>
	</div>
	</div>
	</div>
	<div class="sect1">
	<h2 id="how-to-engage-contributors"><a class="anchor" href="#how-to-engage-contributors"></a><a class="link" href="#how-to-engage-contributors">How to engage contributors</a></h2>
	<div class="sectionbody">
	<div class="paragraph">
	<p>This is a topic for the Town Hall.
	Tanja will create a strawman for the message.</p>
	</div>
	</div>
	</div>
	<div class="sect1">
	<h2 id="next-meeting"><a class="anchor" href="#next-meeting"></a><a class="link" href="#next-meeting">Next Meeting</a></h2>
	<div class="sectionbody">
	<div class="paragraph">
	<p>Tuesday, Jan 29 at 17:00 CET</p>
	</div>
	</div>
	</div>
	</div>
	</body>
	</html>