Gitiles
Code Review Sign In
gerrit-public.fairphone.software / toolchain / llvm-project / 42670d8b24714b6a7ffd3f7f798d00b86f9ed8e8 / . / llvm / docs / DeveloperPolicy.html
blob: 9c8b4d666b8d64137f0cf6829942f29cfa48800d [file] [log] [blame]
Reid Spencera0f02a32007-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>
Bill Wendlingd231f8a2009-04-05 12:38:44 +0000[diff] [blame]5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]6 <title>LLVM Developer Policy</title>
7 <link rel="stylesheet" href="llvm.css" type="text/css">
8</head>
9<body>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]10
11<div class="doc_title">LLVM Developer Policy</div>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]12<ol>
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]13 <li><a href="#introduction">Introduction</a></li>
Chris Lattner76fa27f2007-02-19 06:05:58 +0000[diff] [blame]14 <li><a href="#policies">Developer Policies</a>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]15 <ol>
Chris Lattnera3338192007-02-19 05:57:29 +0000[diff] [blame]16 <li><a href="#informed">Stay Informed</a></li>
17 <li><a href="#patches">Making a Patch</a></li>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]18 <li><a href="#reviews">Code Reviews</a></li>
Chris Lattnerb39e02b2007-12-03 19:00:47 +0000[diff] [blame]19 <li><a href="#owners">Code Owners</a></li>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]20 <li><a href="#testcases">Test Cases</a></li>
Chris Lattner10f15142007-02-19 05:49:11 +0000[diff] [blame]21 <li><a href="#quality">Quality</a></li>
22 <li><a href="#commitaccess">Obtaining Commit Access</a></li>
Chris Lattner76fa27f2007-02-19 06:05:58 +0000[diff] [blame]23 <li><a href="#newwork">Making a Major Change</a></li>
24 <li><a href="#incremental">Incremental Development</a></li>
Chris Lattner793eead2007-02-19 05:43:04 +0000[diff] [blame]25 <li><a href="#attribution">Attribution of Changes</a></li>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]26 </ol></li>
Chris Lattner83967802007-02-19 06:19:16 +0000[diff] [blame]27 <li><a href="#clp">Copyright, License, and Patents</a>
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]28 <ol>
29 <li><a href="#copyright">Copyright</a></li>
30 <li><a href="#license">License</a></li>
Chris Lattner76fa27f2007-02-19 06:05:58 +0000[diff] [blame]31 <li><a href="#patents">Patents</a></li>
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]32 <li><a href="#devagree">Developer Agreements</a></li>
33 </ol></li>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]34</ol>
Chris Lattnerf54ba982007-02-19 06:24:23 +0000[diff] [blame]35<div class="doc_author">Written by the LLVM Oversight Team</div>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]36
37<!--=========================================================================-->
Reid Spencer1e7306d2007-02-14 17:24:04 +0000[diff] [blame]38<div class="doc_section"><a name="introduction">Introduction</a></div>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]39<!--=========================================================================-->
40<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]41<p>This document contains the LLVM Developer Policy which defines the project's
42 policy towards developers and their contributions. The intent of this policy
43 is to eliminate miscommunication, rework, and confusion that might arise from
44 the distributed nature of LLVM's development. By stating the policy in clear
45 terms, we hope each developer can know ahead of time what to expect when
46 making LLVM contributions.</p>
47<p>This policy is also designed to accomplish the following objectives:</p>
48
49<ol>
50 <li>Attract both users and developers to the LLVM project.</li>
51
52 <li>Make life as simple and easy for contributors as possible.</li>
53
54 <li>Keep the top of Subversion trees as stable as possible.</li>
55</ol>
Chris Lattner793eead2007-02-19 05:43:04 +0000[diff] [blame]56
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]57<p>This policy is aimed at frequent contributors to LLVM. People interested in
58 contributing one-off patches can do so in an informal way by sending them to
59 the
60 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">llvm-commits
61 mailing list</a> and engaging another developer to see it through the
62 process.</p>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]63</div>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]64
65<!--=========================================================================-->
Chris Lattner76fa27f2007-02-19 06:05:58 +0000[diff] [blame]66<div class="doc_section"><a name="policies">Developer Policies</a></div>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]67<!--=========================================================================-->
68<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]69<p>This section contains policies that pertain to frequent LLVM developers. We
70 always welcome <a href="#patches">one-off patches</a> from people who do not
71 routinely contribute to LLVM, but we expect more from frequent contributors
72 to keep the system as efficient as possible for everyone. Frequent LLVM
73 contributors are expected to meet the following requirements in order for
74 LLVM to maintain a high standard of quality.<p>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]75</div>
76
77<!-- _______________________________________________________________________ -->
78<div class="doc_subsection"> <a name="informed">Stay Informed</a> </div>
79<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]80<p>Developers should stay informed by reading at least the
81 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">llvmdev</a> email
82 list. If you are doing anything more than just casual work on LLVM, it is
83 suggested that you also subscribe to the
84 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">llvm-commits</a>
Reid Spencer33610372007-02-14 16:21:10 +0000[diff] [blame]85 list and pay attention to changes being made by others.</p>
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]86
87<p>We recommend that active developers register an email account with
88 <a href="http://llvm.org/bugs/">LLVM Bugzilla</a> and preferably subscribe to
89 the <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs">llvm-bugs</a>
90 email list to keep track of bugs and enhancements occurring in LLVM.</p>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]91</div>
92
93<!-- _______________________________________________________________________ -->
Chris Lattnera3338192007-02-19 05:57:29 +0000[diff] [blame]94<div class="doc_subsection"> <a name="patches">Making a Patch</a></div>
95
96<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]97<p>When making a patch for review, the goal is to make it as easy for the
98 reviewer to read it as possible. As such, we recommend that you:</p>
Chris Lattnera3338192007-02-19 05:57:29 +0000[diff] [blame]99
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]100<ol>
101 <li>Make your patch against the Subversion trunk, not a branch, and not an old
102 version of LLVM. This makes it easy to apply the patch.</li>
Chris Lattnera3338192007-02-19 05:57:29 +0000[diff] [blame]103
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]104 <li>Similarly, patches should be submitted soon after they are generated. Old
105 patches may not apply correctly if the underlying code changes between the
106 time the patch was created and the time it is applied.</li>
107
108 <li>Patches should be made with this command:
109<div class="doc_code">
110<pre>
Chris Lattner42670d82009-06-15 04:18:54 +0000[diff] [blame^]111svn diff
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]112</pre>
113</div>
114 or with the utility <tt>utils/mkpatch</tt>, which makes it easy to read
115 the diff.</li>
116
117 <li>Patches should not include differences in generated code such as the code
118 generated by <tt>autoconf</tt> or <tt>tblgen</tt>. The
119 <tt>utils/mkpatch</tt> utility takes care of this for you.</li>
120</ol>
Chris Lattner78914c32007-02-19 06:57:16 +0000[diff] [blame]121
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]122<p>When sending a patch to a mailing list, it is a good idea to send it as an
123 <em>attachment</em> to the message, not embedded into the text of the
124 message. This ensures that your mailer will not mangle the patch when it
125 sends it (e.g. by making whitespace changes or by wrapping lines).</p>
126
127<p><em>For Thunderbird users:</em> Before submitting a patch, please open
128 <em>Preferences &#8594; Advanced &#8594; General &#8594; Config Editor</em>,
129 find the key <tt>mail.content_disposition_type</tt>, and set its value to
130 <tt>1</tt>. Without this setting, Thunderbird sends your attachment using
131 <tt>Content-Disposition: inline</tt> rather than <tt>Content-Disposition:
132 attachment</tt>. Apple Mail gamely displays such a file inline, making it
133 difficult to work with for reviewers using that program.</p>
Chris Lattnera3338192007-02-19 05:57:29 +0000[diff] [blame]134</div>
135
136<!-- _______________________________________________________________________ -->
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]137<div class="doc_subsection"> <a name="reviews">Code Reviews</a></div>
138<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]139<p>LLVM has a code review policy. Code review is one way to increase the quality
140 of software. We generally follow these policies:</p>
Chris Lattner78914c32007-02-19 06:57:16 +0000[diff] [blame]141
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]142<ol>
143 <li>All developers are required to have significant changes reviewed before
144 they are committed to the repository.</li>
145
146 <li>Code reviews are conducted by email, usually on the llvm-commits
147 list.</li>
148
149 <li>Code can be reviewed either before it is committed or after. We expect
150 major changes to be reviewed before being committed, but smaller changes
151 (or changes where the developer owns the component) can be reviewed after
152 commit.</li>
153
154 <li>The developer responsible for a code change is also responsible for making
155 all necessary review-related changes.</li>
156
157 <li>Code review can be an iterative process, which continues until the patch
158 is ready to be committed.</li>
159</ol>
160
161<p>Developers should participate in code reviews as both reviewers and
162 reviewees. If someone is kind enough to review your code, you should return
163 the favor for someone else. Note that anyone is welcome to review and give
164 feedback on a patch, but only people with Subversion write access can approve
165 it.</p>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]166</div>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]167
168<!-- _______________________________________________________________________ -->
Chris Lattnerb39e02b2007-12-03 19:00:47 +0000[diff] [blame]169<div class="doc_subsection"> <a name="owners">Code Owners</a></div>
170<div class="doc_text">
171
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]172<p>The LLVM Project relies on two features of its process to maintain rapid
173 development in addition to the high quality of its source base: the
174 combination of code review plus post-commit review for trusted maintainers.
175 Having both is a great way for the project to take advantage of the fact that
176 most people do the right thing most of the time, and only commit patches
177 without pre-commit review when they are confident they are right.</p>
Chris Lattnerb39e02b2007-12-03 19:00:47 +0000[diff] [blame]178
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]179<p>The trick to this is that the project has to guarantee that all patches that
180 are committed are reviewed after they go in: you don't want everyone to
181 assume someone else will review it, allowing the patch to go unreviewed. To
182 solve this problem, we have a notion of an 'owner' for a piece of the code.
183 The sole responsibility of a code owner is to ensure that a commit to their
184 area of the code is appropriately reviewed, either by themself or by someone
185 else. The current code owners are:</p>
Chris Lattnerb39e02b2007-12-03 19:00:47 +0000[diff] [blame]186
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]187<ol>
188 <li><b>Anton Korobeynikov</b>: Exception handling, debug information, and
189 Windows codegen.</li>
190
191 <li><b>Duncan Sands</b>: llvm-gcc 4.2.</li>
192
193 <li><b>Evan Cheng</b>: Code generator and all targets.</li>
194
195 <li><b>Chris Lattner</b>: Everything else.</li>
196</ol>
Chris Lattnerb39e02b2007-12-03 19:00:47 +0000[diff] [blame]197
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]198<p>Note that code ownership is completely different than reviewers: anyone can
199 review a piece of code, and we welcome code review from anyone who is
200 interested. Code owners are the "last line of defense" to guarantee that all
201 patches that are committed are actually reviewed.</p>
Chris Lattnerb39e02b2007-12-03 19:00:47 +0000[diff] [blame]202
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]203<p>Being a code owner is a somewhat unglamorous position, but it is incredibly
204 important for the ongoing success of the project. Because people get busy,
205 interests change, and unexpected things happen, code ownership is purely
206 opt-in, and anyone can choose to resign their "title" at any time. For now,
207 we do not have an official policy on how one gets elected to be a code
208 owner.</p>
Chris Lattnerb39e02b2007-12-03 19:00:47 +0000[diff] [blame]209</div>
210
Chris Lattnerb39e02b2007-12-03 19:00:47 +0000[diff] [blame]211<!-- _______________________________________________________________________ -->
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]212<div class="doc_subsection"> <a name="testcases">Test Cases</a></div>
213<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]214<p>Developers are required to create test cases for any bugs fixed and any new
215 features added. Some tips for getting your testcase approved:</p>
216
217<ol>
218 <li>All feature and regression test cases are added to the
219 <tt>llvm/test</tt> directory. The appropriate sub-directory should be
220 selected (see the <a href="TestingGuide.html">Testing Guide</a> for
221 details).</li>
222
223 <li>Test cases should be written in <a href="LangRef.html">LLVM assembly
224 language</a> unless the feature or regression being tested requires
225 another language (e.g. the bug being fixed or feature being implemented is
226 in the llvm-gcc C++ front-end, in which case it must be written in
227 C++).</li>
228
229 <li>Test cases, especially for regressions, should be reduced as much as
230 possible, by <a href="Bugpoint.html">bugpoint</a> or manually. It is
231 unacceptable to place an entire failing program into <tt>llvm/test</tt> as
232 this creates a <i>time-to-test</i> burden on all developers. Please keep
233 them short.</li>
234</ol>
Chris Lattner78914c32007-02-19 06:57:16 +0000[diff] [blame]235
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]236<p>Note that llvm/test is designed for regression and small feature tests
237 only. More extensive test cases (e.g., entire applications, benchmarks, etc)
238 should be added to the <tt>llvm-test</tt> test suite. The llvm-test suite is
239 for coverage (correctness, performance, etc) testing, not feature or
240 regression testing.</p>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]241</div>
242
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]243<!-- _______________________________________________________________________ -->
Chris Lattnera90a7d62007-02-19 05:47:13 +0000[diff] [blame]244<div class="doc_subsection"> <a name="quality">Quality</a></div>
245<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]246<p>The minimum quality standards that any change must satisfy before being
247 committed to the main development branch are:</p>
248
249<ol>
250 <li>Code must adhere to the <a href="CodingStandards.html">LLVM Coding
251 Standards</a>.</li>
252
253 <li>Code must compile cleanly (no errors, no warnings) on at least one
254 platform.</li>
255
256 <li>Bug fixes and new features should <a href="#testcases">include a
257 testcase</a> so we know if the fix/feature ever regresses in the
258 future.</li>
259
260 <li>Code must pass the dejagnu (<tt>llvm/test</tt>) test suite.</li>
261
262 <li>The code must not cause regressions on a reasonable subset of llvm-test,
263 where "reasonable" depends on the contributor's judgement and the scope of
264 the change (more invasive changes require more testing). A reasonable
265 subset might be something like
266 "<tt>llvm-test/MultiSource/Benchmarks</tt>".</li>
267</ol>
268
269<p>Additionally, the committer is responsible for addressing any problems found
270 in the future that the change is responsible for. For example:</p>
271
272<ul>
273 <li>The code should compile cleanly on all supported platforms.</li>
274
275 <li>The changes should not cause any correctness regressions in the
276 <tt>llvm-test</tt> suite and must not cause any major performance
277 regressions.</li>
278
279 <li>The change set should not cause performance or correctness regressions for
280 the LLVM tools.</li>
281
282 <li>The changes should not cause performance or correctness regressions in
283 code compiled by LLVM on all applicable targets.</li>
284
285 <li>You are expected to address any <a href="http://llvm.org/bugs/">bugzilla
286 bugs</a> that result from your change.</li>
287</ul>
Chris Lattnera90a7d62007-02-19 05:47:13 +0000[diff] [blame]288
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]289<p>We prefer for this to be handled before submission but understand that it
290 isn't possible to test all of this for every submission. Our nightly testing
291 infrastructure normally finds these problems. A good rule of thumb is to
292 check the nightly testers for regressions the day after your change.</p>
293
294<p>Commits that violate these quality standards (e.g. are very broken) may be
295 reverted. This is necessary when the change blocks other developers from
296 making progress. The developer is welcome to re-commit the change after the
297 problem has been fixed.</p>
Chris Lattnera90a7d62007-02-19 05:47:13 +0000[diff] [blame]298</div>
299
300<!-- _______________________________________________________________________ -->
Chris Lattner10f15142007-02-19 05:49:11 +0000[diff] [blame]301<div class="doc_subsection">
302 <a name="commitaccess">Obtaining Commit Access</a></div>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]303<div class="doc_text">
304
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]305<p>We grant commit access to contributors with a track record of submitting high
306 quality patches. If you would like commit access, please send an email to
307 <a href="mailto:sabre@nondot.org">Chris</a> with the following
308 information:</p>
Chris Lattner4b6d9652007-12-03 00:36:20 +0000[diff] [blame]309
310<ol>
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]311 <li>The user name you want to commit with, e.g. "hacker".</li>
312
Chris Lattner4b6d9652007-12-03 00:36:20 +0000[diff] [blame]313 <li>The full name and email address you want message to llvm-commits to come
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]314 from, e.g. "J. Random Hacker &lt;hacker@yoyodyne.com&gt;".</li>
315
Chris Lattner4b6d9652007-12-03 00:36:20 +0000[diff] [blame]316 <li>A "password hash" of the password you want to use, e.g. "2ACR96qjUqsyM".
317 Note that you don't ever tell us what your password is, you just give it
318 to us in an encrypted form. To get this, run "htpasswd" (a utility that
319 comes with apache) in crypt mode (often enabled with "-d"), or find a web
320 page that will do it for you.</li>
321</ol>
322
323<p>Once you've been granted commit access, you should be able to check out an
324 LLVM tree with an SVN URL of "https://username@llvm.org/..." instead of the
325 normal anonymous URL of "http://llvm.org/...". The first time you commit
326 you'll have to type in your password. Note that you may get a warning from
327 SVN about an untrusted key, you can ignore this. To verify that your commit
328 access works, please do a test commit (e.g. change a comment or add a blank
329 line). Your first commit to a repository may require the autogenerated email
330 to be approved by a mailing list. This is normal, and will be done when
331 the mailing list owner has time.</p>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]332
333<p>If you have recently been granted commit access, these policies apply:</p>
Chris Lattner4b6d9652007-12-03 00:36:20 +0000[diff] [blame]334
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]335<ol>
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]336 <li>You are granted <i>commit-after-approval</i> to all parts of LLVM. To get
337 approval, submit a <a href="#patches">patch</a> to
338 <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits">llvm-commits</a>.
339 When approved you may commit it yourself.</li>
340
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]341 <li>You are allowed to commit patches without approval which you think are
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]342 obvious. This is clearly a subjective decision &mdash; we simply expect
343 you to use good judgement. Examples include: fixing build breakage,
344 reverting obviously broken patches, documentation/comment changes, any
345 other minor changes.</li>
346
347 <li>You are allowed to commit patches without approval to those portions of
348 LLVM that you have contributed or maintain (i.e., have been assigned
349 responsibility for), with the proviso that such commits must not break the
350 build. This is a "trust but verify" policy and commits of this nature are
351 reviewed after they are committed.</li>
352
353 <li>Multiple violations of these policies or a single egregious violation may
354 cause commit access to be revoked.</li>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]355</ol>
Chris Lattner78914c32007-02-19 06:57:16 +0000[diff] [blame]356
357<p>In any case, your changes are still subject to <a href="#reviews">code
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]358 review</a> (either before or after they are committed, depending on the
359 nature of the change). You are encouraged to review other peoples' patches
360 as well, but you aren't required to.</p>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]361</div>
362
363<!-- _______________________________________________________________________ -->
Chris Lattner793eead2007-02-19 05:43:04 +0000[diff] [blame]364<div class="doc_subsection"> <a name="newwork">Making a Major Change</a></div>
365<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]366<p>When a developer begins a major new project with the aim of contributing it
367 back to LLVM, s/he should inform the community with an email to
368 the <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">llvmdev</a>
369 email list, to the extent possible. The reason for this is to:
370
371<ol>
372 <li>keep the community informed about future changes to LLVM, </li>
373
374 <li>avoid duplication of effort by preventing multiple parties working on the
375 same thing and not knowing about it, and</li>
376
377 <li>ensure that any technical issues around the proposed work are discussed
378 and resolved before any significant work is done.</li>
379</ol>
Chris Lattner793eead2007-02-19 05:43:04 +0000[diff] [blame]380
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]381<p>The design of LLVM is carefully controlled to ensure that all the pieces fit
382 together well and are as consistent as possible. If you plan to make a major
383 change to the way LLVM works or want to add a major new extension, it is a
384 good idea to get consensus with the development community before you start
385 working on it.</p>
Chris Lattner793eead2007-02-19 05:43:04 +0000[diff] [blame]386
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]387<p>Once the design of the new feature is finalized, the work itself should be
388 done as a series of <a href="#incremental">incremental changes</a>, not as a
389 long-term development branch.</p>
Chris Lattner793eead2007-02-19 05:43:04 +0000[diff] [blame]390</div>
391
392<!-- _______________________________________________________________________ -->
Chris Lattner76fa27f2007-02-19 06:05:58 +0000[diff] [blame]393<div class="doc_subsection"> <a name="incremental">Incremental Development</a>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]394</div>
395<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]396<p>In the LLVM project, we do all significant changes as a series of incremental
397 patches. We have a strong dislike for huge changes or long-term development
398 branches. Long-term development branches have a number of drawbacks:</p>
399
400<ol>
401 <li>Branches must have mainline merged into them periodically. If the branch
402 development and mainline development occur in the same pieces of code,
403 resolving merge conflicts can take a lot of time.</li>
404
405 <li>Other people in the community tend to ignore work on branches.</li>
406
407 <li>Huge changes (produced when a branch is merged back onto mainline) are
408 extremely difficult to <a href="#reviews">code review</a>.</li>
409
410 <li>Branches are not routinely tested by our nightly tester
411 infrastructure.</li>
412
413 <li>Changes developed as monolithic large changes often don't work until the
414 entire set of changes is done. Breaking it down into a set of smaller
415 changes increases the odds that any of the work will be committed to the
416 main repository.</li>
417</ol>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]418
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]419<p>To address these problems, LLVM uses an incremental development style and we
420 require contributors to follow this practice when making a large/invasive
421 change. Some tips:</p>
422
423<ul>
424 <li>Large/invasive changes usually have a number of secondary changes that are
425 required before the big change can be made (e.g. API cleanup, etc). These
426 sorts of changes can often be done before the major change is done,
427 independently of that work.</li>
428
429 <li>The remaining inter-related work should be decomposed into unrelated sets
430 of changes if possible. Once this is done, define the first increment and
431 get consensus on what the end goal of the change is.</li>
432
433 <li>Each change in the set can be stand alone (e.g. to fix a bug), or part of
434 a planned series of changes that works towards the development goal.</li>
435
436 <li>Each change should be kept as small as possible. This simplifies your work
437 (into a logical progression), simplifies code review and reduces the
438 chance that you will get negative feedback on the change. Small increments
439 also facilitate the maintenance of a high quality code base.</li>
440
441 <li>Often, an independent precursor to a big change is to add a new API and
442 slowly migrate clients to use the new API. Each change to use the new API
443 is often "obvious" and can be committed without review. Once the new API
444 is in place and used, it is much easier to replace the underlying
445 implementation of the API. This implementation change is logically
446 separate from the API change.</li>
447</ul>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]448
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]449<p>If you are interested in making a large change, and this scares you, please
450 make sure to first <a href="#newwork">discuss the change/gather consensus</a>
451 then ask about the best way to go about making the change.</p>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]452</div>
453
454<!-- _______________________________________________________________________ -->
Chris Lattner793eead2007-02-19 05:43:04 +0000[diff] [blame]455<div class="doc_subsection"><a name="attribution">Attribution of
456Changes</a></div>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]457<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]458<p>We believe in correct attribution of contributions to their contributors.
459 However, we do not want the source code to be littered with random
460 attributions "this code written by J. Random Hacker" (this is noisy and
461 distracting). In practice, the revision control system keeps a perfect
462 history of who changed what, and the CREDITS.txt file describes higher-level
463 contributions. If you commit a patch for someone else, please say "patch
464 contributed by J. Random Hacker!" in the commit message.</p>
Chris Lattnerebf56662007-12-29 19:56:08 +0000[diff] [blame]465
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]466<p>Overall, please do not add contributor names to the source code.</p>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]467</div>
468
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]469<!--=========================================================================-->
Chris Lattner83967802007-02-19 06:19:16 +0000[diff] [blame]470<div class="doc_section">
471 <a name="clp">Copyright, License, and Patents</a>
472</div>
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]473<!--=========================================================================-->
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]474
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]475<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]476<p>This section addresses the issues of copyright, license and patents for the
477 LLVM project. Currently, the University of Illinois is the LLVM copyright
478 holder and the terms of its license to LLVM users and developers is the
479 <a href="http://www.opensource.org/licenses/UoI-NCSA.php">University of
480 Illinois/NCSA Open Source License</a>.</p>
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]481
482<div class="doc_notes">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]483<p style="text-align:center;font-weight:bold">NOTE: This section deals with
484 legal matters but does not provide legal advice. We are not lawyers, please
485 seek legal counsel from an attorney.</p>
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]486</div>
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]487</div>
488
489<!-- _______________________________________________________________________ -->
490<div class="doc_subsection"><a name="copyright">Copyright</a></div>
491<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]492<p>For consistency and ease of management, the project requires the copyright
493 for all LLVM software to be held by a single copyright holder: the University
494 of Illinois (UIUC).</p>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]495
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]496<p>Although UIUC may eventually reassign the copyright of the software to
497 another entity (e.g. a dedicated non-profit "LLVM Organization") the intent
498 for the project is to always have a single entity hold the copyrights to LLVM
499 at any given time.</p>
Chris Lattnere1d4c2e2008-05-20 20:06:53 +0000[diff] [blame]500
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]501<p>We believe that having a single copyright holder is in the best interests of
502 all developers and users as it greatly reduces the managerial burden for any
503 kind of administrative or technical decisions about LLVM. The goal of the
504 LLVM project is to always keep the code open and <a href="#license">licensed
505 under a very liberal license</a>.</p>
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]506</div>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]507
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]508<!-- _______________________________________________________________________ -->
509<div class="doc_subsection"><a name="license">License</a></div>
510<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]511<p>We intend to keep LLVM perpetually open source and to use a liberal open
512 source license. The current license is the
513 <a href="http://www.opensource.org/licenses/UoI-NCSA.php">University of
514 llinois/NCSA Open Source License</a>, which boils down to this:</p>
Chris Lattner8087c0b2007-02-19 03:50:31 +0000[diff] [blame]515
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]516<ul>
517 <li>You can freely distribute LLVM.</li>
518
519 <li>You must retain the copyright notice if you redistribute LLVM.</li>
520
521 <li>Binaries derived from LLVM must reproduce the copyright notice (e.g. in
522 an included readme file).</li>
523
524 <li>You can't use our names to promote your LLVM derived products.</li>
525
526 <li>There's no warranty on LLVM at all.</li>
527</ul>
528
529<p>We believe this fosters the widest adoption of LLVM because it <b>allows
530 commercial products to be derived from LLVM</b> with few restrictions and
531 without a requirement for making any derived works also open source (i.e.
532 LLVM's license is not a "copyleft" license like the GPL). We suggest that you
533 read the <a href="http://www.opensource.org/licenses/UoI-NCSA.php">License</a>
534 if further clarification is needed.</p>
535
536<p>Note that the LLVM Project does distribute llvm-gcc, <b>which is GPL.</b>
537 This means that anything "linked" into llvm-gcc must itself be compatible
538 with the GPL, and must be releasable under the terms of the GPL. This
539 implies that <b>any code linked into llvm-gcc and distributed to others may
540 be subject to the viral aspects of the GPL</b> (for example, a proprietary
541 code generator linked into llvm-gcc must be made available under the GPL).
542 This is not a problem for code already distributed under a more liberal
543 license (like the UIUC license), and does not affect code generated by
544 llvm-gcc. It may be a problem if you intend to base commercial development
545 on llvm-gcc without redistributing your source code.</p>
546
547<p>We have no plans to change the license of LLVM. If you have questions or
548 comments about the license, please contact the
549 <a href="mailto:llvm-oversight@cs.uiuc.edu">LLVM Oversight Group</a>.</p>
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]550</div>
Chris Lattner76fa27f2007-02-19 06:05:58 +0000[diff] [blame]551
552<!-- _______________________________________________________________________ -->
553<div class="doc_subsection"><a name="patents">Patents</a></div>
554<div class="doc_text">
Chris Lattnera65670e2007-02-19 06:13:50 +0000[diff] [blame]555<p>To the best of our knowledge, LLVM does not infringe on any patents (we have
556 actually removed code from LLVM in the past that was found to infringe).
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]557 Having code in LLVM that infringes on patents would violate an important goal
558 of the project by making it hard or impossible to reuse the code for
Chris Lattner30ff8f82007-02-19 06:15:33 +0000[diff] [blame]559 arbitrary purposes (including commercial use).</p>
Chris Lattnera65670e2007-02-19 06:13:50 +0000[diff] [blame]560
561<p>When contributing code, we expect contributors to notify us of any potential
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]562 for patent-related trouble with their changes. If you or your employer own
563 the rights to a patent and would like to contribute code to LLVM that relies
564 on it, we require that the copyright owner sign an agreement that allows any
565 other user of LLVM to freely use your patent. Please contact
566 the <a href="mailto:llvm-oversight@cs.uiuc.edu">oversight group</a> for more
Chris Lattnera65670e2007-02-19 06:13:50 +0000[diff] [blame]567 details.</p>
Chris Lattner76fa27f2007-02-19 06:05:58 +0000[diff] [blame]568</div>
569
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]570<!-- _______________________________________________________________________ -->
571<div class="doc_subsection"><a name="devagree">Developer Agreements</a></div>
572<div class="doc_text">
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]573<p>With regards to the LLVM copyright and licensing, developers agree to assign
574 their copyrights to UIUC for any contribution made so that the entire
575 software base can be managed by a single copyright holder. This implies that
576 any contributions can be licensed under the license that the project
577 uses.</p>
Chris Lattner92d79632008-05-22 03:06:14 +0000[diff] [blame]578
Bill Wendlingb95325c2009-04-05 12:37:44 +0000[diff] [blame]579<p>When contributing code, you also affirm that you are legally entitled to
580 grant this copyright, personally or on behalf of your employer. If the code
581 belongs to some other entity, please raise this issue with the oversight
582 group before the code is committed.</p>
Reid Spencer56e56552007-02-14 07:22:19 +0000[diff] [blame]583</div>
584
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]585<!-- *********************************************************************** -->
586<hr>
587<address>
588 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman86242e12008-12-11 17:34:48 +0000[diff] [blame]589 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]590 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman21a63702008-12-11 18:23:24 +0000[diff] [blame]591 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Chris Lattner30ff8f82007-02-19 06:15:33 +0000[diff] [blame]592 Written by the
Reid Spencerc4a1f8b2007-02-14 07:57:48 +0000[diff] [blame]593 <a href="mailto:llvm-oversight@cs.uiuc.edu">LLVM Oversight Group</a><br>
Reid Spencera0f02a32007-02-13 09:06:01 +0000[diff] [blame]594 <a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
595 Last modified: $Date$
596</address>
597</body>
598</html>