Skip to contentSkip to conversation

GPL defense issues

Ksummit-discuss Karen Sandler 18 participants 41 messages Aug 24, 2016 – Aug 28, 2016

lore
Share & tools
lore
#0 lore raw

I know that it's somewhat late in this process, but I was encouraged by a few kernel developers here at LinuxCon to propose a discussion about enforcement at the summit. There has been a lot of news recently (Patrick McHardy's enforcement, the Principles of Community Oriented Enforcement, VMware dismissal/appeal) resulting in quite a bit of speculation and discussion.

I think a Q&A on where things stand on all of these matters would make sense and in that context also have a discussion about the GPL and enforcement generally if there's time. It seems to me by the number of questions I've been getting that many more kernel devs are interested in these topics than ever before, and many who have previously preferred not to think about licensing are starting to change their minds.

There have been so many discussions about these topics by industry lawyers and executives behind closed doors, but developers have been generally kept out of the loop. Understanding what's going on and figuring out if there's consensus on some of these issues is likely to help the kernel community deal with the impact down the road. At the very least, I think kernel developers each need to decide how they feel about GPL enforcement as silence and inaction is as much of a choice as voicing a view. From what I see, the timing on this discussion has become critical.

thanks!
karen

Karen M. Sandler
Executive Director, Software Freedom Conservancy
__________
Become a Supporter today! http://sfconservancy.org/supporter/

#1 lore raw
Quoted 4 lines · Karen Sandler

There have been so many discussions about these topics by industry lawyers and executives behind closed doors, but developers have been generally kept out of the loop.

That's a very unfair comparison, "lawyers and executives" always are "behind closed doors" as that's the way business works (and has to for legal reasons as you know). One can say the same thing about any type of company meeting where anything is discussed.

And "developers" are not being kept out of any "loop" here, please, lots of us know exactly what is going on here.

Quoted 3 lines

Understanding what's going on and figuring out if there's consensus on some of these issues is likely to help the kernel community deal with the impact down the road.

The impact of what? And getting "consensus" from 5000+ people is pretty impossible on any kind of topic at all :)

Quoted 3 lines

At the very least, I think kernel developers each need to decide how they feel about GPL enforcement as silence and inaction is as much of a choice as voicing a view.

That's not fair, it's implying that our current way of doing this type of thing is somehow not working. Remember, we have done something that no other group has ever done before, so please don't discount that we know how to handle stuff like this. Sometimes not making a public statement is actually the correct thing to do.

Quoted 1 line

From what I see, the timing on this discussion has become critical.

Why is things "critical" now vs. the situation we had 5, 10, or 15 years ago?

Anyway, we try to stick to technical topics from the developers of the kernel for the kernel summit wherever possible, and I think that the deadline for proposing new topics has passed, so I don't think there's much that can be done this late in the process.

thanks,

greg k-h

#2 lore raw
Quoted 6 lines · Greg KH
Quoted 4 lines · Karen Sandler

There have been so many discussions about these topics by industry lawyers and executives behind closed doors, but developers have been generally kept out of the loop.

Quoted 7 lines

That's a very unfair comparison, "lawyers and executives" always are "behind closed doors" as that's the way business works (and has to for legal reasons as you know). One can say the same thing about any type of company meeting where anything is discussed.

And "developers" are not being kept out of any "loop" here, please, lots of us know exactly what is going on here.

I'm of course not talking about internal company meetings, but rather invite-only backchannels where lawyers and executives are invited but developers are typically not. I know, Greg, that you and a few other developers do cross between these worlds, but most Linux developers I've spoken to do not. This session is an opportunity for those developers to hear about what's been going on in the last year.

Quoted 9 lines
Quoted 3 lines

At the very least, I think kernel developers each need to decide how they feel about GPL enforcement as silence and inaction is as much of a choice as voicing a view.

That's not fair, it's implying that our current way of doing this type of thing is somehow not working. Remember, we have done something that no other group has ever done before, so please don't discount that we know how to handle stuff like this. Sometimes not making a public statement is actually the correct thing to do.

I absolutely agree that sometimes making a public statement is not the right thing to do. I'm not suggesting that in this session we plan a public statement or pressure anyone to do so in the future. Rather, I suggest that we discuss among the Linux developer community what public statements have been made, what semi-private discussions have occurred, and discuss as a group how this impacts Linux community.

Quoted 4 lines
Quoted 1 line

From what I see, the timing on this discussion has become critical.

Why is things "critical" now vs. the situation we had 5, 10, or 15 years ago?

5, 10, or 15 years ago we didn't have Patrick McHardy engaging in enforcement without coordinating with the rest of the netfilter team. Also, the recent VMware court ruling and its implications are new this year; the community of copyright holders should examine it and discuss it.

Quoted 4 lines

Anyway, we try to stick to technical topics from the developers of the kernel for the kernel summit wherever possible, and I think that the deadline for proposing new topics has passed, so I don't think there's much that can be done this late in the process.

Three people from the TAB, two of which are on this committee suggested yesterday that I submit this session and Ted's original CFP says:
"Obviously, if new topics come up after that, please still send them to us!"

Finally, some of the issues here are very technical. In the VMware ruling, the Court claimed difficulty in understanding how copyright holding is documented in Linux. This is a problem that can be mitigated and even solved with technical solutions that we can discuss in this session.

karen

#3 lore raw
Quoted 15 lines · Karen Sandler
Quoted 6 lines · Greg KH
Quoted 4 lines · Karen Sandler

There have been so many discussions about these topics by industry lawyers and executives behind closed doors, but developers have been generally kept out of the loop.

Quoted 7 lines

That's a very unfair comparison, "lawyers and executives" always are "behind closed doors" as that's the way business works (and has to for legal reasons as you know). One can say the same thing about any type of company meeting where anything is discussed.

And "developers" are not being kept out of any "loop" here, please, lots of us know exactly what is going on here.

Quoted 6 lines

I'm of course not talking about internal company meetings, but rather invite-only backchannels where lawyers and executives are invited but developers are typically not. I know, Greg, that you and a few other developers do cross between these worlds, but most Linux developers I've spoken to do not. This session is an opportunity for those developers to hear about what's been going on in the last year.

Personally, I've seen numerous examples of people not having heard any of the background on these issues. I'd love to see this topic covered far and wide. Not everyone gets to go to LLW or similar, or otherwise has access to much of the information about such topics.

The session in a past Kernel Summit providing timely information on the ongoing court case seemed quite popular.

I think a session providing information on current legal issues and discussing implications of them seems quite relevant, as well as fitting the criteria of "something that doesn't work as a mailing list discussion". *Especially* if the session includes discussion of practical implications and practices.

Linux has pioneered many best-practices, such as the DCO. By both interest and necessity, we have to deal with issues like these. Let's talk about them, and start trying to find solutions for the next round of issues.

- Josh Triplett

#4 lore raw
Quoted 6 lines · Josh Triplett
Quoted 4 lines · Karen Sandler
Quoted 2 lines · Greg KH

And "developers" are not being kept out of any "loop" here, please, lots of us know exactly what is going on here.

Quoted 6 lines
Quoted 6 lines

I'm of course not talking about internal company meetings, but rather invite-only backchannels where lawyers and executives are invited but developers are typically not. I know, Greg, that you and a few other developers do cross between these worlds, but most Linux developers I've spoken to do not. This session is an opportunity for those developers to hear about what's been going on in the last year.

Definitely - there are discussions but they're hardly wide discussions, there's some people with good access to information but it's really not that widespread.

Quoted 4 lines

Personally, I've seen numerous examples of people not having heard any of the background on these issues. I'd love to see this topic covered far and wide. Not everyone gets to go to LLW or similar, or otherwise has access to much of the information about such topics.

Speaking for myself I have no idea what LLW is - I'm guessing it's *not* Low Level Waste (the UK organization for handling nuclear waste) which is what Google suggests!

Quoted 4 lines

Linux has pioneered many best-practices, such as the DCO. By both interest and necessity, we have to deal with issues like these. Let's talk about them, and start trying to find solutions for the next round of issues.

I agree, and there's also the fact that good practice is often helped by understanding so when we have the opportunity to share things in a wider but still not public environment that seems like a great use of Kernel Summit time.

#5 lore raw
In reply to Josh Triplett

I don't expect to be there, but I do agree with several others that this is a good & relevant topic for KS. I expect that most people are not aware of closed meetings and their topics and decisions.

