X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FDeveloperPolicy.html;h=6a3d1b46d4f6d4aa94c2d0ca39bd26cecd80a10e;hb=cfbece50f602c561c5eac046bcfc9a07c8c006cb;hp=6d4a1bd303d1b4d476427ca22bdc41119e112204;hpb=b2030437fc99cf257aa715d83cef36336bb2a76a;p=oota-llvm.git diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html index 6d4a1bd303d..6a3d1b46d4f 100644 --- a/docs/DeveloperPolicy.html +++ b/docs/DeveloperPolicy.html @@ -29,7 +29,6 @@
This policy is also designed to accomplish the following objectives:
Developers should stay informed by reading at least the - llvmdev email - list. If you are doing anything more than just casual work on LLVM, it is - suggested that you also subscribe to the - llvm-commits - list and pay attention to changes being made by others.
+Developers should stay informed by reading at least the "dev" mailing list + for the projects you are interested in, such as + llvmdev for + LLVM, cfe-dev + for Clang, or lldb-dev + for LLDB. If you are doing anything more than just casual work on LLVM, it + is suggested that you also subscribe to the "commits" mailing list for the + subproject you're interested in, such as + llvm-commits, + cfe-commits, + or lldb-commits. + Reading the "commits" list and paying attention to changes being made by + others is a good way to see what other people are interested in and watching + the flow of the project as a whole.
We recommend that active developers register an email account with LLVM Bugzilla and preferably subscribe to the llvm-bugs - email list to keep track of bugs and enhancements occurring in LLVM.
+ email list to keep track of bugs and enhancements occurring in LLVM. We + really appreciate people who are proactive at catching incoming bugs in their + components and dealing with them promptly.-svn diff --
When sending a patch to a mailing list, it is a good idea to send it as an @@ -187,13 +195,17 @@ svn diff
Note that llvm/test is designed for regression and small feature tests - only. More extensive test cases (e.g., entire applications, benchmarks, etc) +
Note that llvm/test and clang/test are designed for regression and small + feature tests only. More extensive test cases (e.g., entire applications, + benchmarks, etc) should be added to the llvm-test test suite. The llvm-test suite is for coverage (correctness, performance, etc) testing, not feature or regression testing.
@@ -261,7 +274,7 @@ svn diff testcase so we know if the fix/feature ever regresses in the future. -For consistency and ease of management, the project requires the copyright - for all LLVM software to be held by a single copyright holder: the University - of Illinois (UIUC).
- -Although UIUC may eventually reassign the copyright of the software to - another entity (e.g. a dedicated non-profit "LLVM Organization") the intent - for the project is to always have a single entity hold the copyrights to LLVM - at any given time.
- -We believe that 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. The goal of the - LLVM project is to always keep the code open and licensed - under a very liberal license.
+ +The LLVM project does not require copyright assignments, which means that the + copyright for the code in the project is held by its respective contributors + who have each agreed to release their contributed code under the terms of the + LLVM License.
+ +An implication of this is that the LLVM license is unlikely to ever change: + changing it would require tracking down all the contributors to LLVM and + getting them to agree that a license change is acceptable for their + contribution. Since there are no plans to change the license, this is not a + cause for concern.
+ +As a contributor to the project, this means that you (or your company) retain + ownership of the code you contribute, that it cannot be used in a way that + contradicts the license (which is a liberal BSD-style license), and that the + license for your contributions won't change without your approval in the + future.
+We intend to keep LLVM perpetually open source and to use a liberal open source license. The current license is the University of - llinois/NCSA Open Source License, which boils down to this:
+ Illinois/NCSA Open Source License, which boils down to this:With regards to the LLVM copyright and licensing, developers agree to assign - their copyrights to UIUC for any contribution made so that the entire - software base can be managed by a single copyright holder. This implies that - any contributions can be licensed under the license that the project - uses.
- -When contributing code, you also affirm that you are legally entitled to - grant this copyright, personally or on behalf of your employer. If the code - belongs to some other entity, please raise this issue with the oversight - group before the code is committed.
-