-</div>
-<!--=========================================================================-->
-<div class="doc_section"><a name="terms">Terminology</a></div>
-<!--=========================================================================-->
-<div class="doc_text">
- <p>So that the policies defined in the next sections are clear, we first
- define some terms here.</p>
- <dl>
- <dt><a name="t_change">Change</a></dt>
- <dd>Any modification to LLVM including documentation, tests, build system,
- etc. either in <a href="#t_patch">patch</a> or
- <a href="#t_commit">commit</a> form.</dd>
- <dt><a name="t_commit">Commit</a><dt>
- <dd>A <a href="t_change">change</a> submitted directly to LLVM software
- respository via the <tt>cvs commit</tt> command.</dd>
- <dt><a name="t_developer">Developer</a></dt>
- <dd>Anyone who submits a <a href="#t_change">change</a> to LLVM.</dd>
- <dt><a name="t_inrement">Increment</a></dt>
- <dd>A <a href="#t_change">change</a> or set of changes, whether by
- <a href="#t_patch">patch</a> or <a href="#t_commit">commit</a>, that are
- related by a single common purpose. Increments are atomic as they
- leave LLVM in a stable state (both compiling and working properly).</dd>
- <dt><a name="t_must">Must</a></dt>
- <dd>When used in a policy statement, the term <i>must</i> implies a
- non-optional requirement on the developer.</dd>
- <dt><a name="t_patch">Patch</a></dt>
- <dd>A <a href="#t_change">change</a> submitted by email in patch (diff)
- format generated by the <tt>cvs diff</tt> command.</dd>
- <dt><a name="t_should">Should</a></dt>
- <dd>When used in a policy statement, the term <i>should</i> implies a
- recommended but optional requirement on the developer.</dd>
- </dl>
-</div>
-
-</td></tr></table>
-
-<!--=========================================================================-->
-<div class="doc_section"><a name="candl">Copyright and License</a></div>
-<!--=========================================================================-->
-<div class="doc_text">
- <p>We address here the issues of copyright and license for the LLVM project.
- A copyright is literally the "right to copy". It is a set of exclusive rights
- granted to a party regulating the particular expression of information.
- In this case, the information is LLVM. A license is something granted by a
- copyright holder to other parties that controls the use of the information
- by them. Currently, the University of Illinois is the LLVM copyright holder
- and the terms of its license to LLVM users and developers is the
- University of Illinois Open Source License (see LICENSE.txt).</p>
-</div>
-<!-- _______________________________________________________________________ -->
-<div class="doc_subsection"><a name="copyright">Copyright</a></div>
-<div class="doc_text">
- <p>The LLVM project believes in correct attribution of contributions to
- their contributors. Developers should, therefore, place their name at the
- top of any source file they originate and list their contributions in the
- CREDITS.TXT file. Furthermore, correct attribution of submitted patches
- should be made in the commit comments.</p>
- <p>However, for consistency and ease of management, the project requires the
- copyright for all LLVM software to be held by a single copyright holder.
- Although UIUC may assign the copyright of the software to another entity,
- the intent for the project is to always have a single entity hold the copy
- rights to LLVM at any given time.
- <p>Having multiple copyright holders for various portions of LLVM is
- problematic in the management of the software. Having a single copyright
- holder is in the best interests of all developers and users as it greatly
- reduces the managerial burden for any kind of administrative or technical
- decisions about LLVM.</p>
-</div>
-<!-- _______________________________________________________________________ -->
-<div class="doc_subsection"><a name="license">License</a></div>
-<div class="doc_text">
- <p>LLVM licensing decisions will be made by the LLVM Oversight Group. Any
- issues, comments or suggestions with the licensing should be sent to
- <a href="mailto:oversight@llvm.org">oversight@llvm.org</a>.</p>
- <p>The LLVM Oversight Group intends to keep LLVM perpetually open source
- and to use liberal open source licenses. The current license is the
- University of Illinois Open Source License (see LICENSE.TXT), which boils
- down to this:</p>
- <ul>
- <li>You can freely distribute LLVM.</li>
- <li>You must retain the copyright notice if you redistribute.</li>
- <li>Binaries derived from LLVM must reproduce the copyright notice.</li>
- <li>You can't use our names to promote your LLVM derived products.</li>
- <li>There's no warranty on LLVM at all.</li>
- </ul>
- <p>We believe this fosters the widest adoption of LLVM because it allows
- commercial products to be derived from LLVM with few restrictions and
- without a requirement for making any derived works also open source. The
- intent of the license is to let people use LLVM freely with only the
- obligation to be honest about where it came from.</p>
-</div>
-<!-- _______________________________________________________________________ -->
-<div class="doc_subsection"><a name="devagree">Developer Agreements</a></div>
-<div class="doc_text">
- <p>With regards to the LLVM copyright and licensing, developer's agree to:</p>
- <ul>
- <li>give up their copy rights to any contribution made so that the entire
- software base can be managed by a single copyright holder.</li>
- <li>allow their contribution(s) to be licensed as open source by the then
- current or subsequent license chosen by the LLVM Oversight Group.</li>
- <li>not make LLVM available under any other licensing agreement.</li>
- </ul>