Mit „gpl“ getaggte Nachrichten, Seite 3

lnxw48 vim , ektoplazm

@ektoplazm !Vim is indeed free software. The license is (by declaration) #GPL compatible (v2 or later). #Vim license: http://url.federati.net/klhqm

fsf

Thank you to @OpenSourceOrg for endorsing #FSF and @Conservancy #GPL enforcement https://u.fsf.org/1gs #FSF30

fsf

Thank you to @OpenSourceOrg for endorsing #FSF and @Conservancy #GPL enforcement https://u.fsf.org/1gs #FSF30

fsf

Creative Commons BY-SA 4.0 declared one-way compatible with #GNU #GPL version 3 https://u.fsf.org/1gl @creativecommons

fsf fsf

@fsf @conservancy release Principles for Community-Oriented GPL Enforcement https://u.fsf.org/1ft #gpl #gnu #fsf30

lnxw48

In response to a talk at #OSCON, @cwebber@identi.ca Christopher Allan Weber writes "Why I Am Pro-GPL" http://url.federati.net/GA8Je #gpl #agpl #lgpl #apache #bsd #mit

lnxw48

In response to a talk at #OSCON, @cwebber@identi.ca Christopher Allan Weber writes "Why I Am Pro-GPL" http://url.federati.net/GA8Je #gpl #agpl #lgpl #apache #bsd #mit

lnxw48 oldnds

@nds If a project plans to choose an OS license, they could start by releasing under both #GPL and #Apachev2.0

lnxw48 dragnucs

@dragnucs Assuming that there were no other copyright holders to consult, new versions can be licensed under whatever license they choose. It should still be possible (for some length of time) to obtain #GPL version's source.

fsf

Kuhn: With a fundamental legal disagreement about the requirements of the GPL, forking, not courts, can be the best solution. #lp2015 #GPL #Stand-Off https//u.fsf.org/193

larjona

I've donated to @Conservancy to support #freesoftware + #GPL Enforcement: http://ur1.ca/jw3m1 - each donation is matched up to $50K

lnxw48 Self Hosting , mmn

@mmn One of my concerns, even though I have not personally used the Gitorious !selfhost ed software, is exactly that: would there be enough interest to keep development going. I, too, generally prefer the #GPL family of licenses. #LGPL #AGPL

lnxw48 xrevan86

@xrevan86 For those who wish to use community contributions, yet lock them up in proprietary “don’t touch this” licenses, the #GPL family is indeed frightening. It should have no such effect if one’s intentions are not so anti-user, but even some #FLOSS advocates hate #copyleft.

lnxw48 nawi

@nawi I can’t see context via #xmpp, but it would be good for a #GPL / #AGPL / #LGPL project to have multiple authors who retain their copyrights. Makes it harder to switch licenses later and protects users better.

cyberkiller drak

@drak long live the #GPL ! :-)

cyberkiller drak

@drak long live the #GPL ! :-)