www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bay...@apache.org
Subject svn commit: r641325 - in /infrastructure/site/trunk: docs/legal/drafts/ docs/legal/process-draft.html xdocs/legal/drafts/ xdocs/legal/process-draft.html
Date Wed, 26 Mar 2008 14:29:31 GMT
Author: bayard
Date: Wed Mar 26 07:29:27 2008
New Revision: 641325

URL: http://svn.apache.org/viewvc?rev=641325&view=rev
Log:
Adding a directory for legal drafts, and a draft that explains the process Apache go through
when bringing in new code

Added:
    infrastructure/site/trunk/docs/legal/drafts/
    infrastructure/site/trunk/docs/legal/process-draft.html   (with props)
    infrastructure/site/trunk/xdocs/legal/drafts/
    infrastructure/site/trunk/xdocs/legal/process-draft.html   (with props)

Added: infrastructure/site/trunk/docs/legal/process-draft.html
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/docs/legal/process-draft.html?rev=641325&view=auto
==============================================================================
--- infrastructure/site/trunk/docs/legal/process-draft.html (added)
+++ infrastructure/site/trunk/docs/legal/process-draft.html Wed Mar 26 07:29:27 2008
@@ -0,0 +1,72 @@
+<?xml version="1.0"?>
+<!--
+Copyright 2006 The Apache Software Foundation
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<document>
+  <properties>
+    <title>ASF Development Process</title>
+    <atom url="http://mail-archives.apache.org/mod_mbox/www-legal-discuss/?format=atom">ASF
legal-disuss Mailing List</atom>
+  </properties>
+<body>
+<section>
+<title>ASF Development Process</title>
+<p>DRAFTDRAFTDRAFT</p>
+<section><title>Purpose and Intended Audience</title>
+<p>Here we summarize the process of development at the Apache Software Foundation (ASF),
with a focus on the legal side of things. It's 
+intended for those who are interested as to what the ASF do to manage the ownership of their
products. </p>
+</section>
+
+<section><title>Incoming code</title>
+<p>Source code enters the foundation in one of the following ways: </p>
+<ol type="i">
+<li>New project joining Apache</li>
+<li>A large one off code contribution</li>
+<li>Repeated contributions applied directly to the source</li>
+<li>Patches applied to issue trackers</li>
+</ol>
+<p>Each of these methods has its own process:</p>
+<ol type="i">
+<li>New projects join through the Apache Incubator project. All copyright holders have
to sign Contributor License Agreements or Software Grants, 
+and names are checked for trademark issues. CLAs tend to be for individuals who will continue
to develop the software, while grants are for those who will 
+not commit or for companies. You can learn more about that process <a href="http://incubator.apache.org/">here</a>.
 </li>
+<li>One off code donations can come in through a software grant. You can see list of
such grants at the 
+<a href="http://incubator.apache.org/ip-clearance/index.html">IP Clearance page</a>.
</li>
+<li>Individuals who will repeatedly commit to the codebase sign a Contributor License
Agreement. Sometimes they and their employer will also want to sign a 
+<a href="http://www.apache.org/licenses/cla-corporate.txt">Corporate CLA</a>,
however it is at the desire of employee and employer and not something the 
+ASF require. </li>
+<li>Patches to the JIRA issue trackers contain a checkbox that users must check to
'Grant license to ASF for inclusion in ASF works'. </li>
+</ol>
+
+<p>In addition to original code licensed to the Apache Software Foundation, Apache
products may include third party code. Whether or not to distribute, 
+or use, that third party code is discussed on the legal-discuss@ mailing list as to whether
the license is acceptable. The very general philosophy is to 
+avoid licenses adding terms beyond the ASF's AL 2.0 license, while also remaining pragmatic
towards the needs of the user. Prior decisions may be viewed at 
+<a href="http://www.apache.org/legal/resolved.html">here</a>. </p>
+
+<p>Finally, Apache projects record their export classifications <a href="http://www.apache.org/licenses/exports/">here</a>.
</p> 
+
+</section>
+
+<section><title>Outgoing code</title>
+<p>All releases require a successful vote from the releasing project's Project Management
Committee (PMC). If a project is in the 
+Incubator, then the PMC is the overall Incubator PMC and not the incubating project's PPMC.
</p>
+<p>In addition to technical quality - releases are checked to confirm source contains
source headers, that LICENSE and NOTICE files are there and include 
+any additional 3rd party requirements. The Incubator Project contains the <a href="http://wiki.apache.org/incubator/RatProposal">Release
Audit Tool</a>
+(RAT) podling, a tool already in use across Apache to automate checking the quality of product
releases. </p>
+<p>Lastly, releases are checksummed with MD5/SHA1 so that downloads can be checked
for quality; and securely signed with PGP to confirm it is the originally 
+released material. </p>
+</section>
+
+</section>
+</body>
+</document>

