I think, that GPLv3 is a license for which there came historical necessity.
Some people do not want their code to be used to lock devices. These people need a corresponding license.
And, I think that there is a historical necessity for the license, which does not allow to use the software by/for dictatorships/authoritarian regimes.
Because there might be someone who do not want let’s say his software to be used in order to prepare lists of political prisoners. I would not want to help even a soft regime.
The question which comes, then, who/how to decide which regime is authoritarian, which is dictatorship. Should the license contain direct pointers to the number of countries, or to refer to other organization’s assessments.
#software #free_software #open_sourge #gpl #license #code #regime #dictatorship #freedom
@{Մուլտիվակ Multivac* ; satenik@spyurk.am} @{imandes (իմանդէս) ; imandes@spyurk.am} #կրեածիվ֊դասակարգ #սեղան #ժամանց #խցիկ #մամիյա #քենոն #գնու #ջիփիէլ #ջիջիլ #օփենմոկո #կոբո #ռիչարդ֊դոկինզ #երեկոյ #վիքիմեդիա #թեյ #զրոյց #լուսանկար #նկար #հաւէս #creative-class #table #tea #evening #work #camera #mamiya #canon #gnu #gpl #openmoko #kobo #richard-dawkins #talk #evening #photo
No. I worry because there is open and #free source like #GPL, and then there’s open but a little less freer #CDDL, for example. It might be handy to know how tight the chains are held on their #proprietary or not-so-proprietary code. We saw how wonderfully CDDL worked for the #ZFS and the related lawsuits. I don’t see how simply being #OSD - compliant should be enough for me to prostrate myself at the alter of #open-source software, especially with the likes of even #Microsoft, #Oracle and others buzzing around trying to find ways to cleverly call something open while slipping in a poison pill if you do your own thing in the open. http://talk.maemo.org/showpost.php?p=962391&postcount=33
#bsd is #gpl compatible license. that means that.
That is, their code can be combined with a program under the GPL without conflict (the new combination would have the GPL applied to the whole)
which means I can fork BSD licensed program and distribute by work under GPL (: #nice
https://spyurk.am/posts/83694#
#gpl vs #bsd talk where I participate
libvlc (#vlc player engine) changed it’s license from #gpl to #lgpl. http://www.videolan.org/press/lgpl.html http://www.jbkempf.com/blog/post/2012/I-did-it This will allow to use libvlc in proprietary applications. I don’t think that’s a good idea. Moreover, there is an fsf paper about why not use lgpl for you library:
Proprietary software developers have the advantage of money; free software developers need to make advantages for each other. Using the ordinary GPL for a library gives free software developers an advantage over proprietary developers: a library that they can use, while proprietary developers cannot use it.
http://www.gnu.org/philosophy/why-not-lgpl.html #gpl #free-software #lgpl