SoftwareLicensing » History » Version 1
laforge, 02/19/2016 10:47 PM
1 | 1 | laforge | = Software Licensing = |
---|---|---|---|
2 | |||
3 | The following notes apply to software described on this wiki, developed as part of the Osmocom project. |
||
4 | Specifically, it applies to OpenBSC, osmo-bsc, osmo-sgsn, gb_proxy, ipaccess-config, bsc_nat, bsc_mgcp, ... |
||
5 | |||
6 | For reasons of simplicity, we always call it ''OpenBSC'' here. |
||
7 | |||
8 | '''OpenBSC is copyrighted software like any other computer program. In order to use OpenBSC, you need |
||
9 | a license from the copyright holders.''' |
||
10 | |||
11 | If you do not arrange for a different license with the copyright holders, the software ships with a |
||
12 | default license: The [http://fsf.org/licenses/agpl-3.0.html AGPLv3] (GNU Affero General Public License, Version 3). |
||
13 | |||
14 | == General idea behind the License == |
||
15 | |||
16 | The general idea behind our licensing model is as follows: You receive the full source code of |
||
17 | the OpenBSC software and can use it like you see fit, '''but''' we require you to release the |
||
18 | source code of any modifications or derivative work you create. |
||
19 | |||
20 | With AGPL, it does not matter whether you ever distribute the OpenBSC software. As soon as you |
||
21 | provide a GSM network using OpenBSC, all users are entitled to receive a copy of the license text |
||
22 | and the ''complete corresponding source code'' of the very version you are using to run the GSM network with. |
||
23 | |||
24 | == Alternative Licenses / Dual Licensing == |
||
25 | |||
26 | If you do not agree to the abovementioned conditions, you may contact the copyright holders and apply for |
||
27 | an alternative license. Business details will depend on your intended use case, size of the installation, ... |