Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / llvm / e7bd7d686b23e32eec797ae80b38af2de2651f13 / . / docs / DeveloperPolicy.html
blob: b3f9d456972a744478bfc2be3c3c408e9bbe4496 [file] [log] [blame]
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
3<html>
4<head>
5 <title>LLVM Developer Policy</title>
6 <link rel="stylesheet" href="llvm.css" type="text/css">
7</head>
8<body>
Reid Spencerbb15b1c2007-02-13 09:09:20 +0000[diff] [blame]9 <div class="doc_warning">DRAFT Only. DRAFT Only. DRAFT Only. DRAFT Only.</div>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]10
11<div class="doc_title">LLVM Developer Policy</div>
12<table class="layout"><tr class="layout"><td class="layout">
13<h2>Contents</h2>
14<ol>
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]15 <li><a href="#introduction">Introduction</a></li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]16 <li><a href="#general">General Policies</a>
17 <ol>
18 <li><a href="#informed">Stay Informed</a> </li>
19 <li><a href="#newwork">Starting New Work</a></li>
20 <li><a href="#reviews">Code Reviews</a></li>
21 <li><a href="#incremental">Incremental Development</a></li>
22 <li><a href="#quality">Quality</a></li>
23 <li><a href="#testcases">Test Cases</a></li>
24 </ol></li>
25 <li><a href="#patches">Patch Policies</a>
26 <ol>
27 <li><a href="#p_form">Patch Form</a></li>
28 <li><a href="#p_testing">Patch Testing</a></li>
29 <li><a href="#p_submission">Patch Submission</a></li>
Reid Spencer0e598722007-02-14 17:20:59 +0000[diff] [blame]30 <li><a href="#p_aftersub">After Submission</a></li>
31 <li><a href="#p_aftercommit">After Commit</a></li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]32 <li><a href="#c_access">Obtaining Commit Access</a></li>
33 <li><a href="#c_new">New Committers</a></li>
34 </ol></li>
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]35 <li><a href="#candl">Copyright and License</a>
36 <ol>
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]37 <li><a href="#attribution">Attribution</a></li>
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]38 <li><a href="#copyright">Copyright</a></li>
39 <li><a href="#license">License</a></li>
40 <li><a href="#devagree">Developer Agreements</a></li>
41 </ol></li>
Reid Spencer0e598722007-02-14 17:20:59 +0000[diff] [blame]42 <li><a href="#terms">Terminology</a></li>
43 <li><a href="#polnotes">Policy Notes</a></li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]44</ol>
45<div class="doc_author">Written by LLVM Oversight Team</div>
46</td><td class="layout">
47
48<!--=========================================================================-->
Reid Spencere7bd7d62007-02-14 17:24:04 +0000[diff] [blame^]49<div class="doc_section"><a name="introduction">Introduction</a></div>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]50<!--=========================================================================-->
51<div class="doc_text">
52 <p>This document contains the LLVM Developer Policy which defines the
Reid Spencerbed92532007-02-13 17:04:09 +0000[diff] [blame]53 project's policy towards developers and their contributions. The intent of
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]54 this policy is to eliminate mis-communication, rework, and confusion that
55 might arise from the distributed nature of LLVM's development. By stating
56 the policy in clear terms, we hope each developer can know ahead of time
57 what to expect when making LLVM contributions.</p>
58</div>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]59
60<!--=========================================================================-->
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]61<div class="doc_section"><a name="general">General Policies</a></div>
62<!--=========================================================================-->
63<div class="doc_text">
64 <p>This section contains policies that pertain generally to LLVM developers.
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]65 LLVM Developers are expected to meet the following obligations in order
Reid Spencer25f9b9b2007-02-14 08:09:40 +0000[diff] [blame]66 for LLVM to maintain a high standard of quality.<p>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]67</div>
68
69<!-- _______________________________________________________________________ -->
70<div class="doc_subsection"> <a name="informed">Stay Informed</a> </div>
71<div class="doc_text">
72 <p>Developers should stay informed by reading at least the
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]73 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">llvmdev</a>
74 email list. If you are doing anything more than just casual work on LLVM,
75 it is suggested that you also subscribe to the
76 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">llvm-commits</a>
77 list and pay attention to changes being made by others.</p>
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]78 <p>We recommend that active developers register an email account with
79 <a href="http://llvm.org/bugs/">LLVM Bugzilla</a> and preferably subscribe to
80 the <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs">llvm-bugs</a>
81 email list to keep track of bugs and enhancements occurring in LLVM.</p>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]82</div>
83
84<!-- _______________________________________________________________________ -->
85<div class="doc_subsection"> <a name="newwork">Starting New Work</a></div>
86<div class="doc_text">
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]87 <p>When a developer begins a major new project with the aim of contributing
88 it back to LLVM, s/he should inform the community with an email to
89 the <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">llvm-dev</a>
90 email list, to the extent possible. The reason for this is to:
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]91 <ul>
92 <li>keep the community informed about future changes to LLVM, </li>
93 <li>avoid duplication of effort by having multiple parties working on the
94 same thing and not knowing about it, and</li>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]95 <li>ensure that any technical issues around the proposed work are
96 discussed and resolved before any significant work is done.</li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]97 </ul>
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]98 <p>The design of LLVM is carefully controlled to ensure that all the pieces
99 fit together well. If you plan to make a major change to the way LLVM works or
100 a major new extension, it is a good idea to get consensus with the development
101 community before you start working on it.</p>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]102</div>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]103</td></tr></table>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]104
105<!-- _______________________________________________________________________ -->
106<div class="doc_subsection"> <a name="reviews">Code Reviews</a></div>
107<div class="doc_text">
108 <p>LLVM has a code review policy. Code review is an excellent way to ensure
109 high quality in the software. The following policies apply:</p>
110 <ol>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]111 <li>All developers are required to have significant changes reviewed
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]112 before they are committed to the repository.</li>
113 <li>Code reviews are conducted by email.</li>
114 <li>Code can be reviewed either before it is committed or after.</li>
115 <li>The developer responsible for a code change is also responsible for
116 making all necessary review changes.</li>
117 <li>Developers should participate in code reviews as both a reviewer and
118 a reviewee. We don't have a dedicated team of reviewers. If someone is
119 kind enough to review your code, you should return the favor for someone
120 else.</li>
121 </ol>
122</div>
123
124<!-- _______________________________________________________________________ -->
125<div class="doc_subsection"> <a name="incremental">Incremental Development</a>
126</div>
127<div class="doc_text">
128 <p>LLVM uses an incremental development style and all developers are expected
129 to follow this practice. Incremental development is a big key to LLVM's
130 success and it is essential that developers submit incremental patches. The
131 following defines the incremental development approach:</p>
132 <ol>
133 <li>The first task is to define the increment and get consensus (with the
134 LLVM development community) on what the end goal of the change is. Making
135 random small changes that go nowhere is not useful for anyone.</li>
136 <li>An increment is the smallest patch size necessary to effect one change
137 in LLVM.</li>
138 <li>Increments can be stand alone (e.g. to fix a bug), or part of a planned
139 series of increments towards some development goal.</li>
140 <li>Increments should be kept as small as possible. This simplifies your
141 work (into a logical progression), simplifies code review and reduces the
142 chance that you will get negative feedback on the change. Small increments
143 also facilitate the maintenance of a high quality code base.</li>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]144 <li>Larger increments require a larger testing effort.</li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]145 </ol>
146</div>
147
148<!-- _______________________________________________________________________ -->
149<div class="doc_subsection"> <a name="quality">Quality</a></div>
150<div class="doc_text">
151 <p>The minimum quality standards for any change to the main development
152 branch are:</p>
153 <ol>
154 <li>Code must adhere to the
155 <a href="CodingStandards.html">LLVM Coding Standards</a>.</li>
156 <li>Code must compile cleanly (no errors, no warnings) on at least one
157 platform.</li>
158 <li>Code must pass the deja gnu (llvm/test) test suite.</li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]159 </ol>
Reid Spencerf1491da2007-02-14 08:19:16 +0000[diff] [blame]160 <p>Additionally, the committer is responsible for addressing all of the
161 following items (preferably before submission):</p>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]162 <ol>
Reid Spencerf1491da2007-02-14 08:19:16 +0000[diff] [blame]163 <li>The code should compile cleanly on all platforms.</li>
164 <li>The changes should not cause regressions in the <tt>llvm-test</tt>
165 suite including SPEC CINT2000, SPEC CFP2000, SPEC CINT2006, and
166 SPEC CFP2006.</li>
167 <li>The change set should not cause performance or correctness regressions
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]168 for the LLVM tools.</li>
Reid Spencerf1491da2007-02-14 08:19:16 +0000[diff] [blame]169 <li>The changes should not cause performance or correctness regressions in
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]170 code compiled by LLVM on all applicable targets.</li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]171 </ol>
172</div>
173
174<!-- _______________________________________________________________________ -->
175<div class="doc_subsection"> <a name="testcases">Test Cases</a></div>
176<div class="doc_text">
177 <p>Developers are required to create test cases for regressions and new
178 features and include them with their changes. The following policies
179 apply:</p>
180 <ol>
181 <li>All feature and regression test cases must be added to the
Reid Spencer80483bb2007-02-13 09:20:14 +0000[diff] [blame]182 <tt>llvm/test</tt> directory. The appropriate sub-directory should be
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]183 selected (see the <a href="TestingGuide.html">Testing Guide</a> for
Reid Spencer40602962007-02-13 20:57:57 +0000[diff] [blame]184 details).</li>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]185 <li>Test cases should be written in
186 <a href="LangRef.html">LLVM assembly language</a> unless the
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]187 feature or regression being tested requires another language (e.g. the
Reid Spencerf1491da2007-02-14 08:19:16 +0000[diff] [blame]188 bug being fixed or feature being implemented is in the lvm-gcc C++
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]189 front-end).</li>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]190 <li>Test cases, especially for regressions, should be reduced as much as
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]191 possible, by <a href="CommandGuide/html/bugpoint.html">bugpoint</a> or
192 manually. It is unacceptable
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]193 to place an entire failing program into <tt>llvm/test</tt> as this creates
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]194 a <i>time-to-test</i> burden on all developers. Please keep them short.</li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]195 <li>More extensive test cases (applications, benchmarks, etc.) should be
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]196 added to the <tt>llvm-test</tt> test suite. This test suite is for
197 coverage not features or regressions.</li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]198 </ol>
199</div>
200
201<!--=========================================================================-->
202<div class="doc_section"><a name="patches">Patch Policies</a></div>
203<!--=========================================================================-->
204<div class="doc_text">
205 <p>This section contains policies that pertain to submitting patches
206 to LLVM and committing code to the repository</p>
207</div>
208<!-- _______________________________________________________________________ -->
209<div class="doc_subsection"> <a name="p_form">Patch Form</a></div>
210<div class="doc_text">
211 <p>When submitting a patch, developers must follow these rules:</p>
212 <ol>
213 <li>Patches must be made against the CVS HEAD (main development trunk),
214 not a branch.</li>
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]215 <li>Patches should be made with this command:<pre>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]216 cvs diff -Ntdup -5</pre> or with the utility <tt>utils/mkpatch</tt>.</li>
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]217 <li>Patches should not include differences in generated code such as the
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]218 code generated by <tt>flex</tt>, <tt>bison</tt> or <tt>tblgen</tt>. The
219 <tt>utils/mkpatch</tt> utility takes care of this for you.</li>
220 </ol>
221</div>
222<!-- _______________________________________________________________________ -->
223<div class="doc_subsection"> <a name="p_testing">Patch Testing</a></div>
224<div class="doc_text">
225 <p>Before a patch is submitted for review, it should be tested to ensure
226 that:</p>
227 <ol>
228 <li>The patch must compile against the CVS HEAD cleanly (zero warnings, zero
229 errors).</li>
230 <li>All the llvm/test (Deja Gnu) tests must pass.</li>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]231 <li>The patch should cause no regressions in the llvm-test test suite. How
232 much testing is appropriate depends on the nature of the patch. We leave it
233 to your good judgement, but you will be responsible for fixing any
234 regressions or reverting the patch.</li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]235 </ol>
236</div>
237<!-- _______________________________________________________________________ -->
238<div class="doc_subsection"> <a name="p_submission">Patch Submission</a></div>
239<div class="doc_text">
240 <p>When a patch is ready to be submitted, these policies apply:</p>
241 <ol>
242 <li>Patches should be submitted immediately after they are generated. Stale
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]243 patches may not apply correctly if the underlying code changes between the
244 time the patch was created and the time it is applied.</li>
245 <li>Patches should be submitted by e-mail to the
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]246 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">
247 llvm-commits</a> list.</li>
248 </ol>
249</div>
250
251<!-- _______________________________________________________________________ -->
Reid Spencer0e598722007-02-14 17:20:59 +0000[diff] [blame]252<div class="doc_subsection"> <a name="p_aftersub">After Submission</a></div>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]253<div class="doc_text">
254 <p>After a patch has been submitted, these policies apply:</p>
255 <ol>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]256 <li>The patch is subject to review by anyone on the
257 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">llvm-commits</a>
258 email list.</li>
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]259 <li>Changes recommended by a reviewer should be incorporated into your
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]260 patch or you should explain why the reviewer is incorrect.
261 <li>Changes to the patch must be re-submitted to the
262 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">llvm-commits</a>
263 email list.</li>
264 <li>This process iterates until all review issues have been addressed.</li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]265 </ol>
266</div>
267
268<!-- _______________________________________________________________________ -->
Reid Spencer0e598722007-02-14 17:20:59 +0000[diff] [blame]269<div class="doc_subsection"> <a name="p_aftercommit">After Commit</a></div>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]270<div class="doc_text">
271 <p>After a patch has been committed, these policies apply:</p>
272 <ol>
273 <li>The patch is subject to further review by anyone on the llvm-commits
274 email list.</li>
275 <li>The patch submitter is responsible for all aspects of the patch per
276 the <a href="quality">quality policy</a> above.</li>
277 <li>If the patch is discovered to not meet the
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]278 <a href="quality">quality policy</a> standards within a reasonable time
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]279 frame (24 hours), it may be subject to reversal.</li>
280 </ol>
281</div>
282
283<!-- _______________________________________________________________________ -->
Reid Spencere7bd7d62007-02-14 17:24:04 +0000[diff] [blame^]284<div class="doc_subsection"> <a name="c_access">Obtaining Commit Access</a></div>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]285<div class="doc_text">
286 <p>Commit access to the repository is granted according to this policy:</p>
287 <ol>
288 <li>Commit access is not granted to anyone unless they specifically ask for
289 it.</li>
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]290 <li>Requests for commit access must be sent to the
291 <a href="mailto:llvm-oversight@cs.uiuc.edu">LLVM Oversight Group</a>.</li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]292 <li>Granting commit access is at the sole discretion of the LLVM Oversight
293 Group.</li>
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]294 </ol>
295 <p>Submitting patches to LLVM via the patch policy above will greatly
296 increase the chance that your request for commit access is granted. Getting
297 to know the members of the LLVM community (email, IRC, in person contact,
298 etc.) will also increase your chances.</p>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]299 </ol>
300</div>
301
302<!-- _______________________________________________________________________ -->
303<div class="doc_subsection"> <a name="c_new">New Committers</a></div>
304<div class="doc_text">
305 <p>For those who have recently obtained commit access, the following policies
306 apply:</p>
307 <ol>
308 <li>You are granted <i>commit-after-approval</i> to all parts of LLVM.
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]309 To get approval, submit a patch to
310 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">llvm-commits</a>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]311 per the <a href="#patches">patch policies</a> above. When approved you
312 may commit it yourself.</li>
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]313 <li>You are allowed to commit patches without approval which you think are
314 obvious. This is clearly a subjective decision. We simply expect you to
315 use good judgement.</li>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]316 <li>You are allowed to commit patches without approval to those portions
317 of LLVM that you own (contributed) or maintain (have been assigned
318 responsibility for), with the proviso that such commits must not break the
319 build. This is a "trust but verify" policy and commits of this nature are
320 reviewed after they are committed.</li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]321 <li>Commits that violate the <a href="quality">quality standards</a> may
322 be reverted. This is necessary when the change blocks other developers from
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]323 making progress. The developer is welcome to re-commit the change after
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]324 the problem has been fixed.</li>
Reid Spencer80483bb2007-02-13 09:20:14 +0000[diff] [blame]325 <li>Multiple violations of these policies or a single egregious violation
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]326 may cause commit access to be revoked.</li>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]327 </ol>
328</div>
329
330<!--=========================================================================-->
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]331<div class="doc_section"><a name="candl">Copyright and License</a></div>
332<!--=========================================================================-->
333<div class="doc_text">
334 <p>We address here the issues of copyright and license for the LLVM project.
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]335 The object of the copyright and license is the LLVM source code and
336 documentation.
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]337 Currently, the University of Illinois is the LLVM copyright holder and the
338 terms of its license to LLVM users and developers is the
339 <a href="http://www.opensource.org/licenses/UoI-NCSA.php">University of
340 Illinois/NCSA Open Source License</a>.
341</div>
342
343<div class="doc_notes">
344 <p>NOTE: This section deals with legal matters but does not provide legal
Reid Spencer134400b2007-02-14 16:21:54 +0000[diff] [blame]345 advice. It is intended only as a general guideline.</p>
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]346</div>
347
348<!-- _______________________________________________________________________ -->
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]349<div class="doc_subsection"><a name="attribution">Attribution</a></div>
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]350<div class="doc_text">
351 <p>The LLVM project believes in correct attribution of contributions to
352 their contributors, as follows:</p>
353 <ol>
354 <li>Developers who originate new files in LLVM should place their name at
355 the top of the file per the
356 <a href="CodingStandards.html">Coding Standards</a>.</li>
357 <li>There should be only one name at the top of the file and it should be
358 the person who created the file.</li>
359 <li>Placing your name in the file does not imply copyright but does
360 correctly attribute the file to its author.</li>
361 <li>Developers should be aware that after some time has passed, the name at
362 the top of a file may become meaningless as maintenance/ownership of files
363 changes.</li>
364 <li>Developers should submit or commit patches to the
365 <a href="http://llvm.org/cvsweb/cvsweb.cgi/llvm/CREDITS.TXT?rev=1.67&content-type=text/x-cvsweb-markup">CREDITS.txt</a>
366 file to summarize their contributions.</li>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]367 <li>Commit comments should contain correct attribution of the person who
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]368 submitted the patch if that person is not the committer (i.e. when a
369 developer with commit privileges commits a patch for someone else).</li>
370 </ol>
371</div>
372
373<!-- _______________________________________________________________________ -->
374<div class="doc_subsection"><a name="copyright">Copyright</a></div>
375<div class="doc_text">
376 <p>
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]377 <p>For consistency and ease of management, the project requires the
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]378 copyright for all LLVM software to be held by a single copyright holder.
379 Although UIUC may assign the copyright of the software to another entity,
380 the intent for the project is to always have a single entity hold the copy
381 rights to LLVM at any given time.
382 <p>Having multiple copyright holders for various portions of LLVM is
383 problematic in the management of the software. Having a single copyright
384 holder is in the best interests of all developers and users as it greatly
385 reduces the managerial burden for any kind of administrative or technical
386 decisions about LLVM.</p>
387</div>
388<!-- _______________________________________________________________________ -->
389<div class="doc_subsection"><a name="license">License</a></div>
390<div class="doc_text">
391 <p>LLVM licensing decisions will be made by the LLVM Oversight Group. Any
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]392 issues, comments or suggestions with the licensing should be sent to the
393 <a href="mailto:llvm-oversight@cs.uiuc.edu">LLVM Oversight Group</a>.</p>
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]394 <p>The LLVM Oversight Group intends to keep LLVM perpetually open source
395 and to use liberal open source licenses. The current license is the
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]396 <a href="http://www.opensource.org/licenses/UoI-NCSA.php">
397 University of Illinois/NCSA Open Source License</a>, which boils
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]398 down to this:</p>
399 <ul>
400 <li>You can freely distribute LLVM.</li>
401 <li>You must retain the copyright notice if you redistribute LLVM.</li>
402 <li>Binaries derived from LLVM must reproduce the copyright notice.</li>
403 <li>You can't use our names to promote your LLVM derived products.</li>
404 <li>There's no warranty on LLVM at all.</li>
405 </ul>
406 <p>We believe this fosters the widest adoption of LLVM because it allows
407 commercial products to be derived from LLVM with few restrictions and
408 without a requirement for making any derived works also open source. We
409 suggest that you read the
410 <a href="http://www.opensource.org/licenses/UoI-NCSA.php">License</a> if
411 further clarification is needed.</p>
412</div>
413<!-- _______________________________________________________________________ -->
414<div class="doc_subsection"><a name="devagree">Developer Agreements</a></div>
415<div class="doc_text">
416 <p>With regards to the LLVM copyright and licensing, developers agree to:</p>
417 <ul>
418 <li>assign their copy rights to UIUC for any contribution made so that
419 the entire software base can be managed by a single copyright holder.</li>
420 <li>allow their contribution(s) to be licensed as open source by the then
421 current license chosen by the LLVM Oversight Group.</li>
Reid Spencer78bade22007-02-14 07:22:19 +0000[diff] [blame]422 </ul>
423</div>
424
425<!--=========================================================================-->
Reid Spencer01f56be2007-02-14 16:21:10 +0000[diff] [blame]426<div class="doc_section"><a name="terms">Terminology</a></div>
427<!--=========================================================================-->
428<div class="doc_text">
429 <p>So that the policies defined in this document are clear, we define some
430 terms here.</p>
431 <dl>
432 <dt><a name="t_change">Change</a></dt>
433 <dd>Any modification to LLVM including documentation, tests, build system,
434 etc. either in <a href="#t_patch">patch</a> or
435 <a href="#t_commit">commit</a> form.</dd>
436 <dt><a name="t_commit">Commit</a><dt>
437 <dd>A <a href="t_change">change</a> submitted directly to LLVM software
438 repository via the <tt>cvs commit</tt> command.</dd>
439 <dt><a name="t_developer">Developer</a></dt>
440 <dd>Anyone who submits a <a href="#t_change">change</a> to LLVM.</dd>
441 <dt><a name="t_inrement">Increment</a></dt>
442 <dd>A <a href="#t_change">change</a> or set of changes, whether by
443 <a href="#t_patch">patch</a> or <a href="#t_commit">commit</a>, that are
444 related by a single common purpose. Increments are atomic as they
445 leave LLVM in a stable state (both compiling and working properly).</dd>
446 <dt><a name="t_must">Must</a></dt>
447 <dd>When used in a policy statement, the term <i>must</i> implies a
448 non-optional requirement on the developer.</dd>
449 <dt><a name="t_patch">Patch</a></dt>
450 <dd>A <a href="#t_change">change</a> submitted by email in patch (diff)
451 format generated by the <tt>cvs diff</tt> command.</dd>
452 <dt><a name="t_should">Should</a></dt>
453 <dd>When used in a policy statement, the term <i>should</i> implies a
454 recommended but optional requirement on the developer.</dd>
455 </dl>
456</div>
457
458<!--=========================================================================-->
Reid Spencer0e598722007-02-14 17:20:59 +0000[diff] [blame]459<div class="doc_section"><a name="polnotes">Policy Notes</a></div>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]460<!--=========================================================================-->
461<div class="doc_text">
462 <p>This section contains some notes on policy topics that need to be
463 resolved and incorporated into the main body of the document above.</p>
464 <ol>
465 <li>When to open a new bug and when to re-use an existing one. For example
466 PR1158. If the same assertion happens do you open a new bug or reopen
467 1158?</li>
468 </ol>
469</div>
470
471<!-- *********************************************************************** -->
472<hr>
473<address>
474 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
475 src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!"></a>
476 <a href="http://validator.w3.org/check/referer"><img
477 src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01!" /></a>
Reid Spencer3eedbd32007-02-14 07:57:48 +0000[diff] [blame]478 Written By: the
479 <a href="mailto:llvm-oversight@cs.uiuc.edu">LLVM Oversight Group</a><br>
Reid Spencer8d0ac692007-02-13 09:06:01 +0000[diff] [blame]480 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
481 Last modified: $Date$
482</address>
483</body>
484</html>