[522002] Construct an EPL-2.0 FAQ

2 files changed, 87 insertions, 0 deletions

diff --git a/documents/epl-2.0/_projectCommon.php b/documents/epl-2.0/_projectCommon.php
index 17dcd5a3..882a0f51 100644
--- a/documents/epl-2.0/_projectCommon.php
+++ b/documents/epl-2.0/_projectCommon.php
@@ -13,6 +13,7 @@
   $Nav->addCustomNav("Plain HTML", "/org/documents/epl-2.0/EPL-2.0.html", "_self", 1);
   $Nav->addCustomNav("Plain Text", "/org/documents/epl-2.0/EPL-2.0.txt", "_self", 1);
   $Nav->addCustomNav("PDF", "/org/documents/epl-2.0/EPL-2.0.pdf", "_self", 1);
+  $Nav->addCustomNav("FAQ", "/org/documents/epl-2.0/faq.php", "_self", 1);
   
   $Nav->addNavSeparator("EPL-1.0",   "/org/documents/epl-v10.php");
   $Nav->addCustomNav("Plain HTML", "/org/documents/epl-v10.html", "_self", 1);
diff --git a/documents/epl-2.0/faq.php b/documents/epl-2.0/faq.php
new file mode 100644
index 00000000..b9c66473
--- /dev/null
+++ b/documents/epl-2.0/faq.php
@@ -0,0 +1,86 @@
+<?php
+/**************************************************************************
+ * Copyright (c) 2017 Eclipse Foundation and others.
+ *
+ * This program and the accompanying materials are made available
+ * under the terms of the Eclipse Public License 2.0 which accompanies
+ * this distribution, and is available at http://eclipse.org/legal/epl-2.0
+ **************************************************************************/
+$common = dirname(__FILE__) . "/../../../eclipse.org-common";
+require_once ("$common/system/app.class.php");
+require_once ("$common/system/nav.class.php");
+require_once ("$common/system/menu.class.php");
+
+$App = new App();
+$Menu = new Menu();
+$Nav = new Nav();
+
+$root = dirname(__FILE__);
+
+include ("$root/_projectCommon.php");
+
+$pageTitle = "Eclipse Public License 2.0 FAQ";
+$pageAuthor = "Wayne Beaton";
+
+ob_start();
+?>
+<div id="maincontent">
+	<div id="midcolumn">
+
+		<h1><?= $pageTitle ?></h1>
+
+		<p>
+			<strong>For informational purposes only.</strong>
+		</p>
+		<p>
+			This FAQ attempts to provide answers to commonly asked questions
+			related to the <a href="/legal/epl-2.0">Eclipse Public License</a>
+			(EPL). It is provided for informational purposes only. It is not part
+			of, nor does it modify, amend, or supplement the terms of the EPL.
+			The EPL is a legal agreement that governs the rights granted to
+			material licensed under it, so please read it carefully. If there is
+			any conflict between this FAQ and the EPL, the terms of the EPL shall
+			govern.
+		</p>
+		<p>
+			<em>This FAQ should not be regarded as legal advice. If you need
+				legal advice, you must contact your own lawyer.</em>
+		</p>
+
+		<h3>This document does not have the answer to my question. How can I
+			get my question answered?</h3>
+		<p>
+			You may want to check the <a href="/legal/legalfaq.php">Eclipse
+				Foundation Legal Frequently Asked Questions</a> document to see if
+			your question is answered there. If not, please send a note to <a
+				href="mailto:license@eclipse.org">license@eclipse.org</a>.
+		</p>
+
+		<h3>Why did the Eclipse Foundation create a new version of the EPL?</h3>
+		<p>The Eclipse Public License 1.0 is very close to the Common Public
+			License, and as such its terms are essentially 16 years old. A lot of
+			the motivation was to simply update the license to reflect the norms
+			and expectations of an industry that has changed a lot in that time.</p>
+
+
+		<h3>My project uses the EPL-1.0. How can we switch to use EPL-2.0?</h3>
+		<p>The Eclipse Public License allows new versions of the license to be
+			adopted by projects with little work. Specifically, the license
+			states that:</p>
+		<blockquote>&ldquo;Each new version of the Agreement will be given a
+			distinguishing version number. The Program (including Contributions)
+			may always be distributed subject to the version of the Agreement
+			under which it was received. In addition, after a new version of the
+			Agreement is published, Contributor may elect to distribute the
+			Program (including its Contributions) under the new version.&rdquo;</blockquote>
+		<p>So a project can use the new version by simply updating the file
+			headers and notices. Note that it would be good community practice to
+			discuss this change on your public mailing lists, and to make every
+			attempt to ensure that downstream users are aware of the change.</p>
+
+	</div>
+</div>
+<?php
+$html = ob_get_contents();
+ob_end_clean();
+$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);