5 ms·
> "I actually think we should talk about GPL enforcement at the kernel summit, because I think it's an important issue," Torvalds gently began, "but we should t
by jcranmer 5y ago
> "I actually think we should talk about GPL enforcement at the kernel summit, because I think it's an important issue," Torvalds gently began, "but we should talk about it the way we talk about other issues: among kernel developers. No lawyers present unless they are in the capacity of a developer and maintainer of actual code, and in particular, absolutely not the Software Freedom Conservancy." - Linus Torvalds
This is fundamentally a pretty stupid take on the issue, to be honest. I can understand why Linus might want to ignore the SF Conservancy in particular here, but banning all lawyers in general is a stupid idea when you're discussing legal documents (that's what software licenses are). It's akin to saying "let's talk about why our car isn't working but NO CAR MECHANICS ALLOWED."
If what you're talking about is legal issues, you absolutely should involve lawyers, and generally earlier is better. This is particularly true when intellectual property is involved, as neglecting to take certain actions can completely foreclose future legal remedies.
- throwaway82652 5y agoFrom the lawyers I've spoken to about this, Linus's view on the GPL and the chosen enforcement strategy has long been known to be nonsense. But nothing will change as long as the kernel developers are intentionally burying their head in the sand and acting like they know better than the legal system.
- mistrial9 5y ago> has long been known to be nonsense could any statement be less substantiated than pure FUD like that?
- onphonenow 5y agoI'm just curious here. If I as a developer want to license my code a certain way (and enforce that license in a certain way) what authority do these lawyers have to tell me I'm "stupid". Especially if my approach has single handedly created the largest body of copyleft / collaborative / open source software out there with massive amounts of actual collaboration. The irony is so strong here. Basically jerks, who can't get along with others (including each other, witness the battles between SFC and SFLC etc etc) with little value creation themselves want to force their view on others, even though folks have already voted with their feet. By all means create the Affero GPLv3. Try to get folks to write software for it. That's fine. But don't pretend to be on some moral high ground speaking for developers / creators who wrote the code. Let them speak for themselves. And don't go back and having lost the effort to get Affero GPLv3 or whatever adopted close the various SAAS and Tivo loopholes, go back and say some old license has these terms.
- throwaway82652 5y ago>If I as a developer want to license my code a certain way (and enforce that license in a certain way) what authority do these lawyers have to tell me I'm "stupid". Are you willing to represent yourself in court? If the answer is no, then that's an admission you are stupider than a lawyer when it comes to legal matters. Nothing wrong with it, I have no problem admitting it myself. Let the programmers handle the programming and let the lawyers handle the law.
- onphonenow 5y agoI'd skip the name calling. You fail to understand how copyright works. If I'm the creator of the work, I have the copyright to it. And yes, I'd be happy to represent myself if SFC came along and told me I could or couldn't do something with the code I wrote because that makes no sense. I can choose a license, I can dual license, I can re-license future releases and I can stop providing updates under any of those licenses. So sure, if you and the SFC want to go after me for my code, go for it. There seems to be a modern confusion that the folks NOT doing any of the work in writing code have all sorts of rights with respect to it (or time of a dev to fix their bugs). False.
- jcranmer 5y ago> If I'm the creator of the work, I have the copyright to it. Not necessarily. For example, work for hire, or copyright being assigned to the employer. Or maybe the work itself isn't copyrightable in the first place. There's even a fun provision where US government work doesn't have any copyright in the first place! You might also have transferred the copyright of your work after you created it in a way which doesn't give you any retained rights.
- mistrial9 5y agoin the USA there is strong copyright for the author of the work in question. Work-for-hire is well understood in Chapter 1 of any book on that topic. Secondly, a court appearance is not required to be an author and therefore copyright holder. Suggestions that "if you are not able to make a court appearance then XYZ and etc" .. is fallacious to start with, condescending and sounds a lot like an attorney arrogance. NOLO Press, read my lips
- dragonwriter 5y ago> can understand why Linus might want to ignore the SF Conservancy in particular here, but banning all lawyers in general is a stupid idea when you're discussing legal documents It's a perfectly valid approach if your goal is to discuss developer's concerns/priorities/goals for GPL enforcement and not legal tactics to achieve some known set of goals, and particularly if your goal is to avoid a talk at mixed purposes because some people have goals in mind that are not agreed on and are trying to talk tactics while other people are trying to talk goals and no one gets anywhere.