commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ggreg...@apache.org
Subject cvs commit: jakarta-commons/commons-build/xdocs/releases prepare.xml
Date Sat, 22 May 2004 00:11:51 GMT
ggregory    2004/05/21 17:11:50

  Modified:    commons-build/xdocs/releases prepare.xml
  Log:
  Update for Apache License 2.0 info.
  
  Revision  Changes    Path
  1.9       +35 -5     jakarta-commons/commons-build/xdocs/releases/prepare.xml
  
  Index: prepare.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/commons-build/xdocs/releases/prepare.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- prepare.xml	13 May 2004 15:30:03 -0000	1.8
  +++ prepare.xml	22 May 2004 00:11:50 -0000	1.9
  @@ -103,12 +103,42 @@
           dependency issues should probably be raised on the commons-dev list.
           </p>
       </subsection>
  -    <subsection name='Check LICENSE'>
  +    <subsection name='Check the Apache License'>
           <p>
  -        Make sure that there is a <strong>complete</strong> 
  -        Apache Software License at the top of each source file. The so-called <em>short
form</em>
  -        of the license has not been approved and should not be used.
  -        </p>	
  +        Check the <a href="http://www.apache.org/licenses/">Apache Licenses</a>
page for current information.
  +        </p>
  +        <p>
  +        Developer documentation on how to apply the Apache License 
  +        can be found in <a href="http://www.apache.org/dev/apply-license.html">Applying
the Apache License, Version 2.0</a>
  +        </p>
  +        <p>
  +        Some of the important items from the aforementioned documents:
  +        </p>
  +        <p>
  +        <b>Do I have to have a copy of the license in each source file?</b>
  +        </p>
  +        <p>
  +        Only one full copy of the license is needed per distribution.  Each source
  +        file only needs to contain the boilerplate notice at:
  +        </p>
  +        <p>
  +        <code><a href="http://www.apache.org/licenses/LICENSE-2.0.html#apply">http://www.apache.org/licenses/LICENSE-2.0.html#apply</a></code>
  +        </p>
  +        <p>
  +        <b>In my current source files I have attribution notices for other works.
  +        Do I put this in each source file now?</b>
  +        </p>
  +        <p>
  +        No. The new license allows for a NOTICE file that contains such attribution
  +        notices (including the Apache attribution notice).  See 
  +        </p>
  +        <p>
  +        <code><a href="http://www.apache.org/licenses/example-NOTICE.txt">http://www.apache.org/licenses/example-NOTICE.txt</a></code>
  +        </p>
  +        <p>
  +        for an example that provides all of the notices applicable to the
  +        httpd-2.0 distribution.
  +        </p>
           <p>
           Also check that the years in the copyright statement in the license in each source
file and
           in the component <code>LICENSE.txt</code> have been updated appropriately.

  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message