Add minutes for meeting 22 and 23
diff --git a/generated/minutes/2018-09-25.html b/generated/minutes/2018-09-25.html
new file mode 100644
index 0000000..044dc3c
--- /dev/null
+++ b/generated/minutes/2018-09-25.html
@@ -0,0 +1,176 @@
+<!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 #22</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 #22</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="#meet-the-specs">Meet the Specs</a></li>
+<li><a href="#committer-status">Committer Status</a></li>
+<li><a href="#working-group-meeting">Working Group Meeting</a></li>
+<li><a href="#project-websites">Project Websites</a></li>
+<li><a href="#pmc-communications">PMC Communications</a></li>
+<li><a href="#eclipse-glassfish">Eclipse GlassFish</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: 2018-09-25</p>
+</div>
+<div class="paragraph">
+<p>Present:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Dmitry Kornilov</p>
+</li>
+<li>
+<p>David Blevins</p>
+</li>
+<li>
+<p>Steve Millidge</p>
+</li>
+<li>
+<p>Mark Little</p>
+</li>
+<li>
+<p>Ivar Grimstad</p>
+</li>
+<li>
+<p>Tanja Obradovic</p>
+</li>
+<li>
+<p>Wayne Beaton</p>
+</li>
+</ul>
+</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>.
+“Meet the Specs” session at EclipseCon Europe
+Immediate Committer status for Mark Wareham on Eclipse Project for Concurrency.
+Working Group Meeting</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="meet-the-specs"><a class="anchor" href="#meet-the-specs"></a><a class="link" href="#meet-the-specs">Meet the Specs</a></h2>
+<div class="sectionbody">
+<div class="ulist">
+<ul>
+<li>
+<p>Please respond to Heiko’s email regarding participating in the EclipseCon Europe “Community Day” session. Solicit participants to join the session to present their specifications to the community.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="committer-status"><a class="anchor" href="#committer-status"></a><a class="link" href="#committer-status">Committer Status</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Wayne will grant Mark Wareham status based on PMC request.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="working-group-meeting"><a class="anchor" href="#working-group-meeting"></a><a class="link" href="#working-group-meeting">Working Group Meeting</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Thank you to Ivar and Dmitry for their participation in the first Working Group Meeting on Monday, September 24/2018.
+Meetings will be organized monthly. Please respond to the Doodle Poll.
+Regular PMC engagement in the Working Group call going forward will be valuable.
+Make a PMC update be a regular feature.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="project-websites"><a class="anchor" href="#project-websites"></a><a class="link" href="#project-websites">Project Websites</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The Jakarta EE Marketing Committee suggests a homogeneous look and feel for the project websites, similar to MicroProfile (<a href="https://microprofile.io" class="bare">https://microprofile.io</a>).</p>
+</div>
+<div class="paragraph">
+<p>Are we interested? If so, the Marketing Committee will create a template and description for us to use.</p>
+</div>
+<div class="paragraph">
+<p>Each specification has an existing website. Next step is to migrate existing websites.</p>
+</div>
+<div class="paragraph">
+<p>Presence of the Specification projects on the jakarta.ee website. Consider generating from GitHub repositories. Eclipse MicroProfile project has code to do this automatically. Provide link to GitHub repo with Asciidoctor file in a standard format. Dmitry and David will coordinate.</p>
+</div>
+<div class="paragraph">
+<p>The PMC thinks that this is a good idea and welcomes the Marketing Committee’s template. EE4J Projects will be encouraged to participate (based on the intrinsic value of the concept). If you want to be part of the Jakarta EE website, do this. Otherwise, good luck to you.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="pmc-communications"><a class="anchor" href="#pmc-communications"></a><a class="link" href="#pmc-communications">PMC Communications</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>It has been suggested on the mailing list that we are clear when communicating on the mailing list. Something in the lines of [PMC DECISION] compared to [PERSONAL OPINION].</p>
+</div>
+<div class="paragraph">
+<p>PMC policies, requirements, best practices, etc. will be posted on the EE4J Website (or Wiki); the website/wiki becomes the source of truth. PMC mailing list is for discussion.</p>
+</div>
+<div class="paragraph">
+<p>Open question: “which website/wiki?” We decided to move discussion to the PMC Mailing list.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="eclipse-glassfish"><a class="anchor" href="#eclipse-glassfish"></a><a class="link" href="#eclipse-glassfish">Eclipse GlassFish</a></h2>
+<div class="sectionbody">
+<div class="ulist">
+<ul>
+<li>
+<p>All code is contributed! The IP Team has granted “checkin” and all projects have code in Eclipse Foundation Git repositories.</p>
+</li>
+<li>
+<p>Eclipse GlassFish is building on Eclipse CI.</p>
+</li>
+<li>
+<p>Java EE 8 CTS tests are running.</p>
+</li>
+<li>
+<p>Dmitry has concerns that the CI/CD release pipelines are not progressing as quickly as they need to. 30 “to do items”; 67 “in progress”, 10 “done”. Again, we need the community leaders/vendors to work with their people to step up to make sure that these tasks are completed.</p>
+</li>
+</ul>
+</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 Oct 9 at 17:00 CET</p>
+</div>
+</div>
+</div>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/generated/minutes/2018-10-09.html b/generated/minutes/2018-10-09.html
new file mode 100644
index 0000000..f67d5a5
--- /dev/null
+++ b/generated/minutes/2018-10-09.html
@@ -0,0 +1,169 @@
+<!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 #23</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 #23</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="#maven-coordinates-for-implementation-projects">Maven coordinates for implementation projects</a></li>
+<li><a href="#module-names">Module Names</a>
+<ul class="sectlevel2">
+<li><a href="#specification-projects">Specification Projects</a></li>
+<li><a href="#implementation-projects">Implementation Projects</a></li>
+</ul>
+</li>
+<li><a href="#new-lead-for-common-annotations-project">New lead for Common Annotations project</a></li>
+<li><a href="#pmc-members-involvement">PMC members involvement</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: 2018-10-09</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>Kevin</p>
+</li>
+<li>
+<p>Dmitry</p>
+</li>
+<li>
+<p>David</p>
+</li>
+<li>
+<p>Mark</p>
+</li>
+<li>
+<p>Steve</p>
+</li>
+<li>
+<p>Ivar</p>
+</li>
+</ul>
+</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="maven-coordinates-for-implementation-projects"><a class="anchor" href="#maven-coordinates-for-implementation-projects"></a><a class="link" href="#maven-coordinates-for-implementation-projects">Maven coordinates for implementation projects</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>There are some implementations using com.sun and org.glassfish groupIds. We need to make a statement about how to deal with it.
+Options are:
+Leave it as it is for now and change it in the next GF release (I vote for it)
+Change it now to something eclipse/ee4j related</p>
+</div>
+<div class="paragraph">
+<p>Recommend using standard Eclipse groupIds like: org.eclipse.<projectname> for the next GlassFish release. Use existing for this upcoming release (if the current TM owners are ok with it).</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="module-names"><a class="anchor" href="#module-names"></a><a class="link" href="#module-names">Module Names</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p><a href="https://www.eclipse.org/lists/ee4j-pmc/msg01229.html" class="bare">https://www.eclipse.org/lists/ee4j-pmc/msg01229.html</a></p>
+</div>
+<div class="paragraph">
+<p><a href="https://www.eclipse.org/lists/ee4j-pmc/msg01195.html" class="bare">https://www.eclipse.org/lists/ee4j-pmc/msg01195.html</a></p>
+</div>
+<div class="sect2">
+<h3 id="specification-projects"><a class="anchor" href="#specification-projects"></a><a class="link" href="#specification-projects">Specification Projects</a></h3>
+<div class="paragraph">
+<p>For the upcoming release, i.e. re-releasing the EE 8 versions, nothing should be changed.
+No changes in module names for upcoming release. No module names must be added for this release.</p>
+</div>
+<div class="paragraph">
+<p>Decision:
+For future releases (master branch), the names should follow a standard, but we are not sure how and by whom this standard should be created.</p>
+</div>
+<div class="paragraph">
+<p>Proposal:
+One way is that it is derived from a community discussion facilitated by the PMC.
+Start of the discussion with a statement where the PMC recommends using “jakarta.*” as module names.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="implementation-projects"><a class="anchor" href="#implementation-projects"></a><a class="link" href="#implementation-projects">Implementation Projects</a></h3>
+<div class="paragraph">
+<p>The jakarta namespace must not be used for implementation projects. Eclipse standard practices should be used. The PMC suggests “org.eclipse.*” as module name. Present on the mailing list and see how the feedback will be.</p>
+</div>
+<div class="paragraph">
+<p>Ivar: Create a GitHub issue and email a link to the issue. One for each of the project types.</p>
+</div>
+<div class="paragraph">
+<p>Spec Projects: <a href="https://github.com/eclipse-ee4j/ee4j/issues/34" class="bare">https://github.com/eclipse-ee4j/ee4j/issues/34</a></p>
+</div>
+<div class="paragraph">
+<p>Implementation Projects: <a href="https://github.com/eclipse-ee4j/ee4j/issues/35" class="bare">https://github.com/eclipse-ee4j/ee4j/issues/35</a></p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="new-lead-for-common-annotations-project"><a class="anchor" href="#new-lead-for-common-annotations-project"></a><a class="link" href="#new-lead-for-common-annotations-project">New lead for Common Annotations project</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Werner Keil and Markus Karg volunteered. The PMC suggest to propose them as co-leads. They must first be voted in as committers. Move discussion to the mailing list.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="pmc-members-involvement"><a class="anchor" href="#pmc-members-involvement"></a><a class="link" href="#pmc-members-involvement">PMC members involvement</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Users are complaining that emails in PMC mailing list are not answered or the response is slow.</p>
+</div>
+<div class="paragraph">
+<p>PMC members are encouraged to be more active on the mailing list.</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 Nov 6 at 17:00 CET<br>
+<strong>NOTE that we skip the meeting scheduled during EclipseCon/Code One</strong></p>
+</div>
+</div>
+</div>
+</div>
+</body>
+</html>
\ No newline at end of file
