incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r636132 - in /incubator/public/trunk: site-author/guides/mentor.xml site-publish/guides/mentor.html
Date Tue, 11 Mar 2008 22:33:44 GMT
Author: rdonkin
Date: Tue Mar 11 15:33:35 2008
New Revision: 636132

URL: http://svn.apache.org/viewvc?rev=636132&view=rev
Log:
Wrote up discussion from list. Better late than never...

Modified:
    incubator/public/trunk/site-author/guides/mentor.xml
    incubator/public/trunk/site-publish/guides/mentor.html

Modified: incubator/public/trunk/site-author/guides/mentor.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/mentor.xml?rev=636132&r1=636131&r2=636132&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/mentor.xml (original)
+++ incubator/public/trunk/site-author/guides/mentor.xml Tue Mar 11 15:33:35 2008
@@ -211,6 +211,7 @@
     </section>
     
     <section id='initial-ip-clearance'><title>IP Clearance</title>
+      <section id='initial-up-clearance-general'><title>Background</title>
       <p>
       Existing codebases need to be imported through the standard IP clearance
       process. This means that software grants or CCLAs need to be submitted
@@ -222,6 +223,46 @@
       PPMC. Otherwise, follow the standard IP clearance 
       <a href='#poding-ip-clearance'>process for podlings</a>.
       </p>
+      </section>
+      <section id='initial-provenance'><title>Establishing Provenance</title>
+        <p>
+        Paperwork needs to be submitted to Apache granting rights to use the
+        code. When code comes from existing close corporate sources,
+        then a SGA or a CCLA is typically used. When code comes from existing
+        projects consisting of individual contributions then each contributor
+        needs to be tracked down and asked to sign either a ICLA (if they 
+        will be coming aboard the podling) or a SGA (if they will not).
+        </p><p>
+        It may take some time to track down all contributors. It is not necessary to 
+        have paperwork on file for all contributions before the code is imported.
+        It may be necessary to reverse some patches and rewrite areas of code if
+        contributors cannot be found or at not happy about given Apache written 
+        permission to use their code. 
+        </p><p>
+        No releases are possible until the provenance of all the code to be release
+        has been clearly established and the relevant paperwork filed with Apache. It is
+        therefore important to keep the status updated.
+        </p><p>
+        Receipts of ICLAs, CCLAs, and SGAs are recorded by the secretary in
+        the private foundation repository. Reading is restricted to members and officers

+        of the foundation. If there is no officer or member available then ask on the
+        general list.
+        </p>
+      </section>
+      <section id='initial-import-code-dump'><title>Initial Code Dump</title>
+        <p>
+        For corporate contributions, the SGA or CCLA MUST be completed, submitted
+        and received before the code is imported.
+        </p><p>
+        For contributions composed of patches from individual contributors,
+        it is safe to import the code once the major contributors (by volume)
+        have completed ICLAs or SGAs.
+        </p><p>
+        In either case, the code to be imported should be attached to a JIRA 
+        and then imported. It is recommended that the previous version 
+        control system is tagged so that the imported version is precisely known.
+        </p>
+      </section>
     </section>
     
     <section id='request-required-resources'><title>Request Required Resources</title>

Modified: incubator/public/trunk/site-publish/guides/mentor.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/mentor.html?rev=636132&r1=636131&r2=636132&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/mentor.html (original)
+++ incubator/public/trunk/site-publish/guides/mentor.html Tue Mar 11 15:33:35 2008
@@ -169,6 +169,20 @@
 <li><a href='#initial-ip-clearance'>
 IP Clearance
  </a>
+ <ul>
+<li><a href='#initial-up-clearance-general'>
+Background
+ </a>
+</li>
+<li><a href='#initial-provenance'>
+Establishing Provenance
+ </a>
+</li>
+<li><a href='#initial-import-code-dump'>
+Initial Code Dump
+ </a>
+</li>
+</ul>
 </li>
 <li><a href='#request-required-resources'>
 Request Required Resources
@@ -417,6 +431,10 @@
    <a name="initial-ip-clearance">IP Clearance</a>
 </h3>
 <div class="section-content">
+<h4>
+   <a name="initial-up-clearance-general">Background</a>
+</h4>
+<div class="section-content">
 <p>
       Existing codebases need to be imported through the standard IP clearance
       process. This means that software grants or CCLAs need to be submitted
@@ -429,6 +447,57 @@
       PPMC. Otherwise, follow the standard IP clearance 
       <a href="#poding-ip-clearance">process for podlings</a>.
       </p>
+</div>
+<h4>
+   <a name="initial-provenance">Establishing Provenance</a>
+</h4>
+<div class="section-content">
+<p>
+        Paperwork needs to be submitted to Apache granting rights to use the
+        code. When code comes from existing close corporate sources,
+        then a SGA or a CCLA is typically used. When code comes from existing
+        projects consisting of individual contributions then each contributor
+        needs to be tracked down and asked to sign either a ICLA (if they 
+        will be coming aboard the podling) or a SGA (if they will not).
+        </p>
+<p>
+        It may take some time to track down all contributors. It is not necessary to 
+        have paperwork on file for all contributions before the code is imported.
+        It may be necessary to reverse some patches and rewrite areas of code if
+        contributors cannot be found or at not happy about given Apache written 
+        permission to use their code. 
+        </p>
+<p>
+        No releases are possible until the provenance of all the code to be release
+        has been clearly established and the relevant paperwork filed with Apache. It is
+        therefore important to keep the status updated.
+        </p>
+<p>
+        Receipts of ICLAs, CCLAs, and SGAs are recorded by the secretary in
+        the private foundation repository. Reading is restricted to members and officers

+        of the foundation. If there is no officer or member available then ask on the
+        general list.
+        </p>
+</div>
+<h4>
+   <a name="initial-import-code-dump">Initial Code Dump</a>
+</h4>
+<div class="section-content">
+<p>
+        For corporate contributions, the SGA or CCLA MUST be completed, submitted
+        and received before the code is imported.
+        </p>
+<p>
+        For contributions composed of patches from individual contributors,
+        it is safe to import the code once the major contributors (by volume)
+        have completed ICLAs or SGAs.
+        </p>
+<p>
+        In either case, the code to be imported should be attached to a JIRA 
+        and then imported. It is recommended that the previous version 
+        control system is tagged so that the imported version is precisely known.
+        </p>
+</div>
 </div>
 <h3>
    <a name="request-required-resources">Request Required Resources</a>



---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message