Debian Codegraph @

RELICENSE/README.md

raw
1 # Permission to Relicense under MPLv2 or BSD
2
3 pyzmq starting with 26.0.0 is fully licensed under the 3-clause Modified BSD License.
4 A small part of the core (Cython backend only) was previously licensed under LGPLv3 for historical reasons.
5 Permission has been granted by the contributors of the vast majority of those components to relicense under MPLv2 or BSD.
6 This backend has been completely replaced in pyzmq 26, and the new implementation is fully licensed under BSD-3-Clause,
7 so pyzmq is now under a single license.
8
9 Original text:
10
11 Most of pyzmq is licensed under [3-Clause BSD](https://opensource.org/licenses/BSD-3-Clause).
12 For historical reasons, the 'core' of pyzmq (the low-level Cython bindings)
13 was licensed under LGPLv3, like libzmq itself.
14
15 libzmq is in the process of moving away from LGPL to the [Mozilla Public License, version
16 2](https://www.mozilla.org/en-US/MPL/2.0/).
17 I'd like to take this opportunity to follow libzmq's example and also eliminate LGPL from pyzmq.
18 For a similarly copyleft license, MPLv2 can be used for the core.
19 However, I would prefer to update the core to follow the example of the rest of pyzmq,
20 and adopt the 3-Clause BSD license.
21
22 This directory collects grants from individuals and firms that hold
23 copyrights in pyzmq to permit licensing the pyzmq code under
24 the MPLv2 or BSD license. See
25 the [0MQ Licensing Page](http://zeromq.org/area:licensing) and
26 [libzmq relicensing effort](https://github.com/zeromq/libzmq/pull/1917)
27 for some background information.
28
29 Please create a separate file in this directory for each individual
30 or firm holding copyright in pyzmq core, named after the individual or
31 firm holding the copyright.
32
33 Each patch must be made with a GitHub handle that is clearly
34 associated with the copyright owner, to guarantee the identity of
35 the signatory. Please avoid changing the files created by other
36 individuals or firms granting a copyright license over their
37 copyrights (if rewording is required contact them and ask them to
38 submit an updated version). This makes it easier to verify that
39 the license grant was made by an authorized GitHub account.