<div dir="ltr"><div><div><div>Hi Christopher<br><br></div>You might want to read up on Mozilla for this topic. They run an unusually thight trademark enforcement regime, precisely for this reason. Basically, the source code is open source, but you cannot leave any user visible traces of their trademark if you add even the smallest change.<br><br></div>Red Hat Enterprise Linux has a similarly thight trademark policy for commercial reasons. You can copy it, but trademark must be removed. (So for example, even in documentation, CentOS might refer pseudonymously to "upstream vendor".)<br><br></div><div>In short, trademark is commonly used for this purpose, while licensing not so much. Since trademark rights are quite independent of copyrights, this is also GPL, etc... compatible, since there are no restrictions on the code, you're just protecting your name and reputation.<br></div><div><br></div>henrik<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 22, 2016 at 11:40 PM, Christopher Sean Morrison <span dir="ltr"><<a href="mailto:brlcad@mac.com" target="_blank">brlcad@mac.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><span style="font-family:Menlo-Regular;font-size:11px">Is there any OSI-approved license that provides injunctive relief to an original author in the situation of a bad actor creating a damaging derivative? To figure this out, I’ve been researching and trying to sort out:</span><br style="font-family:Menlo-Regular;font-size:11px"><br style="font-family:Menlo-Regular;font-size:11px"><span style="font-family:Menlo-Regular;font-size:11px">1) which existing OSI-approved licenses impose derivative requirements (e.g., such that others must rename, that changes must be itemized, etc) and,</span><br style="font-family:Menlo-Regular;font-size:11px"><br style="font-family:Menlo-Regular;font-size:11px"><span style="font-family:Menlo-Regular;font-size:11px">2) whether such a requirement makes the license de facto GPL/LGPL-incompatible?</span><br style="font-family:Menlo-Regular;font-size:11px"><br style="font-family:Menlo-Regular;font-size:11px"><span style="font-family:Menlo-Regular;font-size:11px">For #1, I know CDDL has a required notice of authorship of modifications but didn’t see anything else at least amongst the popular licenses. I know that license+trademark protection is the primary method for several notable open source products (e.g., Firefox), but getting an injunction solely on failing to announce modifications seems weak. </span><br style="font-family:Menlo-Regular;font-size:11px"><br><span style="font-family:Menlo-Regular;font-size:11px">I think the answer to #2 is “probably”, as anything that would hold up in court would likely be an additional requirement, forbidden by the GNUs, but would appreciate any insights.</span><br style="font-family:Menlo-Regular;font-size:11px"><span style="font-family:Menlo-Regular;font-size:11px"><br></span><div><span style="font-family:Menlo-Regular;font-size:11px">The backdrop for this is an author reasonably going to court and obtaining injunctive relief should some bad actor distribute a derivative that was specifically designed to cause some surreptitious harm to the original author. Not just a hypothetical case.</span><br style="font-family:Menlo-Regular;font-size:11px"><br style="font-family:Menlo-Regular;font-size:11px"><span style="font-family:Menlo-Regular;font-size:11px">Consider governmental actors where the outcome is political or newsworthy in nature. State Agency embraces open source, releases “State Agency's Super Something Yellow”. Bad actor modifies and gets a bad SASSY into the marketplace. Is there anything outside of trademark registration that would help State Agency save face and/or get injunctive relief more easily?</span><br style="font-family:Menlo-Regular;font-size:11px"><br style="font-family:Menlo-Regular;font-size:11px"><span style="font-family:Menlo-Regular;font-size:11px">Cheers!</span><span class="HOEnZb"><font color="#888888"><br style="font-family:Menlo-Regular;font-size:11px"><span style="font-family:Menlo-Regular;font-size:11px">Sean</span><div><span style="font-family:Menlo-Regular;font-size:11px"><br></span></div></font></span></div></div><br>_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@opensource.org">License-discuss@opensource.org</a><br>
<a href="https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss" rel="noreferrer" target="_blank">https://lists.opensource.org/cgi-bin/mailman/listinfo/license-discuss</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><a href="mailto:henrik.ingo@avoinelama.fi" target="_blank">henrik.ingo@avoinelama.fi</a><br>+358-40-5697354 skype: henrik.ingo irc: hingo<br><a href="http://www.openlife.cc" target="_blank">www.openlife.cc</a><br><br>My LinkedIn profile: <a href="http://fi.linkedin.com/pub/henrik-ingo/3/232/8a7" target="_blank">http://fi.linkedin.com/pub/henrik-ingo/3/232/8a7</a></div>
</div>