diff options
| author | Jed Barber <jjbarber@y7mail.com> | 2017-06-27 22:31:19 +1000 |
|---|---|---|
| committer | Jed Barber <jjbarber@y7mail.com> | 2017-06-27 22:31:19 +1000 |
| commit | 08109e0a7b8697f3acc81868107162d03516bd2b (patch) | |
| tree | 4587b8bcbb2973f51edc5af86f2e285bffbd0726 | |
| parent | 57fa1fb21a14e4bfa9a130535a4a0453d52bf42a (diff) | |
Revised clause 4 to allow static linking
| -rw-r--r-- | license.txt | 8 | ||||
| -rw-r--r-- | rationale.txt | 10 |
2 files changed, 11 insertions, 7 deletions
diff --git a/license.txt b/license.txt index 0ef1885..8dc18fe 100644 --- a/license.txt +++ b/license.txt @@ -1,7 +1,7 @@ SUNSET LICENSE -Draft Version 3, June 2017 +Version 1.0 Draft Revision 4, June 2017 1. You may copy, modify, use, sell, or distribute this work, verbatim or @@ -13,8 +13,10 @@ no extra charge. 3. A modified version of this work must be clearly labeled as such. -4. Derivative works must also be licensed under this license. Dynamically -linking to this work does not constitute creating a derivative work. +4. Derivative works must also be licensed under this license or a license with +equivalent terms. As an exception, linking this work with another, whether +statically or dynamically, does not impose any license requirements on the +other work. 5. If a minimum of 10 years have passed since the date of first publishing for a part of this work, then that part is placed into the public domain and you diff --git a/rationale.txt b/rationale.txt index 9b02e18..6a31a22 100644 --- a/rationale.txt +++ b/rationale.txt @@ -29,8 +29,11 @@ under the rules of public domain will either have to use code many years out of date, or the work itself has stagnated to the point where nobody cares anyway. Combining this idea with minimalistic copyleft clauses should fill another -hole in available licenses, as all current ones are exceedingly verbose and -precise. +hole in available licenses, as all current ones are exceedingly verbose. + +The copyleft clauses have to be weak however, as otherwise works using this +license would not be able to link against BSD/MIT licensed works, which would +be less than ideal. @@ -50,8 +53,7 @@ you should be responsible for what you release to the public. Again, if this is a problem in your country, you should reform the law. The focus is on the work actually released, not on spreading the license -itself, so dynamic linking will not be considered to constitute making a -derivative work. +itself. Waiving anti-circumvention laws should be redundant and unnecessary, as the license allows usage of the work for any purpose without restriction. |