<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 21, 2013 at 4:59 AM, Gervase Markham <span dir="ltr"><<a href="mailto:gerv@mozilla.org" target="_blank">gerv@mozilla.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 21/02/13 05:40, Richard Fontana wrote:<br></div>
<div class="im"><br>
>> Who decides? That sounds like a recipe for lawyer argument. Is it better<br>
>> to refer to the OSI license list as of a certain date instead?<br>
><br>
> That was essentially what an earlier release did (IIRC). I'm really<br>
> trying to define what 'proprietary licensing' is and I don't know a<br>
> good way to do it. And the goal here isn't perfection, but rather to<br>
> ward off practitioners of certain kinds of business models. I just<br>
> want a way to signal "keep away" to a certain kind of potential<br>
> licensor. The definition doesn't have to be perfect for that purpose.<br>
><br>
> That said, I'm not satisfied that this can't be made better, including<br>
> perhaps in the way you've suggested.<br>
<br>
</div>I think that having a clearly defined list is much easier. Then it's<br>
pretty obvious to all. In the current set up, I can imagine someone<br>
wanting to take advantage of that clause thinking "Hmm, I don't think<br>
their pseudo-open license meets the OSD, but they do. So what now?"<br>
Pseudo-open is currently observed (if not common), and we should plan<br>
for it possibly remaining so.<br></blockquote><div><br></div><div style>What about the Fedora list? Or on any one of the Debian, OSI or Fedora lists? Even if you disagree with the judgment of a particular list it will be a very fringe case, and I agree with Gerv that certainty is better than uncertainty in this case.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> This is just a clarification of what kinds of things absolutely are<br>
> not 'Legal Notices'. It isn't meant to be exhaustive, but I did<br>
> recently add 'Powered by statements' because that is such a common<br>
> form in which I've seen the problematic condition.<br>
<br>
</div>I wonder if we can think of a more generic phrase. Or we could go for<br>
the slightly linguistically ugly '"Powered by"-style statements.' Or you<br>
could try leaning on the legal definition of what makes a valid<br>
copyright statement, and say you only have to preserve those.<br></blockquote><div><br></div><div style>I think the problem is that some licenses require preservation of "attribution" statements. That's not necessarily the same as the name of the copyright owner in the copyright notice, so we can't limit it to preserving copyright notice only. </div>
<div style><br></div><div style>Pam</div></div></div></div>