xref: /JGit/org.eclipse.jgit.packaging/org.eclipse.jgit.source.feature/license.html (revision 84db92bb67caf4fabfc5a1281a49c6f41d96fafa)
1<?xml version="1.0" encoding="ISO-8859-1" ?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml">
4<head>
5<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
6<title>Eclipse Foundation Software User Agreement</title>
7</head>
8<body lang="EN-US">
9	<h2>Eclipse Foundation Software User Agreement</h2>
10	<p>November 22, 2017</p>
11	<h3>Usage Of Content</h3>
12	<p>THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION,
13		INFORMATION AND/OR OTHER MATERIALS FOR OPEN SOURCE PROJECTS
14		(COLLECTIVELY &quot;CONTENT&quot;). USE OF THE CONTENT IS GOVERNED BY
15		THE TERMS AND CONDITIONS OF THIS AGREEMENT AND/OR THE TERMS AND
16		CONDITIONS OF LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED
17		BELOW. BY USING THE CONTENT, YOU AGREE THAT YOUR USE OF THE CONTENT IS
18		GOVERNED BY THIS AGREEMENT AND/OR THE TERMS AND CONDITIONS OF ANY
19		APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED
20		BELOW. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS
21		AGREEMENT AND THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE
22		AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW, THEN YOU MAY NOT
23		USE THE CONTENT.</p>
24	<h3>Applicable Licenses</h3>
25	<p>
26		Unless otherwise indicated, all Content made available by the Eclipse
27		Foundation is provided to you under the terms and conditions of the
28		Eclipse Public License Version 2.0 (&quot;EPL&quot;). A copy of the
29		EPL is provided with this Content and is also available at <a
30			href="http://www.eclipse.org/legal/epl-2.0">http://www.eclipse.org/legal/epl-2.0</a>.
31		For purposes of the EPL, &quot;Program&quot; will mean the Content.
32	</p>
33	<p>Content includes, but is not limited to, source code, object
34		code, documentation and other files maintained in the Eclipse
35		Foundation source code repository (&quot;Repository&quot;) in software
36		modules (&quot;Modules&quot;) and made available as downloadable
37		archives (&quot;Downloads&quot;).</p>
38	<ul>
39		<li>Content may be structured and packaged into modules to
40			facilitate delivering, extending, and upgrading the Content. Typical
41			modules may include plug-ins (&quot;Plug-ins&quot;), plug-in
42			fragments (&quot;Fragments&quot;), and features
43			(&quot;Features&quot;).</li>
44		<li>Each Plug-in or Fragment may be packaged as a sub-directory
45			or JAR (Java&trade; ARchive) in a directory named
46			&quot;plugins&quot;.</li>
47		<li>A Feature is a bundle of one or more Plug-ins and/or
48			Fragments and associated material. Each Feature may be packaged as a
49			sub-directory in a directory named &quot;features&quot;. Within a
50			Feature, files named &quot;feature.xml&quot; may contain a list of
51			the names and version numbers of the Plug-ins and/or Fragments
52			associated with that Feature.</li>
53		<li>Features may also include other Features (&quot;Included
54			Features&quot;). Within a Feature, files named
55			&quot;feature.xml&quot; may contain a list of the names and version
56			numbers of Included Features.</li>
57	</ul>
58	<p>The terms and conditions governing Plug-ins and Fragments should
59		be contained in files named &quot;about.html&quot;
60		(&quot;Abouts&quot;). The terms and conditions governing Features and
61		Included Features should be contained in files named
62		&quot;license.html&quot; (&quot;Feature Licenses&quot;). Abouts and
63		Feature Licenses may be located in any directory of a Download or
64		Module including, but not limited to the following locations:</p>
65	<ul>
66		<li>The top-level (root) directory</li>
67		<li>Plug-in and Fragment directories</li>
68		<li>Inside Plug-ins and Fragments packaged as JARs</li>
69		<li>Sub-directories of the directory named &quot;src&quot; of
70			certain Plug-ins</li>
71		<li>Feature directories</li>
72	</ul>
73	<p>Note: if a Feature made available by the Eclipse Foundation is
74		installed using the Provisioning Technology (as defined below), you
75		must agree to a license (&quot;Feature Update License&quot;) during
76		the installation process. If the Feature contains Included Features,
77		the Feature Update License should either provide you with the terms
78		and conditions governing the Included Features or inform you where you
79		can locate them. Feature Update Licenses may be found in the
80		&quot;license&quot; property of files named
81		&quot;feature.properties&quot; found within a Feature. Such Abouts,
82		Feature Licenses, and Feature Update Licenses contain the terms and
83		conditions (or references to such terms and conditions) that govern
84		your use of the associated Content in that directory.</p>
85	<p>THE ABOUTS, FEATURE LICENSES, AND FEATURE UPDATE LICENSES MAY
86		REFER TO THE EPL OR OTHER LICENSE AGREEMENTS, NOTICES OR TERMS AND
87		CONDITIONS. SOME OF THESE OTHER LICENSE AGREEMENTS MAY INCLUDE (BUT
88		ARE NOT LIMITED TO):</p>
89	<ul>
90		<li>Eclipse Public License Version 1.0 (available at <a
91			href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>)
92		</li>
93		<li>Eclipse Distribution License Version 1.0 (available at <a
94			href="http://www.eclipse.org/licenses/edl-v10.html">http://www.eclipse.org/licenses/edl-v1.0.html</a>)
95		</li>
96		<li>Common Public License Version 1.0 (available at <a
97			href="http://www.eclipse.org/legal/cpl-v10.html">http://www.eclipse.org/legal/cpl-v10.html</a>)
98		</li>
99		<li>Apache Software License 1.1 (available at <a
100			href="http://www.apache.org/licenses/LICENSE">http://www.apache.org/licenses/LICENSE</a>)
101		</li>
102		<li>Apache Software License 2.0 (available at <a
103			href="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</a>)
104		</li>
105		<li>Mozilla Public License Version 1.1 (available at <a
106			href="http://www.mozilla.org/MPL/MPL-1.1.html">http://www.mozilla.org/MPL/MPL-1.1.html</a>)
107		</li>
108	</ul>
109	<p>IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND
110		CONDITIONS PRIOR TO USE OF THE CONTENT. If no About, Feature License,
111		or Feature Update License is provided, please contact the Eclipse
112		Foundation to determine what terms and conditions govern that
113		particular Content.</p>
114	<h3>Use of Provisioning Technology</h3>
115	<p>
116		The Eclipse Foundation makes available provisioning software, examples
117		of which include, but are not limited to, p2 and the Eclipse Update
118		Manager (&quot;Provisioning Technology&quot;) for the purpose of
119		allowing users to install software, documentation, information and/or
120		other materials (collectively &quot;Installable Software&quot;). This
121		capability is provided with the intent of allowing such users to
122		install, extend and update Eclipse-based products. Information about
123		packaging Installable Software is available at <a
124			href="http://eclipse.org/equinox/p2/repository_packaging.html">http://eclipse.org/equinox/p2/repository_packaging.html</a>
125		(&quot;Specification&quot;).
126	</p>
127	<p>You may use Provisioning Technology to allow other parties to
128		install Installable Software. You shall be responsible for enabling
129		the applicable license agreements relating to the Installable Software
130		to be presented to, and accepted by, the users of the Provisioning
131		Technology in accordance with the Specification. By using Provisioning
132		Technology in such a manner and making it available in accordance with
133		the Specification, you further acknowledge your agreement to, and the
134		acquisition of all necessary rights to permit the following:</p>
135	<ol>
136		<li>A series of actions may occur (&quot;Provisioning
137			Process&quot;) in which a user may execute the Provisioning
138			Technology on a machine (&quot;Target Machine&quot;) with the intent
139			of installing, extending or updating the functionality of an
140			Eclipse-based product.</li>
141		<li>During the Provisioning Process, the Provisioning Technology
142			may cause third party Installable Software or a portion thereof to be
143			accessed and copied to the Target Machine.</li>
144		<li>Pursuant to the Specification, you will provide to the user
145			the terms and conditions that govern the use of the Installable
146			Software (&quot;Installable Software Agreement&quot;) and such
147			Installable Software Agreement shall be accessed from the Target
148			Machine in accordance with the Specification. Such Installable
149			Software Agreement must inform the user of the terms and conditions
150			that govern the Installable Software and must solicit acceptance by
151			the end user in the manner prescribed in such Installable Software
152			Agreement. Upon such indication of agreement by the user, the
153			provisioning Technology will complete installation of the Installable
154			Software.</li>
155	</ol>
156	<h3>Cryptography</h3>
157	<p>Content may contain encryption software. The country in which
158		you are currently may have restrictions on the import, possession, and
159		use, and/or re-export to another country, of encryption software.
160		BEFORE using any encryption software, please check the country's laws,
161		regulations and policies concerning the import, possession, or use,
162		and re-export of encryption software, to see if this is permitted.</p>
163	<p>
164		<small>Java and all Java-based trademarks are trademarks of
165			Oracle Corporation in the United States, other countries, or both.</small>
166	</p>
167</body>
168</html>