index.php - www.eclipse.org/legal - Git at Google

 <?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 		= "Legal Resources";
 	$pageKeywords	= "legal, documents, about";
 	$pageAuthor		= "M. Ward Nov 18/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="midcolumn">
     <h1>$pageTitle</h1>
     <p>Legal resource page for the Eclipse Foundation.</p>
       <blockquote>
       <ul>
         <li><a href="#GettingStarted" class=jump>Getting Started</a></li>
         <li><a href="#Agreements" class=jump>Agreement and Licenses</a></li>
         <li><a href="#Trademarks" class=jump>Privacy and Trademarks</a></li>
         <li><a href="#CommitterAgreements" class=jump>Committer Agreements</a></li>
         <li><a href="#Committers" class=jump>Committer Resources</a></li>
       </ul>
       </blockquote>

       <div class="homeitem3col">
 	    <h3><a name="GettingStarted"></a>Getting Started</h3>
 	      <ul>
 		    <li><a href="guidetolegaldoc.php">Guide to the Legal Documents:</a>
 	          This provides an in-depth look at the many legal documents related to the Eclipse open source community. This content is of value to committers, contributors, redistributors of Eclipse content, developers of Eclipse-based products and users of Eclipse technologies.
 	        </li>
 	 		<li><A href="eplfaq.php">EPL Frequently Asked Questions:</A>
 	        	This FAQ answers some of the commonly asked questions about the Eclipse Public License (EPL).
 	      	</li>
           	<li><A href="legalfaq.php">Eclipse Foundation Legal Frequently Asked Questions:</A>
 	        	This document answers some of the commonly asked questions about Eclipse.org licensing, contributions, working as a committer, and cryptography.
 	      	</li>
           	<li>For other questions, email: license (at) eclipse.org
           	</li>
           </ul>
       </div>

 	  <div class="homeitem3col">
         <h3><a name="Agreements"></a>Agreements and Licenses</h3>
          <ul>
           <li><a href="termsofuse.php">Web Site Terms of Use:</a>
 	        By accessing, browsing or using this web site, you acknowledge that you have
             read, understood, and agree to be bound by the terms and conditions
             contained in this agreement.
           </li>
           <li><A href="../org/documents/epl-v10.php">Eclipse Public License (EPL):</A>
 	        	The fundamental license document for the Eclipse projects and community.
 	      </li>
 	      <li><A href="../org/documents/edl-v10.php">Eclipse Distribution License (EDL):</A>
 	        	The BSD license used by some Eclipse projects which require dual-licensing along with the EPL.
 	        	Other than for <a href="noncodelicenses.php">example code or build scipts</a>, use of this
 	        	license by an Eclipse project is on a case-by-case basis and requires unanimous approval
 	        	of the <a href="../org/foundation/directors.php">Board of Directors</a>.
 	      </li>
 	      <li><a href="CLA.php">Contributor License Agreement:</a>
 	      		If you are contributing code or documentation to Eclipse Foundation projects you are
 	      		required to complete this agreement.
 	      </li>
 	      <li><a href="CoO.php">Contributor's Certificate of Originality:</a>
 	      		If you are contributing code or documentation to Eclipse Foundation projects, and using
 	      		the git signed-off-by mechanism, you are agreeing to this certificate.
 	      </li>
 	      <li><a href="copyright.php">Copyright Agent:</a>
 	      		Contact information for the Eclipse Foundation's Copyright Agent.
 	      </li>
           <li><A href="epl/notice.php">Eclipse Foundation Software User Agreement:</A>
             By downloading builds or accessing Eclipse Foundation source code repositories, you
             acknowledge that you have read, understood, and agree to be bound by the
             terms and conditions contained in this agreement.
 	      </li>
 	      <li><a href="noncodelicenses.php">Approved Licenses for Non-Code, Example, and Other Content:</a>
 	      	The Board of Directors has approved the use of certain licenses for specific types of
 	      	content on eclipse.org.
 	      </li>
           <li><A href="updatemanager.php">Eclipse Foundation Update Manager Agreement:</A>
 	        If you package &quot;downloadable features&quot; to be installed
 	        from your web site using the Eclipse Update Manager, you must read,
 	        understand, and agree to the terms and conditions contained in this agreement.
 	      </li>
          </ul>
       </div>
       <div class="homeitem3col">
         <h3><a name="Trademarks"></a>Privacy and Trademarks</h3>
         <ul>
           <li><A href="privacy.php">Privacy Policy:</A>
 	        Your privacy is important to us. This statement discloses the information practices for this web site, including what type of
             information is gathered and tracked, how the information is used, and with whom the information is shared.
           </li>
           <li><A href="logo_guidelines.php">Trademark Usage Guidelines:</A>
 	        Guidelines on permissable use of Eclipse logos and trademarks.
 	      </li>
 	      <li><A href="Trademark_Transfer_Agreement.pdf">Trademark Transfer Agreement:</A>
 	        Pre-existing projects which move to the Eclipse Foundation will be required to execute this agreement
 	        to ensure that the Eclipse Foundation has rights to any trademarks associated with the project name.
 	      </li>
           <li><A href="trademarkattributions.php">Trademark Attributions:</A>
 	        Content on this web site may make reference to trademarks requiring attribution.
 	      </li>
         </ul>
       </div>
       <div class="homeitem3col">
         <h3><a name="CommitterAgreements"></a>Committer Agreements</h3>
         <ul>
           <li><A href="committer_process/EclipseMemberCommitterAgreementFinal.pdf">Member Committer Agreement:</A>
 	        This agreement is used by Member companies to cover all of their committers participating in Eclipse projects.
 	      </li>
           <li><A href="committer_process/EclipseIndividualCommitterAgreementFinal.pdf">Individual Committer Agreement:</A>
 	        This agreement is used by committers participating in Eclipse projects who are not covered by a Member
 	        Committer Agreement.
 	      </li>
           <li><A href="committer_process/employer_consent.pdf">Employer Consent Form:</A>
 	        Committers covered by an Individual Committer Agreement must document the consent of their employer
 	        when participating in Eclipse projects.
 	      </li>

         </ul>
       </div>
       <div class="homeitem3col">
         <h3><a name="Committers"></a>Resources for Committers</h3>
         <ul>
           <li><A href="EclipseLegalProcessPoster.pdf">Due Diligence Process:</A>
 	        This document provides a quick pictorial overview of the due diligence process.
 	      </li>
           <li><A href="../org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf">Third Party Dependencies:</A>
 	        This document contains the guidelines for the review of third-party dependencies.
 	      </li>
 	      <li><A href="committerguidelines.php">Committer Guidelines:</A>
 	        This document outlines the issues to be aware of and the processes one should follow when working as a committer on Eclipse.org projects.  A committer is a person
 	        that has been granted commit rights to systems on the Eclipse.org servers such as git repositories, web pages, download servers, mailing lists and so forth.
 	      </li>
 		  <li><A href="ContributionQuestionnairePart1-v1.0.php">Contribution Questionnaire:</A>
 	        Prior to committing a significant contribution of content to an Eclipse Foundation project, the committer must fill out this questionnaire and submit it to  the Eclipse Management Organization (EMO) for approval. In addition to the EMO, the relevant PMC  must also provide a technical review and approval of the contribution. Follow the link to find out more about what we mean by &quot;significant contribution&quot;. Bug fixes or minor enhancements do not require PMC or EMO approval.
 	      </li>

 	      <li><A href="epl/about.php">&quot;About&quot; Templates:</A>
 	        This provides templates for the &quot;about.html&quot; (&quot;About&quot;) files used to describe
 	        EPL-licensed content.
 	      </li>
           <li><A href="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>
 	      <li><A href="http://wiki.eclipse.org/Development_Resources/Automatic_IP_Log#Contributors">Using the IPLog+ Flag in Bugzilla:</A>
 	        There are two different ways to mark a contribution in bugzilla. If the contribution is an attachment to a bug such as a patch, the attachment itself should be marked with the iplog+ flag. If the contribution is in the form of a comment in the bug, then the iplog+ flag should be set on the bug itself.
 	      </li>
 	      <li><A href="/projects/dev_process/new-committer.php">New Committer Process:</A>
 	        The process for project leads and PMC members to add additional
 	        committers to an existing project.
 	      </li>
 	      <li><a href="http://live.eclipse.org/search/node/Janet+Campbell">Recorded IP Presentations</a>
 	      </li>
 	    </ul>
 	  </div>
   </div>
 	<div id="rightcolumn">
 		<div class="sideitem">
 			<h6>Archives</h6>
 			<ul>
 				<li><a href="cpl2epl">CPL to EPL Conversion</a></li>
 			</ul>
 		</div>
 	</div>


 EOHTML;

 	# Generate the web page
 	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
 ?>
	<?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 = "Legal Resources";
	$pageKeywords = "legal, documents, about";
	$pageAuthor = "M. Ward Nov 18/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="midcolumn">
	<h1>$pageTitle</h1>
	<p>Legal resource page for the Eclipse Foundation.</p>
	<blockquote>
	<ul>
	<li><a href="#GettingStarted" class=jump>Getting Started</a></li>
	<li><a href="#Agreements" class=jump>Agreement and Licenses</a></li>
	<li><a href="#Trademarks" class=jump>Privacy and Trademarks</a></li>
	<li><a href="#CommitterAgreements" class=jump>Committer Agreements</a></li>
	<li><a href="#Committers" class=jump>Committer Resources</a></li>
	</ul>
	</blockquote>

	<div class="homeitem3col">
	<h3><a name="GettingStarted"></a>Getting Started</h3>
	<ul>
	<li><a href="guidetolegaldoc.php">Guide to the Legal Documents:</a>
	This provides an in-depth look at the many legal documents related to the Eclipse open source community. This content is of value to committers, contributors, redistributors of Eclipse content, developers of Eclipse-based products and users of Eclipse technologies.
	</li>
	<li><A href="eplfaq.php">EPL Frequently Asked Questions:</A>
	This FAQ answers some of the commonly asked questions about the Eclipse Public License (EPL).
	</li>
	<li><A href="legalfaq.php">Eclipse Foundation Legal Frequently Asked Questions:</A>
	This document answers some of the commonly asked questions about Eclipse.org licensing, contributions, working as a committer, and cryptography.
	</li>
	<li>For other questions, email: license (at) eclipse.org
	</li>
	</ul>
	</div>

	<div class="homeitem3col">
	<h3><a name="Agreements"></a>Agreements and Licenses</h3>
	<ul>
	<li><a href="termsofuse.php">Web Site Terms of Use:</a>
	By accessing, browsing or using this web site, you acknowledge that you have
	read, understood, and agree to be bound by the terms and conditions
	contained in this agreement.
	</li>
	<li><A href="../org/documents/epl-v10.php">Eclipse Public License (EPL):</A>
	The fundamental license document for the Eclipse projects and community.
	</li>
	<li><A href="../org/documents/edl-v10.php">Eclipse Distribution License (EDL):</A>
	The BSD license used by some Eclipse projects which require dual-licensing along with the EPL.
	Other than for <a href="noncodelicenses.php">example code or build scipts</a>, use of this
	license by an Eclipse project is on a case-by-case basis and requires unanimous approval
	of the <a href="../org/foundation/directors.php">Board of Directors</a>.
	</li>
	<li><a href="CLA.php">Contributor License Agreement:</a>
	If you are contributing code or documentation to Eclipse Foundation projects you are
	required to complete this agreement.
	</li>
	<li><a href="CoO.php">Contributor's Certificate of Originality:</a>
	If you are contributing code or documentation to Eclipse Foundation projects, and using
	the git signed-off-by mechanism, you are agreeing to this certificate.
	</li>
	<li><a href="copyright.php">Copyright Agent:</a>
	Contact information for the Eclipse Foundation's Copyright Agent.
	</li>
	<li><A href="epl/notice.php">Eclipse Foundation Software User Agreement:</A>
	By downloading builds or accessing Eclipse Foundation source code repositories, you
	acknowledge that you have read, understood, and agree to be bound by the
	terms and conditions contained in this agreement.
	</li>
	<li><a href="noncodelicenses.php">Approved Licenses for Non-Code, Example, and Other Content:</a>
	The Board of Directors has approved the use of certain licenses for specific types of
	content on eclipse.org.
	</li>
	<li><A href="updatemanager.php">Eclipse Foundation Update Manager Agreement:</A>
	If you package "downloadable features" to be installed
	from your web site using the Eclipse Update Manager, you must read,
	understand, and agree to the terms and conditions contained in this agreement.
	</li>
	</ul>
	</div>
	<div class="homeitem3col">
	<h3><a name="Trademarks"></a>Privacy and Trademarks</h3>
	<ul>
	<li><A href="privacy.php">Privacy Policy:</A>
	Your privacy is important to us. This statement discloses the information practices for this web site, including what type of
	information is gathered and tracked, how the information is used, and with whom the information is shared.
	</li>
	<li><A href="logo_guidelines.php">Trademark Usage Guidelines:</A>
	Guidelines on permissable use of Eclipse logos and trademarks.
	</li>
	<li><A href="Trademark_Transfer_Agreement.pdf">Trademark Transfer Agreement:</A>
	Pre-existing projects which move to the Eclipse Foundation will be required to execute this agreement
	to ensure that the Eclipse Foundation has rights to any trademarks associated with the project name.
	</li>
	<li><A href="trademarkattributions.php">Trademark Attributions:</A>
	Content on this web site may make reference to trademarks requiring attribution.
	</li>
	</ul>
	</div>
	<div class="homeitem3col">
	<h3><a name="CommitterAgreements"></a>Committer Agreements</h3>
	<ul>
	<li><A href="committer_process/EclipseMemberCommitterAgreementFinal.pdf">Member Committer Agreement:</A>
	This agreement is used by Member companies to cover all of their committers participating in Eclipse projects.
	</li>
	<li><A href="committer_process/EclipseIndividualCommitterAgreementFinal.pdf">Individual Committer Agreement:</A>
	This agreement is used by committers participating in Eclipse projects who are not covered by a Member
	Committer Agreement.
	</li>
	<li><A href="committer_process/employer_consent.pdf">Employer Consent Form:</A>
	Committers covered by an Individual Committer Agreement must document the consent of their employer
	when participating in Eclipse projects.
	</li>

	</ul>
	</div>
	<div class="homeitem3col">
	<h3><a name="Committers"></a>Resources for Committers</h3>
	<ul>
	<li><A href="EclipseLegalProcessPoster.pdf">Due Diligence Process:</A>
	This document provides a quick pictorial overview of the due diligence process.
	</li>
	<li><A href="../org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf">Third Party Dependencies:</A>
	This document contains the guidelines for the review of third-party dependencies.
	</li>
	<li><A href="committerguidelines.php">Committer Guidelines:</A>
	This document outlines the issues to be aware of and the processes one should follow when working as a committer on Eclipse.org projects. A committer is a person
	that has been granted commit rights to systems on the Eclipse.org servers such as git repositories, web pages, download servers, mailing lists and so forth.
	</li>
	<li><A href="ContributionQuestionnairePart1-v1.0.php">Contribution Questionnaire:</A>
	Prior to committing a significant contribution of content to an Eclipse Foundation project, the committer must fill out this questionnaire and submit it to the Eclipse Management Organization (EMO) for approval. In addition to the EMO, the relevant PMC must also provide a technical review and approval of the contribution. Follow the link to find out more about what we mean by "significant contribution". Bug fixes or minor enhancements do not require PMC or EMO approval.
	</li>

	<li><A href="epl/about.php">"About" Templates:</A>
	This provides templates for the "about.html" ("About") files used to describe
	EPL-licensed content.
	</li>
	<li><A href="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>
	<li><A href="http://wiki.eclipse.org/Development_Resources/Automatic_IP_Log#Contributors">Using the IPLog+ Flag in Bugzilla:</A>
	There are two different ways to mark a contribution in bugzilla. If the contribution is an attachment to a bug such as a patch, the attachment itself should be marked with the iplog+ flag. If the contribution is in the form of a comment in the bug, then the iplog+ flag should be set on the bug itself.
	</li>
	<li><A href="/projects/dev_process/new-committer.php">New Committer Process:</A>
	The process for project leads and PMC members to add additional
	committers to an existing project.
	</li>
	<li><a href="http://live.eclipse.org/search/node/Janet+Campbell">Recorded IP Presentations</a>
	</li>
	</ul>
	</div>
	</div>
	<div id="rightcolumn">
	<div class="sideitem">
	<h6>Archives</h6>
	<ul>
	<li><a href="cpl2epl">CPL to EPL Conversion</a></li>
	</ul>
	</div>
	</div>


	EOHTML;

	# Generate the web page
	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
	?>