From: Reid Spencer Date: Wed, 14 Feb 2007 07:22:19 +0000 (+0000) Subject: Incorporate Chris' first round of comments. X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=78bade278f2aa5f89f0856d510aed706d5b3e16c;p=oota-llvm.git Incorporate Chris' first round of comments. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34269 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html index 8936d575d6c..f3b2c70b35a 100644 --- a/docs/DeveloperPolicy.html +++ b/docs/DeveloperPolicy.html @@ -12,14 +12,8 @@

Contents

    -
  1. Overview
    2. +
  2. Introduction
  3. Terminology
    4. -
  4. Copyright and License -
      -
    1. Copyright
      2. -
    2. License
      3. -
    3. Developer Agreements
      4. -
  5. General Policies
    1. Stay Informed
      2. @@ -38,6 +32,12 @@
    2. Obtaining Commit Access
    3. New Committers
    6. +
  6. Copyright and License +
      +
    1. Copyright
      2. +
    2. License
      3. +
    3. Developer Agreements
      4. +
Written by LLVM Oversight Team
 @@ -88,74 +88,6 @@
- -
Copyright and License
- -
-

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).

-
- -
Copyright
-
-

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.

-

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. -

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.

-
- -
License
-
-

LLVM licensing decisions will be made by the LLVM Oversight Group. Any - issues, comments or suggestions with the licensing should be sent to - oversight@llvm.org.

-

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:

- -

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.

-
- -
Developer Agreements
-
-

With regards to the LLVM copyright and licensing, developers agree to:

- -
-
General Policies
@@ -173,18 +105,19 @@ anything more than just casual work on LLVM, it is highly suggested that you also subscribe to the llvm-commits list and pay attention to changes being made by others.

-

Active developers must register an email account with bugzilla - (http://llvm.org/bugs/) and preferably - subscribe to the llvm-bugs email list to keep track of bugs occurring in - LLVM.

+

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.

Starting New Work
-

When a developer begins new work with the aim of contributing it back to - LLVM, s/he must inform the community with an email to llvm-dev email list, - to the extent possible. The reason for this is to: +

When a developer begins a major new project with the aim of contributing + it back to LLVM, s/he should inform the community with an email to + the llvm-dev + email list, to the extent possible. The reason for this is to:

+

The design of LLVM is carefully controlled to ensure that all the pieces + fit together well. If you plan to make a major change to the way LLVM works or + a major new extension, it is a good idea to get consensus with the development + community before you start working on it.

@@ -408,6 +345,100 @@ + +
Copyright and License
+ +
+

We address here the issues of copyright and license for the LLVM project. + The object of the copyright and license is the LLVM source and documentation. + 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/NCSA Open Source License. +

+ +
+

NOTE: This section deals with legal matters but does not provide legal + advice. It is intended only as a general guideline.

+
+ + +
Attribution
+
+

The LLVM project believes in correct attribution of contributions to + their contributors, as follows:

+
    +
  1. Developers who originate new files in LLVM should place their name at + the top of the file per the + Coding Standards.
    2. +
  2. There should be only one name at the top of the file and it should be + the person who created the file.
    3. +
  3. Placing your name in the file does not imply copyright but does + correctly attribute the file to its author.
    4. +
  4. Developers should be aware that after some time has passed, the name at + the top of a file may become meaningless as maintenance/ownership of files + changes.
    5. +
  5. Developers should submit or commit patches to the + CREDITS.txt + file to summarize their contributions.
    6. +
  6. Commit comments should contain correct attribution of the person who s + submitted the patch if that person is not the committer (i.e. when a + developer with commit privileges commits a patch for someone else).
    7. +
+
+ + +
Copyright
+
+

+

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. +

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.

+
+ +
License
+
+

LLVM licensing decisions will be made by the LLVM Oversight Group. Any + issues, comments or suggestions with the licensing should be sent to + oversight@llvm.org.

+

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:

+ +

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. We + suggest that you read the + License if + further clarification is needed.

+
+ +
Developer Agreements
+
+

With regards to the LLVM copyright and licensing, developers agree to:

+ +
+
Policy Notes