Signature · 1 line
~Randy
#6 lore raw
In reply to Josh Triplett
Quoted 23 lines · Josh Triplett
Quoted 15 lines · Karen Sandler
Quoted 6 lines · Greg KH
Quoted 4 lines · Karen Sandler

There have been so many discussions about these topics by industry lawyers and executives behind closed doors, but developers have been generally kept out of the loop.

Quoted 7 lines

That's a very unfair comparison, "lawyers and executives" always are "behind closed doors" as that's the way business works (and has to for legal reasons as you know). One can say the same thing about any type of company meeting where anything is discussed.

And "developers" are not being kept out of any "loop" here, please, lots of us know exactly what is going on here.

Quoted 6 lines

I'm of course not talking about internal company meetings, but rather invite-only backchannels where lawyers and executives are invited but developers are typically not. I know, Greg, that you and a few other developers do cross between these worlds, but most Linux developers I've spoken to do not. This session is an opportunity for those developers to hear about what's been going on in the last year.

Quoted 7 lines

Personally, I've seen numerous examples of people not having heard any of the background on these issues. I'd love to see this topic covered far and wide. Not everyone gets to go to LLW or similar, or otherwise has access to much of the information about such topics.

The session in a past Kernel Summit providing timely information on the ongoing court case seemed quite popular.

Yes, and I know a number of people who "got in trouble" after the fact that they attended it. So we need be aware that if the kernel summit starts discussing legal issues, we open ourselves up to a much wider range of "issues" than we have ever had before.

Quoted 5 lines

I think a session providing information on current legal issues and discussing implications of them seems quite relevant, as well as fitting the criteria of "something that doesn't work as a mailing list discussion". *Especially* if the session includes discussion of practical implications and practices.

