jyates · October 29, 2015 18:13
diff --git a/hbase-maven-plugin.xml b/hbase-maven-plugin.xml
 <?xml version="1.0" encoding="UTF-8"?>
 <document>
  <properties>
    <title>XYZ Codebase Intellectual Property (IP) Clearance Status</title>
  </properties>
  <body>
    <section id="Codebase+IP+Clearance+TEMPLATE">
      <title>Codebase IP Clearance TEMPLATE</title>
    </section>
    <section id="hbase-maven-plugin+Codebase+Intellectual+Property+%28IP%29+Clearance+Status">
      <title>hbase-maven-plugin Codebase Intellectual Property (IP) Clearance Status</title>
    </section>
    <section id="Description">
      <title>Description</title>
      <p>Describe the incoming codebase, including whether it is a large set
 of patches, new functional modules, etc.</p>
    </section>
    <section id="Project+info">
      <title>Project info</title>
      <ul>
        <li>Which PMC will be responsible for the code</li>
        <li>Apache HBase</li>
      </ul>
      <ul>
        <li>Into which existing project/module</li>
        <li>HBase project as a new module, hbase-maven-plugin</li>
      </ul>
      <ul>
        <li>Officer or member managing donation:</li>
        <li>Andrew Purtell</li>
      </ul>
      <p>
        <em>Completed tasks are shown by the completion date (YYYY-MM-dd).</em>
      </p>
      <section id="Identify+the+codebase">
        <title>Identify the codebase</title>
        <table>
          <tr>
            <th>date</th>
            <th>item</th>
          </tr>
          <tr>
            <td>2015-10-29</td>
            <td>If applicable, make sure that any associated name does not
                already exist and is not already trademarked for an existing software
                product.</td>
          </tr>
        </table>
        <p>
 MD5 or SHA1 sum for donated software: MD5=cc05601aead219959206bac5d2fa2307 from hbase-maven-plugin-c444b9b6228327266094df266a99daa4f53958c4.tar.gz (OSX MD5)
        </p>
        <section id="Copyright">
          <title>Copyright</title>
          <table>
            <tr>
              <th>date</th>
              <th>item</th>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Check and make sure that the papers that transfer rights to
                  the ASF been received. It is only necessary to transfer
                  rights for the package, the core code, and any new code
                  produced by the project.</td>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Check and make sure that the files that have been donated
                  have been updated to reflect the new ASF copyright.</td>
            </tr>
          </table>
          <p>
 Identify name recorded for software grant: <em>the name of the grant as recorded
 in the foundation/officers area, in either grants.txt or cclas.txt, so that the 
 grant can be easily identified. If recorded in the grants.txt document, use the 
 "for" or title. If recorded in the cclas.txt document, use the company name
 (field 2 without submitter name) and the "form on file" name (field 4, without 
 any people's names).</em>
          </p>
        </section>
        <section id="Verify+distribution+rights">
          <title>Verify distribution rights</title>
            <p>
 Corporations and individuals holding existing distribution rights: WibiData
            </p>
            <ul>
 <li>
 <em>For individuals, use the name as recorded on the committers page</em>
 </li>
            </ul>
          <table>
            <tr>
              <th>date</th>
              <th>item</th>
            </tr>
            <tr>
              <td>....-..-..</td>
              <td>Check that all active committers have a signed CLA on
                  record.</td>
            </tr>
            <tr>
              <td>2015-10-29</td>
              <td>Remind active committers that they are responsible for
                  ensuring that a Corporate CLA is recorded if such is
                  required to authorize their contributions under their
                  individual CLA.</td>
            </tr>
            <tr>
              <td>2015-10-29</td>
              <td>Check and make sure that for all items included with the
                  distribution that is not under the Apache license, we have
                  the right to combine with Apache-licensed code and
                  redistribute.</td>
            </tr>
            <tr>
              <td>2015-10-29</td>
              <td>Check and make sure that all items depended upon by the
                  project is covered by one or more of the following approved
                  licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or
                  something with essentially the same terms.</td>
            </tr>
          </table>
          <p>Generally, the result of checking off these items will be a
             Software Grant, CLA, and Corporate CLA for ASF licensed code,
             which must have no dependencies upon items whose licenses that
             are incompatible with the Apache License.</p>
        </section>
      </section>
      <section id="Organizational+acceptance+of+responsibility+for+the+project">
        <title>Organizational acceptance of responsibility for the project
 </title>
        <p>
 Related VOTEs:
        </p>
        <ul>
          <li><em>The VOTE thread accepting the donation may happen either
 before or after IP clearance. Adoption by lazy concensus is acceptable but
 not recommended.</em></li>
        </ul>
      </section>
    </section>
  </body>
 </document>
	<?xml version="1.0" encoding="UTF-8"?>
	<document>
	<properties>
	<title>XYZ Codebase Intellectual Property (IP) Clearance Status</title>
	</properties>
	<body>
	<section id="Codebase+IP+Clearance+TEMPLATE">
	<title>Codebase IP Clearance TEMPLATE</title>
	</section>
	<section id="hbase-maven-plugin+Codebase+Intellectual+Property+%28IP%29+Clearance+Status">
	<title>hbase-maven-plugin Codebase Intellectual Property (IP) Clearance Status</title>
	</section>
	<section id="Description">
	<title>Description</title>
	<p>Describe the incoming codebase, including whether it is a large set
	of patches, new functional modules, etc.</p>
	</section>
	<section id="Project+info">
	<title>Project info</title>
	<ul>
	<li>Which PMC will be responsible for the code</li>
	<li>Apache HBase</li>
	</ul>
	<ul>
	<li>Into which existing project/module</li>
	<li>HBase project as a new module, hbase-maven-plugin</li>
	</ul>
	<ul>
	<li>Officer or member managing donation:</li>
	<li>Andrew Purtell</li>
	</ul>
	<p>
	<em>Completed tasks are shown by the completion date (YYYY-MM-dd).</em>
	</p>
	<section id="Identify+the+codebase">
	<title>Identify the codebase</title>
	<table>
	<tr>
	<th>date</th>
	<th>item</th>
	</tr>
	<tr>
	<td>2015-10-29</td>
	<td>If applicable, make sure that any associated name does not
	already exist and is not already trademarked for an existing software
	product.</td>
	</tr>
	</table>
	<p>
	MD5 or SHA1 sum for donated software: MD5=cc05601aead219959206bac5d2fa2307 from hbase-maven-plugin-c444b9b6228327266094df266a99daa4f53958c4.tar.gz (OSX MD5)
	</p>
	<section id="Copyright">
	<title>Copyright</title>
	<table>
	<tr>
	<th>date</th>
	<th>item</th>
	</tr>
	<tr>
	<td>....-..-..</td>
	<td>Check and make sure that the papers that transfer rights to
	the ASF been received. It is only necessary to transfer
	rights for the package, the core code, and any new code
	produced by the project.</td>
	</tr>
	<tr>
	<td>....-..-..</td>
	<td>Check and make sure that the files that have been donated
	have been updated to reflect the new ASF copyright.</td>
	</tr>
	</table>
	<p>
	Identify name recorded for software grant: <em>the name of the grant as recorded
	in the foundation/officers area, in either grants.txt or cclas.txt, so that the
	grant can be easily identified. If recorded in the grants.txt document, use the
	"for" or title. If recorded in the cclas.txt document, use the company name
	(field 2 without submitter name) and the "form on file" name (field 4, without
	any people's names).</em>
	</p>
	</section>
	<section id="Verify+distribution+rights">
	<title>Verify distribution rights</title>
	<p>
	Corporations and individuals holding existing distribution rights: WibiData
	</p>
	<ul>
	<li>
	<em>For individuals, use the name as recorded on the committers page</em>
	</li>
	</ul>
	<table>
	<tr>
	<th>date</th>
	<th>item</th>
	</tr>
	<tr>
	<td>....-..-..</td>
	<td>Check that all active committers have a signed CLA on
	record.</td>
	</tr>
	<tr>
	<td>2015-10-29</td>
	<td>Remind active committers that they are responsible for
	ensuring that a Corporate CLA is recorded if such is
	required to authorize their contributions under their
	individual CLA.</td>
	</tr>
	<tr>
	<td>2015-10-29</td>
	<td>Check and make sure that for all items included with the
	distribution that is not under the Apache license, we have
	the right to combine with Apache-licensed code and
	redistribute.</td>
	</tr>
	<tr>
	<td>2015-10-29</td>
	<td>Check and make sure that all items depended upon by the
	project is covered by one or more of the following approved
	licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or
	something with essentially the same terms.</td>
	</tr>
	</table>
	<p>Generally, the result of checking off these items will be a
	Software Grant, CLA, and Corporate CLA for ASF licensed code,
	which must have no dependencies upon items whose licenses that
	are incompatible with the Apache License.</p>
	</section>
	</section>
	<section id="Organizational+acceptance+of+responsibility+for+the+project">
	<title>Organizational acceptance of responsibility for the project
	</title>
	<p>
	Related VOTEs:
	</p>
	<ul>
	<li><em>The VOTE thread accepting the donation may happen either
	before or after IP clearance. Adoption by lazy concensus is acceptable but
	not recommended.</em></li>
	</ul>
	</section>
	</section>
	</body>
	</document>