SoftwareLicensing » History » Version 4
laforge, 02/19/2016 10:48 PM
1 | 1 | laforge | |
---|---|---|---|
2 | 4 | laforge | h1. Software Licensing |
3 | |||
4 | |||
5 | |||
6 | h2. [[OpenBSC]] executable programs |
||
7 | |||
8 | 1 | laforge | The following notes apply to software described on this wiki, developed as part of the Osmocom project. |
9 | 4 | laforge | Specifically, it applies to [[OpenBSC]], osmo-bsc, osmo-sgsn, gb_proxy, ipaccess-config, bsc_nat, bsc_mgcp, ... |
10 | 1 | laforge | |
11 | 4 | laforge | For reasons of simplicity, we always call it _OpenBSC_ here. |
12 | 1 | laforge | |
13 | 4 | laforge | *OpenBSC is copyrighted software like any other computer program. In order to use [[OpenBSC]], you need |
14 | a license from the copyright holders.* |
||
15 | 1 | laforge | |
16 | If you do not arrange for a different license with the copyright holders, the software ships with a |
||
17 | 4 | laforge | default license: The "AGPLv3":http://fsf.org/licenses/agpl-3.0.html (GNU Affero General Public License, Version 3). |
18 | 1 | laforge | |
19 | |||
20 | 4 | laforge | h4. General idea behind the License |
21 | |||
22 | |||
23 | 1 | laforge | The general idea behind our licensing model is as follows: You receive the full source code of |
24 | 4 | laforge | the [[OpenBSC]] software and can use it like you see fit, *but* we require you to release the |
25 | 1 | laforge | source code of any modifications or derivative work you create. |
26 | |||
27 | 4 | laforge | With AGPL, it does not matter whether you ever distribute the [[OpenBSC]] software. As soon as you |
28 | provide a GSM network using [[OpenBSC]], all users are entitled to receive a copy of the license text |
||
29 | and the _complete corresponding source code_ of the very version you are using to run the GSM network with. |
||
30 | 1 | laforge | |
31 | 2 | laforge | |
32 | 4 | laforge | h3. Alternative Licenses / Dual Licensing |
33 | |||
34 | |||
35 | 1 | laforge | If you do not agree to the abovementioned conditions, you may contact the copyright holders and apply for |
36 | an alternative license. Business details will depend on your intended use case, size of the installation, ... |
||
37 | |||
38 | |||
39 | 4 | laforge | h2. libosmocore |
40 | |||
41 | |||
42 | <pre> |
||
43 | 2 | laforge | "GNU GPL Version 2, or any later version". This means at the time of this writing, you can license them |
44 | 4 | laforge | under either "GPLv2":http://www.gnu.org/licenses/gpl-2.0.html or "GPLv3":http://www.gnu.org/licenses/gpl-3.0.html. |
45 | 2 | laforge | |
46 | 4 | laforge | As both GPLv2 and GPLv3 are _strong copyleft_ licenses, it means that creating a derivative work of |
47 | 2 | laforge | the library and an executable program will require that executable program to be under the same GPL version. |
48 | |||
49 | If you use the libraries together with the Osmocom executable programs (see above), then libosmocore |
||
50 | will be licensed under GPLv3, which is compatible with the AGPLv3 of the executable programs. |
||
51 | 3 | laforge | |
52 | |||
53 | 4 | laforge | h2. Questions |
54 | |||
55 | |||
56 | 1 | laforge | If you have any questions regarding the licenses used in the Osmocom project, please contact the project |
57 | 4 | laforge | authors *before* you create any kind of product or a derivative work. |