Difference between revisions of "License"

From OpenSSLWiki
Jump to: navigation, search
(Added topics for license. Added 'place holders' for standard verbiage to be sited by others (SM?))
Line 1: Line 1:
The OpenSSL project and foundation appreciate material and works produced by individuals and oraganizations for the community. Documentation, patches, and sample programs help ensure the library is reliable and easy to use. To ensure the most benefit to the project and community, contributions to this wiki must either:
+
The OpenSSL project and foundation appreciate material and works produced by individuals and oraganizations for the community. Documentation, patches, and sample programs help ensure the library is reliable and easy to use. To ensure the most benefit to the project and community, contributions to this wiki must be either:
  
 
# existing material copied from a public domain source
 
# existing material copied from a public domain source
Line 5: Line 5:
 
# existing content already released under the current or future OpenSSL license.
 
# existing content already released under the current or future OpenSSL license.
  
The current [http://openssl.org/source/license.html OpenSSL licence] is an "Apache style" license. OpenSSL community feedback indicates the license has opportunity for improvement. Some thought has been given to migrating to a pure [http://www.apache.org/licenses/LICENSE-2.0.html Apache] license. Future contributions to OpenSSL will use [http://openssl.com/testing/license/openssl_icla.pdf Individual Contributor] and [http://openssl.com/testing/license/openssl_ccla.pdf Corporate Contributor]
+
The current [http://openssl.org/source/license.html OpenSSL licence] is an "Apache style" license. There is general consensus that the interests of the OpenSSL community could be better served with a different license. Some thought has been given to migrating to a pure [http://www.apache.org/licenses/LICENSE-2.0.html Apache] license. Future contributions to OpenSSL will use [http://openssl.com/testing/license/openssl_icla.pdf Individual Contributor] and [http://openssl.com/testing/license/openssl_ccla.pdf Corporate Contributor]
 
agreements. The agreements are currently draft status.
 
agreements. The agreements are currently draft status.
  
 
== Source Code Patches ==
 
== Source Code Patches ==
  
If you contribute patches for the library source code, then the OpenSSL project will use the XXX license. You will not need to do YYY to ensure your changes can be accepted by the project.
+
If you contribute patches for the library source code, then the OpenSSL project will use the OpenSSL license. Note there are a variety of reasons why such changes may not be accepted and utilized by the project, not all of them readily apparent [note: the topic of [[contributions]] deserves a separate discussion];
  
 
== Sample Programs ==
 
== Sample Programs ==
  
If you contribute sample programs for using the library, then the OpenSSL project will use the XXX license. You should place the following text at the top of the source files:
+
If you contribute original sample programs for using the library, then the OpenSSL project will use the OpenSSL license. You should place the following text at the top of the source files:
  
<blockquote>Now is the time for all good men to come to the aide of their country.</blockquote>
+
<blockquote>Contents licensed under the terms of the OpenSSL license: http://www.openssl.org/source/license.html</blockquote>
  
 
== Man Page Documentation ==
 
== Man Page Documentation ==
  
If you contribute documentation for the source code, then the OpenSSL project will use the XXX license. You will not need to do YYY to ensure your changes can be accepted by the project.
+
If you contribute original documentation for the source code, then the OpenSSL project will use the OpenSSL license. You will not need to do anything to ensure your changes are suitable for use by by the project. As with source code there are a variety of reasons why documentation may not be accepted and utilized by the project, not all of them readily apparent [note: the topic of [[contributions]] deserves a separate discussion];
  
 
== Wiki Documentation ==
 
== Wiki Documentation ==
  
If you contribute documentation on the wiki, then the OpenSSL project will use the XXX license. You will not need to do anything to place your works under the license.
+
If you contribute original documentation on the wiki, then the OpenSSL project will use the OpenSSL license. You will not need to do anything to place your works under the license.

Revision as of 20:30, 14 March 2013

The OpenSSL project and foundation appreciate material and works produced by individuals and oraganizations for the community. Documentation, patches, and sample programs help ensure the library is reliable and easy to use. To ensure the most benefit to the project and community, contributions to this wiki must be either:

  1. existing material copied from a public domain source
  2. original content created by you and released under the current or future OpenSSL license
  3. existing content already released under the current or future OpenSSL license.

The current OpenSSL licence is an "Apache style" license. There is general consensus that the interests of the OpenSSL community could be better served with a different license. Some thought has been given to migrating to a pure Apache license. Future contributions to OpenSSL will use Individual Contributor and Corporate Contributor agreements. The agreements are currently draft status.

Source Code Patches

If you contribute patches for the library source code, then the OpenSSL project will use the OpenSSL license. Note there are a variety of reasons why such changes may not be accepted and utilized by the project, not all of them readily apparent [note: the topic of contributions deserves a separate discussion];

Sample Programs

If you contribute original sample programs for using the library, then the OpenSSL project will use the OpenSSL license. You should place the following text at the top of the source files:

Contents licensed under the terms of the OpenSSL license: http://www.openssl.org/source/license.html

Man Page Documentation

If you contribute original documentation for the source code, then the OpenSSL project will use the OpenSSL license. You will not need to do anything to ensure your changes are suitable for use by by the project. As with source code there are a variety of reasons why documentation may not be accepted and utilized by the project, not all of them readily apparent [note: the topic of contributions deserves a separate discussion];

Wiki Documentation

If you contribute original documentation on the wiki, then the OpenSSL project will use the OpenSSL license. You will not need to do anything to place your works under the license.