| <!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 #2020-05</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 #2020-05</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="#non-assertion-covenant">Non Assertion Covenant</a></li> |
| <li><a href="#jakarta-ee-9">Jakarta EE 9</a></li> |
| <li><a href="#build-infrastructure">Build infrastructure</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: 2020-05-05</p> |
| </div> |
| <div class="paragraph"> |
| <p>Present:</p> |
| </div> |
| <div class="ulist"> |
| <ul> |
| <li> |
| <p>Steve</p> |
| </li> |
| <li> |
| <p>Dmitry</p> |
| </li> |
| <li> |
| <p>Ed</p> |
| </li> |
| <li> |
| <p>Tanja</p> |
| </li> |
| <li> |
| <p>Ivar</p> |
| </li> |
| <li> |
| <p>Kevin</p> |
| </li> |
| </ul> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="non-assertion-covenant"><a class="anchor" href="#non-assertion-covenant"></a><a class="link" href="#non-assertion-covenant">Non Assertion Covenant</a></h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>We need to ensure that all CONTRIBUTING.md files contain the following:</p> |
| </div> |
| <table class="tableblock frame-all grid-all spread"> |
| <colgroup> |
| <col style="width: 100%;"> |
| </colgroup> |
| <tbody> |
| <tr> |
| <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Eclipse Development Process</strong><br> |
| This Eclipse Foundation open project is governed by the Eclipse Foundation |
| Development Process and operates under the terms of the Eclipse IP Policy.</p> |
| <p class="tableblock">The Jakarta EE Specification Committee has adopted the Jakarta EE Specification |
| Process (JESP) in accordance with the Eclipse Foundation Specification Process |
| v1.2 (EFSP) to ensure that the specification process is complied with by all |
| Jakarta EE specification projects.</p> |
| <p class="tableblock"> * <a href="https://eclipse.org/projects/dev_process" class="bare">https://eclipse.org/projects/dev_process</a><br> |
| * <a href="https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf" class="bare">https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf</a><br> |
| * <a href="https://jakarta.ee/about/jesp/" class="bare">https://jakarta.ee/about/jesp/</a><br> |
| * <a href="https://www.eclipse.org/legal/efsp_non_assert.php" class="bare">https://www.eclipse.org/legal/efsp_non_assert.php</a></p> |
| <p class="tableblock">Automatic creation of PRs won’t work since the contributing files differ between the projects |
| Automatic creation of issues is a way. Will require follow-up. |
| Uncertain whether it is the same text for specifications as for implementations and other projects.</p></td> |
| </tr> |
| </tbody> |
| </table> |
| <div class="ulist"> |
| <div class="title">Actions:</div> |
| <ul> |
| <li> |
| <p>Script issues for the spec projects: Kevin<br> |
| FYI, the script can be found here: <a href="https://github.com/eclipse-ee4j/jakartaee-release" class="bare">https://github.com/eclipse-ee4j/jakartaee-release</a> (needs to be tweaked each time, but the general concept works)</p> |
| </li> |
| <li> |
| <p>Check if it is really needed for implementation projects: Ivar<br> |
| Yes, it is since concepts and code from implementations may end up in specifications.</p> |
| </li> |
| </ul> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="jakarta-ee-9"><a class="anchor" href="#jakarta-ee-9"></a><a class="link" href="#jakarta-ee-9">Jakarta EE 9</a></h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>Reviewed the status.</p> |
| </div> |
| <div class="paragraph"> |
| <div class="title">Progress</div> |
| <p>Specifications: <a href="https://github.com/orgs/eclipse-ee4j/projects/17" class="bare">https://github.com/orgs/eclipse-ee4j/projects/17</a><br> |
| GlassFish: <a href="https://github.com/eclipse-ee4j/glassfish/projects/1" class="bare">https://github.com/eclipse-ee4j/glassfish/projects/1</a><br> |
| TCK: <a href="https://github.com/eclipse-ee4j/jakartaee-tck/projects/1" class="bare">https://github.com/eclipse-ee4j/jakartaee-tck/projects/1</a><br></p> |
| </div> |
| </div> |
| </div> |
| <div class="sect1"> |
| <h2 id="build-infrastructure"><a class="anchor" href="#build-infrastructure"></a><a class="link" href="#build-infrastructure">Build infrastructure</a></h2> |
| <div class="sectionbody"> |
| <div class="paragraph"> |
| <p>Eclipse build infrastructure is slow. |
| Causes problems for projects. |
| Only possible to release during weekends. |
| When GlassFish is buildable, this will really be a problem. |
| Is memberships tied to allocations to build resources? |
| Quota per strategic member or something?</p> |
| </div> |
| <div class="paragraph"> |
| <p><strong>Action:</strong> Figure out how it is allocated. What are available, and how can it be expanded? Ivar and Tanja will check internally at Eclipse Foundation. What are the allocations and how are they allocated?</p> |
| </div> |
| </div> |
| </div> |
| </div> |
| </body> |
| </html> |
