Add minutes for meeting 2018-02-13
diff --git a/generated/minutes/2018-02-13.html b/generated/minutes/2018-02-13.html new file mode 100644 index 0000000..b9f0c5b --- /dev/null +++ b/generated/minutes/2018-02-13.html
@@ -0,0 +1,239 @@ +<!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 #7</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"> +<div id="toc" class="toc2"> +<div id="toctitle">Table of Contents</div> +<ul class="sectlevel1"> +<li><a href="#ee4j-pmc-meeting-7">EE4J PMC Meeting #7</a></li> +<li><a href="#general">General</a></li> +<li><a href="#pmc-quality-control-statement-to-the-community">PMC Quality Control Statement to the Community</a></li> +<li><a href="#pmc-practical">PMC Practical</a> +<ul class="sectlevel2"> +<li><a href="#pmc-agenda-items">PMC Agenda Items</a></li> +<li><a href="#pmc-meeting-frequency">PMC Meeting Frequency</a></li> +<li><a href="#pmc-lead-swap">PMC Lead Swap</a></li> +</ul> +</li> +<li><a href="#project-proposals">Project Proposals</a> +<ul class="sectlevel2"> +<li><a href="#status">Status</a></li> +<li><a href="#new">New</a></li> +<li><a href="#ozark-licensing">Ozark Licensing</a></li> +</ul> +</li> +<li><a href="#next-meeting">Next Meeting</a></li> +</ul> +</div> +</div> +<div id="content"> +<div class="sect1"> +<h2 id="ee4j-pmc-meeting-7"><a class="anchor" href="#ee4j-pmc-meeting-7"></a><a class="link" href="#ee4j-pmc-meeting-7">EE4J PMC Meeting #7</a></h2> +<div class="sectionbody"> + +</div> +</div> +<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: 2018-02-13</p> +</div> +<div class="paragraph"> +<p>Present:</p> +</div> +<div class="ulist"> +<ul> +<li> +<p>Dmitry</p> +</li> +<li> +<p>Wayne</p> +</li> +<li> +<p>Kevin</p> +</li> +<li> +<p>Ivar</p> +</li> +<li> +<p>David</p> +</li> +</ul> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="pmc-quality-control-statement-to-the-community"><a class="anchor" href="#pmc-quality-control-statement-to-the-community"></a><a class="link" href="#pmc-quality-control-statement-to-the-community">PMC Quality Control Statement to the Community</a></h2> +<div class="sectionbody"> +<div class="paragraph"> +<p>How do we handle projects that do not want to follow these guidelines? Is there support in EDP to enforce? +The PMC can step in and review when a project wants to do a release.</p> +</div> +<div class="paragraph"> +<p>Project describe the release etc.</p> +</div> +<div class="paragraph"> +<p>The PMC <em>can</em> require e.g. TCK must pass.</p> +</div> +<div class="paragraph"> +<p>Can require rules to be followed in order to be able to participate in the project.</p> +</div> +<div class="paragraph"> +<p>Release review is where these checks are normally done.</p> +</div> +<div class="olist arabic"> +<ol class="arabic"> +<li> +<p>Publish the rules</p> +</li> +<li> +<p>Set up restrictions on branches in github</p> +</li> +</ol> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="pmc-practical"><a class="anchor" href="#pmc-practical"></a><a class="link" href="#pmc-practical">PMC Practical</a></h2> +<div class="sectionbody"> +<div class="paragraph"> +<p>Approve minutes from two last meetings - <strong>ok</strong></p> +</div> +<div class="sect2"> +<h3 id="pmc-agenda-items"><a class="anchor" href="#pmc-agenda-items"></a><a class="link" href="#pmc-agenda-items">PMC Agenda Items</a></h3> +<div class="paragraph"> +<p>Agenda items will most likely materialize themselves. Something along the lines of:</p> +</div> +<div class="ulist"> +<ul> +<li> +<p>Projects</p> +<div class="paragraph"> +<p>Project Proposals, Projects Status</p> +</div> +</li> +<li> +<p>Releases</p> +</li> +<li> +<p>Actions</p> +<div class="paragraph"> +<p>Status, New</p> +</div> +</li> +</ul> +</div> +</div> +<div class="sect2"> +<h3 id="pmc-meeting-frequency"><a class="anchor" href="#pmc-meeting-frequency"></a><a class="link" href="#pmc-meeting-frequency">PMC Meeting Frequency</a></h3> +<div class="paragraph"> +<p>Decided to keep the current meeting time, but go over to a bi-weekly meeting frequency: +Bi-weekly Meetings +Tuesdays 17-18 (try to keep it to 30 mins)</p> +</div> +</div> +<div class="sect2"> +<h3 id="pmc-lead-swap"><a class="anchor" href="#pmc-lead-swap"></a><a class="link" href="#pmc-lead-swap">PMC Lead Swap</a></h3> +<div class="paragraph"> +<p>Decided to keep it as it is for now and continue with Ivar as PMC Lead. When someone wants to take over, we will take it from there.</p> +</div> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="project-proposals"><a class="anchor" href="#project-proposals"></a><a class="link" href="#project-proposals">Project Proposals</a></h2> +<div class="sectionbody"> +<div class="sect2"> +<h3 id="status"><a class="anchor" href="#status"></a><a class="link" href="#status">Status</a></h3> +<div class="paragraph"> +<p>Go through current proposals and mark those that are ok</p> +</div> +<div class="paragraph"> +<p>Eclipse Project for Common Annotations (API) - <strong>ok</strong></p> +</div> +<div class="paragraph"> +<p>Eclipse Project for Concurrency Utilities (API & RI) - <strong>ok</strong></p> +</div> +<div class="paragraph"> +<p>Eclipse Project for Enterprise Management - <em>postpone for inclusion in the platform project</em></p> +</div> +<div class="paragraph"> +<p>Eclipse Project for Enterprise Security (API) - <em>postponed: reach out to EG</em></p> +</div> +<div class="paragraph"> +<p>Eclipse Soteria - <em>postponed: reach out to the EG</em></p> +</div> +<div class="paragraph"> +<p>Eclipse Project for Expression Language (API) - <strong>ok</strong></p> +</div> +<div class="paragraph"> +<p>Eclipse Project for JAF (API) - <strong>ok</strong></p> +</div> +<div class="paragraph"> +<p>Eclipse Project for JavaMail (API) - <strong>ok</strong></p> +</div> +<div class="paragraph"> +<p>Eclipse Project for JAX-WS (API & RI) - <strong>ok</strong></p> +</div> +<div class="paragraph"> +<p>Eclipse Project for JSON-B (API) - <strong>ok</strong></p> +</div> +<div class="paragraph"> +<p>Eclipse Project for JAX-B (API & RI) - <strong>ok</strong></p> +</div> +<div class="paragraph"> +<p>Eclipse Project for JSTL (API) - <strong>ok</strong></p> +</div> +<div class="paragraph"> +<p>JTA (API) - <strong>ok</strong></p> +</div> +<div class="paragraph"> +<p>Naming discussion tabled to next meeting.</p> +</div> +<div class="paragraph"> +<p>Discuss how to handle platform projects in the next PMC meeting.</p> +</div> +</div> +<div class="sect2"> +<h3 id="new"><a class="anchor" href="#new"></a><a class="link" href="#new">New</a></h3> +<div class="paragraph"> +<p>JSR 330 DI Tabled for next meeting</p> +</div> +</div> +<div class="sect2"> +<h3 id="ozark-licensing"><a class="anchor" href="#ozark-licensing"></a><a class="link" href="#ozark-licensing">Ozark Licensing</a></h3> +<div class="paragraph"> +<p>Ozark is currently Apache 2.0 licensed. In order to keep that license, the PMC must suggest this to the Eclipse Board for approval.</p> +</div> +<div class="paragraph"> +<p>Decision?</p> +</div> +<div class="paragraph"> +<p>Tabled for next meeting</p> +</div> +</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 February 27 at 17:00 CET</p> +</div> +</div> +</div> +</div> +</body> +</html> \ No newline at end of file
diff --git a/src/adoc/minutes/2018-02-13.adoc b/src/adoc/minutes/2018-02-13.adoc new file mode 100644 index 0000000..41a9324 --- /dev/null +++ b/src/adoc/minutes/2018-02-13.adoc
@@ -0,0 +1,107 @@ +== EE4J PMC Meeting #7 + +== General + +Date: 2018-02-13 + +Present: + +* Dmitry +* Wayne +* Kevin +* Ivar +* David + +== PMC Quality Control Statement to the Community + +How do we handle projects that do not want to follow these guidelines? Is there support in EDP to enforce? +The PMC can step in and review when a project wants to do a release. + +Project describe the release etc. + +The PMC _can_ require e.g. TCK must pass. + +Can require rules to be followed in order to be able to participate in the project. + +Release review is where these checks are normally done. + +. Publish the rules +. Set up restrictions on branches in github + +== PMC Practical + +Approve minutes from two last meetings - *ok* + +=== PMC Agenda Items + +Agenda items will most likely materialize themselves. Something along the lines of: + +* Projects ++ +Project Proposals, Projects Status +* Releases +* Actions ++ +Status, New + +=== PMC Meeting Frequency + +Decided to keep the current meeting time, but go over to a bi-weekly meeting frequency: +Bi-weekly Meetings +Tuesdays 17-18 (try to keep it to 30 mins) + +=== PMC Lead Swap + +Decided to keep it as it is for now and continue with Ivar as PMC Lead. When someone wants to take over, we will take it from there. + +== Project Proposals + +=== Status + +Go through current proposals and mark those that are ok + +Eclipse Project for Common Annotations (API) - *ok* + +Eclipse Project for Concurrency Utilities (API & RI) - *ok* + +Eclipse Project for Enterprise Management - _postpone for inclusion in the platform project_ + +Eclipse Project for Enterprise Security (API) - _postponed: reach out to EG_ + +Eclipse Soteria - _postponed: reach out to the EG_ + +Eclipse Project for Expression Language (API) - *ok* + +Eclipse Project for JAF (API) - *ok* + +Eclipse Project for JavaMail (API) - *ok* + +Eclipse Project for JAX-WS (API & RI) - *ok* + +Eclipse Project for JSON-B (API) - *ok* + +Eclipse Project for JAX-B (API & RI) - *ok* + +Eclipse Project for JSTL (API) - *ok* + +JTA (API) - *ok* + +Naming discussion tabled to next meeting. + +Discuss how to handle platform projects in the next PMC meeting. + +=== New + +JSR 330 DI Tabled for next meeting + +=== Ozark Licensing + +Ozark is currently Apache 2.0 licensed. In order to keep that license, the PMC must suggest this to the Eclipse Board for approval. + +Decision? + +Tabled for next meeting + +== Next Meeting + +Tuesday February 27 at 17:00 CET