blob: 9597219397c9a8e7ad6d53f79138e7bf8fda2a78 [file] [log] [blame]
---
layout: default
title: Board Report - April 2015
breadcrumb: Board Report - April 2015
---
<div class="page-title">
<div class="container">
<h1>BOARD REPORT - April 2015</h1>
</div>
</div>
<div class="container">
<div class="row" style="margin-top: 30px">
<div class="col-md-12 col-md-6">
<h5 class="text-green">Community</h5>
<ul>
<li>The development and user lists continue to stay active.</li>
<li>Several ActiveMQ based presentation were given at Apachecon NA.</li>
<li>The ActiveMQ community has voted to name the HortnetQ code donation ActiveMQ Artemis.</li>
<li>Apache board members requested a special report to address what the plan is of the hornetq code donation.  There were some specific question what were directed at the PMC:</li>
<hr/>
<dl>
<dt>Red Hat has a product, called HornetQ, which includes a website; branding, etc. <a href="http://hornetq.jboss.org/" class="uri">http://hornetq.jboss.org/</a></dt>
<dd>ActiveMQ PMC does not intend to use the HornetQ branding in any code, docs or website. The code donation has been updated to remove such references. The HornetQ open source project is now considered a legacy project and the code is no longer maintained as the open source project HornetQ. The ActiveMQ community is beginning to work together to develop a plan to take the donated code base forward and to develop around this code base. </dd>
</dl>
<dl>
<dt>The ActiveMQ PMC needs to deliver a plan for:</dt>
<dd>Apache ActiveMQ has multiple products with multiple versions:</dd>
<ol>
<li>ActiveMQ - (version 5.x.x)</li>
<li>ActiveMQ Artemis - (version 1.x.x)</li>
</ol>
<dd>This means that we are not yet ready to declare that ActiveMQ Artemis is the successor to ActiveMQ 5.x.  We will wait until the product matures to make that decision.</dd>
</dl>
<dl>
<dt>The current chair has been the chair for *many* years and based on the current status and issues in the community, I would strongly suggest having a plan for potentially replacing the chair of the project.</dt>
<dd>The PMC agrees.</dd>
</dl>
<hr/>
<li>The PMC has voted to give the code donation a code name so that it is not referred to as HornetQ anymore within ActiveMQ.</li>
<li>IP clearance for the code donation is almost complete: <a href="http://incubator.apache.org/ip-clearance/hornetq.html">http://incubator.apache.org/ip-clearance/hornetq.html</a></li>
<li>At least one member of the PMC, as well as several members of the community, feels strongly that disagreements and concerns are not getting addressed.  They would rather have Artemis go through the incubator.</li>
<li>PMC is in discussions looking for ways to increase community diversity</li>
<li>PMC has voted to appoint Bruce Snyder as the ActiveMQ PMC chair.  The PMC requests that the board approve the the following resolution:</li>
<hr/>
<blockquote>
<p>WHEREAS, the Board of Directors heretofore appointed Hiram Chirino to the office of Vice President, Apache ActiveMQ, and</p>
<p>WHEREAS, the Board of Directors is in receipt of the resignation of Hiram Chirino from the office of Vice President, Apache ActiveMQ, and</p>
<p>WHEREAS, the Project Management Committee of the Apache ActiveMQ project has chosen by vote to recommend Bruce Snyder as the Successor to the post;</p>
<p>NOW, THEREFORE, BE IT RESOLVED, that Hiram Chirino is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache ActiveMQ, and</p>
<p>BE IT FURTHER RESOLVED, that Bruce Snyder be and hereby is appointed to the office of Vice President, Apache ActiveMQ, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed.</p>
</blockquote>
<hr/>
</ul>
<h5 class="text-green">Development</h5>
<ul>
<li>Development on ActiveMQ 5.12 is in progress.</li>
<li>Development on ActiveMQ Artemis is in progress.</li>
</ul>
<h5 class="text-green">Trademark / Branding Status</h5>
<ul>
<li>Sub-projects need to be reviewed to make sure they are also compliant /w TM policies</li>
<li>Documentation and readme files will also be reviewed for compliance</li>
</ul>
<h5 class="text-green">Releases</h5>
<ul>
<li>Apache ActiveMQ 5.11.1 - 2/17/15</li>
<li>Apache ActiveMQ 5.10.2 - 2/17/15</li>
<li>Apache ActiveMQ-CPP v3.8.4 - 2/19/15</li>
</ul>
</div>
</div>
</div>