Will your employer allow you to attend something like this? If so, great, but again we would need to warn people ahead of time to get that type of approval :(

thanks,

greg k-h

#7 lore raw
Quoted 29 lines · Greg KH
Quoted 28 lines · Josh Triplett
Quoted 15 lines · Karen Sandler
Quoted 6 lines · Greg KH
Quoted 4 lines · Karen Sandler

There have been so many discussions about these topics by industry lawyers and executives behind closed doors, but developers have been generally kept out of the loop.

Quoted 7 lines

That's a very unfair comparison, "lawyers and executives" always are "behind closed doors" as that's the way business works (and has to for legal reasons as you know). One can say the same thing about any type of company meeting where anything is discussed.

And "developers" are not being kept out of any "loop" here, please, lots of us know exactly what is going on here.

Quoted 6 lines

I'm of course not talking about internal company meetings, but rather invite-only backchannels where lawyers and executives are invited but developers are typically not. I know, Greg, that you and a few other developers do cross between these worlds, but most Linux developers I've spoken to do not. This session is an opportunity for those developers to hear about what's been going on in the last year.

Personally, I've seen numerous examples of people not having heard any of the background on these issues. I'd love to see this topic covered far and wide. Not everyone gets to go to LLW or similar, or otherwise has access to much of the information about such topics.

Quoted 5 lines
Quoted 2 lines

The session in a past Kernel Summit providing timely information on the ongoing court case seemed quite popular.

Yes, and I know a number of people who "got in trouble" after the fact that they attended it.

Huh, because of the last discussion at kernel summit? Holy spaghetti monster!

Quoted 9 lines
Quoted 5 lines

I think a session providing information on current legal issues and discussing implications of them seems quite relevant, as well as fitting the criteria of "something that doesn't work as a mailing list discussion". *Especially* if the session includes discussion of practical implications and practices.

Will your employer allow you to attend something like this? If so, great, but again we would need to warn people ahead of time to get that type of approval :(

Case in point -- can a Linux developer working for a company really care about GPL enforcement or has this right been taken away by a lot of companies ? Is it a thing only a few can care for ? What are the implications ? Do we care ? Do you ?

My opinion of course is you should be able to care. The fact that this topic can be an issue *is an issue* in and of itself. My own logistical approach to addressing this however is a bit different then -- those that should care should just simply join SFC Conservancy. If you are not sure then talk to one of us that is part of the alliance, or that do care. If you can't talk to us because your employer does want you to talk to us or join SFC -- well snap. There's obviously only a few options then.

Luis

#8 lore raw
In reply to Greg KH
Quoted 6 lines
Quoted 3 lines

The session in a past Kernel Summit providing timely information on the ongoing court case seemed quite popular.

Yes, and I know a number of people who "got in trouble" after the fact that they attended it.

This is really sad news :( That put aside, I don't see the conclusion that we shouldn't have topics like this at KS then. As this thread shows, there is enough interest from individuals (or employees speaking as individuals or companies being fine with it) to justify this topic, or?

Quoted 3 lines

So we need be aware that if the kernel summit starts discussing legal issues, we open ourselves up to a much wider range of "issues" than we have ever had before.

I'd think the variety of opinions will make it impossible to reach a common statement or conclusion anyhow (as this thread shows as well). But to inform (interested) people what is happening right now and discuss it, why not? What kind of issues could come from that?

#9 lore raw
Quoted 8 lines · Wolfram Sang
Quoted 3 lines

So we need be aware that if the kernel summit starts discussing legal issues, we open ourselves up to a much wider range of "issues" than we have ever had before.

I'd think the variety of opinions will make it impossible to reach a common statement or conclusion anyhow (as this thread shows as well). But to inform (interested) people what is happening right now and discuss it, why not? What kind of issues could come from that?

When someone involved in a legal suit talks to other people about it, those other people, in some countries/jurisdictions, can then be called in to testify / be disposed as part of that suit by the other member of it.

I do my best to _never_ have to be disposed in anything, and so should everyone else, as what can be asked in that can be _very_ wide ranging and is almost always used in ways that you never want or intended it to be.

And if you work for a company, you can be seen as a company representative and all sorts of other things come into play very quickly.

I served on a Grand Jury in the US for a while, so I've seen how the legal system can work. It can be arbitrary and unfair at times, unfortunately.

Talk to any lawyer with experience in litigation for lots of stories if you are curious.

So please be careful,

greg k-h

#10 lore raw
Quoted 19 lines · Greg KH
Quoted 6 lines · Wolfram Sang
Quoted 5 lines

So we need be aware that if the kernel summit starts discussing legal
issues, we open ourselves up to a much wider range of "issues" than we
have ever had before.

Quoted 6 lines

I'd think the variety of opinions will make it impossible to reach a
common statement or conclusion anyhow (as this thread shows as well).
But to inform (interested) people what is happening right now and discuss it, why not? What kind of issues could come from that?

When someone involved in a legal suit talks to other people about it, those other people, in some countries/jurisdictions, can then be called in to testify / be disposed as part of that suit by the other member of it.

Quoted 4 lines

I do my best to _never_ have to be disposed in anything, and so should everyone else, as what can be asked in that can be _very_ wide ranging and is almost always used in ways that you never want or intended it to be.

To clarify for everyone: the specific danger here is that if we have a discussion on legal issues, any statement you make as part of the discussion is discoverable as evidence in a court proceeding, meaning that if one side or the other thinks whatever you said can help them, they can call you to repeat it in court. Worse still, such a statement could potentially be portrayed as "the opinion of the community" if we're not careful. Lawyers become trained to recognise what is safe to say in this regard and what isn't, but we, as kernel developers, aren't used to guarding our opinions in this way.

Everyone has to bear this in mind, and that's why, when Christoph gave his statement about VMware, we didn't actually allow any discussion.

The way companies escape from this is to have a corporate lawyer be part of the conversation so it's protected under attorney client privilege. However, we have no such protections. (In case you're wondering, the lawyer who's present actually has to be your counsel, it's not enough that they simply be a lawyer).

James

#11 lore raw
In reply to Greg KH
Quoted 4 lines · Greg KH

When someone involved in a legal suit talks to other people about it, those other people, in some countries/jurisdictions, can then be called in to testify / be disposed as part of that suit by the other member of it.

Perhaps I am confused - are there recordings of kernel summit sessions? Is attendance recorded? I don't see how participating in a closed door discussion here by folks who want to do so is any different risk-wise than discussions happening behind other closed doors.

It's true that someone can be called (by subpoena or other mechanisms in various jurisdictions) to be deposed, often whether or not they are disposed to doing so :)

But I urge caution - you stated in an earlier email which is publicly archived:

Quoted 1 line

lots of us know exactly what is going on here.

Unless I've misunderstood how the kernel summit works, I think an unrecorded invitation only conversation is much lower risk than a substantive discussion in writing, which is why I propose it.

I note that many developers have a personal stake in the kernel, and not a lot of places to have these discussions. One of the reasons I'm so dedicated to Conservancy's coalition, enforcing pursuant to stated principles and am resigned to bringing last resort law suits is that otherwise these issues will get decided in law suits between companies. There, GPL interpretation will be collateral damage.

I think we should start the session by explaining possible risks for those attending and encouraging them to seek legal counsel, which obviously this session won't provide.

karen

#12 lore raw
Quoted 5 lines · Karen Sandler

Perhaps I am confused - are there recordings of kernel summit sessions? Is attendance recorded? I don't see how participating in a closed door discussion here by folks who want to do so is any different risk-wise than discussions happening behind other closed doors.

There are no recordings of kernel summits, but who the attendees of the kernel summit is public knowledge, and there is generally photographic evidence. :-)

	     https://lwn.net/Articles/662699/

It's true that an unrecorded conversaion with 75+ of your best is "safer" (and a hallway conversation with a handful of people is even safer), but nothing is risk-free, and the risks can come in multiple dimensions. I encourage folks to talk to their corporate counsels for legal, because nobody else can give you that legal advice.

One of the things which very much worries me is the open scope of the proposal. e.g., let's have "discussions".

If there was a concrete proposal to consider, it would be much easier for people to evaluate whether or not (a) it would be considered safe for them to be in the room, and (b) whether it would be safe for them to participate in the discussion.

In the ideal world, said proposal would have already received signoffs from a number of General Counsels from most of our employers, and we would be looking for the community assent to that proposal before we went ahead with it.

If you have such a proposal, I would suggest bringing it to the attention of Mike Dolan and Karen Cooperhaven who are lawyers from the Linux Foundation (and since Linus and Greg works for the LF, they can provide legal advice to them :-). If it makes sense, they can help with trying to circulate proposals to the various LF members' GC's. There are also a number of of the TAB that are quite well informed in this area, if you are less comfortable talking to lawyers right off the bat.

Cheers,

- Ted

P.S. It would be a lot easier for both the progam committee and your lawyers to evaluate whether or not it would make sense for invidual engineers to attend such a session is if there was concrete proposal on the table, not only because the risks are much easier to evaluate, but the upside benefits of such a session are also much easier to consider. It also significantly improves the chances of concrete, positive results afterwards!

#13 lore raw
In reply to Karen Sandler
Quoted 15 lines · Karen Sandler
Quoted 6 lines · Greg KH
Quoted 4 lines · Karen Sandler

There have been so many discussions about these topics by industry lawyers and executives behind closed doors, but developers have been generally kept out of the loop.

Quoted 7 lines

That's a very unfair comparison, "lawyers and executives" always are "behind closed doors" as that's the way business works (and has to for legal reasons as you know). One can say the same thing about any type of company meeting where anything is discussed.

And "developers" are not being kept out of any "loop" here, please, lots of us know exactly what is going on here.

Quoted 6 lines

I'm of course not talking about internal company meetings, but rather invite-only backchannels where lawyers and executives are invited but developers are typically not. I know, Greg, that you and a few other developers do cross between these worlds, but most Linux developers I've spoken to do not. This session is an opportunity for those developers to hear about what's been going on in the last year.

But how are you going to present this if those were "closed meetings"? Honestly, I'm curious?

Quoted 10 lines
Quoted 4 lines
Quoted 1 line

From what I see, the timing on this discussion has become critical.

Why is things "critical" now vs. the situation we had 5, 10, or 15 years ago?

5, 10, or 15 years ago we didn't have Patrick McHardy engaging in enforcement without coordinating with the rest of the netfilter team. Also, the recent VMware court ruling and its implications are new this year; the community of copyright holders should examine it and discuss it.

15 years ago we had tons of closed source kernel drivers being created and shipped by companies like IBM and Intel. Without having to "enforce the license" we converted and changed them such that they are now our most ardent supporters.

10 years ago we had companies try to use the "GPL condom" defense to ship closed source kernel modules. We got that taken care of in ways that had nothing to do with legal methods.

Yes, Patrick is not a good thing to have happen, but as numerous of us have said to the companies involved, "let us know if we can help out" and so far they have refused to do so. So unless that happens, there's not much we can do as a community.

thanks,

greg k-h

#14 lore raw
In reply to Greg KH
Quoted 4 lines · Greg KH

Anyway, we try to stick to technical topics from the developers of the kernel for the kernel summit wherever possible, and I think that the deadline for proposing new topics has passed, so I don't think there's much that can be done this late in the process.

Hm, I always thought the point of KS is to talk about process, painpoints in the same and other topics of larger scale. Personally I think Karen's topic fits into this, and I think it would be interesting (at least for me). The pure technical topics are interesting to keep up on general things, but lwn.net does a great job at covering these wherever they happen - no reason for me to fly around the globe for those. At least that's been my experience with the past few KS, I've always took home a lot more from the process/more general sessions than the latest deep technical topic. Might just be that gfx folks are somewhat in a world of their own. -Daniel

Signature · 3 lines
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
#15 lore raw
Quoted 6 lines · Daniel Vetter
Quoted 4 lines · Greg KH

Anyway, we try to stick to technical topics from the developers of the kernel for the kernel summit wherever possible, and I think that the deadline for proposing new topics has passed, so I don't think there's much that can be done this late in the process.

Quoted 10 lines

Hm, I always thought the point of KS is to talk about process, painpoints in the same and other topics of larger scale. Personally I think Karen's topic fits into this, and I think it would be interesting (at least for me). The pure technical topics are interesting to keep up on general things, but lwn.net does a great job at covering these wherever they happen - no reason for me to fly around the globe for those. At least that's been my experience with the past few KS, I've always took home a lot more from the process/more general sessions than the latest deep technical topic. Might just be that gfx folks are somewhat in a world of their own.

It's not just you. Kernel Summit exists to cover things that a mailing list discussion just won't work for. We can handle the vast majority of technical issues with asynchronous, distributed discussions, to the point that Kernel Summit regularly rejects some technical topics either because they don't actually need an in-person discussion or because someone just needs to go write a patch or make an RFC proposal. Process issues, on the other hand, go much more smoothly if you get the right people in the room, quickly bounce around a few concrete possibilities, and make a call for what path to start down (even if that changes later).

#16 lore raw
In reply to Greg KH
Quoted 7 lines · Greg KH
Quoted 4 lines

At the very least, I think kernel developers each need to decide how they feel about GPL enforcement as silence and inaction is as much of a choice as voicing a view.

That's not fair, it's implying that our current way of doing this type of thing is somehow not working.

There are many who believe that it *isn't* working. Companies violate the GPL all the time, and are encouraged by the fact that there is no consistent enforcement when they do so.

And it's worse than "silence and inaction". There are even some who actually argue *against* and try to derail any efforts to improve and enforce compliance. It's almost as if they'd rather the kernel was under a BSD licence, so that such usage was permitted.

Quoted 4 lines

Remember, we have done something that no other group has ever done before, so please don't discount that we know how to handle stuff like this.  Sometimes not making a public statement is actually the correct thing to do.

Well, that of course depends on what you want to achieve.

If you are happy with the status quo, and do not want violators to be brought into compliance, then of course it's the correct thing to do.

I don't think everybody *is* happy with the status quo, though.

Signature · 1 line
dwmw2
#17 lore raw
Quoted 6 lines · David Woodhouse
Quoted 5 lines · Greg KH
Quoted 4 lines

At the very least, I think kernel developers each need to decide how they feel about GPL enforcement as silence and inaction is as much of a choice as voicing a view.

Quoted 6 lines
Quoted 2 lines

That's not fair, it's implying that our current way of doing this type of thing is somehow not working.

There are many who believe that it *isn't* working. Companies violate the GPL all the time, and are encouraged by the fact that there is no consistent enforcement when they do so.

That's not fair, companies have always "violated" our license, and violate lots of other licenses, that doesn't make them any less real or valid.

Personally, it seems that we are much better off today than we were 15, 10, and even 5 years ago on this front. There's a standing offer from the Linux foundation to get any code from any company that someone things is not open that is in the kernel. That offer has been taken up on a few times, and has never failed so far.

And that's the best that we can do without getting lawyers involved. Once we do that, to quote Linus, "we lost".

Quoted 4 lines

And it's worse than "silence and inaction". There are even some who actually argue *against* and try to derail any efforts to improve and enforce compliance. It's almost as if they'd rather the kernel was under a BSD licence, so that such usage was permitted.

Sure, lots of companies would like that because they are stupid and selfish. The best thing we have to combat that is what we have been doing for the past 20+ years. It has made huge changes to huge companies (just look at Intel, and now Microsoft!) Once you get legal involved, all bets are off as this now stops being something that we can help address, and instead have to rely on lawyers and courts, a fickle beast as the vmware thing is proving :(

And we aren't "silent" at all, but it's all about providing a big enough carrot for companies to join us, and not go after them with a stick to drive them away.

As someone else once said, "never sue your customer".

Quoted 6 lines
Quoted 4 lines

Remember, we have done something that no other group has ever done before, so please don't discount that we know how to handle stuff like this.  Sometimes not making a public statement is actually the correct thing to do.

Well, that of course depends on what you want to achieve.

I want the code, and I want the company that produced that code to join our community. So far we are doing really well in achieving that goal. You might have other goals, which is fine.

Quoted 2 lines

If you are happy with the status quo, and do not want violators to be brought into compliance, then of course it's the correct thing to do.

I do, but I don't ever think that suing them is the right way to do it, given that we have been _very_ successful so far without having to do that.

Quoted 1 line

I don't think everybody *is* happy with the status quo, though.

That's fine, and understandable, someone is always never happy :)

So, specifics, what are you upset about that we can do specifically better? What company is shipping code that we don't have that we want?

I have a shortlist that I'm working on, what's yours?

thanks,

greg k-h

#18 lore raw

We're getting off into the weeds on this.

The question is whether there's an interest among the attendees of KS in hearing about this type of thing. Based on the feedback from Christoph's session last year and some of the replies to this thread, I'd say there is. There is an argument that we shouldn't do this because it expands our exposure to legal jeopardy ... if you want to argue on that tack, I'm listening.

Dragging up employers not liking it is a red herring: last year's session was organised very late and some employer's did veto their developers attending (like yours), but the resolution was simple: you didn't stay in the room. Anyone whose employer orders them to stay away can do the same. We can make sure to have the same warnings we had last year, so I don't really see the employer angle being an objection to holding a GPL session at KS.

One of the good things about last years session was that I think we did get an embryo of a process to actually share this type of information responsibly with the kernel community and that enabled more information to be discussed reliably.

James

#19 lore raw
Quoted 8 lines · James Bottomley

We're getting off into the weeds on this.

The question is whether there's an interest among the attendees of KS in hearing about this type of thing. Based on the feedback from Christoph's session last year and some of the replies to this thread, I'd say there is. There is an argument that we shouldn't do this because it expands our exposure to legal jeopardy ... if you want to argue on that tack, I'm listening.

Yes, that's the issue here.

I discussed this last year with you, and others. By us talking about this in a setting like this, we open ourselves up to being part of any lawsuits that are discussed. That's _really_ dangerous, and is why I didn't attend the session last year. I was not told by anyone that I could not, it was my own decision.

That's my objection, I don't want any of us to be exposed to that risk.

Quoted 8 lines

Dragging up employers not liking it is a red herring: last year's session was organised very late and some employer's did veto their developers attending (like yours), but the resolution was simple: you didn't stay in the room. Anyone whose employer orders them to stay away can do the same. We can make sure to have the same warnings we had last year, so I don't really see the employer angle being an objection to holding a GPL session at KS.

Quoted 4 lines

One of the good things about last years session was that I think we did get an embryo of a process to actually share this type of information responsibly with the kernel community and that enabled more information to be discussed reliably.

Maybe, but really, this has the huge potential to politicize our community (if it hasn't already). The kernel summit has always been about technical things. We have had outside people (user group representatives, crazy Germans wanting changes for userspace, etc.) attend in the past, but those are all technical issues. I never want to have a topic at the kernel summit be such that I am forced to have my personal lawyer present just to ensure that I don't get in any sort of legal trouble.

So yes, the license matters. And yes, the GPL is one of the main reasons we have succeeded so well. And yes, us being engineers love arguing the technical issues involved in legal matters. But being as these are legal matters, shouldn't we be trusting this to our lawyers (personal and corporate?) That's what they do best, not us!

As the creators of this body of code, let's stick to the technical issues at hand, as we do that really well.

thanks,

greg k-h

#20 lore raw
Quoted 3 lines · Greg KH

I discussed this last year with you, and others. By us talking about this in a setting like this, we open ourselves up to being part of any lawsuits that are discussed. That's _really_ dangerous

Is it? What if a person actually wouldn't mind to participate because he actually believes in what the lawsuit is trying to achieve, and would be happy to provide his testimony in a lawsuit if need be?

Sure, there are corporations/employers involved (either due to copyright assignment, or due to other contract details), but that's up to every individual to judge and decide himself (together with his/her employer of course).

But I don't understand your implication that having yourself dragged into a GPL enforcement lawsuit is somehow a personal disaster.

Thanks,

Signature · 2 lines
Jiri Kosina
SUSE Labs
#21 lore raw
Quoted 9 lines · Jiri Kosina
Quoted 3 lines · Greg KH

I discussed this last year with you, and others. By us talking about this in a setting like this, we open ourselves up to being part of any lawsuits that are discussed. That's _really_ dangerous

Is it? What if a person actually wouldn't mind to participate because he actually believes in what the lawsuit is trying to achieve, and would be happy to provide his testimony in a lawsuit if need be?

Even if it's VMware compelling you as witness for their case?

Quoted 7 lines

Sure, there are corporations/employers involved (either due to copyright assignment, or due to other contract details), but that's up to every individual to judge and decide himself (together with his/her employer of course).

But I don't understand your implication that having yourself dragged into a GPL enforcement lawsuit is somehow a personal disaster.

The specific problem is that we, as kernel developers, are used to giving frank and unvarnished opinions, which are totally unlike the carefully phrased non-statements that lawyers usually make. Fine, if what you've said helps Christoph or other plaintifs, but consider what happens if an unguarded statement of yours ends up helping the alleged violator because it can be construed in a way you didn't intend. This, exactly, is the fear and, I think, you would regard something like this as a bit of a disaster.

James

#22 lore raw
Quoted 8 lines · James Bottomley
Quoted 6 lines
Quoted 2 lines

about this in a setting like this, we open ourselves up to being part of any lawsuits that are discussed. That's _really_ dangerous

Is it? What if a person actually wouldn't mind to participate because he actually believes in what the lawsuit is trying to achieve, and would be happy to provide his testimony in a lawsuit if need be?

Even if it's VMware compelling you as witness for their case?

As I said, this first of course needs to be resolved between each individual person and his/her employer, because mileage might vary a lot due to contract differences.

But in a hypothetical case of an individual either not contributing to kernel under emploympent contract, or an individual having a clearance from his employer to act in this particular matter solely on his own (with the copyright not being assigned to the company, etc), why not?

Quoted 11 lines
Quoted 2 lines

But I don't understand your implication that having yourself dragged into a GPL enforcement lawsuit is somehow a personal disaster.

The specific problem is that we, as kernel developers, are used to giving frank and unvarnished opinions, which are totally unlike the carefully phrased non-statements that lawyers usually make. Fine, if what you've said helps Christoph or other plaintifs, but consider what happens if an unguarded statement of yours ends up helping the alleged violator because it can be construed in a way you didn't intend. This, exactly, is the fear and, I think, you would regard something like this as a bit of a disaster.

Sure, but if everyone is "just afraid" to provide a sincere testimony (especially if this includes just people from one side of the dispute), then I wouldn't put my bets on a positive result of the lawsuit.

Signature · 2 lines
Jiri Kosina
SUSE Labs
#23 lore raw
Quoted 1 line · Jiri Kosina

On Wed, 24 Aug 2016, James Bottomley wrote:

[...]

Quoted 13 lines
Quoted 4 lines
Quoted 3 lines

But I don't understand your implication that having yourself dragged into a GPL enforcement lawsuit is somehow a personal disaster.

Quoted 8 lines

The specific problem is that we, as kernel developers, are used to giving frank and unvarnished opinions, which are totally unlike the carefully phrased non-statements that lawyers usually make. Fine, if what you've said helps Christoph or other plaintifs, but consider what happens if an unguarded statement of yours ends up helping the alleged violator because it can be construed in a way
you didn't intend. This, exactly, is the fear and, I think, you
would regard something like this as a bit of a disaster.

Quoted 4 lines

Sure, but if everyone is "just afraid" to provide a sincere testimony (especially if this includes just people from one side of the dispute), then I wouldn't put my bets on a positive result of the lawsuit.

I think the classic lawyer joke about their memoirs is that they should be entitled "what my client meant to say ...". Cases can be won or lost (sometimes regardless of the issues) because of an unguarded remark made by the client.

I'm not advocating that we don't have the session, I just want everyone to have a very clear understanding of why there's a huge concern about discussing an ongoing case.

James

#24 lore raw
Quoted 3 lines · James Bottomley

I'm not advocating that we don't have the session, I just want everyone to have a very clear understanding of why there's a huge concern about discussing an ongoing case.

Especially given the fact that it hasn't been proposed by Karen (at least as I read it) as solely VMWare-centric topic in the first place at all. My reading of the proposal is "Seems like some of you guys seem to be uncertain or uncomfortable regarding the GPL enforcement success in today's world; let's discuss that".

Thanks,

Signature · 2 lines
Jiri Kosina
SUSE Labs
#25 lore raw
In reply to James Bottomley
Quoted 8 lines · James Bottomley
Quoted 7 lines · Jiri Kosina
Quoted 4 lines · Greg KH

I discussed this last year with you, and others.  By us talking about this in a setting like this, we open ourselves up to being part of any lawsuits that are discussed.  That's _really_ dangerous

Quoted 6 lines
Quoted 4 lines

Is it? What if a person actually wouldn't mind to participate because
he actually believes in what the lawsuit is trying to achieve, and would be happy to provide his testimony in a lawsuit if need be?

Even if it's VMware compelling you as witness for their case?

It's a good thing that the German court system
does not have a discovery process, unlike US
courts.

#26 lore raw
In reply to Greg KH

Greg,

Greg KH wrote today:

Quoted 2 lines

There's a standing offer from the Linux foundation to get any code from any company that someone things is not open that is in the kernel.

I'm certainly glad to hear that in a few cases among the many hundreds of active Linux GPL violations, Linux Foundation's "ask for our help to find the compliance officer at a violator company" program has helped some.

Quoted 1 line

That offer has been taken up on a few times, and has never failed so far.

However, I know for a fact that it *has* sometimes failed. Specifically, I've utilized this service of Linux Foundation (which others can find at
https://compliance.linuxfoundation.org/references/open-compliance-directory
), with 0-for-2 results.

I did go through channels. I used that online form and got no reply. In both cases, I ultimately approached Jim Zemlin directly to discuss the matter. Jim and other LF staff did make efforts, in both cases, to talk with the companies, but no compliance results were achieved by Linux Foundation.

First, regarding VMware, Jim told me in August 2012 that Linux Foundation (LF) was "in communication with VMware" and "they assured [us] that VMware would work with Conservancy and comply". I explained then to Jim that VMware was conflating different issues: (a) their easy-to-resolve violations regarding BusyBox and GNOME software, and (b) their more central issue of combining their kernel with Linux source code -- an issue which Linus called "in very poor taste", and which you yourself, Greg, told me "really bothered you". I also told Jim in 2012 that eventually, if VMware didn't resolve that issue, that someone would likely sue them over the matter.

Over the next few years, both Karen Sandler and I attempted to follow up with LF executives and employees -- up and down Linux Foundation's org chart. They were unable (or unwilling) to offer any assistance in bringing VMware into compliance. Christoph got fed up and wanted to sue them. After 4 years of trying every other alternative, Conservancy decided to help him do so.

But, VMware is not my only example here. I tried again, a year after I'd first contacted LF about VMware, with another violator, in the automotive industry, who had a zero-day GPL violation in their cars that contain Linux -- no source nor offer -- and they remain out of compliance today. I won't name them because, per Conservancy's GPL enforcement principles (see
https://sfconservancy.org/copyleft-compliance/principles.html ), we're keeping their name confidential as we continue to patiently work toward a compliant resolution of their violation.

In that case, I waited about six months for an answer from LF on who to contact at that automotive company. In the end, LF just stopped responding to Conservancy staff on the matter and we had to find our own way to get in touch with the violator. LF remains aware ( -- indeed -- I remind Jim, Mike Dolan, Karen Copenhaver, and you, too, Greg, every time I see you all) that this automotive company remains out of compliance on Linux, but LF has rendered no assistance on getting them into compliance.

Quoted 3 lines

I want the code, and I want the company that produced that code to join our community. ..
So far we are doing really well in achieving that goal.

Yes, with companies who "get it". There are many of those, and they are great stalwarts of our community. No one is proposing suing them! For those
companies: Karen or I call the person we know at the company and any GPL violation is fixed in a matter of days (usually). I've had *that* wonderful experience with many major companies who employ many kernel developers. Those are not the companies we're talking about here.

There are many companies, including some big ones, who just get away with GPL violations year after year, have no intention of complying, and refuse every effort by *everyone* (LF, Conservancy, etc.) to convince them to comply. In some cases, these bad actors even *flaunt* their violations; they market products by saying that those products do things other products in the sector can't -- because, of course, their products have proprietary Linux modules that aren't available in source and certainly not upstream.

Anyway, as others have said, it's quite clear that there are strong policy opinions on both sides of this issue. As Luis mentioned, Conservancy is actively enforcing for a growing coalition of Linux copyright holders. But, as Conservancy representatives, we want to hear from the entire community and coordinate with that community. KS is the best venue to communicate about complex policy discussions with Linux developers.

--
Bradley M. Kuhn
Distinguished Technologist of Software Freedom Conservancy
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter

#27 lore raw
Quoted 7 lines · Bradley M. Kuhn

Greg KH wrote today:

Quoted 1 line

That offer has been taken up on a few times, and has never failed so far.

However, I know for a fact that it *has* sometimes failed. Specifically, I've utilized this service of Linux Foundation (which others can find at
https://compliance.linuxfoundation.org/references/open-compliance-directory
), with 0-for-2 results.

<snip>

Ok, let's work together off-list to get these issues resolved, it's not on-topic here, thanks.

Quoted 6 lines
Quoted 3 lines

I want the code, and I want the company that produced that code to join our community. ..
So far we are doing really well in achieving that goal.

Yes, with companies who "get it". There are many of those, and they are great stalwarts of our community. No one is proposing suing them!

But note, many, if not all, of those companies who you say "get it", did get it 15, 10, or even 5 years ago. If we had done what you are proposing to do here then, those companies would never now be part of our community and we would be much worse off, and possibly, not even be here at all.

Again, "never sue your customer".

Quoted 7 lines

There are many companies, including some big ones, who just get away with GPL violations year after year, have no intention of complying, and refuse every effort by *everyone* (LF, Conservancy, etc.) to convince them to comply. In some cases, these bad actors even *flaunt* their violations; they market products by saying that those products do things other products in the sector can't -- because, of course, their products have proprietary Linux modules that aren't available in source and certainly not upstream.

I know about these just as well as everyone else. And we all deal with it the best that we can, through various ways. But to somehow think that by taking legal action against them, they will then gladly join our community and work to make Linux better overall, is just not true. It never happened with the Busybox lawsuits from what I could tell, right?

In fact, it seems the opposite happened, there's now a replacement for Busybox that does much the same thing, under a non-copyleft license, that is being used in lots of places that Busybox used to be in. That's the exact opposite any project should ever want to see happen to them.

I don't want Linux to be a test case for the GPL as you put it recently[1]. That's not how I personally feel a project succeeds in the long run. And I'm in it for the long haul. Remember, at this point in time, the only thing that will ever be able to stop us, is ourselves. So we should do our best not to fuck it up. The history of Busybox development shows me one way a project can fuck up, and I try to learn from history.

Quoted 6 lines

Anyway, as others have said, it's quite clear that there are strong policy opinions on both sides of this issue. As Luis mentioned, Conservancy is actively enforcing for a growing coalition of Linux copyright holders. But, as Conservancy representatives, we want to hear from the entire community and coordinate with that community. KS is the best venue to communicate about complex policy discussions with Linux developers.

The kernel summit is to discuss technical issues involving the kernel, and developing it. Personally, I do not feel that it is a place for legal matters. Our community is made up of people, and companies, that have an extremely hard time agreeing on technical matters, throw culture, corporate competition, free software vs. open software, and legal issues into the mix and it would turn into a total and complete mess.

As Linus today said on stage at LinuxCon, some of us barely like each other to begin with, but we all know that we are working together to make the best technological solution that we can, so we tolerate each other :)

