Difference between revisions of "License"

From OpenSSLWiki
Jump to navigationJump to search
(Made it clear that no decision has been made to go with a pure Apache license)
m (Update License terms. State current requirement to comply with both licenses.)
 
(14 intermediate revisions by 5 users not shown)
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
# original content created by you and released under the current or future OpenSSL license
+
# original content created by you and released under the current OpenSSL license (and any future version of it that the OpenSSL project may adopt)
 
# 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 license] is a combination of OpenSSL and Apache-style license. Both licenses must be complied with.
agreements. The agreements are currently draft status.
 
  
== Source Code Patches ==
+
For OpenSSL 3.0 we are moving to purely an Apache 2.0 license; see our [https://www.openssl.org/blog/blog/categories/license/ blog posts].
  
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];
+
We do not accept patches through the Wiki.
  
== Sample Programs ==
+
== Wiki Documentation ==
  
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:
+
[[Category:Wiki Usage]]
  
<blockquote>Contents licensed under the terms of the OpenSSL license: http://www.openssl.org/source/license.html</blockquote>
+
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.
  
== Man Page Documentation ==
+
== Copyright Notice ==
  
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];
+
Use the following copyright notice for source files, sample programs on the wiki, etc.
  
== Wiki Documentation ==
+
<pre>  Copyright OpenSSL <nowiki>[YEAR]</nowiki>
 +
  Contents licensed under the terms of the OpenSSL license
 +
  See https://www.openssl.org/source/license.html for details</pre>
  
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.
+
[[Category:Legal]]

Latest revision as of 13:35, 22 July 2020

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 license is a combination of OpenSSL and Apache-style license. Both licenses must be complied with.

For OpenSSL 3.0 we are moving to purely an Apache 2.0 license; see our blog posts.

We do not accept patches through the Wiki.

Wiki Documentation[edit]

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[edit]

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