tetsuya     2004/01/23 16:46:52

  Modified:    docs/site elsewhere.html
               xdocs/site elsewhere.xml
  Log:
  21 January 2004 - Apache License 2.0 came into effect
  
  Congratulations to everybody who devoted to the new license, especially Roy Fielding
  
  Revision  Changes    Path
  1.113     +2 -2      jakarta-site2/docs/site/elsewhere.html
  
  Index: elsewhere.html
  ===================================================================
  RCS file: /home/cvs/jakarta-site2/docs/site/elsewhere.html,v
  retrieving revision 1.112
  retrieving revision 1.113
  diff -u -r1.112 -r1.113
  --- elsewhere.html    23 Jan 2004 17:54:53 -0000      1.112
  +++ elsewhere.html    24 Jan 2004 00:46:52 -0000      1.113
  @@ -199,7 +199,7 @@
       <h3>21 January 2004 - Apache License 2.0 came into effect</h3>
   </a>
                                                   <p>
  -The 2.0 version of the Apache License was approved by the ASF (The Board has 
approved the new Apache License 2.0) in 2004. The goals of this license revision have 
been to reduce the number of frequently asked questions, to allow the license to be 
reusable without modification by any project (including non-ASF projects), to allow 
the license to be included by reference instead of listed in every file, to clarify 
the license on submission of contributions, to require a patent license on 
contributions that necessarily infringe the contributor's own patents, and to move 
comments regarding Apache and other inherited attribution notices to a location 
outside the license terms (the NOTICE file).
  +The 2.0 version of the Apache License was approved by the ASF (The Board has 
approved the new Apache License 2.0) in 2004. The goals of this license revision have 
been to reduce the number of frequently asked questions, to allow the license to be 
reusable without modification by any project (including non-ASF projects), to allow 
the license to be included by reference instead of listed in every file, to clarify 
the license on submission of contributions, to require a patent license on 
contributions that necessarily infringe the contributor's own patents, and to move 
comments regarding Apache and other inherited attribution notices to a location 
outside the license terms (the <a 
href="http://www.apache.org/licenses/example-NOTICE.txt";>NOTICE</a> file).
   </p>
                                                   <p>
   The result is a license that is compatible with other open source licenses, such as 
the GPL, and yet still remains true to the original goals of the Apache Group and 
supportive of collaborative development across both nonprofit and commercial 
organizations.
  @@ -208,7 +208,7 @@
   All packages produced by the ASF will be implicitly licensed under the Apache 
License, version 2.0, unless otherwise explicitly stated.
   </p>
                                                   <p>
  -For more information, see <a href="http://www.apache.org/licenses/";>Apache Lisenses 
Page</a>.
  +For more information, see <a href="http://www.apache.org/licenses/";>Apache Licenses 
Page</a>.
   </p>
                                                   <hr noshade="noshade" size="1" />
                                                   <a name="20040115.1">
  
  
  
  1.75      +2 -2      jakarta-site2/xdocs/site/elsewhere.xml
  
  Index: elsewhere.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-site2/xdocs/site/elsewhere.xml,v
  retrieving revision 1.74
  retrieving revision 1.75
  diff -u -r1.74 -r1.75
  --- elsewhere.xml     23 Jan 2004 17:54:53 -0000      1.74
  +++ elsewhere.xml     24 Jan 2004 00:46:52 -0000      1.75
  @@ -16,7 +16,7 @@
       <h3>21 January 2004 - Apache License 2.0 came into effect</h3>
   </a>
   <p>
  -The 2.0 version of the Apache License was approved by the ASF (The Board has 
approved the new Apache License 2.0) in 2004. The goals of this license revision have 
been to reduce the number of frequently asked questions, to allow the license to be 
reusable without modification by any project (including non-ASF projects), to allow 
the license to be included by reference instead of listed in every file, to clarify 
the license on submission of contributions, to require a patent license on 
contributions that necessarily infringe the contributor's own patents, and to move 
comments regarding Apache and other inherited attribution notices to a location 
outside the license terms (the NOTICE file).
  +The 2.0 version of the Apache License was approved by the ASF (The Board has 
approved the new Apache License 2.0) in 2004. The goals of this license revision have 
been to reduce the number of frequently asked questions, to allow the license to be 
reusable without modification by any project (including non-ASF projects), to allow 
the license to be included by reference instead of listed in every file, to clarify 
the license on submission of contributions, to require a patent license on 
contributions that necessarily infringe the contributor's own patents, and to move 
comments regarding Apache and other inherited attribution notices to a location 
outside the license terms (the <a 
href="http://www.apache.org/licenses/example-NOTICE.txt";>NOTICE</a> file).
   </p>
   <p>
   The result is a license that is compatible with other open source licenses, such as 
the GPL, and yet still remains true to the original goals of the Apache Group and 
supportive of collaborative development across both nonprofit and commercial 
organizations.
  @@ -25,7 +25,7 @@
   All packages produced by the ASF will be implicitly licensed under the Apache 
License, version 2.0, unless otherwise explicitly stated.
   </p>
   <p>
  -For more information, see <a href="http://www.apache.org/licenses/";>Apache Lisenses 
Page</a>.
  +For more information, see <a href="http://www.apache.org/licenses/";>Apache Licenses 
Page</a>.
   </p>
   
   <hr noshade="noshade" size="1"/>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to