GPL vs MS EULA's
by
Gentoo+Fan
·
· Score: 5, Interesting
I know it's mostly apples to oranges, but considering how infrequently the GPL is updated comparing this with both the size and likely tweaking of a standard MS EULA would hopefully be a good arguing point with possible Linux converts. Anyone know of a repository of EULAs and how frequently they get updated?
Patents and compatiability?
by
m50d
·
· Score: 5, Interesting
Will this version become comptiable with licenses with patent clauses, like the apache, IBM and CPL licenses?
-- I am trolling
Changes to the GPL
by
KJACK98
·
· Score: 5, Interesting
For me the weaknesses that need to be addressed in the GPL are most definitely patents, the confusion around dynamic/static compiling + web services. Get rid of this issue of two licenses (GPL/LGPL/ or the new trend that is even more confusing GPL + Linking Clause?!?) which causes a lot of problems for reuse of code. Having a 'viral license' just scares corporate use of our code. Other issues are enforcement of trademarks, so that companies can have commercial offerings by offering a particular 'brand'. At the end of the day the license must continue to protect its most important aspect, that all code changes to the software must be contributed back - preferably in a free downloadable manner (mailing $15 for the source code when the binary is available free online goes against its principles).
Re:Changes to the GPL
by
GigsVT
·
· Score: 4, Interesting
See, the thing is, the GPL FAQ isn't the GPL. It's just sorta the way they see it.
The GPL FAQ has no legal weight, other than seeing what the FSF might sue you over and what they might not.
-- I've had enough abrasive sigs. Kittens are cute and fuzzy.
GPL Server Hole
by
SashaM
·
· Score: 4, Interesting
Hopefully they will plug the server hole. As it stands right now, the GPL makes no sense for server-side applications.
Forum to discuss new GPL, defensive patents, etc?
by
expro
·
· Score: 4, Interesting
I have significant code I have been working on for some time. I have placed GPL language at the top, etc. in anticipation that I would publish it as soon as I felt I and it were ready.
One thing stopping me is that the code has lots of quite new ideas in it that I feel could become quickly widespread in use, in some cases as an alternative to existing, increasingly encumbered and controlled, standards.
I feel that it may be good to take out lots of patent claims, not that I feel that offensive patent use is ever justified, but that I see Microsoft patent around such things as XML.
I would like to stop them or anyone else to the extent from patenting use of the technology for X or Y (as Microsoft does with XML, for example), when it is obvious to anyone that it is a technology that is general purpose in nature and should be open to all uses.
I need to discuss this sort of thing, preferrably on a forum with someone actively pursuing FSF agendas to talk about the pitfalls and what might be possible in this respect. I would be perfectly happy signing patent rights to a third party as long as they could be used defensively by myself and others to the widest extent possible.
(Let me make it clear that it would not be my intent to use such to control or enforce a particular usage in any way, as Sun or Microsoft, for example, often try to do when making a "public" grant).
Slashdot Mirror
I know it's mostly apples to oranges, but considering how infrequently the GPL is updated comparing this with both the size and likely tweaking of a standard MS EULA would hopefully be a good arguing point with possible Linux converts. Anyone know of a repository of EULAs and how frequently they get updated?
Will this version become comptiable with licenses with patent clauses, like the apache, IBM and CPL licenses?
I am trolling
For me the weaknesses that need to be addressed in the GPL are most definitely patents, the confusion around dynamic/static compiling + web services. Get rid of this issue of two licenses (GPL/LGPL/ or the new trend that is even more confusing GPL + Linking Clause?!?) which causes a lot of problems for reuse of code. Having a 'viral license' just scares corporate use of our code. Other issues are enforcement of trademarks, so that companies can have commercial offerings by offering a particular 'brand'. At the end of the day the license must continue to protect its most important aspect, that all code changes to the software must be contributed back - preferably in a free downloadable manner (mailing $15 for the source code when the binary is available free online goes against its principles).
Hopefully they will plug the server hole. As it stands right now, the GPL makes no sense for server-side applications.
I have significant code I have been working on for some time. I have placed GPL language at the top, etc. in anticipation that I would publish it as soon as I felt I and it were ready.
One thing stopping me is that the code has lots of quite new ideas in it that I feel could become quickly widespread in use, in some cases as an alternative to existing, increasingly encumbered and controlled, standards.
I feel that it may be good to take out lots of patent claims, not that I feel that offensive patent use is ever justified, but that I see Microsoft patent around such things as XML.
I would like to stop them or anyone else to the extent from patenting use of the technology for X or Y (as Microsoft does with XML, for example), when it is obvious to anyone that it is a technology that is general purpose in nature and should be open to all uses.
I need to discuss this sort of thing, preferrably on a forum with someone actively pursuing FSF agendas to talk about the pitfalls and what might be possible in this respect. I would be perfectly happy signing patent rights to a third party as long as they could be used defensively by myself and others to the widest extent possible.
(Let me make it clear that it would not be my intent to use such to control or enforce a particular usage in any way, as Sun or Microsoft, for example, often try to do when making a "public" grant).