1 | Take note of the GNU Affero General Public License (COPYING.Affero), |
1 | Take note of the GNU Affero General Public License (COPYING.Affero), |
2 | which applies to part of this release, which means you have to follow the |
2 | which applies to part of this release, which means you have to follow the |
3 | requirements laid out in section 13. of both licenses. |
3 | requirements laid out in section 13 of both licenses (see COPYING.GNU). |
4 | |
4 | |
5 | As long as you follow the provisions of the APGL you should be safe. |
5 | As long as you follow the provisions of the APGL you should be safe. |
6 | |
6 | |
7 | Note that ALL changes introduced by the Deliantra team are under the |
7 | Note that ALL changes introduced by the Deliantra team are under the |
8 | Affero GNU Public License. Specifically, the files listed below are 100% |
8 | Affero General Public License. Specifically, the files listed below are |
9 | AGPL. The listing of these files does not imply the remaining files do not |
9 | 100% AGPL. The listing of these files does not imply the remaining files |
10 | contain any AGPL code (the opposite is actually true). |
10 | do not contain any AGPL code (the opposite is actually true). |
11 | |
11 | |
12 | The archetypes and maps are mostly GPL, but all maps and archetype file |
12 | The archetypes and maps are mostly GPL, but all maps and archetype file |
13 | added by Deliantra are AGPL, unless otherwise noted (many media files are |
13 | added by Deliantra are AGPL, unless otherwise noted (many media files are |
14 | cc:by or similarly permissive, and this is noted in the META.json files in |
14 | cc:by or similarly permissive, and this is noted in the META.json files in |
15 | directories that have them). Again, note that unless you remove the AGPL |
15 | directories that have them). Again, note that unless you remove the AGPL |