Update License
Steev Klimaszewski
1 year, 4 months ago
3 | 3 | |
4 | 4 | Files: * |
5 | 5 | Copyright: Brian Holyfield - Gotham Digital Science <[email protected]> |
6 | License: RPL1.5 | |
7 | The Reciprocal Public License (RPL) is based on the concept of reciprocity or, | |
8 | if you prefer, fairness. | |
6 | License: Apache-2.0 | |
7 | Licensed under the Apache License, Version 2.0 (the "License"); | |
8 | you may not use this file except in compliance with the License. | |
9 | Unless required by applicable law or agreed to in writing, software | |
10 | distributed under the License is distributed on an "AS IS" BASIS, | |
11 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | |
12 | See the License for the specific language governing permissions and | |
13 | limitations under the License. | |
9 | 14 | . |
10 | In short, this license grew out of a desire to close loopholes in previous open | |
11 | source licenses, loopholes that allowed parties to acquire open source software | |
12 | and derive financial benefit from it without having to release their | |
13 | improvements or derivatives to the community which enabled them. This occurred | |
14 | any time an entity did not release their application to a "third party". | |
15 | . | |
16 | While there is a certain freedom in this model of licensing, it struck the | |
17 | authors of the RPL as being unfair to the open source community at large and to | |
18 | the original authors of the works in particular. After all, bug fixes, | |
19 | extensions, and meaningful and valuable derivatives were not consistently | |
20 | finding their way back into the community where they could fuel further, and | |
21 | faster, growth and expansion of the overall open source software base. | |
22 | . | |
23 | While you should clearly read and understand the entire license, the essence of | |
24 | the RPL is found in two definitions: "Deploy" and "Required Components". | |
25 | . | |
26 | Regarding deployment, under the RPL your changes, bug fixes, extensions, etc. | |
27 | must be made available to the open source community at large when you Deploy in | |
28 | any form -- either internally or to an outside party. Once you start running | |
29 | the software you have to start sharing the software. | |
30 | . | |
31 | Further, under the RPL all components you author including schemas, scripts, | |
32 | source code, etc. -- regardless of whether they're compiled into a single | |
33 | binary or used as two halves of client/server application -- must be shared. | |
34 | You have to share the whole pie, not an isolated slice of it. | |
35 | . | |
36 | In addition to these goals, the RPL was authored to meet the requirements of | |
37 | the Open Source Definition as maintained by the Open Source Initiative (OSI). | |
38 | 15 | |
39 | 16 | Files: debian/* |
40 | 17 | Copyright: 2013 Devon Kearns <[email protected]> |
18 | 2022 Steev Klimaszewski <[email protected]> | |
41 | 19 | License: GPL-2+ |
42 | 20 | This package is free software; you can redistribute it and/or modify |
43 | 21 | it under the terms of the GNU General Public License as published by |