cpl2epl/index.php

<?php  																														require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); 	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); 	$App 	= new App();	$Nav	= new Nav();	$Menu 	= new Menu();		include($App->getProjectCommon());    # All on the same line to unclutter the user's desktop'


	#
	# Begin: page-specific settings.  Change these. 
	$pageTitle 		= "CPL to EPL Conversion";
	$pageKeywords	= "legal, documents, about, cpl, epl, conversion";
	$pageAuthor		= "M. Milinkovich Nov 21/05";
	
	# Add page-specific Nav bars here
	# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
	# $Nav->addNavSeparator("My Page Links", 	"downloads.php");
	# $Nav->addCustomNav("My Link", "mypage.php", "_self", 1);
	# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 1);

	# End: page-specific settings
	#
		
	# Paste your HTML content between the EOHTML markers!	
	$html = <<<EOHTML

<div id="maincontent">
    <div id="midcolumn">
    <h1>$pageTitle</h1>
	<p>As part of the formation of the Eclipse Foundation, the Eclipse community migrated from 
	the Common Public License (<a href="http://www.ibm.com/developerworks/library/os-cpl.html" target="blank">CPL</a>) to the 
	Eclipse Public License (<a href="../../org/documents/epl-v10.php">EPL</a>). This conversion
	resulted in changes to quite a few legal documents on our website. This page maintains the transition
	plan and the old versions of the eclipse.org documents which reference the CPL.</p>
	<p><a href="http://www.opensource.org/licenses/eclipse-1.0.php" target="blank"><img align="absbottom" src="../../images/osi-certified-60x50.gif" border="0"/></a> &nbsp; &nbsp; 
	The Eclipse Public License
	is an OSI-approved open source license.</p> 
	<p>The Eclipse Foundation began the transition from the CPL to the EPL on September 9th, 2004.
	It was substantially completed with the release of Eclipse 3.1 on June 28, 2005.</p>
	
          
    <div class="homeitem3col">
        <h3>CPL to EPL Transition</h3>
          <ul>
            <li><A href="cpl2eplfaq.php">CPL to EPL Transition Plan Frequently Asked Questions</a><br />
  	          This FAQ answers some of the commonly asked questions about transition from the 
  	          <a href="http://www.ibm.com/developerworks/library/os-cpl.html" target="_blank">Common Public License (CPL)</a> 
  	          to the <a href="../../org/documents/epl-v10.php">Eclipse Public License (EPL)</a>.
  	        </li>
            <li><A href="CPL2EPLTransitionPlan.pdf">CPL to EPL Transition Plan</A>
	           The detailed plan (.pdf) for transitioning from the Common Public License (CPL) to the Eclipse Public License (EPL).
	        </li>
	      </ul>
	  </div>
	 <div class="homeitem3col">
	 	<h3>Agreements and Licenses</h3>
	 	<li><A href="notice.php">Eclipse.org Software User Agreement</A> 
            By downloading builds or accessing the CVS repository, you 
            acknowledge that you have read, understood, and agree to be bound by the 
            terms and conditions contained in this agreement.  This agreement is
	        used for projects that default to the Common Public License (CPL).
	      </li>
	  </div>
	<div class="homeitem3col">
        <h3>Frequently Asked Questions</h3>
        	<li><A href="http://www.ibm.com/developerworks/opensource/library/os-cplfaq/index.html" target="_blank">CPL Frequently Asked Questions</A> 
            Written by IBM and hosted at IBM&rsquo;s developerWorks site, this FAQ answers some of the commonly asked questions about the Common Public License (CPL).
          	</li>
	</div>
	<div class="homeitem3col">
        <h3>Resources for Committers</h3>
            <li><A href="about.php">&quot;About&quot; Template (CPL References)</A>
	        This is a template for an &quot;about.html&quot; (&quot;About&quot;) file that describes 
	        CPL-licensed content.  Abouts contain legal documentation and are maintained in the CVS repository
	        and subsequently included in builds in plug-in and other directories.  They usually contain 
	        information about licensing and sometimes also information
	        about any use of cryptography.  By convention, every plug-in usually has an About.  If all the 
	        content in a plug-in, directory or module can be correctly
	        licensed under the CPL then this template can be used without modification.  Any other About 
	        should be approved by the relevant PMC who can also assist committers with drafting an About.
	        </li>
            <li><A href="cpl_copyrightandlicensenotice.php">Default Copyright and License Notice</A>
	        The standard copyright and license notice should appear in all source files where possible.  Variations on this notice may be required (for example where a license other than
	        the CPL or EPL governs the use of the file).
	        </li>
	</div>
	</div>		
  </div>

EOHTML;
	$App->setOutDated('now');
	# Generate the web page
	$App->generatePage('solstice', $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>