And as I said earlier in this thread, I don't want to have to have my personal lawyer sitting next to me for me to be able to attend the kernel summit.

thanks,

greg k-h

[1] https://lwn.net/Articles/695014/

#28 lore raw
Quoted 2 lines · Greg KH

I don't want Linux to be a test case for the GPL as you put it recently.

I am certainly sympathetic to your position. But I myself don't have the power nor will to make Linux into GPL's test case; a confluence of external events already did that without my help. I've been involved with copyleft enforcement and policy for almost copyleft's entire existence. I observe now that the last 10 years brought something that never occurred before with any other copylefted code. Specifically, with Linux, we find both major and minor industry players determined to violate the GPL, on purpose, and refuse to comply, and tell us to our faces: "you think that we have to follow the GPL? Ok, then take us to Court. We won't comply otherwise." (None of the companies in your historical examples ever did this, Greg.) And, the decision to take that position is wholly in the hands of the violators, not the enforcers.

In response, we have two options: we can all decide to give up on the GPL, or we can enforce it in Courts. As always, no one is compelled to enforce the GPL; Linux remains a multi-copyright-held project and copyright holders make their own decisions, as Linus reminded us this week in his press comments.

I work for an organization that holds copyrights in Linux, and Conservancy furthermore coordinates a coalition of developers who signed agreements asking us to enforce their copyrights. We also have embedded device users writing us weekly asking us to please get the Linux sources for their devices. We have a huge mandate, and we're going to enforce (always adhering to the Principles of Community-Oriented Enforcement, of course). Together, we are a vocal, but significant, minority of Linux contributors and users.

