Difference between revisions of "License"

From OpenSSLWiki
Jump to: navigation, search
m (Dropped 'project' from copyright; fixed spelling.)
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 be either:
+
We appreciate material and works produced 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. 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, although no decisions have been made and other licenses may be considered. 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 [https://openssl.org/source/license.html OpenSSL licence] is an "Apache style" license. We are moving to the Apache license soon; see our [https://www.openssl.org/blog/blog/categories/license/ blog posts].
agreements. The agreements are currently draft status.
 
  
 
== Source Code Patches ==
 
== Source Code Patches ==
Line 16: Line 15:
 
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:
 
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:
  
<pre>Contents licensed under the terms of the OpenSSL license: http://www.openssl.org/source/license.html</pre>
+
<pre>Contents licensed under the terms of the OpenSSL license: https://www.openssl.org/source/license.html</pre>
  
 +
You must also sign a [https://www.openssl.org/policies/cla.html CLA].
 
== Man Page Documentation ==
 
== Man Page Documentation ==
  
Line 34: Line 34:
 
<pre>  Copyright OpenSSL <nowiki>[YEAR]</nowiki>
 
<pre>  Copyright OpenSSL <nowiki>[YEAR]</nowiki>
 
   Contents licensed under the terms of the OpenSSL license
 
   Contents licensed under the terms of the OpenSSL license
   See http://www.openssl.org/source/license.html for details</pre>
+
   See https://www.openssl.org/source/license.html for details</pre>
  
 
[[Category:Legal]]
 
[[Category:Legal]]

Revision as of 20:53, 30 November 2017

We appreciate material and works produced 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 OpenSSL license (and any future version of it that the OpenSSL project may adopt)
  3. existing content already released under the current or future OpenSSL license.

The current OpenSSL licence is an "Apache style" license. We are moving to the Apache license soon; see our blog posts.

Source Code Patches

If you contribute patches for the library source code, then the OpenSSL project will use the OpenSSL license. Not all patches will be accepted or Incorporated, and there are a variety of reasons why such changes may not be accepted and utilized by the project (not all of them readily apparent). See Contributions for a discussion of patches and potential concerns.

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: https://www.openssl.org/source/license.html

You must also sign a CLA.

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

All contributions to this wiki are considered to be released under the current OpenSSL License (and any future version of it) and contributors agree the contributed content is original, or copied from a public domain or similar free resource, or copied from OpenSSL.

Copyright Notice

Use the following copyright notice for source files, sample programs on the wiki, etc.

   Copyright OpenSSL [YEAR]
   Contents licensed under the terms of the OpenSSL license
   See https://www.openssl.org/source/license.html for details