<div dir="ltr"><br><div class="gmail_extra">On Sun, Feb 23, 2014 at 12:47 AM, anatoly techtonik <span dir="ltr"><<a href="mailto:techtonik@gmail.com" target="_blank">techtonik@gmail.com</a>></span> wrote:<br><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Sat, Feb 22, 2014 at 8:45 PM, Aaron Wolf <<a href="mailto:wolftune@gmail.com">wolftune@gmail.com</a>> wrote:<br>
>><br>
>> What are you protecting from with AGPL?<br>
><br>
</div><div class="">> The purpose of AGPL is to block software from becoming proprietary.<br>
<br>
</div>I believe it is far-fetched argument. Nobody can turn what is already written<br>
under non-restrictive license to become proprietary. They can build something<br>
on top of it - yes - is it what AGPL supporters afraid of? But they<br>
can not force<br>
people to use their paid and proprietary versions and these people are free to<br>
develop their own branch as before.<br></blockquote><div><br><br></div><div>Sorry, I did not mean to imply that the software would be subsumed in proprietary versions. All I meant was, the purpose of AGPL is to hamper the development of <i>any</i> proprietary software.<br>
<br>It only works, of course, if enough people in the community embrace it. A large community embracing AGPL can do as well as a large community embracing a permissive license. In that case, AGPL will hamper any proprietary forks and thus the net freedom will be higher since the creation of proprietary forks is a negative for freedom.<br>
<br></div><div>If the community will <i>not</i> embrace the AGPL and will only embrace permissive licenses, then using a permissive license may be better for freedom. So while the best thing for overall freedom is for <i>everyone</i> to together embrace the AGPL, <i>if </i>that is not possible, then the balance of compromises must be weighed. Hence, it is a tactical question.<br>
<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I have a good understanding of licensing issues and can even explain some<br>
of them. I just want to clarify the exact position of NPO accounting<br>
project members to ensure that I got it right that people are afraid of.<br>
<div class=""><br></div></blockquote><div><br></div><div>I cannot speak for others here, but it is inappropriate to assume a position of fear. License choice may be one made from other thoughtful, pragmatic, idealogical, dogmatic, tactical, or other reasons.<br>
</div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
> It is also consistent to say that you care about freedom and believe that<br>
> AGPL is less free than CC0, but only if you also recognize that proprietary<br>
> software is obviously much less free. If you're ok with proprietary, you<br>
> should be ok with AGPL, which is clearly much much more free than<br>
> proprietary.<br>
<br>
</div>Let's talk without "only if".<br>
<br>
For my accounting purposes I am not ok with limiting my personal freedom<br>
and the freedom of others in either way.<br>
<div class=""><br></div></blockquote><div><br></div><div>Sure, and as I said, that is the consistent respectable position. Just be aware of the need to distance yourself then from those who oppose copyleft <i>in order</i> to advocate for proprietary interests.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
> But you seem to be arguing not that AGPL is bad for freedom but merely that<br>
> it isn't a good tactic for making the software successful. That's a fine<br>
> argument. Not everyone may agree. It's complex how to choose the right<br>
> compromises.<br>
<br>
</div>Right. But the project had goal, and didn't reach it. The AGPL tactic already<br>
failed, before the battle began. I don't really care that the project chooses to<br>
continue slaughter soldiers anyway, but just want people to know the opinion.<br>
<div class=""><br></div></blockquote><div><br></div><div>If the AGPL has failed to get support from the community and the battle is truly lost, that is an important thing to recognize. I am not convinced this is the case, but I agree that many aspects of the situation do not look good. I think it is more important here to bring up concerns than to be simplistically conclusive in your claims. It's an important concern to be addressed. Maybe you're right. I just don't think it's as simple as you make it out to be.<br>
</div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
> Either way, please don't conflate the words "commercial" and "proprietary"<br>
> though. It is perfectly fine for Free Software to be commercial and stay<br>
> free-as-in-freedom.<br>
<br>
</div>I don't care about both of those. I care about limiting the freedom of people<br>
to maintaining and even selling their own modification that may not be useful<br>
for the main line at all.<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br></div><div>AGPL does <i>not</i> restrict selling of software in principle. Yes, in practice, it is harder to sell software if you don't use your government-enforced monopoly control to do it.<br>
<br></div><div>Respectfully,<br></div><div>Aaron<br></div></div><br></div></div>