There's another vocal and significant minority of Linux contributors and users who oppose GPL enforcement. Greg, I wouldn't have pegged you for being in that camp until this thread, but it seems that you now are. :)

Both of these minorities should have their voices heard, and we should discuss and debate issues together. Furthermore, both groups should encourage the silent majority to share their views -- which might bring us entirely new ideas that neither side has hitherto considered.

As others have pointed out, that silent majority may not want to discuss complex licensing policy topics in public email discussions for various reasons. IIUC, the KS is designed as a venue for discussion of any issue important to Linux that's difficult to discuss by email and online fora.

So, what baffles me, Greg, is not that you and I are on different sides of this debate, but that your position appears to be that the issue should simply not be discussed at the KS. Frankly, seeing the diversity of views on this thread has made me even more eager to sit down in a room to figure out how and why our positions seem so far apart. I'd like to learn from you, Greg, what caused you to change your position so much in recent years, because I respect your opinions and I know you understand these issues very well. (You've certainly given me some clever ideas about GPL enforcement over the years that I've utilized to good effect.) I'd like that conversation to occur in a room with other smart, thoughtful Linux developers in real time so we can all learn from each other. The KS seems a perfect fit.

As to this side-thread about risk of "being in a room where such things are discussed", obviously it's probably not a bad idea to talk to one's employer's legal department before deciding to *speak up* in a session about GPL enforcement. And, I suppose there are a very few hyper-conservative legal departments that would raise alarm bells even if an employee silently attended such a session. (I doubt that the latter is common, though.) Anyway, if there there's even a glimmer of a concern, there's currently plenty of time for those who need to double-check with their management/legal department to see if there's a ban on attending conference sessions that discuss GPL enforcement.