Propchange: infrastructure/site/trunk/docs/legal/process-draft.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: infrastructure/site/trunk/xdocs/legal/process-draft.html
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/xdocs/legal/process-draft.html?rev=641325&view=auto
==============================================================================
--- infrastructure/site/trunk/xdocs/legal/process-draft.html (added)
+++ infrastructure/site/trunk/xdocs/legal/process-draft.html Wed Mar 26 07:29:27 2008
@@ -0,0 +1,72 @@
+<?xml version="1.0"?>
+<!--
+Copyright 2006 The Apache Software Foundation
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<document>
+  <properties>
+    <title>ASF Development Process</title>
+    <atom url="http://mail-archives.apache.org/mod_mbox/www-legal-discuss/?format=atom">ASF
legal-disuss Mailing List</atom>
+  </properties>
+<body>
+<section>
+<title>ASF Development Process</title>
+<p>DRAFTDRAFTDRAFT</p>
+<section><title>Purpose and Intended Audience</title>
+<p>Here we summarize the process of development at the Apache Software Foundation (ASF),
with a focus on the legal side of things. It's 
+intended for those who are interested as to what the ASF do to manage the ownership of their
products. </p>
+</section>
+
+<section><title>Incoming code</title>
+<p>Source code enters the foundation in one of the following ways: </p>
+<ol type="i">
+<li>New project joining Apache</li>
+<li>A large one off code contribution</li>
+<li>Repeated contributions applied directly to the source</li>
+<li>Patches applied to issue trackers</li>
+</ol>
+<p>Each of these methods has its own process:</p>
+<ol type="i">
+<li>New projects join through the Apache Incubator project. All copyright holders have
to sign Contributor License Agreements or Software Grants, 
+and names are checked for trademark issues. CLAs tend to be for individuals who will continue
to develop the software, while grants are for those who will 
+not commit or for companies. You can learn more about that process <a href="http://incubator.apache.org/">here</a>.
 </li>
+<li>One off code donations can come in through a software grant. You can see list of
such grants at the 
+<a href="http://incubator.apache.org/ip-clearance/index.html">IP Clearance page</a>.
</li>
+<li>Individuals who will repeatedly commit to the codebase sign a Contributor License
Agreement. Sometimes they and their employer will also want to sign a 
+<a href="http://www.apache.org/licenses/cla-corporate.txt">Corporate CLA</a>,
however it is at the desire of employee and employer and not something the 
+ASF require. </li>
+<li>Patches to the JIRA issue trackers contain a checkbox that users must check to
'Grant license to ASF for inclusion in ASF works'. </li>
+</ol>
+
+<p>In addition to original code licensed to the Apache Software Foundation, Apache
products may include third party code. Whether or not to distribute, 
+or use, that third party code is discussed on the legal-discuss@ mailing list as to whether
the license is acceptable. The very general philosophy is to 
+avoid licenses adding terms beyond the ASF's AL 2.0 license, while also remaining pragmatic
towards the needs of the user. Prior decisions may be viewed at 
+<a href="http://www.apache.org/legal/resolved.html">here</a>. </p>
+
+<p>Finally, Apache projects record their export classifications <a href="http://www.apache.org/licenses/exports/">here</a>.
</p> 
+
+</section>
+
+<section><title>Outgoing code</title>
+<p>All releases require a successful vote from the releasing project's Project Management
Committee (PMC). If a project is in the 
+Incubator, then the PMC is the overall Incubator PMC and not the incubating project's PPMC.
</p>
+<p>In addition to technical quality - releases are checked to confirm source contains
source headers, that LICENSE and NOTICE files are there and include 
+any additional 3rd party requirements. The Incubator Project contains the <a href="http://wiki.apache.org/incubator/RatProposal">Release
Audit Tool</a>
+(RAT) podling, a tool already in use across Apache to automate checking the quality of product
releases. </p>
+<p>Lastly, releases are checksummed with MD5/SHA1 so that downloads can be checked
for quality; and securely signed with PGP to confirm it is the originally 
+released material. </p>
+</section>
+
+</section>
+</body>
+</document>

Propchange: infrastructure/site/trunk/xdocs/legal/process-draft.html
------------------------------------------------------------------------------
    svn:eol-style = native



---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message