WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Difference between revisions of "Contribution Policy"

From Obsolete Lustre Wiki
Jump to navigationJump to search
Line 1: Line 1:
 
Before you contribute code to Lustre or obtain write access to the CVS repository, you must sign our [http://wiki.lustre.org/images/c/cd/Sun_Contributor_Agreement_1_5.pdf Contributor Agreement] and return it to lustre-ca@sun.com. We require this step for several reasons:
 
Before you contribute code to Lustre or obtain write access to the CVS repository, you must sign our [http://wiki.lustre.org/images/c/cd/Sun_Contributor_Agreement_1_5.pdf Contributor Agreement] and return it to lustre-ca@sun.com. We require this step for several reasons:
  
* We need to make sure that you are only contributing code that you own. By certifying that you wrote the code (and that you control the rights), you take legal responsibility for your contribution.
+
* We need to make sure that you only contribute code that you own. By certifying that you wrote the code (and that you control the rights), you take legal responsibility for your contribution.
  
 
* By agreeing to Joint Copyright, you make it easier for us to protect the project and company from license violations. Only the copyright holder is empowered to act against violations (see the [http://www.gnu.org/licenses/why-assign.html Free Software Foundations's comments] about this topic).
 
* By agreeing to Joint Copyright, you make it easier for us to protect the project and company from license violations. Only the copyright holder is empowered to act against violations (see the [http://www.gnu.org/licenses/why-assign.html Free Software Foundations's comments] about this topic).
  
* By agreeing, you also make it possible to continue to sell and distribute Lustre under other licenses, including non-free licenses. This business model is what pays the bills, allowing us to maintain and improve Lustre, release the code under an open source license, and participate in open development (which, generally speaking, pays few of the bills).
+
* By signing the agreement, you also make it possible for us to continue to sell and distribute Lustre under other licenses, including non-free licenses. This business model is what pays the bills, allowing us to maintain and improve Lustre, release the code under an open source license, and participate in open development.
  
Because you remain a copyright holder of what you wrote, you can use the code you contributed in almost any fashion. Of course, this only applies to the software that you contribute, not software written by others.
+
Because you remain a copyright holder of the code you contribute, you can use the code in almost any fashion. Of course, this only applies to the software that you contribute, not software written by others.
  
We will gladly acknowledge your authorship in the source code. Our point is not to try to take credit for your work. If you make a substantial contribution, please update the boilerplate at the top of the source file as part of your patch.
+
We will gladly acknowledge your authorship in the source code. If you make a substantial contribution, please update the boilerplate at the top of the source file as part of your patch.
  
Finally, if you write software for a living (or attend a university), there is a good chance that your organization owns all of the software that you create. In this case, you have three options:
+
Finally, if you write software for a living (or attend a university), your organization may all of the software that you create. In this case, you have three options:
  
* Get an officer or authorized representative of the organization to contribute the software.
+
* Have an officer or authorized representative of the organization contribute the software.
* Get an officer or authorized representative of the organization to waive its rights to your software, so that you can contribute it yourself. In this case, please enclose a short waiver signed by the officer.
+
* Get an officer or authorized representative of the organization to waive its rights to your software so that you can contribute it yourself. In this case, please enclose a short waiver signed by the officer.
 
* Do not contribute the software.
 
* Do not contribute the software.
  
You are responsible for making sure that you control the rights to the software before you contribute it. If there is any doubt, please consult the organization or an attorney. If you ever find that you contributed software that you shouldn't have for any reason, please notify us right away.
+
You are responsible for making sure that you control the rights to the software before you contribute it. If in doubt, please consult your organization or an attorney. If you ever find that you have contributed software that you shouldn't have for any reason, please notify us right away.

Revision as of 12:17, 27 August 2009

Before you contribute code to Lustre or obtain write access to the CVS repository, you must sign our Contributor Agreement and return it to lustre-ca@sun.com. We require this step for several reasons:

  • We need to make sure that you only contribute code that you own. By certifying that you wrote the code (and that you control the rights), you take legal responsibility for your contribution.
  • By agreeing to Joint Copyright, you make it easier for us to protect the project and company from license violations. Only the copyright holder is empowered to act against violations (see the Free Software Foundations's comments about this topic).
  • By signing the agreement, you also make it possible for us to continue to sell and distribute Lustre under other licenses, including non-free licenses. This business model is what pays the bills, allowing us to maintain and improve Lustre, release the code under an open source license, and participate in open development.

Because you remain a copyright holder of the code you contribute, you can use the code in almost any fashion. Of course, this only applies to the software that you contribute, not software written by others.

We will gladly acknowledge your authorship in the source code. If you make a substantial contribution, please update the boilerplate at the top of the source file as part of your patch.

Finally, if you write software for a living (or attend a university), your organization may all of the software that you create. In this case, you have three options:

  • Have an officer or authorized representative of the organization contribute the software.
  • Get an officer or authorized representative of the organization to waive its rights to your software so that you can contribute it yourself. In this case, please enclose a short waiver signed by the officer.
  • Do not contribute the software.

You are responsible for making sure that you control the rights to the software before you contribute it. If in doubt, please consult your organization or an attorney. If you ever find that you have contributed software that you shouldn't have for any reason, please notify us right away.