Le 11/08/16 à 14:58, SHAWN E SMITH a écrit : > Thanks. I'm in the middle of fixing a bug, so the extra time will be well > used.
Hi Shawn, and fellow SCIMple developpers ! Back froma long week-end, far from my computer (a needed brak...). I'm currently checking the document that need to be send to the apahe secretary to accept the donation (paper work, paper work :/). Here is teh template : http://incubator.apache.org/ip-clearance/ip-clearance-template.html and some sample : http://incubator.apache.org/ip-clearance/sling-dynamic-includes.html There are a few things that we need to check : - do you need a corporate CLA for this donation ? Ie, is the Penn university the owner of this code, and if so, is it ready to fill this CCLA ? - the SCIMple-identity name seems pretty genuine, but we probably have to double check that it's not overlaping with any other code with a similar name. So far, I think we are good to go. Can you confirm ? - do we have any dependency on any other third party code that is not under the AL 2.0 license, or a compatible license ? So far, I have checked that : * weld-se is AL 2.0 * args4j is MIT * lombok is probably a MIT-like license. To be checked * JUnitParams : AL 2.0 * FasterXML : seems to be AL 2.0 (to be checked) * Junit : Eclipse Publice License 1.0 * Hibernate : AL 2.0 * Glassfish : CDDL * SLF4j : MIT * Mockito : MIT * assertj : AL 2.0 * restfuse : Eclipse Publice License 1.0 ATM, here is the XML file that has to be completed (I partially updated it) : <?xml version="1.0" encoding="UTF-8"?> <document> <properties> <title>SCIMple-identity Codebase Intellectual Property (IP) Clearance Status</title> </properties> <body> <section id="Codebase+IP+Clearance+TEMPLATE"> <title>Codebase IP Clearance TEMPLATE</title> </section> <section id="SCIMple+Codebase+Intellectual+Property+%28IP%29+Clearance+Status"> <title>SCIMple-identity 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>Apache Directory will be responsible for this code</li> </ul> <ul> <li>This project will be a sub-project</li> </ul> <ul> <li>Officer or member managing donation: Emmanuel Lecharny ([email protected])</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>2016-08-16</th> <th>-----</th> </tr> <tr> <td>2016-08-16</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: (<em>Note versioned software used to calculate sum in parentheses</em>). </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: --- to be completed --- </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>2016-08-16</td> <td>Check that all active committers have a signed CLA on record.</td> </tr> <tr> <td>2016-08-16</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>2016-08-16</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>2016-08-16</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>Vote on [email protected]: https://lists.apache.org/thread.html/48cd1ceeb6b96036bc9b7a98f4cc41618ac61ef15415b096a0d5c1ee@%3Cdev.directory.apache.org%3E</em></li> <li><em>Vote result on [email protected]: https://lists.apache.org/thread.html/913f40526ab02115a1da65f49451ec1f3abb025a5552a6e0bb7247b6@%3Cdev.directory.apache.org%3E</em></li> </ul> </section> </section> </body> </document>