Linux developers are a smart bunch, thus I don't think they need more instruction than what's already been said on this thread to determine the risk level to their livelihoods. I thus don't see any reason that a session at the KS on GPL enforcement would require different preauthorization than many other sessions (e.g., such as one on UEFI or handling wireless spectrum, which both also have many complex policy, legal, and licensing concerns for many employers in the software industry).

As to Ted's point about the purported vagueness of the proposal, Karen gave a clear list of things that occurred this year, all of which are public, that we from Conservancy will bring up for discussion at the session. Obviously other ideas are welcome, but I can't imagine there are any issues to discuss that aren't already mostly public by now -- Karen and I have certainly succeeded a lot this year in removing excessive industry secrecy around various issues (such as McHardy's enforcement actions). If it helps to know this too: neither Karen nor I plan to name any violators who have not already been publicly named as violators before the session. Indeed, I don't expect to say anything I wouldn't say in a regular public talk. --
Bradley M. Kuhn
Distinguished Technologist of Software Freedom Conservancy
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter

#29 lore raw
Quoted 6 lines · Bradley M. Kuhn

I work for an organization that holds copyrights in Linux, and Conservancy furthermore coordinates a coalition of developers who signed agreements asking us to enforce their copyrights. We also have embedded device users writing us weekly asking us to please get the Linux sources for their devices. We have a huge mandate, and we're going to enforce (always adhering to the Principles of Community-Oriented Enforcement, of course).

Bradley,

If the Conservancy is going to do what it's going to do, it's not clear what's the purpose of having a discussion.

Having a debate implies that there is a question on the floor, and to date it's not clear what the question or questions would be. Yes, it's clear what you and Karen have proposed as the *topic*, and the Conservancy's positions aren't really a secret --- but that's not a debatable question; it's not a specific proposal that could be examined.

And even if we have a question on the floor; say, "Resolved: that hackers should only use Emacs and not vi" --- we would want to evaluate that question on several metrics: "Is the question what that can be profitably debated?" "Is the a way to determine which side has one the debate?" "Will the 'winners' of the debate be able to enforce the outcome of the debate?" "Do the people deciding who wins and who loses have the legal / moral standing to be make such a decision and to bind the rest of the community or industry?"

There is plenty of time for discussion for the sake of dicussion and that's at the bar. :-)

- Ted

#30 lore raw
Quoted 13 lines · Theodore Ts'o
Quoted 6 lines · Bradley M. Kuhn

I work for an organization that holds copyrights in Linux, and Conservancy furthermore coordinates a coalition of developers who signed agreements asking us to enforce their copyrights. We also have embedded device users writing us weekly asking us to please get the Linux sources for their devices. We have a huge mandate, and we're going to enforce (always adhering to the Principles of Community-Oriented Enforcement, of course).

Bradley,

If the Conservancy is going to do what it's going to do, it's not clear what's the purpose of having a discussion.

Quoted 6 lines

Having a debate implies that there is a question on the floor, and to date it's not clear what the question or questions would be. Yes, it's clear what you and Karen have proposed as the *topic*, and the Conservancy's positions aren't really a secret --- but that's not a debatable question; it's not a specific proposal that could be examined.

A few possibilities:

- What's the right way to handle enforcement? (The most general version of this question has no hope of consensus, but I suspect we could fairly easily reach consensus about what we don't want to see people doing, for instance.)

- What (if anything) do we do in response to the "wrong" way to handle enforcement? Would we ever have a response at the kernel level, rather than just within a maintainer team (as happened with netfilter)? Is there a line where we'd stop taking patches from someone because they've created problems in the legal arena? Where is that line?

- Do any of our current development procedures make enforcement easier or harder?

- Could we incorporate anything into our development procedures that improves the situation, analogous to the DCO? (Not suggesting a live brainstorming session, but rather suggesting that if a concrete proposal exists for such a change, Kernel Summit seems like the place to discuss it.)

- EXPORT_SYMBOL_GPL and MODULE_LICENSE. I know that some history exists suggesting that they've helped with some cases. Do they potentially make enforcement more difficult, though? (This also includes informal or internal enforcement/compliance efforts; for instance, EXPORT_SYMBOL_GPL may provide a supporting argument for such efforts, but conversely EXPORT_SYMBOL may then hinder such efforts.)

- A recent proposal (with patch) suggested adding an additional (GPL-compatible) license to the table of licenses in MODULE_LICENSE. Should that happen? Would it make sense to use a different approach in MODULE_LICENSE, such as just "GPL-compatible" or "GPL and additional rights"? Would any of the possible approaches there cause problems?

Some of these questions may potentially work better on a mailing list; some of them seem like good topics for in-person discussion, especially if there's research or answers that friendly legal experts could provide.

#31 lore raw
Quoted 44 lines · Josh Triplett
Quoted 13 lines · Theodore Ts'o
Quoted 6 lines · Bradley M. Kuhn

I work for an organization that holds copyrights in Linux, and Conservancy furthermore coordinates a coalition of developers who signed agreements asking us to enforce their copyrights. We also have embedded device users writing us weekly asking us to please get the Linux sources for their devices. We have a huge mandate, and we're going to enforce (always adhering to the Principles of Community-Oriented Enforcement, of course).

Bradley,

If the Conservancy is going to do what it's going to do, it's not clear what's the purpose of having a discussion.

Quoted 6 lines

Having a debate implies that there is a question on the floor, and to date it's not clear what the question or questions would be. Yes, it's clear what you and Karen have proposed as the *topic*, and the Conservancy's positions aren't really a secret --- but that's not a debatable question; it's not a specific proposal that could be examined.

