Mercurial > repos > ImageTools / file comparison
comparison: LICENSE
LICENSE
- changeset 58
- 4a2c4ee27858
- parent 40
- 927d738d4ca4
equal
deleted
inserted
replaced
| 57:d3688b3c7c4e | 58:4a2c4ee27858 |
|---|---|
| 1 This software is distributed under an ANTI-ABUSE LICENSE (aka. *bollocks | |
| 2 to copyright and distributions* license), and without any warranty whatsoever. | |
| 3 If you redistribute this software as part of a larger collection, distribution, | |
| 4 or suite of software, you must do one of the following: | |
| 5 | 1 |
| 6 (a) Always redistribute the **unmodified** and **latest** version provided | 2 # Anti-abuse license |
| 7 by the lead author. If the lead author releases a new version (on a specific | 3 |
| 8 branch, such as 'stable' or 'development'), you must promptly make that new | 4 ## Rationale |
| 9 version the default version offered to your users (on that specific branch). | 5 |
| 6 The purpose of this license is to give end-users and developers maximal | |
| 7 freedom to use this software while preventing the authors from being | |
| 8 abused by powerful middle-men that repackage software for convenient | |
| 9 installation by users. Such potentially abusive middle-men include in | |
| 10 particular Linux distributions and similar centralising software | |
| 11 distribution schemes developed for other operating systems. | |
| 12 The ethos of this license is *bollocks to copyright and distributions!* | |
| 13 | |
| 14 ## Rules | |
| 15 | |
| 16 This software is distributed without any warranty whatsoever. | |
| 17 | |
| 18 If you redistribute modified versions of this software to the public, | |
| 19 you must clearly mark them as modified. | |
| 20 | |
| 21 If you redistribute this software to the public as part of a large | |
| 22 collection of software with the purpose of providing end-users with | |
| 23 a convenient installation method, you must do one of the following: | |
| 24 | |
| 25 (a) Always redistribute the **unmodified** and **latest** version | |
| 26 provided by the authors. If the lead author releases a new version (on a | |
| 27 specific branch, such as 'stable' or 'development'), you must promptly | |
| 28 make that new version the default version offered to your users (on | |
| 29 that specific branch). | |
| 10 | 30 |
| 11 (b) Rename the software, and make it obvious that your modified or obsolete | 31 (b) Rename the software, and make it obvious that your modified or obsolete |
| 12 software is in no way connected to the lead author of the original software. | 32 software is in no way connected to the authors of the original software. |
| 13 The users of your version should under no circumstances be under the | 33 The users of your version should under no circumstances be under the |
| 14 illusion that they can contact the lead author or any of the authors of the | 34 illusion that they can contact the lead author or any of the authors |
| 15 original software if they have any complaints or queries. | 35 of the original software if they have any complaints or queries. |
| 16 | 36 |
| 17 (c) Do not in any way directly expose this software to your users. | 37 (c) Do not in any way directly expose this software to your users. |
| 18 | 38 |
| 19 Otherwise, do whatever you want with this software. In particular, you may | 39 Otherwise, do whatever you want with this software. In particular, you may |
| 20 freely use code snippets in other projects. | 40 freely use the software as part of other projects, and redistribute to |
| 21 | 41 the public archival copies of the software (as long as your archive cannot |
| 42 be considered a “convenient installation method” that will be governed by | |
| 43 the rules above). |
