X-Git-Url: http://demsky.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FDeveloperPolicy.html;h=6a3d1b46d4f6d4aa94c2d0ca39bd26cecd80a10e;hb=cfbece50f602c561c5eac046bcfc9a07c8c006cb;hp=b53b1eb8292a0485a635cdeca82996a1c86359ce;hpb=b742ff084f6fc18ba2421a5c231a8a72a22d5e62;p=oota-llvm.git diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html index b53b1eb8292..6a3d1b46d4f 100644 --- a/docs/DeveloperPolicy.html +++ b/docs/DeveloperPolicy.html @@ -29,7 +29,6 @@
  • Copyright
  • License
  • Patents
  • -
  • Developer Agreements
  • Written by the LLVM Oversight Team
    @@ -196,7 +195,11 @@
    1. Evan Cheng: Code generator and all targets.
    2. -
    3. Doug Gregor: Clang Basic, Lex, Parse, and Sema Libraries.
    4. +
    5. Greg Clayton: LLDB.
    6. + +
    7. Doug Gregor: Clang Frontend Libraries.
    8. + +
    9. Howard Hinnant: libc++.
    10. Anton Korobeynikov: Exception handling, debug information, and Windows codegen.
    11. @@ -506,20 +509,24 @@ Changes
      Copyright
      -

      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.

      +
      @@ -584,21 +591,6 @@ Changes details.

      - -
      Developer Agreements
      -
      -

      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.

      -
      -