<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body >I removed and updated some sections. Sorry if I wrote multiple answers but they weren't reviewed. I think it's because I accidently wrote a wrong new link. The real new link: http://paste.moritz30.de/view/raw/21f88fe1
<div id="message"></div>
<br id="br3">
<div id="signature"></div>
<div id="content"><blockquote><br> ---- On Di, 07 Jun 2016 17:55:29 +0200 <b> fontana@opensource.org </b> wrote ----<br><br><div>On 06/07/2016 07:41 AM, Carlo Piana wrote:<br>> Sorry for the rude answer, but there is no other license like it because<br>> it's very badly written (including some English mistakes).<br><br>It is certainly very difficult to understand because of what seems to be<br>a significant amount of non-idiomatic English.<br><br>> Just read section 5:<br>> <br>>> If the license get’s removed by the original software owner nothing will change for end users that already use the software. Redistributors will have to remove their redistributions if nothing other is stated by the new license after request. For new end users this license won’t be valid and they have to accept the new one. All newer versions of this software will be only under their new license. Also end users that started using this software will have to accept the new agreement to use the newer versions. Redistributors mustn’t publish newer versions of this software unless something other is stated by the new license.<br>> <br>> This section of the license is totally unacceptable and is liable to<br>> jeopardize everything, as the new license is a) compulsory and b)<br>> undefined, and therefore the original license is totally revocable.<br>> <br>> Make no mistake, this is not at all similar to the "or any later<br>> version" in *GPL or the upgrade provision in MPL. In both versions, the<br>> upgrade is optional to the downstream developer, not imposed by the<br>> upstream one, and the license itself is not revoked.<br>> <br>> Also section 11 reads as badgeware.<br>> <br>> I suggest outright rejection of this submission.<br><br>I believe it would need to be rewritten and resubmitted (though I'd<br>encourage Matthias to reconsider whether licenses such as GPLv2 or GPLv3<br>would meet his objectives). It is not really possible to assess as-is,<br>other than to conservatively assume that it's not OSD-conformant. For<br>example I really can't tell whether Carlo's interpretation of section 5<br>is correct.<br><br>Richard<br><br><br>_______________________________________________<br>License-review mailing list<br><a href="mailto:License-review@opensource.org" target="_blank">License-review@opensource.org</a><br><a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-review</a><br></div></blockquote></div></body></html>