A few possibilities:

- What's the right way to handle enforcement? (The most general version of this question has no hope of consensus, but I suspect we could fairly easily reach consensus about what we don't want to see people doing, for instance.)

- What (if anything) do we do in response to the "wrong" way to handle enforcement? Would we ever have a response at the kernel level, rather than just within a maintainer team (as happened with netfilter)? Is there a line where we'd stop taking patches from someone because they've created problems in the legal arena? Where is that line?

- Do any of our current development procedures make enforcement easier or harder?

- Could we incorporate anything into our development procedures that improves the situation, analogous to the DCO? (Not suggesting a live brainstorming session, but rather suggesting that if a concrete proposal exists for such a change, Kernel Summit seems like the place to discuss it.)

Quoted 6 lines

- EXPORT_SYMBOL_GPL and MODULE_LICENSE. I know that some history exists suggesting that they've helped with some cases. Do they potentially make enforcement more difficult, though? (This also includes informal or internal enforcement/compliance efforts; for instance, EXPORT_SYMBOL_GPL may provide a supporting argument for such efforts, but conversely EXPORT_SYMBOL may then hinder such efforts.)

Oh I really wish someone could answer that. I hate _GPL as I believe it makes it legal to create GPL modules with MODULE_LICENSE, when really they violate the license just as much if not more. If something isn't a derivate work for MODULE_LICENSE, but using one _GPL work somehow makes it one, is insane.

Although I can't attend this year, I think there should be less stop energy from the senior developers, and more discussion in the only place it's probably safe to discuss this, in a closed room with no press, I'm nearly sure this is one of the reasons KS existed in the first place to have unreportable discussions.

Everyone who stays in the room can later drink heavily and deny any knowledge of having been there.

Dave.

#32 lore raw
Quoted 9 lines · Dave Airlie

On 25 August 2016 at 17:03, Josh Triplett <[email protected]>

Quoted 7 lines

- EXPORT_SYMBOL_GPL and MODULE_LICENSE. I know that some history
exists suggesting that they've helped with some cases. Do they
potentially make enforcement more difficult, though? (This also includes informal or internal enforcement/compliance efforts; for instance, EXPORT_SYMBOL_GPL may provide a supporting argument for such efforts, but conversely EXPORT_SYMBOL may then hinder such efforts.)

Quoted 5 lines

Oh I really wish someone could answer that. I hate _GPL as I believe it makes it legal to create GPL modules with MODULE_LICENSE, when really they violate the license just as much if not more. If something isn't a derivate work for MODULE_LICENSE, but using one _GPL work somehow makes it one, is insane.

Well, having talked to some corporations who are fast and loose with kernel modules: They fear accessing the GPL symbols (by lying about their module licence) because, in the US, their lawyers have advised them that this could be construed as circumventing a technological protection mechanism under the DMCA.

I'm not sure I believe that pushing symbols to become GPL only helps because the lawyers now seem to think that open source shims which give access to the symbols are generally OK.

Quoted 8 lines

Although I can't attend this year, I think there should be less stop energy from the senior developers, and more discussion in the only place it's probably safe to discuss this, in a closed room with no press, I'm nearly sure this is one of the reasons KS existed in the first place to have unreportable discussions.

Everyone who stays in the room can later drink heavily and deny any knowledge of having been there.

That's about what we did last year.

Just on that, I would like to remind everyone that last year, we did something fairly similar to what's being proposed and the sky didn't fall ... there may have been a few irritated corporations, but there weren't huge consequences.

What I think last year demonstrated was that we could use the forum of the KS to have a useful dissemination of information and I think it's got to be better than simply refusing to talk about it.

James

#33 lore raw
Quoted 6 lines

That's about what we did last year.

Just on that, I would like to remind everyone that last year, we did something fairly similar to what's being proposed and the sky didn't fall ... there may have been a few irritated corporations, but there weren't huge consequences.

Yes, like did anyone get fired? if not then nobody actually did anything their company cared about wrong.

Dave.

#34 lore raw
In reply to Bradley M. Kuhn
Quoted 17 lines · Bradley M. Kuhn
Quoted 2 lines · Greg KH

I don't want Linux to be a test case for the GPL as you put it recently.

I am certainly sympathetic to your position. But I myself don't have the power nor will to make Linux into GPL's test case; a confluence of external events already did that without my help. I've been involved with copyleft enforcement and policy for almost copyleft's entire existence. I observe now that the last 10 years brought something that never occurred before with any other copylefted code. Specifically, with Linux, we find both major and minor industry players determined to violate the GPL, on purpose, and refuse to comply, and tell us to our faces: "you think that we have to follow the GPL? Ok, then take us to Court. We won't comply otherwise." (None of the companies in your historical examples ever did this, Greg.) And, the decision to take that position is wholly in the hands of the violators, not the enforcers.

Quoted 2 lines

In response, we have two options: we can all decide to give up on the GPL, or we can enforce it in Courts.

I call bullshit on this.

And frankly, I'm tired of hearing it, as it's completely incorrect and trivializes the effort that thousands of people have been doing for 25+ years to preserve the rights that the GPL grants us.

Quoted 3 lines

There's another vocal and significant minority of Linux contributors and users who oppose GPL enforcement. Greg, I wouldn't have pegged you for being in that camp until this thread, but it seems that you now are. :)

I have NEVER said I oppose "GPL enforcement", I will say that I oppose the way that _you_ approach this task.

And here is why.

I too have had people say to my face, numerous times, "you think that we have to follow the GPL? Ok, then take us to Court. We won't comply otherwise." And guess what, no one took anyone to court, and every single time, I ended up with the code[1].

As you well know, when you take legal action against someone, you have to be prepared to lose, and accept the consequences of that loss.

Frankly, I am not prepared to lose, and there is no way in hell that I am willing to accept the consequences of such a loss.

You have told me yourself that you are willing to take that risk, and I have told you that I am not. I want Linux to succeed, I think it's the right way to develop a software project, it's personally immensely satisfying work, and the benefits it brings to millions of people allowing them to create and control their lives is invaluable.

I've spent the last decade of my life working to support, grow, and enhance our community. And corporations are a _huge_ part of our community, and frankly, the only reason we are where we are today. We _have_ to work to bring more companies and their developers into our group, never working to purposefully alienate anyone.

Here's what happens when you threaten legal action against a company:
- they instantly stop talking to any "external" developer that might have been working with them to figure this community and license thing out. So much for our "back channel" to them that was slowing starting to pay off.
- they bring in more lawyers, and react defensively to protect themselves, as that's what they have to do to preserve the company.
- Anyone in the company that pushed to use Linux is now seen as "wrong" and instantly is pissed off that external people just messed up their employment future.
- Anyone in the company that resisted the use of Linux (possibly in ways that caused the code not to be released over the objection of the previously mentioned people) are vindicated in their opinion of those "hippy"[2] programmers who develop Linux.
- The lawyers know that now that you are willing to accept that loosing is an option, and will do everything in their capability to ensure that it happens (drag it out, annoy the hell out of developers by disposing them, burn your money in whatever way they can, etc.)

Now, even if, after many years of work on your part, you do get that code, what is the end result? You have made an enemy for life from the people who brought Linux into the company, you have pissed off the people who didn't like Linux in the first place as they were right and yet you "defeated" them. Both of those groups of people will now work together to never use Linux again as they don't want to go through that hell again, no matter what.

And look, we have a case study of this, BusyBox. That's exactly what happened numerous times. Some of those people/companies you upset had enough resources to create a competing project to replace it and ensure that they never have to deal with that mess again.

And yes, you are "vindicated", but at what cost? You have the code, it's useless as it's old, obsolete, not mergable, and oops, your development community is now dead and the project is obsolete.

So, turn it around, and look at how _we_ have been doing enforcement in the Linux community for the past 25 years.

