Re: [License-discuss] open source licenses addressing malicious derivatives

Hi Henrik, Thanks for the inputs. I have been trying to make the case that trademark is adequate to address injunctive relief needs, but needed to survey the landscape of alternative possibilities (and their downsides). As it is, the best defensive argument is looking to be license

Re: [License-discuss] open source licenses addressing malicious derivatives

On Wed, Jun 22, 2016 at 10:40 PM, Christopher Sean Morrison wrote: > > 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. Same for MPL 1.1, but it was removed in MPL 2.0. Somehow similar

Re: [License-discuss] open source licenses addressing malicious derivatives

Hi Christopher 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.

Re: [License-discuss] open source licenses addressing malicious derivatives

Hi Charles, Thanks for the response and apologies in advance on the html-encoding; responding from a web client that doesn't let me recode the message. Judges are likely to support reasonable contractual terms, but they will evaluate the specific circumstances at hand and have no obligation

Re: [License-discuss] open source licenses addressing malicious derivatives

Hi, Sean-- On Jun 22, 2016, at 4:40 PM, Christopher Sean Morrison wrote: > 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? At least for the US, injunctive relief is a

[License-discuss] open source licenses addressing malicious derivatives

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: 1) which existing OSI-approved licenses impose derivative requirements