<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If a community of people is writing write some GPL'd software (such as<br>
the Liunx kernel), and I come and make an unfree, proprietary fork of<br>
it, then my fork won't keep track of the changes in the<br>
community-developed version. If I do want to catch up with changes to<br>
it, I'll have to go through a labourious process of re-integrating my<br>
changes with their changes, and I'll have to do this every time I want<br>
to use their new changes. It probably won't be worth my effort to do<br>
this, so it would make more sense for me to make my changes part of<br>
the public community-developed version.<br></blockquote><div><br>Didn't Apple recently contribute for exactly this reason? The "Free" code they use is under BSD (or similar license?) but if they contribute patches back to the community, Apple get those patches maintained for free, or at the very least future patches elsewhere are aware of them and less likely to break something. <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There are many FOSS projects such as Python or Apache that use<br>
MIT-like licences and suffer no significant bad conseqences.<br>
<div class="im"><br>
--<br>
Philip Hunt, <<a href="mailto:cabalamat@googlemail.com">cabalamat@googlemail.com</a>><br>
Campaigns Officer / Press Officer, Pirate Party UK<br>
____________________________________________________<br>
</div><div><div></div><div class="h5">Pirate Parties International - General Talk<br>
<a href="mailto:pp.international.general@lists.pirateweb.net">pp.international.general@lists.pirateweb.net</a><br>
<a href="http://lists.pirateweb.net/mailman/listinfo/pp.international.general" target="_blank">http://lists.pirateweb.net/mailman/listinfo/pp.international.general</a><br>
</div></div></blockquote></div><br>