We do it quietly, working with companies, from within, convincing them that yes, this license that seems so strange and crazy is really worth following, not only because it is the law (companies ignore the law all the time, it's called risk management), but because it turns out it is the right thing to do from a business point of view. It's cheaper to do so, the benefit is huge, and the return on investment is immense when they join together to work with us, instead of off in their own bubble.

By doing this, the people that pushed for Linux in their company are vindicated and love you more, some of the naysayers are convinced, slowly, of the real truth here, and boom, you now have grown and strengthened your community and the feedback loop continues.

Now back to one of those companies that told me to my face I was going to have to sue them. I just reviewed a major patch set from that company a few weeks ago[3] Would that have worked if I had taken legal action against them? No way! They are now a part of our community and helping to make it succeed as their company relies on it.[4] It took many many years of work, but it happened.

So, by working with people, and showing them the BENEFIT of the GPL, we grow our community, ensure our survival, and win converts to the license itself as now those people have a stake in it as their company relies on it.

A very smart senior kernel developer once told me over drinks in a bar in Germany many years ago, something along the lines of "A foolish man bangs on the outside trying to change a company, a wise and cunning man works from within the company, changing it from inside such that it never knew what happened."

And look, that's _exactly_ what we have done. Us "punks" have grown up, changed companies from within in ways that no one had ever imagined was possible, and now hold major influence within them, if not total control in some instances! Look at the success of Linux, we took over the world, by working from the bottom up, embracing and taking over all possible industries in ways that has never been done before.

And we did it all by not suing anyone, as some of us know that's the quickest way to piss businesses off and make enemies.[5]

Now you are in a problem here. Being the representative of a number of copyright holders, you only can use a legal approach in order to try to get companies to comply. All you have is a threat of litigation, which clouds the viewpoint you are coming from (as is evident in your original statement above about "enforce or give up".)

But me, and hundreds like me, who are the developers of the code, and the people with the most at stake in the project, have more tools at our disposal in order to achieve the goal of getting the code created by companies, and bringing them into "the fold." Bringing a developer in to talk to people, and work with people, and discussing things face-to-face, without any lawyers involved, is a incredibly powerful force. Yeah, it's not flashy or public, it's slow, a grind, frustrating, thankless, and burns airline miles like crazy.

But it's working. And has worked. So to dismiss the way a large number of us have been doing this for decades as "not working" is personally hurtful, and totally short-sighted. I feel we have the proof that this _does_ work based on the success of Linux.

Remember, "carrot vs. stick", "honey vs. vinegar", and the like. Maybe it's just me and my "attachment parenting" model of approaching the world, but I honestly think that it's better to be nice to people than to piss them off, if you wish to have them join you in your goals.

Another proof point, look at Microsoft and the BSA. How many companies did they piss of when they went in with lawyers to enforce their licenses? Wasn't it Fender Guitar that flat out refuses to ever use anything from Microsoft again because of that? We don't ever want to be accused of acting like that to any company.

And yes, I know you work with companies before resorting to legal action. But it's not the developers of the project working with the company, it's their representative, a VERY big difference, as is seen by how it has worked out with Busybox.

This has gotten way off topic, sorry, but I felt I had to set the record straight of being accused of not working on, or wanting to, enforce the license of the project I have spent decades working on, that I feel is one of the main reasons it has succeeded.

As you like to quote Linus, I will too, "once the lawyers are involved, you have lost".

And you can quote me, "I do not want to lose."

So, back on topic, I think that the kernel summit should be left to technical issues, as well as development issues (how maintainers work, how releases happen, if we will finally turn off bugzilla, etc.) Let's keep the legal, and political, things out of it, in my opinion that doesn't belong there.

Especially as I don't want to have to have my lawyer present in order for me to be able to attend :)

thanks,

greg k-h

[1] It always, without fail, totally sucked.
[2] Personally I prefer being called a "punk", as that's much more accurate as to where the majority of us came from, yourself included.
[3] It still sucked, they haven't learned much, but they are trying and willing to learn.
[4] I want to resist the analogy of a drug pusher "first hit is free!", so I'll bury it here in a footnote.
[5] Till and Harald did take people to court, and it was good, but the issues there were much different than what you are proposing, and the stakes were much lower.

#35 lore raw
Quoted 4 lines · Greg KH

I too have had people say to my face, numerous times, "you think that we have to follow the GPL? Ok, then take us to Court. We won't comply otherwise." And guess what, no one took anyone to court, and every single time, I ended up with the code[1].

And yet, if you and I were to go into a store today I bet we could find more examples of infringing Linux than compliant. Of the ones that *are* compliant, I strongly suspect that most would be companies that were either sued over Busybox or came very close to being sued over Busybox. Sure, it's not an approach that would have worked with Intel or IBM, but they're a tiny fraction of the Linux that's sold.

If your focus is mainly on "How can we maximise contribution of $ and developers to Linux", then yes, your approach makes sense. But that comes at the cost of a vast number of users left with closed devices, abandoned by their manufacturers, waiting for someone to find another massive security flaw that we left behind in 2.6. These people matter, and we shouldn't ignore their needs.

We've already got plenty of corporate investment. Let's not forget that many of us are here because Linux gave us a way to hack on devices that would otherwise have been closed to us, and let's do what we can to ensure that the next generation of interested hackers have the same opportunity.

#36 lore raw
Quoted 6 lines

If your focus is mainly on "How can we maximise contribution of $ and developers to Linux", then yes, your approach makes sense. But that comes at the cost of a vast number of users left with closed devices, abandoned by their manufacturers, waiting for someone to find another massive security flaw that we left behind in 2.6. These people matter, and we shouldn't ignore their needs.

A better legal tactic might be to get some product liability laws on the books that include a specific long term liability exception for products that ship with full source. If those existed, then corporate lawyers would be advising that using open source and making it available would be the way to avoid giant liabilities like the asbestos and lead-in-paint suits.

[Disclaimer: my own random musings, not the opinion of my employer]

-Tony

#37 lore raw
In reply to Greg KH
Quoted 8 lines · Greg KH

We do it quietly, working with companies, from within, convincing them that yes, this license that seems so strange and crazy is really worth following, not only because it is the law (companies ignore the law all the time, it's called risk management), but because it turns out it is the right thing to do from a business point of view. It's cheaper to do so, the benefit is huge, and the return on investment is immense when they join together to work with us, instead of off in their own bubble.

To give support to this point, I've spent most of my career working at fairly high levels within various companies to build open source strategies and business models for them. There is a very solid business rationale for any corporation both releasing code under the GPL and for using projects which are under the GPL. It takes a while to communicate and work out the strategy, but if you do it properly, everyone just gets why. Take a certain Russian company as an example.
When I joined, that company really fancied permissive licences. However, it also feared releasing code that its competition would then
use against it in the market. The give back clause of the GPL has a solid answer to this (your competition has to show you the code they would compete with you on), so it took under a year for the GPL to become the default licence for them to release projects they controlled under.

This isn't a "comply or else" approach, it's a "here's the business value you're missing with your current position approach". I'm happy to negotiate with any company on this point and, as Greg says, the fact that I haven't sued anyone and that I do have a reputation in the industry really helps to get my foot in the door when it comes to persuading some entity to be more GPL friendly.

James

#38 lore raw
Quoted 7 lines

everyone just gets why. Take a certain Russian company as an example.
When I joined, that company really fancied permissive licences. However, it also feared releasing code that its competition would then
use against it in the market. The give back clause of the GPL has a solid answer to this (your competition has to show you the code they would compete with you on),

Here is the core question of consequences for non-compliance again:

What if the competition doesn't want to show the code? Were you able to advertise a "don't sue" approach to that company?

#39 lore raw
In reply to Bradley M. Kuhn
Quoted 8 lines · Bradley M. Kuhn

I work for an organization that holds copyrights in Linux, and Conservancy furthermore coordinates a coalition of developers who signed agreements asking us to enforce their copyrights. We also have embedded device users writing us weekly asking us to please get the Linux sources for their devices. We have a huge mandate, and we're going to enforce (always adhering to the Principles of Community-Oriented Enforcement, of course). Together, we are a vocal, but significant, minority of Linux contributors and users.

Thanks to the ruling you've landed us with in Germany, it does appear that this means you actually don't have any standing to enforce GPL for the Linux kernel .... and now neither do the rest of us.

I fear the two pong test the court required could easily be applied here in the US once the lack of standing defence is raised. I've actually spent some time this week working out how we might satisfy the tests if they can't be overturned on appeal. It turns out that Kate Stewart and her Montreal Polytechnic crowd have spent years developing a tool set that we can use to demonstrate precisely what the two prong test demands and if we have to go down this road, I trust you'll be grateful for the time and effort the Linux Foundation (Kate's employer for all of this) has spent ensuring that the above ruling won't be the disaster for us that it currently appears.

James

#40 lore raw

I've been trying to ignore this stupid flame war, but..

Quoted 3 lines

Thanks to the ruling you've landed us with in Germany, it does appear that this means you actually don't have any standing to enforce GPL for the Linux kernel .... and now neither do the rest of us.

Event despite lots of help Bradley and the Conservancy this is my case, and I have lost the first instance. I really don't want incorrect statements like this rest on a mailing list with a public archive.