Skip to contentSkip to conversation

GPL defense issues

Ksummit-discuss Jeremy Allison 21 participants 84 messages Aug 26, 2016 – Aug 31, 2016 2 messages not in the archive

lore
Share & tools
lore
#0 lore raw
Quoted 5 lines · Linus Torvalds

So note how I said earlier that it's not an entirely black-and-white thing.
...
We've also seen how even successful lawsuits haven't actually helped the project involved. So there was certainly an education there too - for the developer side.

Apologies for the drive-by posting. I'm not normally on this list, but this discussion is important enough I wanted to correct the above point.

The Samba project has never sued anyone over GPL-violations. We've discussed violations with companies more times than I can remember, but never had to go to court over the GPL being violated on our code.

These days we rely on Conservancy doing the kind of back-room negotiation that they are really good at, and they've never failed us on this. Lawsuits *are* a last-ditch nuclear option.

However, we do have experience with one successful lawsuit, which provides a good counter example to the comment above.

Samba and the FSFE were the last entities standing in the Microsoft vs EU anti-trust lawsuit. We even helped cost them over $1b in fines.

Next month I'll be going up to my second invite-only Microsoft plugfest of the year - this one set up specifically for the Team that sued them.

I'll be visiting several of my friends there, including one of their lawyers (although the rest of them are engineers :-).

The Microsoft vs EU lawsuit was not only successful, it helped the Samba project a great deal. The documentation that was released because of the lawsuit has provided impetus for a great deal of new Samba development, as well as creating a diverse marketplace of new proprietary competitors (which has helped raise everyones code and improved interop for the users).

None of this would have happened without the successful lawsuit, rancorous though it was at the time (and in public too :-).

So as someone said earlier, this is not an entirely black-and-white thing :-).

Jeremy.

Full disclosure: I'm on the Conservancy Board of Directors, so I obviously agree with their mission.

#1 lore raw
Quoted 3 lines · Jeremy Allison via Ksummit-discuss

These days we rely on Conservancy doing the kind of back-room negotiation that they are really good at, and they've never failed us on this. Lawsuits *are* a last-ditch nuclear option.

Without the option of a lawsuit, there *is* no negotiation. The GPL has certain requirements and they are backed up by law. If you don't have that, you might as well have a BSD licence.

You won't get far in negotiating with someone to release their modifications if the code in question is under a BSD licence and you start the conversation by saying "You need to release the changes you made or... we'll be sad". And that's *precisely* the same as the GPL if you state up front that you'll never sue. You'll just get laughed at.

Conservancy quite rightly use legal action as a last resort after all other reasonable avenues have been exhausted. But you can't abandon it completely.

And the idea that legal action against violators would scare away those who are using the software *legally* is laughable. There is *always* risk...

If you use commercial software and don't pay for the licence, you can be sued.

If you use Free Software and don't comply with the licence, you can be sued.

And even if you write it yourself, you have to be really careful your engineers don't pick up code snippets they found on the Internet... or you can be sued.

Whatever you do, you have to actually follow the rules and do it right. Holding persistent violators to the rules the hard way, if they refuse to do the right thing after years of negotiation, *really* shouldn't scare off anyone sensible from using Free Software.

Signature · 1 line
dwmw2
#2 lore raw
In reply to Jeremy Allison
Quoted 4 lines · Jeremy Allison

These days we rely on Conservancy doing the kind of back-room negotiation that they are really good at, and they've never failed us on this. Lawsuits *are* a last-ditch nuclear option.

Jeremy, I trust *you*.

But I do not trust Bradley, for example.

Bradley talks the talk here when called out on it, but elsewhere he clearly sees enforcement not as just a last ditch nuclear option. I've heard that complaint from people in private conversations, but you can find it in public posts too.

For example, we had a really nasty issue with Patrick McHardy, and sadly, the companies involved apparently didn't dare talk about it for fear of bad press (even if the badness was from our side). I was actually informed by Karen that the SFC finally made the thing public (thanks Karen - I really appreciated that), but when I went looking for it I find Bradley Kuhn making comments like these:

http://lwn.net/Articles/695014/

Let me highlight that l;ast sentence:

"Finally, while discussions about GPL and its derivative/combined
works requirements are basically “old hat” to our community, the discussion is completely new to the Courts. We'll have to bring the question to a lot of Courts in a lot of different ways to get clarity. But, once we do that, then we'll know, and everyone can proceed with more certainty."

Look, guys. This is Bradley EXPLICITLY talking about using the courts as a way to "clarify" issues.

So _excuse_ me for not finding Bradley Kuhn very trustworthy on this issue. He's on public record on doing exactly that I am arguing we should *NOT* be doing.

Lawsuits aren't about "clarification". They aren't something we should hope for in order to "proceed with more certainty".

Quoted 2 lines

Full disclosure: I'm on the Conservancy Board of Directors, so I obviously agree with their mission.

Please, see above. If you're on the Conservancy board of directors, maybe you should clarify with Bradley, who is listed as _president_ of the board, what that mission actually is?

Because right now, I'm getting some _very_ mixed messages.

Linus

#3 lore raw
Quoted 9 lines · Linus Torvalds
Quoted 4 lines · Jeremy Allison

These days we rely on Conservancy doing the kind of back-room negotiation that they are really good at, and they've never failed us on this. Lawsuits *are* a last-ditch nuclear option.

Jeremy, I trust *you*.

But I do not trust Bradley, for example.

Thanks. I'm in the happy position of trusting both you *and* Bradley. But I know you don't know him as well as I do.

Quoted 5 lines

Bradley talks the talk here when called out on it, but elsewhere he clearly sees enforcement not as just a last ditch nuclear option. I've heard that complaint from people in private conversations, but you can find it in public posts too.

Quoted 7 lines

For example, we had a really nasty issue with Patrick McHardy, and sadly, the companies involved apparently didn't dare talk about it for fear of bad press (even if the badness was from our side). I was actually informed by Karen that the SFC finally made the thing public (thanks Karen - I really appreciated that), but when I went looking for it I find Bradley Kuhn making comments like these:
...

Linus, I hope you of all people realize what can happen when you take people's email quotes out of context. You end up with things like this:

http://www.theregister.co.uk/2016/08/26/linus_torvalds_calls_own_lawyers_nasty_festering_disease/

Which isn't a nuanced look at the discussion we are having here :-).

You have to remember you get to talk to the engineers about GPL violations, who sheepishly look at their shoes and say, "yeah, I'm talking to management about fixing that." That's the approach I take too when talking about GPL violations. But if that doesn't work (and there are some companies for which it really doesn't), then you have to talk to management.

Bradley has to have that talk with the management instead. That can give a completely different perception of what is going on ("fsck you, we're never giving you that code" :-). Remember, Conservancy are the people we call in when we're not getting anywhere through the unofficial channels.

I've (very) occasionally been on one of those calls. They're not pleasant.

The other thing to remember is Bradley isn't the one making the decisions here. It's the developers - *ALWAYS* the developers. Bradley and the Conservancy staff can give advice, but they do not do *anything* without a direct mandate from the copyright holders.

Conservancy acts when developers ask them to. It isn't accurate to think of Bradley or Conservancy as a rogue actor running around doing their own thing. They're more like the union rep who does the tough negotiations with the employer. No one likes the union rep. (or maybe I've lived in the USA too long :-).

Quoted 9 lines

Look, guys. This is Bradley EXPLICITLY talking about using the courts as a way to "clarify" issues.

So _excuse_ me for not finding Bradley Kuhn very trustworthy on this issue. He's on public record on doing exactly that I am arguing we should *NOT* be doing.

Lawsuits aren't about "clarification". They aren't something we should hope for in order to "proceed with more certainty".

Corparate lawyers talk like that ("clarification"). It's the language they understand. No one files lawsuits for "clarification", if they do (and there have been amazingly few open source lawsuits compared to the litigous hell that is proprietary software) they're either a bad actor doing it for money (not mentioning names here) or they're trying to get compliance (Conservancy).

Quoted 5 lines

Please, see above. If you're on the Conservancy board of directors, maybe you should clarify with Bradley, who is listed as _president_ of the board, what that mission actually is?

Because right now, I'm getting some _very_ mixed messages.

I think the best message Conservancy has made on GPL compliance is here:

https://sfconservancy.org/copyleft-compliance/principles.html

and I *know* everyone there is on board with that ! As for the general mission - more Free Software for all ! :-).

https://sfconservancy.org/about/

"Software Freedom Conservancy helps promote, improve, develop, and defend Free, Libre, and Open Source Software (FLOSS) projects. Conservancy provides a non-profit home and infrastructure for FLOSS projects. This allows FLOSS developers to focus on what they do best — writing and improving FLOSS for the general public — while Conservancy takes care of the projects' needs that do not relate directly to software development and documentation."

I think we all want the same thing. To mess with the code :-).

#4 lore raw
Quoted 9 lines · Jeremy Allison via Ksummit-discuss

The other thing to remember is Bradley isn't the one making the decisions here. It's the developers - *ALWAYS* the developers. Bradley and the Conservancy staff can give advice, but they do not do *anything* without a direct mandate from the copyright holders.

Conservancy acts when developers ask them to. It isn't accurate to think of Bradley or Conservancy as a rogue actor running around doing their own thing.

Ah, but *which* developers? There are a huge number of entities who own copyrights in the Linux kernel. Does the Conservancy get to pick and choose which developers they will listen to? What about the companies that own copyright in the Linux kernel, such as Red Hat, IBM, Intel, Google, and others? Do they get a seat at the table?

What about Linus's opinions? Is the Conservancy going to at least ask the major copyright holders whether they are OK with a lawsuit before going ahead, and stop if they say No? Or so long as you can find some number of developers who say, "go for it!" you'll start filing the paperwork at the courthouse?

There have been at least some representation made by Conservancy staff that appear to denote that they have their set of developers and that they are going to do what they are going to do, regardless of what other copyright holders might think. Perhaps it might be understandable why some might feel that your term of "rogue actor" might actually be appropriate?

As I said in another e-mail; at the heart of this question is really a governance / polity issue, and I don't believe the Kernel Summit is well situated to address these sorts of questions, as we don't have all of the stakeholders present.

- Ted

#5 lore raw
Quoted 6 lines · Theodore Ts'o

Ah, but *which* developers? There are a huge number of entities who own copyrights in the Linux kernel. Does the Conservancy get to pick and choose which developers they will listen to? What about the companies that own copyright in the Linux kernel, such as Red Hat, IBM, Intel, Google, and others? Do they get a seat at the table?

It's pretty clear that this applies to individual copyright holders who have joined Conservancy's GPL Compliance Project for Linux Developers, not corporations with their own legal department and lawyers who can make decisions about compliance for themselves.

Even closer to my analogy of a union than I originally thought, actually :-).

By definition these are developers who agree with the published "Principles of Community-Oriented GPL Enforcement" document, which does a good job of setting out when and how enforcement should be handled.

Quoted 5 lines

What about Linus's opinions? Is the Conservancy going to at least ask the major copyright holders whether they are OK with a lawsuit before going ahead, and stop if they say No? Or so long as you can find some number of developers who say, "go for it!" you'll start filing the paperwork at the courthouse?

Can you describe the conditions you personally would feel justify filing a lawsuit over GPL non-compliance ?

Even if you reply "never" that would be a good data point to understand your opinions on this.

Quoted 6 lines

There have been at least some representation made by Conservancy staff that appear to denote that they have their set of developers and that they are going to do what they are going to do, regardless of what other copyright holders might think. Perhaps it might be understandable why some might feel that your term of "rogue actor" might actually be appropriate?

If following this:

https://sfconservancy.org/copyleft-compliance/principles.html

means you are a "rogue actor", then I question your understanding of the language.

#9 lore raw
In reply to Linus Torvalds

Linus,

Linus Torvalds wrote at 14:51 (PDT):

Quoted 6 lines

For example, we had a really nasty issue with Patrick McHardy, and sadly, the companies involved apparently didn't dare talk about it for fear of bad press (even if the badness was from our side). I was actually informed by Karen that the SFC finally made the thing public (thanks Karen - I really appreciated that), but when I went looking for it

The link to that statement, which Karen and I made jointly, is here:
https://sfconservancy.org/blog/2016/jul/19/patrick-mchardy-gpl-enforcement/

Quoted 2 lines

So _excuse_ me for not finding Bradley Kuhn very trustworthy on this issue.

I don't expect you to trust me; we don't know each other very well.

However, you don't need to trust me to examine my or Conservancy's actions, because they're very transparent and any mandate that I have to do GPL enforcement for Linux comes from Conservancy's agreements with Linux developers who signed agreements that ask Conservancy to act.

Quoted 2 lines

He's on public record on doing exactly that I am arguing we should *NOT* be doing.

No, that's not what I've said, neither on nor off the public record.

To step back, the chain of events of what Conservancy does in Linux GPL enforcement is a simple flowchart:

0. Talk to the Linux developers in our coalition about the violation until there's general consensus about what to do next.

1. Approach violating company and ask nicely for them to comply, and offer help them do so.

(a) If they do comply, thank them and (if they want) help them upstream the code and/or form a community to help work on it (for firmwares). "goto all_the_other_work_Conservancy_does_that_is_not_enforcement;"

(b) If they don't comply, try to help them comply by giving them detailed technical reports about what parts of their product aren't in compliance.

2. If still no compliance & a long time has yet to go by: goto 0.

3. After that long time has passed, talk to the Linux developers in our coalition to see if someone feels a lawsuit is necessary.

4. After all that & much time has passed, support any Linux developer(s) who wants to file a lawsuit, in the way they specify they want that help.

And, in the four years that Conservancy has run the GPL Compliance program for Linux developers, we got to (4) *exactly once*, with VMware, and we even sat in (3) for quite a while, until Christoph joined the coalition and decided he wanted to act [0].

In your last email, you quoted me (out of context) on a comment I made regarding a situation where *we were already at step 4* (i.e., VMware's violation). There are lots of tactics and details to consider when we reach steps 3 and 4, and those include: how the GPL appears to the Courts, whether they can achieve clarity in interpretation of the GPL, what venue makes sense, and whether we'll get a certain decision. Also, it's likely that true clarity won't come until steps (3) and (4) are a hit multiple times, which may never happen (in history, any novel legal instrument has required multiple Court cases to understand fully). However, my observation of that does not mean I'm *seeking* to hit steps (3) & (4). Anyone who has done GPL enforcement with me can tell you that I *loathe* Steps 1(b), (2), (3) and (4). For the record, step 1(a) is the only one I *want*, and I always try everything I can think of to get to 1(a).

Meanwhile, I do suspect you would rather Conservancy operate transparently and comment publicly as much as we can. Of course, Conservancy *could* just do our work silently, communicate only with our coalition of developers, and refuse to talk to the wider Linux community. We *don't* do that because we believe in openness and transparency.

Speaking just for myself, I'm *glad* to be held accountable by the Linux developer community. That's why I'm bothering to respond in this thread, why I've done many calls over the years with LF's TAB, and why I propose talks to every single Linux Foundation conference and leave plenty of time for Q&A. I believe if I'm involved in enforcing the GPL on Linux, the Linux community has a right to question my activities and expect answers.

But, please, don't take open and transparent comments out of context and assume that such statements on narrow issues of specific situations implies a conspiratorial agenda. It doesn't, and the *actions* show that...

Quoted 1 line

Because right now, I'm getting some _very_ mixed messages.

... a wise man once said, "talk is cheap; show me the code". So, judge me by my actual actions, not by twisting my words. It's easy to do because all this work has been done transparently. As a public charity, you can look at Conservancy's 990s and see all financial details related to GPL enforcement. As I said in another post, in more than ten years, Conservancy has been involved in exactly *two* lawsuits, with plenty of public documentation of what happened there. Recently, I and Karen were the *only* ones who were willing to publicly criticized Patrick McHardy for being unnecessarily litigious and non-transparent [1]. Overall, we only began the GPL Compliance program for Linux developers because developers *asked* for it. We remain accountable to them. We published the Principles of Community-Oriented GPL Enforcement, which were endorsed and/or lauded by many Linux developers, including the entire Netfilter team, as well as other charitable organizations including FSF, FSF Europe and the Open Source Initiative.

I *think* you are saying that I'm doing something wrong and hurting Linux. I'm not only willing to hear you on that -- in fact, I am alarmed and want to understand immediately what it is. But, you've not pointed to any specific problematic action that I've taken. Plus, before moving to Step (4) with VMware, I asked you in person how you felt about enforcement against VMware, and you said "what they're doing is in bad taste and someone should probably do something about it". You certainly did *not* say "please don't pursue that!" I am delighted to be accountable for my actions, but I'm baffled here trying to figure out what action you're criticizing and why you didn't tell me to stop when I explicitly sought your opinion.

Regardless, I'm happy to keep discussing the details with you and everyone else, saying as much as is appropriate publicly. I and Karen both were hoping everyone who is stakeholder regarding Linux (i.e., the copyright holders and developers) could have a discussion at KS about this.

Linus Torvalds wrote elsewhere in the thread:

Quoted 3 lines

But as I started out saying, I actually support discussing this at the kernel summit, it's just that I absolutely do *not* think it's about having lawyers present.

IANAL, and I also agree that everyone showing up at KS with their lawyers by their side is a _horrible_ idea. Anyway, there are no actual legal questions to discuss -- rather, nearly every issue raised are *policy* questions. Policy discussion should include actual stakeholders (which, with regard to GPLv2, means anyone who is a copyright holder in Linux).

[0] https://sfconservancy.org/copyleft-compliance/vmware-lawsuit-faq.html#why-lawsuit
has the full story on how these steps went with VMware.

[1] Company representatives of all sorts have been thanking us for weeks, BTW, for finally coming forward and criticizing McHardy's lawsuits, because, as Linus mentioned, companies have been freaked out about it and "didn't dare talk about for fear of bad press". (And, Conservancy did get some bad press and aggressive complaints from a few for our statement on it.) But we did it because we believed it was right for the community, and because companies that try hard to comply with the GPL were asking us to do so. We felt it important to go public about what we knew and had learned, because companies were scared and many didn't know what was going on, therefore creating a net-search-findable explanation about the situation was essential for the community.

Signature · 4 lines
Bradley M. Kuhn
President & Distinguished Technologist of Software Freedom Conservancy
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter
#6 lore raw
In reply to Jeremy Allison
Quoted 3 lines · Jeremy Allison

Can you describe the conditions you personally would feel justify filing a lawsuit over GPL non-compliance ?

You asked Ted, but I'll answer for one of the conditions for me: that it is not some gray area. It has to be a pretty damn clear violation.

Quite frankly, I've seen a lot of people be confused about what the GPLv2 actually says over the years. The most common confusion is the whole thing about "linking". It gets mentioned a lot.

Not only is "linking" not something that has any legal meaning, but the GPLv2 doesn't even mention it. Yet people _continually_ talk about linking.

I think the confusion actually comes from the FSF itself, and the original LGPL discussions, where the FSF at some point tried to convince people that linking against a GPL library somehow meant that the end result was a "derived work" in a very different way than "mere aggregation". It comes from some GPL maximalist argument, and it's where the whole LGPL came from, after all.

So a *lot* of people think that "linking" means that the GPLv2 is automatically in effect.

But what the license says - and more importantly, what copyright law itself actually is all about - is not linking, but "derived work".

And there's a _lot_ of gray areas there, and no, technical measures does not make something derived or not.

In the kernel, we have tried to kind of clarify our thinking with the whole module interface, and the EXPORT_SYMBOL_GPL() distinction - the argument being one of both intent (which does have some legal weight, although the key word there is "some") and just to clarify that some parts are so clearly "internal Linux implementation" that if you need them, you're clearly not an independent module.

But everybody should know that that is not necessarily black and white either. Are GPL'd shim modules that use that EXPORT_SYMBOL_GPL() and thjen export something else (non-GPL'd) that uses them legal? They certainly fail the _smell_ test. A technical trick doesn't really have any legal meaning. If I were a judge (and I'm not, not even a lawyer), I'd certainly frown on it, but I might not take the initial EXPORT_SYMBOL_GPL() distinction all that seriously _either_.

Anyway, end result is that there's a lot of very murky "what is actually a derived work" issues.

I'd not be interested in ever having a lawsuit to "clarify" such an issue. I don't think it would really clarify anything anyway (it will just set one boundary in one case for one specific thing).

So it has to be a pretty damn obvious violation.

We should not be another crazy Oracle. Those guys are just looking like morons with their crazy legal theories. And I'm not saying that just because they keep losing.

And quite frankly, I've seen some crazy legal theories from the people who want to maximize the reach of the GPL. Things that would literally depend on the jury and judge not having a clue.

Linus

#7 lore raw
Quoted 46 lines · Linus Torvalds
Quoted 2 lines · Jeremy Allison

Can you describe the conditions you personally would feel justify filing a lawsuit over GPL non-compliance ?

You asked Ted, but I'll answer for one of the conditions for me: that it is not some gray area. It has to be a pretty damn clear violation.

Quite frankly, I've seen a lot of people be confused about what the GPLv2 actually says over the years. The most common confusion is the whole thing about "linking". It gets mentioned a lot.

Not only is "linking" not something that has any legal meaning, but the GPLv2 doesn't even mention it. Yet people _continually_ talk about linking.

I think the confusion actually comes from the FSF itself, and the original LGPL discussions, where the FSF at some point tried to convince people that linking against a GPL library somehow meant that the end result was a "derived work" in a very different way than "mere aggregation". It comes from some GPL maximalist argument, and it's where the whole LGPL came from, after all.

So a *lot* of people think that "linking" means that the GPLv2 is automatically in effect.

But what the license says - and more importantly, what copyright law itself actually is all about - is not linking, but "derived work".

And there's a _lot_ of gray areas there, and no, technical measures does not make something derived or not.

In the kernel, we have tried to kind of clarify our thinking with the whole module interface, and the EXPORT_SYMBOL_GPL() distinction - the argument being one of both intent (which does have some legal weight, although the key word there is "some") and just to clarify that some parts are so clearly "internal Linux implementation" that if you need them, you're clearly not an independent module.

But everybody should know that that is not necessarily black and white either. Are GPL'd shim modules that use that EXPORT_SYMBOL_GPL() and thjen export something else (non-GPL'd) that uses them legal? They certainly fail the _smell_ test. A technical trick doesn't really have any legal meaning. If I were a judge (and I'm not, not even a lawyer), I'd certainly frown on it, but I might not take the initial EXPORT_SYMBOL_GPL() distinction all that seriously _either_.

Quoted 8 lines

Anyway, end result is that there's a lot of very murky "what is actually a derived work" issues.

I'd not be interested in ever having a lawsuit to "clarify" such an issue. I don't think it would really clarify anything anyway (it will just set one boundary in one case for one specific thing).

So it has to be a pretty damn obvious violation.

So it's a "I know it when I see it" boundary, like porn or indecency :-).

Actually, that was pretty damn helpful. At least it shows there is a "this far and no further" line beyond which you think a lawsuit can be appropriate. I was getting worried that there was no violation so egregious that you'd think was worth legal action.

That way lies BSD-land.. (and the mountains of Madness :-).

Actually, your feelings are pretty similar to mine (other than the harsh words about the FSF, but then again they did kill your dog :-).

I try and set a similar set of boundaries when it comes to Samba - which can load the equivalent of kernel modules via our pluggable VFS interface.

My rules are:

1). In kernel - not my business (unless you're crazy enough to try and put the entirety of Samba in-kernel) - go forth with my blessings.

2). In kernel-but with "special“ system calls used by Samba VFS modules. Here I want the source code for the Samba VFS module released, but what's in the kernel is your business.

Interestingly enough there have been some vendors who tried to argue they could keep their system calls secret by hiding the Samba VFS code - but we ended up with a successful outcome (in one case by getting them to commit next release to a fully specified syscall interface as the one they were using was too ugly to support long term).

3). In a separate process - but Samba talks to it via IPC. Still not my code, but it's getting closer depending on how closely tied the IPC is. If your daemon simply won't do anything without Samba talking to it, then I'd argue this is probably a derived work. But it depends. This is the most difficult case, similar to your "independent module" question above.

I usually say if the IPC interface has other uses than just Samba (i.e. the NFS server uses it too), then it's not a derived work. I've successfully gotten several companies to architect their solutions this way to avoid any possible violation questions. It usually gets them to create a better solution as well, as thinking about an interface having to be used by multiple consumers almost always ends up in a better design.

4). Code modifications to Samba itself. You code is *mine*. Unless you're Amazon of course, who run Samba4 Active Directory in their cloud and never ship to their customers :-). Even then they're slowly but surely getting their changes upstream by contracting with one of the vendors who employ Samba Team members.

There are many other grey areas, but the main thing I try and do by enumerating these rules is to give clarity to corporations wanting to use the code.

The only time we've ever come close to a lawsuit was a long time ago with a company that just renamed the source code files, added a license manager and tried to sell us as a proprietary solution ! Even then it was only after we contacted their main purchaser to let them know what they were buying that these guys went back to stealing car radios, or whatever previous petty criminality they used to make a living doing.

Having said that these are just my opinions, and I know there are differing opinions within the Samba Team developers.

The main thing is that we all reach consensus before asking Conservancy to take any action on our behalf. The other Team developers trust Conservancy to act in a responsible way.

The way to ensure that happens is to join the Conservancy "GPL Compliance Project For Linux Developers" so your individual voice is heard. I'm sure they'd love to have you ! :-).

#8 lore raw
In reply to Linus Torvalds
Quoted 3 lines · Linus Torvalds

Not only is "linking" not something that has any legal meaning, but the GPLv2 doesn't even mention it.  Yet people _continually_ talk about linking.

They do, and it's a pain.

Quoted 2 lines

But what the license says - and more importantly, what copyright law itself actually is all about - is not linking, but "derived work".

You're close to one of the other errors that people continually make.

The licence specifically talks about "derivative or collective works".

It isn't just about "derived work" in the sense of "is your module a derived work of the kernel?".

It also includes "is your module shipped as part of a collective work including the kernel?".

And I'm not intending to get into specific *answers* to those questions in this case, but we should not forget that they *are* the questions.

You're right; we should not keep talking about "linking".

And we should not keep talking about "derived work" as if it's all that matters.

Signature · 1 line
dwmw2
#10 lore raw
In reply to Bradley M. Kuhn
Quoted 18 lines · Bradley M. Kuhn
Quoted 1 line

Because right now, I'm getting some _very_ mixed messages.

... a wise man once said, "talk is cheap; show me the code". So, judge me by my actual actions, not by twisting my words. It's easy to do because all this work has been done transparently. As a public charity, you can look at Conservancy's 990s and see all financial details related to GPL enforcement. As I said in another post, in more than ten years, Conservancy has been involved in exactly *two* lawsuits, with plenty of public documentation of what happened there. Recently, I and Karen were the *only* ones who were willing to publicly criticized Patrick McHardy for being unnecessarily litigious and non-transparent [1]. Overall, we only began the GPL Compliance program for Linux developers because developers *asked* for it. We remain accountable to them. We published the Principles of Community-Oriented GPL Enforcement, which were endorsed and/or lauded by many Linux developers, including the entire Netfilter team, as well as other charitable organizations including FSF, FSF Europe and the Open Source Initiative.

Quoted 3 lines

I *think* you are saying that I'm doing something wrong and hurting Linux. I'm not only willing to hear you on that -- in fact, I am alarmed and want to understand immediately what it is.

As I said earlier, you are somehow saying that if we don't "defend" the GPL in courts, we need to give up on it.

And that's just flat out not true, as I said before.

Your LCA talk this past year, which is online, you say many things about how the BusyBox lawsuits worked out (caused the creation of Toybox), how LLVM came about (supported because companies didn't want to deal with the FSF and GPLv3), and how that the only thing left to "fight over" is Linux.

I don't want to fight. For when you start fighting like this, you have lost, as I, and Linus now, keep pointing out.

Again, when the lawyers get involved, you have lost. I know you feel that you have to get lawyers involved to "win" the last bit of a fight, but really, that's pointless, because you just lost.

Someone in a reddit thread about this email conversation said, in trying to quote Linus, something along the lines of "the nuclear option should have been done to Allwinner a long time ago". And that proved my point exactly. Allwinner was a pain for a very long time. But as developers, and through the efforts of a lot of people at the Linux Foundation and Linaro, Allwinner is now a contributor to the kernel, and actively sponsors developers to write GPLv2 code for their chips. So, if, after talks like yours (between a representative of a kernel copyright holder and the company) breaks down, you would be forced to take legal action. And then we lost, even if you would have "won" the suit.

Seriously, this is NOT how to to things. Over the years yes, my position has changed from being pissed when I see devices ship without code for their changes, to realizing that I actually can do much more than any lawyer can. I can take those developers and make them part of our own project, ensuring we can survive.

Also, in your LCA talk you say about Linux kernel modules, and if I get this quote wrong, please let me know,
"And we’re going to have to actually adjudicate that, we don’t have a choice now. I used to shy away from this because it’s considered so controversial but we won’t have copyleft if we don’t have this confrontation."

And that's a very dangerous thing to say, or do. Because again, if you want to adjudicate this, that means you are willing to loose.

I told you this in the lobby of LinuxCon last year in Ireland around a table with many others present. You value the GPL over Linux, and I value Linux over the GPL. You are willing to risk Linux in order to try to validate the GPL in some manner. I an not willing to risk Linux for anything as foolish as that. And I told you that then in front of a small audience, and am willing to do so now in front of a much larger one.

Both you and Karen keep saying "we have to know and defend this", but that's what burned Busybox to the ground, and is what is threatening the future of gcc as well. It's great that Samba has survived this type of enforcement effort, but as Jeremy has pointed out, he's done that primarily by working directly with the companies, not having legal people get involved. So thanks Jeremy for proving my point :)

Let's please stick to what has gotten us this far, and not change to being rude and disrespectful to our users and developers by getting lawyers involved. That way we know will cause us to fail.

I routinely say that the only thing that will cause Linux to fail is if we do something stupid to ourselves, it's not going to happen by something outside of us. I see this as one of those extremely stupid things that we could easily do to ourselves that would cause us to fail.

Again, learn from history, suing people is not the way to survive. Working with the developers is the way. As companies like Intel (who used to be one of the worse offenders of the GPL out there before members of our community worked very hard to turn them around) and Allwinner and RockChip (getting more and more involved in our community) and even Microsoft (who now gets huge revenue from running Linux and is sponsoring kernel development because of this).

Look at the existing vendors you see today as not as "offenders" but rather as "potential members of our community" and treat them that way. It is the way we will continue to survive and grow. To not do so, is to kill off our own future.

Do you know who the next "Intel" will be as a huge corporate sponsor of Linux developers and intrinsic to our future? I sure don't, but I do know that by treating offenders with lawyers, you ensure that they never will be that type of supporter.

It's just like we treat new developers, you never know who will start out with just one patch, realize it's a lot of fun, and continue on to becoming a core developer. I started that way, and so did everyone except Linus. You have to treat everyone with respect in order to ensure that you can grow and survive.

So please stop this now, it's not helpful, but instead, hurtful, and harmful to our very survival.

greg k-h

#11 lore raw

I *thought* this list was for KS proposal meta-discussion, but this thread is now mostly substance and very little meta. :) However, AFAICT, no one has declared this thread as off-topic, and generally speaking, I believe everyone in the GPL Compliance Program for Linux Developers, including me, is glad to see GPL enforcement discussed openly. So, I'm continuing with replies:

Today, Greg made references to a talk I gave, and drew broad conclusions about my beliefs. Yesterday, Linus made reference to an LWN comment I made, and made conclusions about my moral character. This is a complex topic, and the entire breadth of everyone's view cannot be summarized by out of context snippets. I do think Greg's summary of my talk is inaccurate on many fronts, but the details on that don't really matter.

I believe we function well as a community by trying lots of different strategies in parallel. This works for Linux development itself, and it works for GPL enforcement too. I, Greg, and many others have done excellent work convincing companies to abide by GPL without lawsuits. Nearly all the work by the GPL Compliance Program for Linux Developers doesn't use lawyers or lawsuits. We all use the same strategy, and *almost* all the same tactics to achieve GPL compliance for Linux.

Our disagreement is over a finer point of a specific tactic that is only relevant in roughly 0.57% [0] of GPL violations, which is this: "What do we do in those cases that have no resolution for years, after many try to gain compliance and failed. Should anyone sue in that case?". Greg says: "No, never." The consensus in Conservancy's GPL Compliance Program for Linux developers is: we're giving up on the GPL as a strategy if we let those 0.57% just get away with violating, because even though the number is small, that group contains the truly bad actors; they'll set example for future bad actors. One reason (among many) we should bring lawsuits in those rare cases is to show everyone the 99.43% that they are much better off working with the community. We have plenty of evidence from company representatives who say
clearly: "I can't get my company to comply unless the threat of lawsuit is realistic; we agree it's totally reasonable to sue the very few bad actors". Greg, representatives of some the same companies that I know you've worked with to improve compliance have told me and Karen that directly.

Greg, in your email today, you've called for us to close up our Program:

Quoted 2 lines

So please stop this now, it's not helpful, but instead, hurtful, and harmful to our very survival.

The GPL Compliance Program for Linux Developers only does this work because real developers who have written code upstream in Linux work actively with Conservancy. You've ask them to stop working with us. Fortunately, they can see your directive above and act. The enforcement agreements are revocable. Every one of our many coalition members could walk away tomorrow, and I assure you that we'll close up the Program if they do.

Quoted 2 lines

and not change to being rude and disrespectful to our users and developers by getting lawyers involved.

I do know lawyers who are rude and disrespectful by default. (I also know some Linux developers who are rude and disrespectful by default.) But you're saying above that can't be categorically true about lawyers (or Linux developers): namely, that *all* lawyers are rude and disrespectful, in every situation. In our coalition's Linux enforcement actions, we don't typically bring a lawyer into the conversation until we're close to what I called Step
(3) [1]. But, even when we do, we'd only employ a respectful and friendly lawyer. I stopped working with rude and disrespectful lawyers years ago.

Quoted 1 line

Let's please stick to what has gotten us this far,

You ignore that we got this far by working in parallel toward the same goal. The GPL Compliance program for Linux Developers is more than four years old now. Before that, Harald was enforcing for Linux -- more litigiously than our coalition ever would, BTW -- since 2004. So, extremely rare litigation, guided by Linux developers, has been part of "what got us this far" for at least 12 years. Greg: you, and James, and me, and Karen, and Conservancy, and gpl-violations.org, and every member of the GPL Compliance Program for Linux Developers are all part of the "us" that "got us this far".

Greg wrote, on 27 August 2016:

Quoted 2 lines

Look at the existing vendors you see today as not as "offenders" but rather as "potential members of our community" and treat them that way.

Karen and I wrote together on 19 July 2016 [2]:

Quoted 1 line
Quoted 1 line
Quoted 1 line

Today's violators can then become tomorrow's contributors.

I wrote on 8 November 2009 [3]:

Quoted 3 lines
Quoted 3 lines

We therefore must ensure that enforcement action is reasonable and friendly. I view every GPL violator as a potential FLOSS contributor, and try my best to open every enforcement action with that attitude.

...and I made similar statements as far back as 2002. My position on this has never changed; I agreed with what you said today before you said it. Karen has also always held this position. Most importantly, to my knowledge, every developer in the GPL Compliance Program for Linux Developers agrees.

Quoted 4 lines

It's great that Samba has survived this type of enforcement effort, but as Jeremy has pointed out, he's done that primarily by working directly with the companies, not having legal people get involved. So thanks Jeremy for proving my point :)

You're misattributing Jeremy's statements as well. Jeremy said specifically that he works *with* Conservancy and that our methods *don't* get lawyers involved until the very tiniest fraction of situations where it's absolutely necessary. If Jeremy proved your point, then he also proved that Conservancy and our coalitions *are using the method of enforcement you want*.

Quoted 2 lines

that's what burned Busybox to the ground...and is what is threatening the future of gcc as well.

You're assessments of BusyBox and GCC are definitely incorrect. (BusyBox is still widely used and deployed, and the future of GCC is much more complicated than any enforcement-specific issues.) But I won't go into details on that because I worry it's just too far off topic for this list.

Finally, I'll address just one more of your assumptions about my values:

Quoted 2 lines

You value the GPL over Linux, and I value Linux over the GPL. You are willing to risk Linux in order to try to validate the GPL in some manner.

... which is false. Before you posted the above, I had already told you in response to your private email (which contained the same text) that it misrepresented my values. I won't bore the list with everything I said in my private reply, but here's the most relevant part:

You said that you "care more about Linux than the GPL". I would probably agree with that. But, I do care about software freedom generally much more than I care about Linux *or* the GPL. I care about Linux because it's the only kernel in the world that brings software freedom to lots of users. The GPL is a tool that helps Linux do that, but I don't see the GPL as a moral pinnacle. It's a tool and a strategy to advance software freedom. Linux doesn't matter merely because it's GPL'd. It matters because it's *great software* *and* it's GPL'd.

The GPL Compliance Program for Linux Developers works together to ensure all users may copy, modify, and redistribute all versions of that great software.

[0] I didn't just guess at this number. I searched my email archives, which roughly show that I've been sent reports of at least 3,000 GPL violations in my life, and I count only 17 defendants who have ever been sued by Erik Andersen, Christoph Hellwig, FSF or Conservancy (i.e., I'm counting BusyBox and Linux violations in there together, which should theoretically make the numbers as high as possible). That gives me 99.43% of GPL violators -- again, only count the ones I personally have been informed of -- have never been sued. I didn't include Harald's lawsuits because I'm not really sure on the count of his cases, but someone who'd like to can go through
http://gpl-violations.org/news/archive/ and count them up and update my numbers, but I think to make it a good estimate, you'd have to also update the denominator to count all violations ever reported to the gpl-violations.org mailing list too, which sadly are not online at the moment. ( links from http://gpl-violations.org/mailinglists/ are dead.)

[1] https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2016-August/003637.html
[2] https://sfconservancy.org/blog/2016/jul/19/patrick-mchardy-gpl-enforcement/
[3] http://ebb.org/bkuhn/blog/2009/11/08/gpl-enforcement.html

Signature · 4 lines
Bradley M. Kuhn
President & Distinguished Technologist of Software Freedom Conservancy
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter
#56 lore raw
In reply to Greg KH
Quoted 4 lines · Greg KH

Again, when the lawyers get involved, you have lost. I know you feel that you have to get lawyers involved to "win" the last bit of a fight, but really, that's pointless, because you just lost.

This seems to be your answer to the question:

"Can you describe the conditions you personally would feel justify filing a lawsuit over GPL non-compliance ?"

and your answer is "never".

That's a valid answer, and I respect that.

However, other Linux devs feel differently as they joined the Conservancy GPL Compliance Project For Linux Developers. There are licenses that embody the "no consequence for non compliance" attitude, the most popular being the BSD or MIT licenses of course.

Indeed there are popular alternative kernels under those licenses as I'm sure you're aware.

But they are not the license you have. You have the GPL.

The GPL allows legal penalties for non-compliance. We know this as there have already been such.

Your project has been enourmously successful - more so than any other Free Software project in the world. And it did so under the GPL.

You now appear to want to change the conditions under which most contributors added code - to one that has no legal penalties for non-compliance with the license.

If you really want that I'd genuinely be interested in you making such a proposal to the Linux kernel developers and askng them to change the license. Not being a kernel developer (other than some small cifsfs changes) I have no skin in the game but I'd love to see the results of that vote, I think it would be fascinating (and I give no predictions as to which way that vote would go).

But at that point you would have the condition you articulate above. You could ask non-compliant companies to send in code, and keep patiently working with them if they refused.

I do feel I should point out to you that this strategy has not worked with Apple, EMC, Isilon or NetApp - all of whom have significant kernels based on code under the BSD license but have refused to return any valuable code to the parent project.

But maybe the FreeBSD devs haven't just given them enough time or been nice enough to them or asked them enough times.

Maybe this experiment will turn out in their favour, it may be too early to tell (and Samba works on all the *BSD's so I'm ok either way :-).

In the meantime if you want to work on a kernel with your preferred license could you please fix the missing per-thread credentials in FreeBSD ? Samba has been needing that for years now (almost as long as I've been needing RichACLs in Linux :-).

Quoted 6 lines

Both you and Karen keep saying "we have to know and defend this", but that's what burned Busybox to the ground, and is what is threatening the future of gcc as well. It's great that Samba has survived this type of enforcement effort, but as Jeremy has pointed out, he's done that primarily by working directly with the companies, not having legal people get involved. So thanks Jeremy for proving my point :)

If you think that was the point I was making, I feel you didn't understand what I said.

I said that the outcome of lawsuits wasn't always the "loss" you seem to claim, and that the Microsoft vs EU lawsuit (although not a compliance-based one) is an excellent counterexample. Everyone in that lawsuit ended up winning, even Microsoft (give or take a billion dollars or so, which is pocket change for them :-).

When I do compliance work for Samba - before Conservancy ever hears about it (because I'm talking developer to developer), I'd like to think the companies I work with talk to me because I'm a nice guy and very helpful.

But on more than one occasion when I've been talking to the devs they also arrange a meeting with their legal staff involved.

What they always want to ask is if what we have architected or discussed together is sufficient to comply with their responsibilities under the GPL.

The reason they take me seriously, and I even get a seat at the table, is because of the work that Conservancy (and others) have done to ensure that GPL compliance is something that must be respected. Would I get a conversation going without that ? Maybe - but on more than one occasion I've only ever had a callback from the developers *after* I've sent a notice to the company they they are violating our license, a situation which if it continued could lead to real legal consequences for their products.

Quoted 2 lines

So please stop this now, it's not helpful, but instead, hurtful, and harmful to our very survival.

Greg, that's insulting to the hard work by Karen and Bradley and Conservancy staffers and is such a naive statement I find it hard to believe you believe it.

It reminds me of the "if only the lawyers would leave us alone we'd live in a sunshine paradise of unicorns and rainbows - us developers together" attitude I used to have back in the early 1990's when I first discovered the GPL.

You are second in command of a project that has generated literally *trillions* of dollars of revenue around the world and you think that involvement in legal issues is hurtful and harmful to the survival of that project.

I have news for you - Linux passed out of that phase around 1.10 in 1994 when you first got TCP/IP support (I think I have the history right, it was around then we decided to port Samba from SunOS to Linux as you finally had networking :-).

Dealing with legal and compliance issues is *mandatory* for all open source projects larger than one developer and their dog with a github account.

#57 lore raw
Quoted 4 lines · Jeremy Allison

Dealing with legal and compliance issues is *mandatory* for all open source projects larger than one developer and their dog with a github account.

You state that as an absolute fact, but there is nothing that really backs that up. An as mentioned, there really are very real arguments against your "fact".

Quite frankly, after having watched a few videos of Bradley talking about what he does and _why_ he does it, I really would never want to have him or the SFC represent Linux in court. Ever. Not unless they make it very clear that their agenda has changed.

Why? Because he explains how he feels that "strong copyleft" is inherently good, and Linux is the only remaining project big enough and meaningful enough to force legal attention on the GPL.

In other words, his publicly stated motivation for license compliance isn't for the good of the kernel - it's for the good of his license enforcement.

Quite frankly, if you let people like that be in charge of your legal team, you're crazy. That's insane. I'm not insane.

The only people I'd ever let be in charge of a lawsuit around Linux are the people who have the best interests of Linux in mind.

Definitely not people with an agenda, where Linux is just the *tool*.

We need to be very clear about this. The only possible situation where license enforcement makes sense is when it's good for the *project*. Not when it's good for license enforcement.

Linus

#58 lore raw
Quoted 9 lines · Linus Torvalds
Quoted 4 lines · Jeremy Allison

Dealing with legal and compliance issues is *mandatory* for all open source projects larger than one developer and their dog with a github account.

You state that as an absolute fact, but there is nothing that really backs that up. An as mentioned, there really are very real arguments against your "fact".

Well I'm remembering the early days of Samba, where we ran into lawyers pretty early. I also work with lawyers in my day job who have to talk to small FLOSS projects all the time (many who are just one person + dog + github).

So maybe I'm biased :-). I also could be wrong as well (it does happen :-).

Quoted 9 lines

Quite frankly, after having watched a few videos of Bradley talking about what he does and _why_ he does it, I really would never want to have him or the SFC represent Linux in court. Ever. Not unless they make it very clear that their agenda has changed.

Why? Because he explains how he feels that "strong copyleft" is inherently good, and Linux is the only remaining project big enough and meaningful enough to force legal attention on the GPL.

Quoted 6 lines

In other words, his publicly stated motivation for license compliance isn't for the good of the kernel - it's for the good of his license enforcement.

Quite frankly, if you let people like that be in charge of your legal team, you're crazy. That's insane. I'm not insane.

I could watch (in fact I *have* watched) some of your public talks and say "if you let people like that be in charge of your developer team, you're crazy" :-).

Everyone has some peculiarities (to quote Avenue Q: "Everyone's a little bit racist, sometimes" :-). You really have to judge their work, not their public persona I find.

Quoted 2 lines

The only people I'd ever let be in charge of a lawsuit around Linux are the people who have the best interests of Linux in mind.

That's funny - tridge and my original criteria for being on the Samba Team was being able to make a decision on behalf of Samba that went against the interests of your employer. We were very excited when we first saw that happen with IBM employees.

Quoted 5 lines

Definitely not people with an agenda, where Linux is just the *tool*.

We need to be very clear about this. The only possible situation where license enforcement makes sense is when it's good for the *project*. Not when it's good for license enforcement.

So I 100% agree with this. Which is why when Conservancy represents us it's only after consulting with and reaching consensus with the project developers and stakeholders (as not all stakeholders develop code - we have the "Samba Team" mail alias that represents this).

People can have a personal agenda, then put it aside when it's time to go to work. I've seen Bradley do that - but then again as I said I've known him a long time.

#61 lore raw
In reply to a message not in the archive
Quoted 3 lines · Linus Torvalds

We need to be very clear about this. The only possible situation where license enforcement makes sense is when it's good for the *project*. Not when it's good for license enforcement.

Can you clarify whether or not you believe that source availability for owners of devices that run Linux (even if the vendor chooses not to participate upstream) is something you consider to be good for the project?

#66 lore raw
In reply to Linus Torvalds
Quoted 5 lines · Linus Torvalds

Quite frankly, after having watched a few videos of Bradley talking about what he does and _why_ he does it, I really would never want to have him or the SFC represent Linux in court. Ever. Not unless they make it very clear that their agenda has changed.

So the thing I think you're missing here, is your own agument about enlightened "self interest".

Yes, Bradley and Conservancy have an agenda. They represent us (Samba) when that agenda and self interest *align with ours*. When they don't, nothing happens (remember they only act on our behalf).

It's just like development - they want one legal thing, you want another. Only when the two align do you work together.

So far it's worked very well (just like Linux :-).

#62 lore raw
In reply to Matthew Garrett
Quoted 4 lines · Matthew Garrett

Can you clarify whether or not you believe that source availability for owners of devices that run Linux (even if the vendor chooses not to participate upstream) is something you consider to be good for the project?

That question makes no sense.

Without an actual case, and without being able to judge the upsides *AND* downsides, your question is just silly.

You have clearly shown that you don't care about downsides. You don't seem to think it matters that yes, companies get very antsy about lawsuits even when they _themselves_ are not the target.

Because yes, I know for a *fact* that some companies stopped using BusyBox just because of the lawsuits. They weren't targeted, they weren't misusing it, they just decided that "it's a litigious project, it's simply not worth the risk".

And what is the source you would get available? Is it just the standard kernel sources? To be good to the project, there needs to be a point to the lawsuit - not just some technicality.

For example, there's a number of fly-by (mainly Chinese) companies that really seem to just put Linux on their devices and churn out one-offs. What does the project get from going after such a company that didn't even modify the source code, or made some silly one-liner things?

I know that some people are absolutely *itching* to see how copyright actually works in China, and I don't doubt for a second that there would be cases there if you want it for a test case.

But is there something really interesting going on? Or did you just want a test-case in China (or wherever)? Or was there just a proprietary module that you didn't like and you try to make a derived work on despite our years of accepting them?

These are questions that a person who cares about the *project* should ask.

Your questions seem to be questions that are asked by somebody who cares about compliance first.

See the difference?

Linus

#63 lore raw
Quoted 6 lines · Linus Torvalds
Quoted 4 lines · Matthew Garrett

Can you clarify whether or not you believe that source availability for owners of devices that run Linux (even if the vendor chooses not to participate upstream) is something you consider to be good for the

project?

Quoted 5 lines

That question makes no sense.

Without an actual case, and without being able to judge the upsides *AND* downsides, your question is just silly.

OK. A vendor sells 500,000 network-connected devices running a version of Linux that has a vulnerability in the network driver that's discovered a year later. The hardware is custom, they refuse to release source, and they've discontinued the product line, so nobody else is able to fix it. Is it acceptable to engage in litigation in order to ensure that owners of these devices can receive a security update, even if by doing so we alienate the vendor and cause them to choose another kernel in future?

(other than sales numbers, which I don't have direct insight into, this is not a hypothetical)

#64 lore raw
Quoted 8 lines · Matthew Garrett

OK. A vendor sells 500,000 network-connected devices running a version of Linux that has a vulnerability in the network driver that's discovered a year later. The hardware is custom, they refuse to release source, and they've discontinued the product line, so nobody else is able to fix it. Is it acceptable to engage in litigation in order to ensure that owners of these devices can receive a security update, even if by doing so we alienate the vendor and cause them to choose another kernel in future?

So why don't you name them and shame them very publicly and try everything else first?

If the vendor still exists, and sells other devices, make a big stink about it. It sounds like you've talked to them in private already, but why do you still call them "a vendor" now when you start talking about wanting to sue them?

Because without that, the answer is always going to be absolutely no, simply because of the "absolute last option" thing.

And you talk about how you're helping users, but how many of them would actually upgrade? Very few people end up upgrading firmware even when it's automatic, much less so if it would mean that they'd switch to OpenWRT or DD-WRT or something (since presumably the *existing* firmware ends up having lots of non-GPL'd sources that you wouldn't get even with a lawsuit)?

In other words, you say it is "for the users", but it still smells to me like it's actually "for the lawsuit".

In practical terms, how would that help Linux?

I can understand being annoyed. I'm annoyed by bad companies too. But I'm also saying that lawsuits aren't automatically the solution, and you really have to ask yourself if it's worth it. And you have to do a lot of other things first.

Linus

#12 lore raw
In reply to Bradley M. Kuhn
Quoted 1 line · Bradley M. Kuhn

I *thought* this list was for KS proposal meta-discussion,

Ideally if we can resolve it in email, we don't need a session ...

Quoted 6 lines

but this thread is now mostly substance and very little meta. :)
However, AFAICT, no one has declared this thread as off-topic, and generally speaking, I believe everyone in the GPL Compliance Program for Linux Developers, including me, is glad to see GPL enforcement discussed openly. So, I'm continuing with replies:

Quoted 7 lines

Today, Greg made references to a talk I gave, and drew broad conclusions about my beliefs. Yesterday, Linus made reference to an LWN comment I made, and made conclusions about my moral character.
This is a complex topic, and the entire breadth of everyone's view
cannot be summarized by out of context snippets. I do think Greg's summary of my talk is inaccurate on many fronts, but the details on that don't really matter.

OK, let me try for an accurate summary of the salient issues: A lot of kernel developers don't trust your motives enough to let you enforce their copyrights. Personally, I don't believe you even understand what it takes to convince a company of the business rightness of the GPL and thus, when you say "we tried talking to them", I believe you but I don't believe you had any conversations which could lead to a significant change in business practices, which is my primary issue.

However, Some developers do trust you and you've built a coalition of the willing around that and you're off selecting targets; but our problem, as a community, is that what you do with your coalition affects all of us and impacts the project we care about deeply.

There is a factual disagreement about what enforcement in other projects gained them. However, the loss of momentum in busybox is factual and does resonate and so does the theory that it's because of too many enforcement actions.

Quoted 8 lines

I believe we function well as a community by trying lots of different strategies in parallel. This works for Linux development itself, and it works for GPL enforcement too. I, Greg, and many others have done excellent work convincing companies to abide by GPL without lawsuits.
Nearly all the work by the GPL Compliance Program for Linux
Developers doesn't use lawyers or lawsuits. We all use the same strategy, and *almost* all the same tactics to achieve GPL compliance for Linux.

What's this "we"? Community is generated by contribution and most contribution gives rise to copyright. If you had enough copyright in Linux, you wouldn't need a coalition because you could enforce on your own.

Quoted 5 lines

Our disagreement is over a finer point of a specific tactic that is only relevant in roughly 0.57% [0] of GPL violations, which is this:
"What do we do in those cases that have no resolution for years, after many try to gain compliance and failed. Should anyone sue in that case?".

Heh, well, if I called bullshit, I'd lose my reputation for politeness (although perhaps Linus would finally come to respect me). Let me just point at that your 0.57% or however you define it, is why no corporation currently trusts you or wants to talk to you unless forced by their lawyers. Without mutual trust, there's no basis for negotiation, so all your attempts at compliance are overshadowed by this end game.

Your inability to recognise that there are other methods beyond holding out this 0.57% club, and that a lot of other people have achieved significant compliance and even community contributions using them, is why your statements generate such a lot of strong reactions. It reminds me a lot of the 70s and 80s "Mr President, under what conditions would you be willing to press the nuclear button?" which isn't really a world I want to go back to.

James

#13 lore raw

James Bottomley wrote, a few minutes ago:

Quoted 3 lines

I believe you but I don't believe you had any conversations which could lead to a significant change in business practices, which is my primary issue.... Your inability to recognise that there are other methods

Everyone here is talented and has different skills; please don't assume that yours are the only ones that produce value and good results. Anyway, this is why we brought VMware's violation [0] (and many other ones too) to you, to Greg, to Jim Zemlin, and to many others *before* we even began our Step 1. I told you privately many times what I now say publicly: you can acheive important compliance results that we can't, but vice-versa is also true.

Quoted 3 lines

but our problem, as a community, is that what you do with your coalition affects all of us and impacts the project we care about deeply. ... Without mutual trust, there's no basis for negotiation

Together, we're greater than the sum of our parts, if we all see past "my way or the highway" tendencies. Our coalition did that, by disclosing, to you and the LF, the violation reports that Conservancy received, so you could work on them first. When will you show similar cooperation and trust?

[0] https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2016-August/003562.html
--
-- bkuhn
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter

#70 lore raw
In reply to Jeremy Allison
Quoted 21 lines · On Sat, 27 Aug 2016 16:02:10 -0700 Jeremy Allison via Ksummit-discuss…
Quoted 4 lines · Greg KH

Again, when the lawyers get involved, you have lost. I know you feel that you have to get lawyers involved to "win" the last bit of a fight, but really, that's pointless, because you just lost.

This seems to be your answer to the question:

"Can you describe the conditions you personally would feel justify filing a lawsuit over GPL non-compliance ?"

and your answer is "never".

That's a valid answer, and I respect that.

However, other Linux devs feel differently as they joined the Conservancy GPL Compliance Project For Linux Developers. There are licenses that embody the "no consequence for non compliance" attitude, the most popular being the BSD or MIT licenses of course.

[...]

Quoted 11 lines

You now appear to want to change the conditions under which most contributors added code - to one that has no legal penalties for non-compliance with the license.

If you really want that I'd genuinely be interested in you making such a proposal to the Linux kernel developers and askng them to change the license. Not being a kernel developer (other than some small cifsfs changes) I have no skin in the game but I'd love to see the results of that vote, I think it would be fascinating (and I give no predictions as to which way that vote would go).

Who can predict that? Nobody ever expected Brexit to pass, right? ;-)

Anyway, if you ask 10 Linux kernel developers how they feel about their contributions to the kernel and the GPL, you'll get 10 different answers. The Linux kernel is owned by several copyright owners, and thus, everyone has the ability to choose how they will respond to non-compliance. Some may want to have the Conservancy to support them, others may not. It's really up to them. Obviously Linus and Greg choose not to. But they can't control what others may do.

Karen handed me a contract (again), and I still haven't had time to read it (lots of personal matters at hand at the moment). I wont know if I'll sign it till I've fully read it.

Personally, I believe the GPL has been the reason for the success of Linux, and yes, part of that is that people don't want to be sued for non-compliance. But copyright isn't the same as a trademark where one must defend it when an issues is known (at least in the US). Greg and Linus feel that diplomacy is the best method for getting companies to come around. But that takes time. Lawsuits are similar to going to war, and although war has faster results, usually those results do not end up as well as diplomacy would have in the long run.

I'm not sure Greg's answer is really "never". But I think this is similar to the analogy of dealing with rogue nations. Going to war is never actually off the table, but it's something that one really will avoid. One doesn't need to threaten lawsuits (or war), but the fact that lawsuits (and war) do exist and can be used, does live in the back of minds of those that are not in compliance.

Basically what I'm trying to say is that this is nothing like making Linux have a BSD license, but that GPL insists that people share, and that's the intent of the license. Being in non-compliance isn't just against the law, but also makes you look like a schmuck, and you can be shamed for that. One isn't shamed for not sharing the BSD code, because the BSD intent is do what you want, we'll just make more.

-- Steve

#14 lore raw
In reply to Bradley M. Kuhn
Quoted 9 lines · Bradley M. Kuhn

James Bottomley wrote, a few minutes ago:

Quoted 4 lines

I believe you but I don't believe you had any conversations which could lead to a significant change in business practices, which is my primary issue.... Your inability to recognise that there are other methods

Everyone here is talented and has different skills; please don't assume that yours are the only ones that produce value and good results.

I'm wasn't, but I get the impression you do. I also wasn't talking about results, I was talking about methods. Knowing there's a threat of legal action lurking in the background produces far different conversations because it puts the other party on the legal defensive ... for all of us, not just for you.

Quoted 5 lines

Anyway, this is why we brought VMware's violation [0] (and many
other ones too) to you, to Greg, to Jim Zemlin, and to many others *before* we even began our Step 1. I told you privately many times what I now say publicly: you can acheive important compliance results that we can't, but vice-versa is also true.

Well, my recollection of the first conversation about VMware in San Diego airport in 2012 was you telling me you wanted to go after them and me giving you all my concerns around the possibility of an adverse judgement. Beyond wanting my copyrights, I don't recall you asking for any strategic input.

Quoted 3 lines
Quoted 3 lines

but our problem, as a community, is that what you do with your coalition affects all of us and impacts the project we care about deeply. ... Without mutual trust, there's no basis for negotiation

That's not quite what I said since the latter statement referred to the process of negotiating compliance not negotiating within a community.
However, I suppose that is a valid point I didn't raise, so I'll
address it.

Quoted 4 lines

Together, we're greater than the sum of our parts, if we all see past "my way or the highway" tendencies. Our coalition did that, by disclosing, to you and the LF, the violation reports that Conservancy received, so you could work on them first.

Well, you told me you were going after them. I didn't realise that meant you were also offering me the opportunity to get them to settle on your terms ... However, now I do, the problem would have been that your terms aren't mine.

Quoted 1 line

When will you show similar cooperation and trust?

Since co-operation and trust seems to mean disclosure of intended actions, I believe I have. If it is to mean more, it would have to be mutual.

James

Quoted 4 lines

[0] https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2016-
August/003562.html
--
-- bkuhn

#74 lore raw
In reply to Jeremy Allison
Quoted 10 lines · Jeremy Allison via Ksummit-discuss

The GPL allows legal penalties for non-compliance. We know this as there have already been such.

Your project has been enourmously successful - more so than any other Free Software project in the world. And it did so under the GPL.

You now appear to want to change the conditions under which most contributors added code - to one that has no legal penalties for non-compliance with the license.

This might also be a core issue. I believe everyone participating in this debate agrees there should be consequences for non-compliance.
However, some people believe that the emphasis on "legal penalties"
produces an escalating atmosphere that precludes other avenues.

James

#17 lore raw
In reply to James Bottomley
Quoted 8 lines · James Bottomley

Heh, well, if I called bullshit, I'd lose my reputation for politeness (although perhaps Linus would finally come to respect me). Let me just point at that your 0.57% or however you define it, is why no corporation currently trusts you or wants to talk to you unless forced by their lawyers. Without mutual trust, there's no basis for negotiation, so all your attempts at compliance are overshadowed by this end game.

In an discussion, when you accuse your oponent of flat-out lying and being untrustworthy there's no place left to go.

Let's not do that. I don't think it's helpful.

However, "no corporation currently trusts you or wants to talk to you unless forced by their lawyers" is inaccurate (note I don't think you're lying, just mistaken here).

My employer is a large funder of Conservancy (check their funding spreadsheet for details), and I promise you we talk without legal requests to do so (even though Karen managed to crash the badging system here last time she visited :-).

Quoted 7 lines

Your inability to recognise that there are other methods beyond holding out this 0.57% club, and that a lot of other people have achieved significant compliance and even community contributions using them, is why your statements generate such a lot of strong reactions. It reminds me a lot of the 70s and 80s "Mr President, under what conditions would you be willing to press the nuclear button?" which isn't really a world I want to go back to.

That isn't the question that's being asked though. The question that is being asked is "should there be a nuclear button *at all* ?".

Your opinion on that is clear and I understand why you hold it. There are many other developers who hold the same opinion, but lots of them work on FreeBSD not Linux.

Respectfully, I don't agree with you. Greg and Ted seem to agree with you, Linus (like me) seems to imagine there can be a case for that shiny red button.

To be honest I never would have put you down as a CND supporter (but I suppose all those years you spent in a tent at Greenham Common should have given me a hint :-).

#71 lore raw
In reply to Steven Rostedt
Quoted 3 lines · Steven Rostedt

I'm not sure Greg's answer is really "never". But I think this is similar to the analogy of dealing with rogue nations. Going to war is

It seemed pretty clear to me that Greg's answer was that there was no possible situation where he would countenance an enforcement lawsuit against a GPL violator.

I really don't want to put words in anyones mouth or misread their intent so if I am mistaken or misread what he wrote I'd love to be corrected here.

#75 lore raw
In reply to James Bottomley
Quoted 9 lines · James Bottomley
Quoted 7 lines · Jeremy Allison via Ksummit-discuss

The GPL allows legal penalties for non-compliance. We know this as there have already been such.

Your project has been enourmously successful - more so than any other Free Software project in the world. And it did so under the GPL.

Quoted 5 lines
Quoted 3 lines

You now appear to want to change the conditions under which most contributors added code - to one that has no legal penalties for non-compliance with the license.

This might also be a core issue.

I agree this is a core issue.

Quoted 2 lines

I believe everyone participating in this debate agrees there should be consequences for non-compliance.

That isn't clear to me at all, unless "ask again, try and be nicer" counts as a consequence. I don't believe that it does.

Quoted 2 lines

However, some people believe that the emphasis on "legal penalties"
produces an escalating atmosphere that precludes other avenues.

"legal penalties" are a last, worst option - that I think everyone agrees with. The core issue to me is - should "legal penalties" *ever* be an option ?

My opinion (for Samba, the only area my opinion matters and feel free to tell me to bugger off a Linux kernel list and I'll shut up) is that they should. I would have sued the bastards renaming my code and adding a license manager for example :-). I'm only glad I didn't have to.

#67 lore raw
In reply to Jeremy Allison
Quoted 10 lines · Jeremy Allison via Ksummit-discuss
Quoted 5 lines · Linus Torvalds

Quite frankly, after having watched a few videos of Bradley talking about what he does and _why_ he does it, I really would never want to have him or the SFC represent Linux in court. Ever. Not unless they make it very clear that their agenda has changed.

So the thing I think you're missing here, is your own agument about enlightened "self interest".

Quoted 7 lines

Yes, Bradley and Conservancy have an agenda. They represent us (Samba) when that agenda and self interest *align with ours*. When they don't, nothing happens (remember they only act on our behalf).

It's just like development - they want one legal thing, you want another. Only when the two align do you work together.

Jeremy --- suppose there was a single person who had contributed to Samba, and he had a different opinion from the rest of the Samba team, and he went to the Conservancy on his own, and he and the Conservancy decided to take legal action on that one person's behalf (since it helped pursue the Conservancy's agenda, even if it didn't advance Samba's interests) --- and so it was something that you and the rest of the Samba developers didn't think was in the best interest of the Project. In fact, what if that legal action was something that disrupted a relationship with a company that you considered extremely strategic?

What would happen then? (Assume you weren't on the board, so you wouldn't be able to put the kibosh on it that way.) Perhaps more importantly, would you think that was morally a sound thing to do?

It's the fact that the Conservancy feels that it can cherry pick developers, and act even on matters where Linus has expressed a clear preference that it is *not* in the best interst of Linux, is why I think the term "rogue agent" very much applies.

- Ted

#15 lore raw
In reply to James Bottomley

James Bottomley wrote earlier today:

Quoted 3 lines

Knowing there's a threat of legal action lurking in the background produces far different conversations because it puts the other party on the legal defensive ... for all of us

Your primary argument centers around the idea that the mere *existence* of *anyone* willing to file a lawsuit about a Linux violation irreparably thwarts your ability to exercise your unique compliance-seeking skills. Greg has made similar arguments. If that's true, then I wonder what time frame you're talking about, since Harald has been filing lawsuits since 2004, and has filed so many about Linux. Conservancy has filed none; rather, we helped fund and provided some logistical support for Christoph's lawsuit.

Quoted 3 lines

Well, my recollection of the first conversation about VMware in San Diego airport in 2012 was you telling me you wanted to go after them and me giving you all my concerns around the possibility of an adverse judgement.

That was just a short time after we discovered a Linux violation was also present in addition to VMware's BusyBox violation [0], a full two years before Christoph became involved and three years before he chose to sue. (This timeline has been in the VMware lawsuit FAQ on Conservancy's website since the lawsuit was filed [1].) That FAQ makes reference to the fact that we sought assistance from "every industry contact we had".

You were among those industry contacts. That very LinuxCon week you mention, I encouraged you, Greg, and Jim Zemlin to do whatever you could to attempt to get VMware to DTRT and comply with GPL. I specifically asked you and Jim to reach out to them, since as LF Board members, you would have direct contacts with VMware, as a member company that funds LF.

Also, I believed, as you say, that you were skilled in some types of negotiation that I am not. (I specifically recall saying to you as I left for my flight: "we've just discovered the violation, so there's time; please do what you can in the meantime".) The large group of copyright holders who were unhappy at VMware's violation then waited for years for all of you to work your magic, but VMware never complied. I now understand...

Quoted 1 line

the problem would have been that your terms aren't mine.

... that whole part of the exercise was moot because you probably didn't want VMware to comply, anyway. That explains a lot; thank you for telling me.

Quoted 4 lines · Bradley M. Kuhn
Quoted 3 lines

Everyone here is talented and has different skills; please don't assume that yours are the only ones that produce value and good results.

Quoted 1 line · James Bottomley

I'm wasn't, but I get the impression you do.

Your impression is incorrect. I have great respect for your skill in achieving GPL compliance outcomes in the specific industry sectors where you've deployed them. I believe your stories of all the successes you've had and told me about over the years, and I thank you for that work.

[0] VMware's BusyBox violation was resolved *without* litigation, and VMware still ships, AFAIK, a GPL-compliant BusyBox as part of their products today -- yet another counter example to the incorrect memes about BusyBox and its enforcement in this thread.

[1] https://sfconservancy.org/copyleft-compliance/vmware-lawsuit-faq.html
--
-- bkuhn
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter

#55 lore raw
In reply to James Bottomley
Quoted 4 lines · James Bottomley

However, Some developers do trust you and you've built a coalition of the willing around that and you're off selecting targets; but our problem, as a community, is that what you do with your coalition affects all of us and impacts the project we care about deeply.

The fact that some developers felt it necessary to join a coalition to enforce their copyright rights suggests that they don't feel that the current structures around protecting Linux are doing a good enough job of doing so. You might want to think about why that is.

On another note - why does Bradley get such a bad rap ?

Personally, and having worked with him long enough, I think it's because when Bradley and Conservancy have to step into a situation it's because it's already gone beyond the normal methods of community engagement and policing.

My opinion of Bradley is that he is similar to Winston Wolf in Pulp Fiction. You don't call him in until you need him, but when you "got no friends in the 818 and someone needs to pick up itty-bitty pieces of GPL-violating code from your upholstery" then he's the guy whose number you need to remember :-).

We as developers usually get to play good cop to other developers, asking them to do the things that they really would like to do anyway. When they're prevented from doing that for whatever reason then you do need a bad cop to make the case to the people who are controling the actions of said developers that cooperation is good for all in the long run.

Without someone willing to do that thankless task - and it *IS* a thankless task as this mailing list thread has so aptly proven - all the good cops are left doing is asking if you need more coffee and donuts whilst you decide if you want to do the right thing. Some people will never get there on their own (see my previous comments about Apple, EMC, Isilon and NetApp for examples).

#68 lore raw
In reply to Theodore Ts'o
Quoted 30 lines · Theodore Ts'o
Quoted 10 lines · Jeremy Allison via Ksummit-discuss
Quoted 5 lines · Linus Torvalds

Quite frankly, after having watched a few videos of Bradley talking about what he does and _why_ he does it, I really would never want to have him or the SFC represent Linux in court. Ever. Not unless they make it very clear that their agenda has changed.

So the thing I think you're missing here, is your own agument about enlightened "self interest".

Quoted 7 lines

Yes, Bradley and Conservancy have an agenda. They represent us (Samba) when that agenda and self interest *align with ours*. When they don't, nothing happens (remember they only act on our behalf).

It's just like development - they want one legal thing, you want another. Only when the two align do you work together.

Jeremy --- suppose there was a single person who had contributed to Samba, and he had a different opinion from the rest of the Samba team, and he went to the Conservancy on his own, and he and the Conservancy decided to take legal action on that one person's behalf (since it helped pursue the Conservancy's agenda, even if it didn't advance Samba's interests) --- and so it was something that you and the rest of the Samba developers didn't think was in the best interest of the Project. In fact, what if that legal action was something that disrupted a relationship with a company that you considered extremely strategic?

Quoted 3 lines

What would happen then? (Assume you weren't on the board, so you wouldn't be able to put the kibosh on it that way.) Perhaps more importantly, would you think that was morally a sound thing to do?

I would be pissed off, for sure. But first I'd ask them why they felt they needed to do so ? What wasn't the Samba leadership doing that they wanted us to do ?

If they had been raising the issue for a long time, and had been ignored or their concerns sidelined without any resolution then I'd still be pissed off, but I'd understand why they did what they did.

And I'd have no grounds to prevent them from doing.

Samba has been forked in the past by people who wanted different things than we were willing to do - which came from a far more acrimonious internal discussion than this one within Linux (as forks often do).

How did we publicly respond ? Like this:

https://www.samba.org/samba/tng.html

"I look forward to seeing more development in TNG now that the developers are not constrained by the more conservative elements of the Samba Team (such as myself!) and I will be delighted to see the project flourish. There has been only one viable SMB server solution for the free software community for far too long, and a world with only one choice is a boring place indeed.

Andrew Tridgell
October 2000"

The fork failed, but that's not the point.

tridge always had more class than all the rest of us put together.

Quoted 4 lines

It's the fact that the Conservancy feels that it can cherry pick developers, and act even on matters where Linus has expressed a clear preference that it is *not* in the best interst of Linux, is why I think the term "rogue agent" very much applies.

See above for why I think you're wrong in calling Conservancy a "rogue agent".

#69 lore raw
In reply to Theodore Ts'o

Theodore Ts'o wrote a little while ago:

Quoted 2 lines

and act even on matters where Linus has expressed a clear preference that it is *not* in the best interst of Linux,

I can't figure out which matter you're talking about here. It can't be VMware, because, as I posted yesterday [0], I specifically talked with Linus about VMware before Conservancy made a commitment to work with Christoph, and Linus said "what they're doing is in bad taste and someone should probably do something about it".

Quoted 2 lines

It's the fact that the Conservancy feels that it can cherry pick developers,

The cherry-pick went the other way: developers cherry-picked *us*. As previously explained [1], developers came to Conservancy to ask us to help them enforce because no one else would help. Once Harald's organization, gpl-violations.org, was defunct, it was tough to keep saying "no" to them, so we finally just said "yes". (BTW, Harald told us in April that he may get gpl-violations.org running again, and if so he will coordinate with Conservancy.)

Also, either side can terminate the enforcement agreements at any time: the developers if they no longer trust Conservancy, or Conservancy can terminate if Conservancy chooses not to help those developers enforce anymore.

[0] https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2016-August/003637.html
[1] https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2016-August/003620.html
--
-- bkuhn
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter

#76 lore raw
In reply to Jeremy Allison
Quoted 4 lines · Jeremy Allison via Ksummit-discuss

"legal penalties" are a last, worst option - that I think everyone agrees with. The core issue to me is - should "legal penalties" *ever* be an option ?

As I said before, they have to be an option.

Because otherwise you basically don't have a negotiating position at all.

The GPL gives a *legal* framework under which a party is required to do certain things. You can't even point that fact out to a violator without *some* kind of implicit suggestion that they might be held to their legal obligations.

If all it took was "it'll be good for you and everyone else is doing it" then we wouldn't actually need the GPL licence at all; a BSD licence would be sufficient.

And if we added a clause to the kernel's COPYING file which made it says that "legally you have to release source... but we promise we'll never sue if you don't", then that basically *turns* it into a BSD licence for most purposes.

Legal penalties are a last worst option. Absolutely. But they have to *be* an option.

Signature · 1 line
dwmw2
#72 lore raw
In reply to Jeremy Allison
Quoted 5 lines · Jeremy Allison
Quoted 3 lines · Steven Rostedt

I'm not sure Greg's answer is really "never". But I think this is similar to the analogy of dealing with rogue nations. Going to war is

Quoted 7 lines

It seemed pretty clear to me that Greg's answer was that there was no possible situation where he would countenance an enforcement lawsuit against a GPL violator.

I really don't want to put words in anyones mouth or misread their intent so if I am mistaken or misread what he wrote I'd love to be corrected here.

Ok, I'm not saying "never should legal action be taken", but what I am saying is the same thing that Linus said, "only under the most dire circumstances", the nuclear option.

So yes, if someone takes all of our source code, slaps a different license on it and calls it something else, I would be first in line to call up my lawyer to get them to stop doing that. But that's never been the case here.

What is the case is that so far, I have seen that it is _ALWAYS_ better to work with the offending company than it is to go in with lawyers. Or representatives.

Go back and read my response to Bradley again and think about what a company goes through when someone shows up knocking at their door saying "I am a representative of copyright holders of the kernel, and want you to release all the code you are shipping." They batten down the hatches and work to fight against it for all of the reasons I already gave.

Compare that to a _developer_ going to that same company, finding the engineers who wrote that code, and asking them "hey, need any help in getting your code merged upstream to make your lives easier for your next product?"

Now you can work with that company, getting them to upstream bits and pieces of their code, until they are suddenly really invested in this community much more so than before and they see the business benefit of working together.

It's a totally different question, approach, and in the end, our way works, while the SFC's way does not.

I object to the SFC's position of "let us handle those pesky copyright issues for you" (paraphrased), as when a developer does that, they give up the real power that they have. The SFC's a one-trick pony (give us the code, all of it, throw it over the wall or we will sue), while as a developer, I have 101 tricks I can use to achieve even a better end-solution (the company is part of the community, not alienated by it.)

Developers are in a more powerful position than they realize, and I object to the SFC taking that power away. In fact, the SFC _needs_ developers in order to even be in business, if no developer signs their agreements, there's nothing for them to do!

So I strongly support developers getting the rights to their copyrights, not because it can be then used as a legal club to wield against others, but as a way to help ensure that their company continues to always invest and support Linux, as they know it works out better when everyone has a stake in it, not just individuals, and not just corporations.

We really are one big happy family here, but when the SFC (or the FSF) gets involved, we start bickering and problems happen. It did so with Busybox, and it is now doing so in Linux. And I don't want that to happen.

thanks,

greg k-h

#18 lore raw
In reply to Jeremy Allison
Quoted 7 lines · Jeremy Allison via Ksummit-discuss

Your opinion on that is clear and I understand why you hold it. There are many other developers who hold the same opinion, but lots of them work on FreeBSD not Linux.

Respectfully, I don't agree with you. Greg and Ted seem to agree with you, Linus (like me) seems to imagine there can be a case for that shiny red button.

For the record, I believe there can be a case for the shiny red button. I just want Linus, and not the SFC (or some --- as admitted by the SFC --- minority set of developers), to be the one who decides when it's appropriate to push it.

I've said it before, and I've said it again. For me, this is much more about a project governance issue. We don't let random pissed off army officers decide when to start World War III. Similarly Linux has establish consensus processes that take into accout *all* of the stakeholder, which yes, includes the those "evil corporations" that Bradley loves to bash so much in his conference talks. (Both Linus, Greg, and I have alluded to Bradley's talks, because fortunately, they are available on YouTube. And we've been looking at them, and then comparing them to what has been claimed to be the SFC's position by Bradley, Karen, and yourself.)

The SFC seems to be willing to take on a small subset of developers and seems to have asserted "we will do what our clients tell us to do". We might not or might not be able to stop the SFC, just as there are limits to what we could do to stop Patrick McHardy.

But Linus has stated pretty clearly what his preferences are, and if the SFC is going to 100% back the position Bradley has taken in his linux.conf.au talk vis-a-vis "we have to take on the kernel module question in as many legal venues as possible" and "having exhausted Busybox because companies have switched to Toybox due to the litigation risks, Linux is the next great battleground for the GPL" --- then perhaps it's understandable why a number of kernel developers aren't going to trust the SFC's agenda and motives.

- Ted

#19 lore raw
Quoted 3 lines

I've said it before, and I've said it again. For me, this is much more about a project governance issue. We don't let random pissed off army officers decide when to start World War III.

This, too, is completely inappropriate hyperbole. It is bizarre to draw comparisons between the level of destruction that a nuclear war would involve, and the act of holding a few law-breakers to account when years of attempting to get them to stop breaking the law has failed.

Remember, Harald held criminals to account in Germany for years without any signs of triggering armageddon.

The only people who have *anything* to fear are those who are breaking the law.

Even though I abhor what Patrick McHardy is doing, I still can't quite find it in my heart to have *sympathy* for his victims. Because it's not as if he's just taking random pot-shots at passers-by on the street. These people defended their actions in court, and lost.

In some way, we should all take responsibility for Patrick. Because if we hadn't been *so* lax about holding offenders to account, and if we hadn't allowed *so* much rampant abuse of our code to pass without taking action, there wouldn't have been so much low-hanging fruit for Patrick to make use of.

We'd all have been better off with *someone* doing what Conservancy does, and taking the time to work with companies to bring them into compliance -- using the far-off threat of litigation that nobody *really* wants to resort to, purely to keep them at the table..

Quoted 3 lines

Similarly Linux has
establish consensus processes that take into accout *all* of the stakeholder,

Linus explicitly declined to take copyright assignments, actually, so no consensus is required. Of course, you still only really have anything to fear from litigation if you'd actually *lose* it.

And sure, courts can be fickle but it's not exactly hard to make sure you are *clearly* obeying the licence.

Signature · 1 line
dwmw2
#54 lore raw
In reply to Jeremy Allison
Quoted 13 lines · Jeremy Allison via Ksummit-discuss
Quoted 11 lines · James Bottomley

Heh, well, if I called bullshit, I'd lose my reputation for politeness
(although perhaps Linus would finally come to respect me). Let me just
point at that your 0.57% or however you define it, is why no corporation currently trusts you or wants to talk to you unless forced
by their lawyers. Without mutual trust, there's no basis for negotiation, so all your attempts at compliance are overshadowed by this end game.

Quoted 4 lines

In an discussion, when you accuse your oponent of flat-out lying and being untrustworthy there's no place left to go.

Let's not do that. I don't think it's helpful.

I attacked the argument not the man.

Quoted 8 lines

However, "no corporation currently trusts you or wants to talk to you unless forced by their lawyers" is inaccurate (note I don't think you're lying, just mistaken here).

My employer is a large funder of Conservancy (check their funding spreadsheet for details), and I promise you we talk without legal requests to do so (even though Karen managed to crash the badging system here last time she visited :-).

OK, I'll modify no to hardly any. However, Google isn't such a great exemplar given that it's currently doing its new kernel under apache-2 and sees this as an advantage.

Quoted 11 lines
Quoted 7 lines

Your inability to recognise that there are other methods beyond holding out this 0.57% club, and that a lot of other people have achieved significant compliance and even community contributions using them, is why your statements generate such a lot of strong reactions. It reminds me a lot of the 70s and 80s "Mr President, under what conditions would you be willing to press the nuclear button?" which isn't really a world I want to go back to.

That isn't the question that's being asked though. The question that is being asked is "should there be a nuclear button *at all* ?".

Quoted 7 lines

Your opinion on that is clear and I understand why you hold it. There are many other developers who hold the same opinion, but lots of them work on FreeBSD not Linux.

Respectfully, I don't agree with you. Greg and Ted seem to agree with you, Linus (like me) seems to imagine there can be a case for that shiny red button.

That's a bit of a straw man: I've drawn the equivalency between litigation and the nuclear button, but I've never said there shouldn't be one.

I've actually spent a lot of time carefully preserving this option:
it's not actually an easy feat in modern America to ensure you own copyright in your own code, but I've done it. I certainly believe that once you press it, you're forever contaminated by the fallout.

James

Quoted 8 lines

To be honest I never would have put you down as a CND supporter (but I suppose all those years you spent in a tent at Greenham Common should have given me a hint :-).
_______________________________________________
Ksummit-discuss mailing list [email protected]
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

#25 lore raw
In reply to Theodore Ts'o
Quoted 9 lines · Theodore Ts'o

For the record, I believe there can be a case for the shiny red button. I just want Linus, and not the SFC (or some --- as admitted by the SFC --- minority set of developers), to be the one who decides when it's appropriate to push it.

I've said it before, and I've said it again. For me, this is much more about a project governance issue. We don't let random pissed off army officers decide when to start World War III...

Ted, there is a massive inconsistency here.

For decisions on legal action you want a top-town, corporate power structure - with only authorized management making decisions on when and how to proceed.

But for the project as a whole Linus has clearly said he expects self-interest to govern peoples actions.

*You can't have it both ways* ! If self interest governs peoples actions in joining in the project, then self interest also governs their activities in enforcing the license.

What you seem to have trouble with is that other contributors have *different* self-interests to you when it comes to enforcement.

You don't agree, and that's fine. But you can't control what other people chose to do, just like you can't control if they decide to participate in the project or not. People will do what they feel is in their own self-interest - just as you are doing here.

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

Ok, I'm not saying "never should legal action be taken", but what I am saying is the same thing that Linus said, "only under the most dire circumstances", the nuclear option.

So yes, if someone takes all of our source code, slaps a different license on it and calls it something else, I would be first in line to call up my lawyer to get them to stop doing that. But that's never been the case here.

Haha ! That's *exactly* what happened to us, and is the closest we've ever gotten to legal action over licensing :-).

Quoted 5 lines

Go back and read my response to Bradley again and think about what a company goes through when someone shows up knocking at their door saying "I am a representative of copyright holders of the kernel, and want you to release all the code you are shipping." They batten down the hatches and work to fight against it for all of the reasons I already gave.

But that's *not* what happens. You're implying that this is first contact. It isn't. The developers have already gone to that same company, tried to find the engineers who wrote that code, and asked them "hey, need any help in getting your code merged upstream to make your lives easier for your next product?"

Someone only shows up knocking at their door when that approach has failed - for *years*.

Quoted 4 lines

Compare that to a _developer_ going to that same company, finding the engineers who wrote that code, and asking them "hey, need any help in getting your code merged upstream to make your lives easier for your next product?"

Oh snap, eh ! :-).

Quoted 7 lines

Now you can work with that company, getting them to upstream bits and pieces of their code, until they are suddenly really invested in this community much more so than before and they see the business benefit of working together.

It's a totally different question, approach, and in the end, our way works, while the SFC's way does not.

You seem to think the two are completely mutually exclusive. That's not correct. The SFC has great flexibility in negotiations, and is responsible to the developers who allow them to act on their behalf.

Do you really think SFC is some kind of "independent" actor in these things ? SFC has an agenda, as does everyone. But developers interests are *paramount* for them.

Quoted 7 lines

I object to the SFC's position of "let us handle those pesky copyright issues for you" (paraphrased), as when a developer does that, they give up the real power that they have. The SFC's a one-trick pony (give us the code, all of it, throw it over the wall or we will sue), while as a developer, I have 101 tricks I can use to achieve even a better end-solution (the company is part of the community, not alienated by it.)

Again, that's not what is done. SFC also does these 101 tricks, and just like you they have to do them in *private*, to avoid embarrassment to the company in question.

Which may be why you have a wildly distorted view of what the SFC actually does when negotiating with companies.

Quoted 4 lines

Developers are in a more powerful position than they realize, and I object to the SFC taking that power away. In fact, the SFC _needs_ developers in order to even be in business, if no developer signs their agreements, there's nothing for them to do!

This is a misrepresentation of what the SFC does. As I've said before the SFC is like a union. Their interest is in their membership's rights.

Quoted 5 lines

So I strongly support developers getting the rights to their copyrights, not because it can be then used as a legal club to wield against others, but as a way to help ensure that their company continues to always invest and support Linux, as they know it works out better when everyone has a stake in it, not just individuals, and not just corporations.

This is 100% agree with ! Developers - KEEP YOUR OWN COPYRIGHTS ! I have always done so for Samba. It can be hard, but as Greg says here keeping your state as an individual gives you a voice.

Quoted 4 lines

We really are one big happy family here, but when the SFC (or the FSF) gets involved, we start bickering and problems happen. It did so with Busybox, and it is now doing so in Linux. And I don't want that to happen.

SFC is part of the family. Might be the ones you don't want to invite to your wedding, but they're related nonetheless :-).

#33 lore raw
In reply to Theodore Ts'o

Theodore Ts'o wrote at 05:55 (PDT) today:

Quoted 1 line

there are limits to what we could do to stop Patrick McHardy.

That's precisely why Conservancy and our coalition cooperated fully with the efforts by LF and others to seek mitigation techniques to deal with Patrick's activities. Conservancy worked closely with the Netfilter team as they developed their statement [0], and made a statement too about the problems with his enforcement [1]. We were delighted to help you with that issue.

Quoted 4 lines

For the record, I believe there can be a case for the shiny red button. I just want Linus, and not the SFC (or some --- as admitted by the SFC --- minority set of developers), to be the one who decides when it's appropriate to push it.

Others have replied to point out the way to centralize such GPL enforcement control is to mandate copyright assignment to Linus.

That isn't to say we shouldn't listen very carefully to what Linus has to say on the subject. We should take his opinions on this very seriously. This is why I sought Linus' advice before agreeing to help Christoph in the VMware case, and Linus told me he didn't want that control, and always wanted individual developers to make their own decisions. Like James and others, I also believe all copyrights should reside with individual developers, and copyright assignment should always be 100% optional.

Linux has a mixed bag on that last point. While there fortunately is no central authority that demands copyright assignment for all merged-upstream contributions to Linux, a non-scientific review indicates that most new Linux copyrights generated aren't in the hands of developers, but assigned to their employers. I suggest that Linux developers start demanding to keep their own copyrights, rather than giving them to any corporation (a for-profit company *or* a charity like I work for). Conservancy led the way by making copyright assignment 100% optional for all our projects since our inception, and recently launching the ContractPatch [2] initiative to help developers demand to keep (or get back) their own copyrights from their employers.

Quoted 4 lines

.... includes the those "evil corporations" that Bradley loves to bash so much in his conference talks. (Both Linus, Greg, and I have alluded to Bradley's talks, because fortunately, they are available on YouTube. And we've been looking at them...

I am glad that you've found the availability of my and Karen's talks useful. I take great logistical effort to make sure both my and Karen's talks are available because Conservancy does all of our work transparently. But, please don't attribute to me things I didn't say.

Specifically, I don't recall ever using the phrase "evil corporations" to refer to anything other than a joke. First of all I also work hard to avoid describing anything as "evil". It's inappropriate hyperbole; "evil" accurately describes atrocities like mass murder. Anyone able to respond to this thread is privileged because little (if anything) ever happens in our lives that's evil. Anyway, I *work* for a corporation (it's "Software Freedom Conservancy, Inc."), so if I thought corporations are were evil (or bad), I'd also think my own employer is evil (or bad). I don't.

Instead, what I have said, as I put on a final slide of a recent talk, is suggest that we should question the authority of corporations. I regularly question the behavior of all the employers of people posting on this thread, just as four of you here are questioning the behavior of my employer. Questioning, and receiving answers to those questions, is a healthy community process. (BTW, there are very few corporations who participate in the Linux community that rally the Chief Executive (Karen), a high-ranking staffer (me), and a member of their Board of Directors (Jeremy) to participate directly with the Linux community in discussions about important policy throughout the week *and* all weekend long.)

Finally, with regard generally to my past statements, I see a tendency by a small few on this thread to look at statements I made in years ago, and shoehorn those statements as a response to something specific in this discussion. This is particularly strange behavior given that I am *actually* responding actively to this thread -- it's not as if I'm some inaccessible public figure whom you can't ask to clarify and discuss an issue.

Also, I have not even been in *charge* of Conservancy's day-to-day operations for almost three years. Karen is, and she has *also* responded to this thread. So, worrying that my statements in some talk sets perpetual policy is akin to worrying that some statement that Linus makes in a mailing list will be automatically adopted by Jim Zemlin as official Linux Foundation policy. Linus surely has huge influence over LF policy just as I have huge influence over Conservancy policy, but neither of us makes the final call for our orgs. I explicitly abdicated that authority at Conservancy because Karen is the much better person for the job. As I said to James last night on this thread, I recognize when other people are better at things than I am and I work hard to ensure my work complements theirs. In my view, that's a fundamentally necessary trait for a Free Software contributor.

Quoted 1 line

But Linus has stated pretty clearly what his preferences are,

Yes, and like me, Linus makes lots of public statements, so we can just read his preferences [3]:

"I think licence choice is very much a personal issue, and while I personally prefer the GPL exactly because it 'forces' you to co-operate"

"if somebody decides that they want to enforce the GPL, and seriously believe they have a strong case for code they wrote, I think that's their choice too."

[0] https://marc.info/?l=netfilter&m=146887465012705&w=2
https://www.netfilter.org/files/statement.pdf
[1] https://sfconservancy.org/blog/2016/jul/19/patrick-mchardy-gpl-enforcement/
[2] https://sfconservancy.org/blog/2016/aug/04/everything-is-negotiable/
[3] http://www.itwire.com/open-source/74432-no-highs,-no-lows-linus-torvalds-on-25-years-of-linux.html
--
-- bkuhn
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter

#26 lore raw
In reply to Jeremy Allison
Quoted 11 lines · Jeremy Allison
Quoted 9 lines · Theodore Ts'o

For the record, I believe there can be a case for the shiny red button. I just want Linus, and not the SFC (or some --- as admitted by the SFC --- minority set of developers), to be the one who decides when it's appropriate to push it.

I've said it before, and I've said it again. For me, this is much more about a project governance issue. We don't let random pissed off army officers decide when to start World War III...

Quoted 5 lines

Ted, there is a massive inconsistency here.

For decisions on legal action you want a top-town, corporate power structure - with only authorized management making decisions on when and how to proceed.

I didn't say that. I said consensus driven and taking into account all of the stakeholders. If it makes you feel better, how about "Linus as the benevolent dictator"? He makes a point of gathering input from multiple stakeholders, and delegating authority to others for day to day decisions. That's how we do our development, after all.

- Ted

#34 lore raw
In reply to Bradley M. Kuhn
Quoted 7 lines · Bradley M. Kuhn

Finally, with regard generally to my past statements, I see a tendency by a small few on this thread to look at statements I made in years ago, and shoehorn those statements as a response to something specific in this discussion. This is particularly strange behavior given that I am *actually* responding actively to this thread -- it's not as if I'm some inaccessible public figure whom you can't ask to clarify and discuss an issue.

Actually, we're taking it from your 2016 LCA talk, "Copyleft for the Next Decade: A Comprehensive Plan", which you gave in February of this year. And one of the things which is interesting is that on this thread, there's an emphasis on "oh, we just want to get access to the source", whereas in the talk, it's more of "Linux will be the battleground over the future of Copyleft", with an explicit and clear emphasis of trying to litigate the question of kernel modules in multiple legal jourisdictions.

Well, people who live near battlegrounds often have a different opinion about sending in the troops compared to generals back in Washington D.C. whore are ordering in the drone strikes. So this is where listening to regrets of one of the Busybox founders might be educational.

The reason why it's fair game to compare your statements with statements made a few months ago is for the same reason why the Daily Show played back old clips of politicians. One of the really powerful things about You Tube and modern video technology in general is that it's much harder for politicians to say one thing to one constituency, and another thing to a different constituency. And to my mind, that's a really good thing.

Regards,

- Ted

#27 lore raw
In reply to Theodore Ts'o
Quoted 7 lines · Theodore Ts'o

I didn't say that. I said consensus driven and taking into account all of the stakeholders. If it makes you feel better, how about "Linus as the benevolent dictator"? He makes a point of gathering input from multiple stakeholders, and delegating authority to others for day to day decisions. That's how we do our development, after all.

So quite honestly, I think everybody would be much happier if we were not even ever in the situation where that would be required.

Personally, I really think that legal action by the "community" is not at all what we should hope for, or even _aim_ for. As mentioned, I don't think it has worked wonderfully well.

But we do have examples of Linux GPL-related legal action that I think we *all* can agree has worked absolutely stunningly well.

I don't think anybody disagrees that IBM's legal actions against SCO were a really good thing. No, that was not mainly about some "GPL test case" or "license clarification", and it wasn't even _mainly_ about the GPL.

But the GPL _was_ part of it, and both the license and the community came out really well in it.

What I'm happy about it is also that it was a defensive suit, and quite frankly, when we talk about "going to war" and "nuclear options", I have to say that "defensive" is also a big big positive. Because offensive use of nuclear options is just a f*cking bad idea. Seriously.

And to further take that example: it was also a very good example of how companies really can help us. Any legal enforcement discussion absolutely should *not* be about "how does the open source community enforce the GPL against companies". That's just stupid talk, and makes it be about "individuals vs companies", which IS NOT TRUE. That's simply not how the community has worked in Linux, and it isn't how it *should* work.

Seriously. I think we should see the IBM/SCO thing as an example of how we should all wish the GPL is to be used.

Do I want some "community effort" to try to create a "GPL test case" against some random badly behaving company that isnt' even all that *meaningful* from a development standpoint? Hell no. Quite frankly, anybody who sees that as a good end goal should haev their head examined. Yet that seems to be what the SFC sees as their goal in life.

We should put our goal posts in a totally different direction. We don't have a ":community effort" to do marketing. We all realize how completely idiotic and stupid that would be. A "Software Freedom Marketing Center" would be laughed at.

Why the hell do people not laugh at it when it comes to legal issues?

The fact is, Linux is in a very different position than the one that Jeremy Allison describes for samba. Or the one we were in 20 years ago. We have very consciously tried to make various companies be *part* of our community, and they have been an incredibly powerful resource. They employ a lot of the engineers, but they do so much more too.

So I seriously believe that we should not see companies as the "enemy" and as a target of lawsuits. We should see the Linux companies as a big part of the community, and as the natural *defender* of the GPL.

And we already have a really good example of that that people seem to be ignoring.

I would really want people to completely change their thinking about this "GPL enforcement" thing.

The great thing about the GPLv2 was how it turned copyright law "against itself" (really just against traditional use of copyrigth) and it has been described as a legal "judo move" - using copyright to *open* software instead of using it as a way to *restrict* software. It's why people call it "copyleft", after all.

THAT is the beauty of the GPLv2.

But the people who then see proprietary software as "evil", and see companies as being amoral, and as the enemy (and this very much is how rms and the FSF was acting), those people were doing exactly the wrong thing, and I have been fighting that idiocy for as long as I've been using the GPLv2.

The fact that we didnt' see proprietary software as evil, and that we opened our arms to companies made all the difference.

Now those same small-minded people are making the SAME MISTAKE, all over again. I do *not* want anybody who talks about "evil" proprietary software to be the seen as the "protector" of the GPL. No, people who talk about how proprietary software is "evil" should be seen as *stupid* people. Because they are. We showed them wrong.

And similarly, we should *not* see this as some crazy "community is protecting itself against companies" crap. Again, that's the stupid and wrong-headed FSF thinking. It's bad.

We have a ton of companies that are part of the community, and the same way we're bad at marketing and rely on companies to do that, we should at least _strive_ to work towards companies doing legal enforcement too.

That's the true "judo" move.

Because quite frankly, I think just by going by existing history, companies are better at lawsuits than the community is anyway. Just look at IBM.

Linus

#16 lore raw
In reply to Bradley M. Kuhn
Quoted 5 lines · Bradley M. Kuhn

James Bottomley wrote earlier today:

Quoted 3 lines

Knowing there's a threat of legal action lurking in the background produces far different conversations because it puts the other party on the legal defensive ... for all of us

Quoted 8 lines

Your primary argument centers around the idea that the mere *existence* of *anyone* willing to file a lawsuit about a Linux violation irreparably thwarts your ability to exercise your unique compliance-seeking skills. Greg has made similar arguments. If that's true, then I wonder what time frame you're talking about, since Harald has been filing lawsuits since 2004, and has filed so many about Linux. Conservancy has filed none; rather, we helped fund and provided some logistical support for Christoph's lawsuit.

I thought it was clear, but just in case, we're talking about now.

Quoted 27 lines
Quoted 4 lines

Well, my recollection of the first conversation about VMware in San Diego airport in 2012 was you telling me you wanted to go after them and me giving you all my concerns around the possibility of an adverse judgement.

That was just a short time after we discovered a Linux violation was also present in addition to VMware's BusyBox violation [0], a full two years before Christoph became involved and three years before he chose to sue. (This timeline has been in the VMware lawsuit FAQ on Conservancy's website since the lawsuit was filed [1].) That FAQ makes reference to the fact that we sought assistance from "every industry contact we had".

You were among those industry contacts. That very LinuxCon week you mention, I encouraged you, Greg, and Jim Zemlin to do whatever you could to attempt to get VMware to DTRT and comply with GPL. I specifically asked you and Jim to reach out to them, since as LF Board members, you would have direct contacts with VMware, as a member company that funds LF.

Also, I believed, as you say, that you were skilled in some types of negotiation that I am not. (I specifically recall saying to you as I left for my flight: "we've just discovered the violation, so there's time; please do what you can in the meantime".) The large group of copyright holders who were unhappy at VMware's violation then waited for years for all of you to work your magic, but VMware never complied. I now understand...

Quoted 5 lines
Quoted 1 line

the problem would have been that your terms aren't mine.

... that whole part of the exercise was moot because you probably didn't want VMware to comply, anyway. That explains a lot; thank you for telling me.

I didn't tell you that. You're equating not supporting all the terms you want to impose (some of which are pretty onerous in the post settlement regime) with being pro violators. This would appear to be your way or the highway.

James

Quoted 34 lines
Quoted 4 lines · Bradley M. Kuhn
Quoted 3 lines

Everyone here is talented and has different skills; please don't assume that yours are the only ones that produce value and good results.

Quoted 1 line · James Bottomley

I'm wasn't, but I get the impression you do.

Your impression is incorrect. I have great respect for your skill in achieving GPL compliance outcomes in the specific industry sectors where you've deployed them. I believe your stories of all the successes you've had and told me about over the years, and I thank you for that work.

[0] VMware's BusyBox violation was resolved *without* litigation, and VMware
still ships, AFAIK, a GPL-compliant BusyBox as part of their
products
today -- yet another counter example to the incorrect memes about
BusyBox
and its enforcement in this thread.

[1]
https://sfconservancy.org/copyleft-compliance/vmware-lawsuit-faq.html
--
-- bkuhn
=====================================================================
===
Become a Conservancy Supporter today:
https://sfconservancy.org/supporter
_______________________________________________
Ksummit-discuss mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

#35 lore raw
In reply to Theodore Ts'o

Theodore Ts'o wrote earlier today:

Quoted 3 lines

The reason why it's fair game to compare your statements with statements made a few months ago is for the same reason why the Daily Show played back old clips of politicians.

I'd be delighted to go through a political vetting process with those of you that want that, but I suggest it's better to move that off-list. We could later produce the email thread as one unit for people to read if they like. Contact me off list if you'd like to do that. (As such, this will be my last on-list response to anything related to material from my past talks, etc.)

I do wonder, however, if vetting me will actually yield the results you want. Many already pointed out that (a) Conservancy's actions are on behalf of our coalition, at their behest, and also that (b) Karen Sandler is my boss. So, I answer to both the coalition *and* her in any actual work that I might do. While I admit that I love talking about my own opinions on things (and it seems that Ted enjoys watching videos of my opinions -- BTW, I'd certainly enjoy the "Daily Show with Ted Ts'o" more than "with Trevor Noah"), I really wonder if most folks on the list, or in the larger Linux developer community, care about *my* words as opposed to the *coalition's* actual actions, which I agree do deserve substantial attention and I encourage you to vet them.

Quoted 3 lines

Well, people who live near battlegrounds often have a different opinion about sending in the troops compared to generals back in Washington D.C. whore are ordering in the drone strikes.

...
Linus Torvalds wrote elsewhere in the thread:

Quoted 1 line
Quoted 1 line

But the people who then see proprietary software as "evil"

I don't believe any company, organization, entity or person mentioned in this thread is evil, including the ones that produce proprietary software. I certainly want a world where proprietary software doesn't exist, but proprietary software is not evil; calling it such is as hyperbolic as comparing enforcing the GPL to drone strikes.
--
-- bkuhn
========================================================================
Become a Conservancy Supporter today: https://sfconservancy.org/supporter

#20 lore raw
In reply to David Woodhouse
Quoted 4 lines · David Woodhouse

Even though I abhor what Patrick McHardy is doing, I still can't quite find it in my heart to have *sympathy* for his victims. Because it's not as if he's just taking random pot-shots at passers-by on the street. These people defended their actions in court, and lost.

No, that's not what Patrick did. Whenever he actually took something to court, _he_ lost. Companies paid him off before then because they were scared for foolish reasons, or it was honestly just cheaper to do it than go to court and win. He took the traditional model of patent troll to the next level.

No one I have talked to has ever said that any of those companies were actually doing anything "wrong" with regards to the GPL at all. He just went for small companies who couldn't defend themselves.

Again, just like patent trolls. Go watch the wonderful talk at the LF Collab summit this year from Lee Cheng, the lawyer from New Egg as to how he has worked really hard to stop patent trolls, and how, even if you don't do anything wrong at all, you can easily get sued by them, and how much work it takes to fight these type of things.

We don't want GPL "enforcement" to ever be like patent trolls, that way is a death sentence for Linux. Just like what happened to Busybox.

thanks,

greg k-h

#36 lore raw
In reply to Bradley M. Kuhn

Dear Linus, Ted, Greg and others,

sorry for being late to the party.

Given that I've been somebody doing quite a bit of GPL enforcement on the Linux kernel in the 2003-2010 time frame with my gpl-violations.org initiative, I think I may share some perspective.

For those not aware, gpl-violations.org was created out of some netfilter/iptables project enforcement after the first Linux based WiFi routers came on the market in about 2003. It used my own copyright on netfilter/iptables, as well as some copyright from Rusty Russel, David Woodhouse and Werner Almesberger, who helped me with that effort.

As I've been mostly absent from netfilter/iptables and moved my focus to a topic that I feel is in more desparate need of free software development (FOSS cellular infrastructure, now at osmocom.org), the gpl-violations.org efforts had become dormant meanwhile.

During the active time of the project, we had some ~ 300 GPL violation cases, out of which the large majority could be resolved out of court. IIRC, less than 10 had to go to court, because the respective infringing entity has not been willing to get into compliance. All enforcement in court was successful, i.e. in the end, the ruling was in favor of upholding and enforcing the GPL against those infringers. All of the cases were about cease + desist, and none about damages.

We always had way more (confirmed) reports of GPL violations than we ever could handle, and despite a general trend to more compliance in the industry today than 10 years ago, Linux is entering new markets / device types / uses cases, and as a result of that I doubt that we've reached "peak violation" yet. So *lots* of work remains to be done.

I've also been a bit sad that many developers of copyleft-licensed software told me they think it's great that somebody is doing enforcement - but they didn't want to get active themselves, due to the unpleasant paperwork involved, which only distracts them from actual development work.

So there clearly was space for an entity that would enable the developers (who hold their own copyright) to do something about license enforcement, but without having to take care of all the nitty-gritty legal details themselves. And I'm quite happy that the SFC has done something to fill that void.

* I agree with David Woodhouse and others earlier in the thread: Using the GPL and not doing enforcement is useless, and you should have gone for BSD/MIT instead, if that's the goal.

* In all I know, see and hear about the activities of the Software Freedom Conservancy, they always explicitly act upon what the developers ask them to do. What I know about their "Coalition Membership" agreement is that it exactly reflects that notion, i.e. the SFC cannot act on its own, but only on behalf of its coalition members, who are individual Linux kernel developers who hold their copyright.

* It might differ from jurisdiction to jurisdiction, but in general if you hold copyright on one part of a collaborative project like the Linux kernel, you are entitled to enforce at least a cease + desist claim on your own behalf and do not need the support of all the other copyright holders or even the majority of the copyright holders. I consider this a strength of the "distributed copyright" approach, where you don't have a single point of failure (copyright holder), or an ologopoly of large corporations who have control over who can enforce or cannot enforce. Sure, this has some risks as we have seen with the alleged actions by Patrick McHardy. But then, doesn't every freedom come with some risk?

Quoted 3 lines · Linus Torvalds

I'd not be interested in ever having a lawsuit to "clarify" such an issue. I don't think it would really clarify anything anyway (it will just set one boundary in one case for one specific thing).

You might not have an interest in that lawsuit, but actually a lot of corporate users (and lawyers) might actually like to have more clarity here. Yes, every case will be very specific about the exact type of integration between two parts of the code, within the given jurisdiction, etc. - but if you have a set of these, they can give guidance as to what is acceptable under copyright law and it's notion of derived (and other combined/collective) works, and what not.

That's how legal grey areas are generally treated. Some rules exist, some people do something that other people thinks goes beyond the boundary of those rules, a legal conflict ensues and one precedent after another, courts bring more fine-grained clarity to narrow down the grey area into more black and white, and less grey.

Now whether it would be good for Linux (or FOSS in general), is probably a philosophical question. I'm just saying particularly corporate users would love to have more clear-cut rules by which they could determine compliance in derived works.

Also, of course it is not clear whether "we" (Linux developers) would like the exact outcome of suhc cases.

In the end it boils down to: Do we want to linger more in grey areas and have people with varying view points and agendas making all kinds of statements and assumptions, or do we defer to the "arbitration" of case law to do it for us?

I'm personally not so sure that keeping things lingering in the grey is always the best strategy, also from a commercial/economical point of view.

But then, I still think that cases about derived works like the VMware vs. Christph Hellwig are important. Otherwise, once again, what is the point of having a copyleft/GPL licensed OS kernel, if vendors of proprietary OSs can just take entire sub-systems (or parts of that), and hack that up to run inside their proprietary kernels? If that's the intent, again, BSD/MIT would have been the right license.

Quoted 5 lines · Greg-KH

Seriously, this is NOT how to to things. Over the years yes, my position has changed from being pissed when I see devices ship without code for their changes, to realizing that I actually can do much more than any lawyer can. I can take those developers and make them part of our own project, ensuring we can survive.

I don't think it is an exclusive-or. In many cases, legal action (either out of court or in court) has been a trigger to companines putting attention on FOSS / GPL license compliance in the first place, and massively helped even those forces inside the company that wanted to release the code.

You talk in legal language to the legal departments. They bring it up to the senior management for a risk assessment. And the result of that assessment will determine whether or not they feel inclined to do anything about it (both for the current case and for future strategy), as the latter will cost money/resources. So in the absence or mostly absence of legal enforcement, the result of the risk analysis will be "it won't cost us anything to continue to not care".

At the same time you can try to get in touch with the engineers in terms of working more cooperatively with the community. But then, they don't make those decisions and have to defert that up to their management. If the management then in the ideal case at some point realizes that
a) they don't want to keep stuff proprietary for legal risk reasons, and
b) they might have other benefits from not doing 'gpl code drops' but working with upstream,
you have won.

However, the legal enforcement is in my experience often a neccessary first step to make them release source code in the first place. Only then you can have a discussion about the form (code drop vs. git repos vs. community interaction).

Quoted 3 lines · Greg-KH

Let's please stick to what has gotten us this far, and not change to being rude and disrespectful to our users and developers by getting lawyers involved.

I am not sure if we live on the same planet ;)

Using a lawsuit as the last resort option to get incompliant companies in line is not rude at all. It is at the end of a process, where the infringing entity is not willing to be compliant (translates to: release the complete+corresponding source code) without such a lawsuit.

So if you want to talk about 'rude' in this context, you could also say the other way around: The infringing entity is rude by ignoring our community and how it works, and by furthermore ignoring the essential requirement to comply with the license term (like any software or copyrighted material).

I can even confirm about several cases where the "Linux friendly" people (including lawyers + technical) at formerly-infringing companies have thanked me privately again and again for giving their cause inside the company a stronger backing, and for being the external trigger that helps to bring them around internally.

As described above, I think talking to the legal departments gives you a very important vector into those companies.

Quoted 1 line · Greg-KH

That way we know will cause us to fail.

I can tell you about one of te largest electronics companies on this planet, who have set up internal teams to study and review license compliance in more than 1000 products _after_ their market introduction, and who have significnat departments inside the organizations to ensure license compliance from thereon. That all was the result of legal enforcement (all out of court, but involving lawyers) being done at gpl-violations.org. And btw, at some point later, they also started contributing to FOSS projects more openly.

The point here is: Legal threats (or sometimes lawsuits) are wake-up calls to companies that _want_ to do the right thing, but who simply haven't been aware of it, or who haven't given it theright attention/priority before. They are *not* upset about enforcement being brought against them.

Of course this largely depens on corporate culture of the respective formerly-infringing entity. But I really have to dispute your blanket statement on "getting lawyers involved will cause us to fail".

Quoted 4 lines · Greg-KH

Do you know who the next "Intel" will be as a huge corporate sponsor of Linux developers and intrinsic to our future? I sure don't, but I do know that by treating offenders with lawyers, you ensure that they never will be that type of supporter.

I don't want to call out the name of my above example, but they actually fit your description pretty well and have become a large corporate sponsor of Linux. I'm happy to share the example privately, if you'd like.

Legal disputes are not the end of the world, or a nuclear option, or a drone bomb. They are part of a civilized discoures between entities that at least at that point have a different opinion, or had ben ignorant. And a legal dispute escalating to court (even in case the infringing defendant agrees they were wrong) may have all kinds of reasons unreated to the subject matter.

Quoted 3 lines · Greg-KH

What is the case is that so far, I have seen that it is _ALWAYS_ better to work with the offending company than it is to go in with lawyers. Or representatives.

You can get very good results by talking to legal departments of companies, I can absolutely vouch for that. In fact, at gpl-violations.org I had given up to try to contact the companies in any other way. You simply never get to the right person in charge, and are mostly wasting your time. However, if you go through the legal department, you get the attention of the decision makers pretty soon. In most cases, it is a very productive dialogue, and not a battle or a fight. I really think you're overly paranoid when it comes to members of the legal profession.

In any case, getting slightly more on topic regarding ksummit: If anyone was interested to hear more about my take on Linux GPL enforcement, I'd be more than happy to share it. Be it at the kernel summit or other event. Be it as a bof, talk, panel, whatever. I would like to hope that I'm perceived as less "partisan" here, given that
a) I am an actual (albeit past) Linux kernel developer, and
b) was never aligned with the SFC or the FSF, nor any large corporation
c) have lots of hands-on experience on the subject matter.

It's an offer. I don't seek to push myself onto centerstage with this, but let me know if anyone thought it would be useful.

Regards,
Harald

Signature · 4 lines
- Harald Welte <[email protected]>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)
#21 lore raw
In reply to Greg KH

Hi Greg,

Quoted 2 lines · Greg KH

No one I have talked to has ever said that any of those companies were actually doing anything "wrong" with regards to the GPL at all.

I'm not sure whether this is generally true. As somebody very concerned about "bad" enforcement and the fall-out it can generate, and also as somebody who has maybe even set the example on how to do GPL enforcement (in Germany) at all, I have had a look at some of the (few) cases that actually went to court, and actually also attended one of the court hearings (against Telefonica) in person. And the reason he lost (or rather backed out before loosing) that particular one was merely based on procedural mistakes, and not on merits of the case. Unfortunately the detailed legal briefs and filings of lawsuits in Gemany are not published (and to the contrary, they are copyrighted works of the lawyers who write them), so it is rather hard to know what actually happened.

So yes, there are all kinds of allegations and rumours about what Patrick did or didn't do. With none of the parties involved talking about what actually happened, it is difficult to get down to the truth.

The biggest problem that I actually see in terms of Patrick's enforcement that he didn't talk about it, and hence created an atmosphere where rumours, fear, uncertainty and doubt can dominate the discussions. His unwillingness to explain himself even within the netfilter developers or the netfilter core team were also the reason why he ultimately was suspended.

Quoted 1 line

He just went for small companies who couldn't defend themselves.

This is getting more and more off-topic, but I wouldn't e.g. call Telefonica a "small company".

Quoted 2 lines

We don't want GPL "enforcement" to ever be like patent trolls, that way is a death sentence for Linux.

This is very clear, and that's what the SFC has spearheaded with it's "principles of community-oriented enforcement".

So yes, if the allegations against Patrick are true, then it is something where probably everyone in this discussion thread agrees it is far outside the consensus of when or how enforcement should be done. But it is exactly because it is _against_ what the SFC stands for, not because the SFC is in any way doing anything that can be compared to the alleged activities of Patrick McHardy.

Regards,
Harald

Signature · 4 lines
- Harald Welte <[email protected]>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)
#77 lore raw
In reply to Greg KH

Hi Greg,

Quoted 7 lines · Greg KH

Someone in a reddit thread about this email conversation said, in trying to quote Linus, something along the lines of "the nuclear option should have been done to Allwinner a long time ago". And that proved my point exactly. Allwinner was a pain for a very long time. But as developers, and through the efforts of a lot of people at the Linux Foundation and Linaro, Allwinner is now a contributor to the kernel, and actively sponsors developers to write GPLv2 code for their chips.

While I generally agree with you on this topic, this is simply not true.

As the Allwinner SoC maintainer, I never received any patch from someone either from the Linux Foundation or Linaro. And to the best of my knowledge, I'm not aware of anyone being paid by Allwinner to work on the kernel.

Allwinner is not a pain anymore because a few hobbyists started working on the kernel to improve the situation.

Maxime

Signature · 3 lines
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#78 lore raw
Quoted 11 lines · Maxime Ripard

Hi Greg,

Quoted 7 lines · Greg KH

Someone in a reddit thread about this email conversation said, in trying to quote Linus, something along the lines of "the nuclear option should have been done to Allwinner a long time ago". And that proved my point exactly. Allwinner was a pain for a very long time. But as developers, and through the efforts of a lot of people at the Linux Foundation and Linaro, Allwinner is now a contributor to the kernel, and actively sponsors developers to write GPLv2 code for their chips.

Quoted 7 lines

While I generally agree with you on this topic, this is simply not true.

As the Allwinner SoC maintainer, I never received any patch from someone either from the Linux Foundation or Linaro. And to the best of my knowledge, I'm not aware of anyone being paid by Allwinner to work on the kernel.

You wouldn't have gotten anything from the LF (we don't have many developers as you know), but I thought that Allwinner was part of Linaro, is that not correct?

Quoted 2 lines

Allwinner is not a pain anymore because a few hobbyists started working on the kernel to improve the situation.

Really? How did the work for the Chip computer come about? That's an Allwinner processor, right?

thanks,

greg k-h

#28 lore raw
In reply to Linus Torvalds
Quoted 7 lines · On Sun, 28 Aug 2016 13:36:38 -0700 Linus Torvalds…

And to further take that example: it was also a very good example of how companies really can help us. Any legal enforcement discussion absolutely should *not* be about "how does the open source community enforce the GPL against companies". That's just stupid talk, and makes it be about "individuals vs companies", which IS NOT TRUE. That's simply not how the community has worked in Linux, and it isn't how it *should* work.

If it is not "individuals vs companies" then what is it? "companies vs companies" like IBM vs SCO? Or "foundation vs companies"? I guess the question I have is if a copyright holder of code in the Linux kernel finds that his code is being used in proprietary software, and wants that code released (or simply the code of the developer be removed), what steps should that developer take? I agree legal action is the worse course, but there needs to be somewhere the developer can go to get help, and influence to make the company comply.

Quoted 10 lines

Seriously. I think we should see the IBM/SCO thing as an example of how we should all wish the GPL is to be used.

Do I want some "community effort" to try to create a "GPL test case" against some random badly behaving company that isnt' even all that *meaningful* from a development standpoint? Hell no. Quite frankly, anybody who sees that as a good end goal should haev their head examined. Yet that seems to be what the SFC sees as their goal in life.

If the SFC were not to use legal actions, and only be that organization to help the above developer influence the company (by talking with them to show how opening up their software is actually beneficial to them, or by the shaming method if that doesn't work). What I read from you is that you feel that the SFC is too trigger happy on the legal action side. If SFC were to say they really wont do that, unless they get permission from the Linux kernel community as a whole, would that make you feel better about them?

Quoted 3 lines

We should put our goal posts in a totally different direction. We don't have a ":community effort" to do marketing. We all realize how

Really? I thought that was what the Linux Foundation was ;-)

Quoted 4 lines

completely idiotic and stupid that would be. A "Software Freedom Marketing Center" would be laughed at.

Why the hell do people not laugh at it when it comes to legal issues?

Again, I'm guessing that is because not all kernel developers feel they are empowered to enforce the GPL when someone abuses *their* code.

Personally, I agree with everything you say, except that those that feel otherwise are *stupid*. We are a bit more pragmatic, and as my wife keeps telling me, I decide things more based on logic and not emotion. Others, like RMS base their decisions mostly on principle, even if it logically does not make sense. I respect that, even if I don't agree with it, but I wont call it "stupid", just "illogical".

Quoted 3 lines

So I seriously believe that we should not see companies as the "enemy" and as a target of lawsuits. We should see the Linux companies as a big part of the community, and as the natural *defender* of the GPL.

100% agree.

Quoted 13 lines

And we already have a really good example of that that people seem to be ignoring.

I would really want people to completely change their thinking about this "GPL enforcement" thing.

The great thing about the GPLv2 was how it turned copyright law "against itself" (really just against traditional use of copyrigth) and it has been described as a legal "judo move" - using copyright to *open* software instead of using it as a way to *restrict* software. It's why people call it "copyleft", after all.

Quoted 7 lines

THAT is the beauty of the GPLv2.

But the people who then see proprietary software as "evil", and see companies as being amoral, and as the enemy (and this very much is how rms and the FSF was acting), those people were doing exactly the wrong thing, and I have been fighting that idiocy for as long as I've been using the GPLv2.

I agree with you on this too.

Quoted 9 lines

The fact that we didnt' see proprietary software as evil, and that we opened our arms to companies made all the difference.

Now those same small-minded people are making the SAME MISTAKE, all over again. I do *not* want anybody who talks about "evil" proprietary software to be the seen as the "protector" of the GPL. No, people who talk about how proprietary software is "evil" should be seen as *stupid* people. Because they are. We showed them wrong.

Again, I would not call them "stupid". "illogical" perhaps but not "stupid". It's not a lack of intelligence that drives these decisions, but the sense of principle over logic.

Quoted 9 lines

And similarly, we should *not* see this as some crazy "community is protecting itself against companies" crap. Again, that's the stupid and wrong-headed FSF thinking. It's bad.

We have a ton of companies that are part of the community, and the same way we're bad at marketing and rely on companies to do that, we should at least _strive_ to work towards companies doing legal enforcement too.

OK, I guess this answers my question above. You feel that legal enforcement should be "companies vs companies".

Quoted 6 lines

That's the true "judo" move.

Because quite frankly, I think just by going by existing history, companies are better at lawsuits than the community is anyway. Just look at IBM.

The reason why I'm responding to this email is because even though I agree with the gist of your email, the tone is very much disheartening. Perhaps you just want the FSF and SFC to go away and not exist anymore. But I feel that they still have done more positive than negative and are good for the community as a whole. I agree with you that we can't let the "principle over logic" win. But people that are driven by principle are much more likely to get new things done than those that just do the logical actions. The GPL was created exactly because of this.

You once said on stage that you are more like an Edison and not a Tesla. You like to look at what's ahead and you are not a visionary. Which for running a project like Linux has worked out very well, because you let the visionaries do their thing, but ground them with reality when they needed it. I say this is not much different. We need people like those in FSF and SFC, but we also need to ground them with logic. I believe working with them, but really vocalizing our voice such that they don't represent us in a light we disapprove of, would be helpful. But simply calling them "stupid" isn't helping anyone, and that is stupid in itself.

-- Steve

#29 lore raw
Quoted 4 lines · Steven Rostedt

What I read from you is that you feel that the SFC is too trigger happy on the legal action side. If SFC were to say they really wont do that, unless they get permission from the Linux kernel community as a whole, would that make you feel better about them?

I, as well, pretty much agree with most of the things that have been said in the "lawsuits shouldn't be a regular tool to excercise GPL validity, there are a lot of other options which are more useful at the end of the day" tone.

However, to be fair -- isn't what you've written above exactly what SFC has been doing? Please correct me if I am wrong, but they are not executing any legal actions "on their own", are they? There always has to be someone from the community coming to them and initiating the trigger actions.

Now, if that is seen as a real problem, then a KS session just in between developers / maintainers, to shake out all the possibilities for Mr. Joe Developer in case of having really bad feelings about his code being misused, might be really helpful.

Signature · 2 lines
Jiri Kosina
SUSE Labs
#31 lore raw
In reply to Linus Torvalds
Quoted 7 lines · Linus Torvalds

We should put our goal posts in a totally different direction. We don't have a ":community effort" to do marketing. We all realize how completely idiotic and stupid that would be. A "Software Freedom Marketing Center" would be laughed at.

Why the hell do people not laugh at it when it comes to legal issues?

Well you don't need any real training to do marketing. I know as I have done marketing for Samba for years, and I know bugger-all about it :-).

Like it or not, legal issues *are* different. Screw up your marketing, and you just fail to sell stuff. Screw up your legal compliance or anti-trust, and you can find yourself with a $1bn fine (See Microsoft vs. EU for the example I know most about). That concentrates the mind *wonderfully* :-).

Quoted 3 lines

So I seriously believe that we should not see companies as the "enemy" and as a target of lawsuits. We should see the Linux companies as a big part of the community, and as the natural *defender* of the GPL.

Expecting Linux companies to be defenders of the GPL is a nice thought, but is not going to happen. If it was, it would have already happened by now. The IBM lawsuit was IBM counter-suing SCO after SCO went nuts, and I believe Red Hat have also counter sued a company that went after them for software patents.

Linux companies, like all companies, look after their own interests. Nothing bad about that, just good business. Enforcing the GPL other than in a counter-suit or for some other business purpose doesn't make any sense.

Linux companies are our friends, and I'm happy to work for and with them, but they're not going to represent the interests of the project developers. That's simply not what they are for.

SFC I'm happy to say, *does* represent our interests. That *IS* what they are for so I'm happy to support them.

Quoted 5 lines

But the people who then see proprietary software as "evil", and see companies as being amoral, and as the enemy (and this very much is how rms and the FSF was acting), those people were doing exactly the wrong thing, and I have been fighting that idiocy for as long as I've been using the GPLv2.

I don't see proprietary software as "evil", it's more of a nusance (like public littering :-).

Quoted 2 lines

The fact that we didnt' see proprietary software as evil, and that we opened our arms to companies made all the difference.

This is a good point I think. Samba has always been open to working with proprietary software, and it has helped us build our ecosystem (although for some reason we get labelled as zealots. I remember at one SambaXP conference one company founder told me, "everyone told me you were Free Software crazies but you're some of the most business friendly developers I've ever met" :-).

Quoted 3 lines

Because quite frankly, I think just by going by existing history, companies are better at lawsuits than the community is anyway. Just look at IBM.

That's because companies have a *lot* more practice at suing people than we do. A fact that seems lost on some of the people on this list (some of whom seem to think that community lawsuits are so common and opportunistic that they simply *must* be gumming up the courts :-).

#65 lore raw
In reply to Linus Torvalds
Quoted 4 lines · Linus Torvalds
Quoted 2 lines · Matthew Garrett

OK. A vendor sells 500,000 network-connected devices running a version

of

Quoted 3 lines
Quoted 3 lines

Linux that has a vulnerability in the network driver that's discovered a year later. The hardware is custom, they refuse to release source, and they've discontinued the product line, so nobody else is able to fix

it. Is

Quoted 2 lines
Quoted 2 lines

it acceptable to engage in litigation in order to ensure that owners of these devices can receive a security update, even if by doing so we

alienate

Quoted 4 lines
Quoted 1 line

the vendor and cause them to choose another kernel in future?

So why don't you name them and shame them very publicly and try everything else first?

I'm still at the point of trying to work with the company in a way that avoids all that, and things get rather more complicated when you're also trying to practice responsible disclosure over security issues. But yes, obviously I'm not going to press for anything else unless every other option has been exhausted first.

Quoted 4 lines

If the vendor still exists, and sells other devices, make a big stink about it. It sounds like you've talked to them in private already, but why do you still call them "a vendor" now when you start talking about wanting to sue them?

I *don't* want to sue them. I just don't have faith that the other options will be fruitful, and that seems to be a case you're not really focusing on.

Quoted 9 lines

Because without that, the answer is always going to be absolutely no, simply because of the "absolute last option" thing.

And you talk about how you're helping users, but how many of them would actually upgrade? Very few people end up upgrading firmware even when it's automatic, much less so if it would mean that they'd switch to OpenWRT or DD-WRT or something (since presumably the *existing* firmware ends up having lots of non-GPL'd sources that you wouldn't get even with a lawsuit)?

The number would end up being small, but the alternative is that they *all* end up running insecure code. Doesn't giving people the option seem worth it?

Quoted 1 line

In practical terms, how would that help Linux?

There would probably be no direct benefits at all for Linux as a technical project. There are potentially benefits in public perception of Linux-based IoT devices as being less likely to be left behind after vendors move on. But really, that's the question. If something has no significant benefit to the Linux project, but does benefit users of the product, are you fundamentally against lawsuits after every other option has been exhausted?

#30 lore raw
In reply to Jiri Kosina

This has all been quite a discussion! I wanted to clarify a few things:

* <insert lawyer joke here> [1]

* Some of the statements made in this discussion rely on legal
assertions that aren't quite right. [2]

* As others have pointed out, every part of Conservancy's approach to
enforcement is designed to take risk away from companies out of compliance. [3]

* I'm really glad that people are thinking about these issues. [4]

* Over time, regardless of what individual Linux copyright holders or
Conservancy do, others will bring law suits that will impact the kernel. [5]

Conservancy spearheads a coordinated[6] and downright timid approach, codifying our principles so that companies out of compliance can hold us to them. We merely represent some kernel developers in exercising their rights. We do this because we think it's right, and we re-evaluate this together with our coalition at every step. And we do so in a coordinated and litigation-avoiding style. I only proposed the KS session after getting encouragement from several prominent kernel developers (and given that there was precedence for such a legal-related discussion [7]).

I want proper time for everyone to reflect on what has been said on this thread and to provide well thought out feedback in whatever forum is comfortable for them.

We propose to have this discussion in many different venues and places over the next six months (whether or not there's an official session at KS and whether or not we are there to participate if so). Bradley and I will each be present at a lot of conferences and events over the next six months. At any of these events where people are interested, we'll host sessions in whatever format is appropriate to meet with Linux developers and stakeholders to discuss Conservancy's enforcement activities, to get feedback, and incorporate the ideas we hear into our work and strategies. We'll post summaries of the meet-ups (to the extent we can and still respect requested confidentiality) to our principles mailing list[8].

Conservancy will be less active on this thread in the future. Obviously we can't respond to every single criticism on every list, anyway. Developers from our coalition are already participating and likely will continue to do so directly.

Also, I'd be remiss if I didn't mention that Conservancy has tons of other work to do, supporting its member projects (many of which are permissively licensed btw), Outreachy[9] and a number of other important initiatives like our employment agreement project, providing good copyleft educational materials and solving the nonprofit accounting problem.

karen

[1] I admit, the legal profession isn't the best... I maintain my legal credentials, but other than teaching classes for other lawyers I'm not primarily in that role anymore. (I do continue as a volunteer and give legal advice to FSF and GNOME as my free time permits - not much this past weekend after following this whole thread, haha!) As Executive Director of Conservancy, I rely on other lawyers for Conservancy's legal work. Not being able to see the source code to a device that is literally sewn into my body and screwed into my heart gives me a slightly different perspective on software freedom and has caused me to contribute anyway I can, even if I haven't coded in years. I appeal for the copyleft generally on safety, security and business reasons. I also admit that while I have a pretty thick skin, I was somewhat taken aback by the not-so-veiled threat of disbarment. FWIW, lawyers can hold public or quasi-public sessions without automatically running afoul of legal ethics. There is a long list of attorneys active in the field who have presented at free and open source software events about myriad topics.

[2] IAAL (though my primary work role is no longer in legal capacity) but TINLA. I cannot point all of these out for obvious reasons.

[3] When we contact them one of the first things they see are the ways we commit to making the process comfortable for them. This is true for anyone who researches who we are and finds the Principles on our site. The Principles not only talk about law suits as a last resort, but provide the much more generous termination provisions, giving first-time violators automatic restoration if the violation is fixed in a timely fashion. We also respect confidentiality from companies who we believe have a chance of doing the right thing, because while Linus may enjoy taking a public potshot at a company out of compliance, I know from some companies first hand that this is the singular thing that makes them most nervous about committing to the kernel. There's a real fear that even if they come into compliance they'll exposed to liability by some other rightsholder in some jurisdiction somewhere.

[4] I don't think that a publicly archived list is the best venue for it. Also, some of the developers in our coalition have strong beliefs but soft voices.

[5] The majority of law suits in the last couple of years have not been from anyone in Conservancy's coalition. Obviously, there are the suits brought by Patrick, but there's also Versata/Ameriprise/Ximpleware in which the GPL got caught in unrelated cross-fire. Whether or not the kernel community wants to participate in law suits, courts will surely wind up having GPL-related issues brought before them, and the results of those cases will apply to the kernel as well. Info on the Versata case is here:
https://opensource.com/law/14/7/lawsuit-threatens-break-new-ground-gpl-and-software-licensing-issues

[6] We try to coordinate with anyone active in the space who is willing to coordinate with us. This incidentally has included rogue enforcers, industry lawyers and anyone who does work to understand the copyright status of the kernel (btw, in an early post, I said we coordinated with dmg when I really meant 'gave feedback on big picture issues and tried to coordinate' with the work LF is funding. They have graciously listened to our comments, but I want to be clear that Conservancy has not been invited to participate or collaborate in the project in any way.)

[7] The Q&A I proposed was not intended as a negotiation or an attempt to provide legal advice to anyone. In fact it was not dissimilar in character from the session Karen Copenhaver (lawyer to Linux Foundation) led with Keith Bergelt in 2009.

[8] https://lists.sfconservancy.org/mailman/listinfo/principles-discuss
which we launched last year to discuss the Principles of Community-Oriented GPL Enforcement.

[9] I note that Outreachy itself has around 10 paid interns per year for the kernel, and apparently "ranked #13 for contributions to the Linux kernel during the last cycle" for organizations.
https://www.linuxfoundation.org/announcements/linux-foundation-releases-development-report-highlighting-contributions-to-linux
Thanks to everyone on this list who mentored and supported these interns.

#79 lore raw
In reply to Greg KH

Hi Greg,

Quoted 12 lines · Greg KH
Quoted 12 lines · Greg KH
Quoted 7 lines

Someone in a reddit thread about this email conversation said, in trying to quote Linus, something along the lines of "the nuclear option should have been done to Allwinner a long time ago". And that proved my point exactly. Allwinner was a pain for a very long time. But as developers, and through the efforts of a lot of people at the Linux Foundation and Linaro, Allwinner is now a contributor to the kernel, and actively sponsors developers to write GPLv2 code for their chips.

While I generally agree with you on this topic, this is simply not true.

Quoted 8 lines
Quoted 4 lines

As the Allwinner SoC maintainer, I never received any patch from someone either from the Linux Foundation or Linaro. And to the best of my knowledge, I'm not aware of anyone being paid by Allwinner to work on the kernel.

You wouldn't have gotten anything from the LF (we don't have many developers as you know), but I thought that Allwinner was part of Linaro, is that not correct?

They used to yes. However, even though I don't really how Linaro works internally, my understanding was that being part of Linaro doesn't imply that you have engineers assigned. It's probably related to some level of membership.

Anyway, like I was saying, no one from Linaro ever contributed something meaningful (except some cross-tree patches, and the usual "maintainance" patches).

Quoted 5 lines
Quoted 2 lines

Allwinner is not a pain anymore because a few hobbyists started working on the kernel to improve the situation.

Really? How did the work for the Chip computer come about? That's an Allwinner processor, right?

It is. But it was built on what the community did (ie, the hardware is from Allwinner, the software is not).

Maxime

Signature · 3 lines
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#80 lore raw
Quoted 18 lines · Maxime Ripard
Quoted 17 lines · Greg KH
Quoted 16 lines · Greg KH
Quoted 7 lines

Someone in a reddit thread about this email conversation said, in trying to quote Linus, something along the lines of "the nuclear option should have been done to Allwinner a long time ago". And that proved my point exactly. Allwinner was a pain for a very long time. But as developers, and through the efforts of a lot of people at the Linux Foundation and Linaro, Allwinner is now a contributor to the kernel, and actively sponsors developers to write GPLv2 code for their chips.

While I generally agree with you on this topic, this is simply not true.

As the Allwinner SoC maintainer, I never received any patch from someone either from the Linux Foundation or Linaro. And to the best of my knowledge, I'm not aware of anyone being paid by Allwinner to work on the kernel.

Quoted 8 lines
Quoted 3 lines

You wouldn't have gotten anything from the LF (we don't have many developers as you know), but I thought that Allwinner was part of Linaro, is that not correct?

They used to yes. However, even though I don't really how Linaro works internally, my understanding was that being part of Linaro doesn't imply that you have engineers assigned. It's probably related to some level of membership.

Correct, the higher membership levels require assigning engineers, but that doesn't mean these engineers work on upstreaming code of that member company, or even working on the kernel.

We do provide all kinds of help to member companies and engineers to learn everything about upstreaming their code and working with the communities, and a lot of member companies use that help, but other members don't.

Quoted 3 lines

Anyway, like I was saying, no one from Linaro ever contributed something meaningful (except some cross-tree patches, and the usual "maintainance" patches).

I'm not surprised at all. Most of the kernel work we do in Linaro is intentionally cross-platform (so it benefits all members equally), or it is done on those platforms that the members decide are important upstream.

Arnd

#81 lore raw
Quoted 10 lines · Arnd Bergmann
Quoted 4 lines

Anyway, like I was saying, no one from Linaro ever contributed something meaningful (except some cross-tree patches, and the usual "maintainance" patches).

I'm not surprised at all. Most of the kernel work we do in Linaro is intentionally cross-platform (so it benefits all members equally), or it is done on those platforms that the members decide are important upstream.

One may wonder how your Linux kernel patches and merges are classified per the above.

Thank you for all your work in the Linux kernel. It is anything but meaningless, and it obviously goes far beyond "some cross-tree patches, and the usual maintenance patches".

Guenter

#37 lore raw
In reply to Theodore Ts'o
Quoted 9 lines · Theodore Ts'o
Quoted 7 lines · Jeremy Allison via Ksummit-discuss

Your opinion on that is clear and I understand why you hold it. There are many other developers who hold the same opinion, but lots of them work on FreeBSD not Linux.

Respectfully, I don't agree with you. Greg and Ted seem to agree with you, Linus (like me) seems to imagine there can be a case for that shiny red button.

Quoted 8 lines

For the record, I believe there can be a case for the shiny red button. I just want Linus, and not the SFC (or some --- as admitted by the SFC --- minority set of developers), to be the one who decides when it's appropriate to push it.

I've said it before, and I've said it again. For me, this is much more about a project governance issue. We don't let random pissed off army officers decide when to start World War III.

If you are trying to equate "random pissed off officers" with those kernel developers part of the SFC alliance, then I have to say that is perhaps one of the most stupid misrepresentations of members of SFC that I have heard so far. Unless of course your statement is educated, you know all members part of SFC and have asked each one why they joined.

If you don't know then please educate yourself on this as reading this type of incoherent nonsense being spouted out is just offending and does nothing to help.

Luis

#38 lore raw
Quoted 19 lines · Luis R. Rodriguez
Quoted 9 lines · Theodore Ts'o
Quoted 7 lines · Jeremy Allison via Ksummit-discuss

Your opinion on that is clear and I understand why you hold it. There are many other developers who hold the same opinion, but lots of them work on FreeBSD not Linux.

Respectfully, I don't agree with you. Greg and Ted seem to agree with you, Linus (like me) seems to imagine there can be a case for that shiny red button.

Quoted 8 lines

For the record, I believe there can be a case for the shiny red button. I just want Linus, and not the SFC (or some --- as admitted by the SFC --- minority set of developers), to be the one who decides when it's appropriate to push it.

I've said it before, and I've said it again. For me, this is much more about a project governance issue. We don't let random pissed off army officers decide when to start World War III.

Quoted 5 lines

If you are trying to equate "random pissed off officers" with those kernel developers part of the SFC alliance, then I have to say that is perhaps one of the most stupid misrepresentations of members of SFC that I have heard so far. Unless of course your statement is educated, you know all members part of SFC and have asked each one why they joined.

That brings up a question, who exactly is the SFC representing here? What developers have signed over copyrights to the SFC? Was this done in a "permanent" way? "revoking" copyright assignment isn't exactly a simple thing to do, last I checked, so is this really true?

Quoted 2 lines

If you don't know then please educate yourself on this as reading this type of incoherent nonsense being spouted out is just offending and does nothing to help.

Without knowing the above, it's hard to know what is, or is not, a stupid misrepresentation :)

thanks,

greg k-h

#85 lore raw
In reply to Arnd Bergmann
Quoted 10 lines · Arnd Bergmann
Quoted 4 lines · Maxime Ripard

They used to yes. However, even though I don't really how Linaro works internally, my understanding was that being part of Linaro doesn't imply that you have engineers assigned. It's probably related to some level of membership.

Correct, the higher membership levels require assigning engineers, but that doesn't mean these engineers work on upstreaming code of that member company, or even working on the kernel.

To be more concrete: the assignees function essentially as contractors for Linaro. They're doing Linaro work on free software products and infrastructure like direct Linaro employees do, they're not working for the member company but rather for Linaro when they're assignees.

Linaro does also have landing teams for members at higher levels, these function in the opposite direction and have their work assigned by the members but there's no requirement that this work be upstreaming or even kernel related, it is in some cases (eg, a bunch of the Qualcomm and ST work upstream is being done by Linaro landing teams) but not all.

Quoted 4 lines

We do provide all kinds of help to member companies and engineers to learn everything about upstreaming their code and working with the communities, and a lot of member companies use that help, but other members don't.

Plus the fact some member companies are large enough that they have several groups working with Linux and in those cases it may only be one of those groups that's joined Linaro and the SoCs people generally see may be from another group.

[Specifically in the context of Linaro working on Allwinner SoCs]

Quoted 8 lines
Quoted 3 lines

Anyway, like I was saying, no one from Linaro ever contributed something meaningful (except some cross-tree patches, and the usual "maintainance" patches).

I'm not surprised at all. Most of the kernel work we do in Linaro is intentionally cross-platform (so it benefits all members equally), or it is done on those platforms that the members decide are important upstream.

Where possible we'll try to use platforms that already work well upstream rather than trying to do basic upstreaming work.

#50 lore raw
In reply to Luis R. Rodriguez
Quoted 20 lines · Luis R. Rodriguez
Quoted 10 lines · Theodore Ts'o
Quoted 7 lines · Jeremy Allison via Ksummit-discuss

Your opinion on that is clear and I understand why you hold it. There are many other developers who hold the same opinion, but lots of them work on FreeBSD not Linux.

Respectfully, I don't agree with you. Greg and Ted seem to agree with you, Linus (like me) seems to imagine there can be a case for that shiny red button.

Quoted 8 lines

For the record, I believe there can be a case for the shiny red button. I just want Linus, and not the SFC (or some --- as admitted by the SFC --- minority set of developers), to be the one who decides when it's appropriate to push it.

I've said it before, and I've said it again. For me, this is much more about a project governance issue. We don't let random pissed off army officers decide when to start World War III.

Quoted 6 lines

If you are trying to equate "random pissed off officers" with those kernel developers part of the SFC alliance, then I have to say that is perhaps one of the most stupid misrepresentations of members of SFC that I have heard so far. Unless of course your statement is educated, you know all members part of SFC and have asked each one why they joined.

Given that the names aren't public, that's somewhat of an impossible test.

The problem Ted has is that a tiny minority of the copyright holders can launch a GPL action under the law today with out regard to the opinions of the majority. So could one person try to set up a permanent fork of linux; What holds it together isn't legal principles, it's sound governance, which is why Ted says this is a governance issue.

The analogy is to try to get you to understand, not to insult you by equating members of the SFC coalition with random pissed off generals.

Quoted 3 lines

If you don't know then please educate yourself on this as reading this type of incoherent nonsense being spouted out is just offending and does nothing to help.

OK, so leaving the rhetoric aside, do you understand why we see this as an unsolved governance issue? Solving it correctly is a hard problem, because it involves finding some mechanism for bringing GPL violators into line that everyone (including those in the SFC coalition) can support.

James

#32 lore raw
In reply to Linus Torvalds
Quoted 11 lines · Linus Torvalds
Quoted 7 lines · Theodore Ts'o

I didn't say that. I said consensus driven and taking into account all of the stakeholders. If it makes you feel better, how about "Linus as the benevolent dictator"? He makes a point of gathering input from multiple stakeholders, and delegating authority to others for day to day decisions. That's how we do our development, after all.

So quite honestly, I think everybody would be much happier if we were not even ever in the situation where that would be required.

Absolutely. Proactive measures are best, always. If we don't have good proactive measures in place then I think we have only ourselves to blame.

Quoted 2 lines

Personally, I really think that legal action by the "community" is not at all what we should hope for, or even _aim_ for.

The problem is some folks are taking stupid action and it seems for profit. At least SFC's approach is transparent, has a published Principles guideline *and* has an open invitation to anyone to participate in the discussion. The goal is to prevent stupid things, but to obviously address the high level or violations being reported, somehow.

Quoted 1 line

As mentioned, I don't think it has worked wonderfully well.

So let us learn from that.

Quoted 5 lines

But we do have examples of Linux GPL-related legal action that I think we *all* can agree has worked absolutely stunningly well.

I don't think anybody disagrees that IBM's legal actions against SCO were a really good thing.

Sure.

Quoted 3 lines

No, that was not mainly about some "GPL test
case" or "license clarification", and it wasn't even _mainly_ about the GPL.

I agree with not using suits for test cases. That is just plain stupid.

Quoted 8 lines

But the GPL _was_ part of it, and both the license and the community came out really well in it.

What I'm happy about it is also that it was a defensive suit, and quite frankly, when we talk about "going to war" and "nuclear options", I have to say that "defensive" is also a big big positive. Because offensive use of nuclear options is just a f*cking bad idea. Seriously.

Absolutely.

Quoted 7 lines

And to further take that example: it was also a very good example of how companies really can help us. Any legal enforcement discussion absolutely should *not* be about "how does the open source community enforce the GPL against companies". That's just stupid talk, and makes it be about "individuals vs companies", which IS NOT TRUE. That's simply not how the community has worked in Linux, and it isn't how it *should* work.

Absolutely.

Quoted 4 lines

Seriously. I think we should see the IBM/SCO thing as an example of how we should all wish the GPL is to be used.

Do I want some "community effort" to try to create a "GPL test case"

Emphasis, "test case".

Quoted 5 lines

against some random badly behaving company that isnt' even all that *meaningful* from a development standpoint? Hell no. Quite frankly, anybody who sees that as a good end goal should haev their head examined. Yet that seems to be what the SFC sees as their goal in life.

Agreed.

Quoted 4 lines

We should put our goal posts in a totally different direction. We don't have a ":community effort" to do marketing. We all realize how completely idiotic and stupid that would be. A "Software Freedom Marketing Center" would be laughed at.

Laughable as it may be such campaigns do exist, such as the FSF's "Respect your freedom" hardware product certification thing [0]. Having been involved in making freedom available on one of these devices, an 802.11 device with open firmware, I can tell you that its been a success with those that care. Sure, the group of interested folks in this sort of stuff might be small -- so to me more important is the breed of better developers, better software, potential new hires, and eventually showing how only a group of a few open developers can end up replacing an entire fucking team doing a completely sub-par quality firmware. Fortunately, as code was opened one can inspect what the quality was during initial release against the latest development in collaboration with the community. I left Atheros leaving behind *two* test cases of open firmware on the 802.11 world, and any security researcher should be able to have a good field day in showing what the quality of changes that opening brought about.

For open firmware though, the market simply is too late to take advantage of if one is to do this as a test case, which is what we were doing. Silicon cycles are fast and based on experiences you'd need to be releasing and engaging *with the community* even during hardware ramp up, while you are working on the first pieces of software being stitched together, not as a *port work*. Port work is just dumb and too late.

Quoted 1 line

From a practical point of view, resource point of view -- so, corporate -- tons

of lessons to be learned form these efforts. Those were the good 'ol days.

[0] https://www.fsf.org/resources/hw/endorsement/respects-your-freedom

Quoted 9 lines

Why the hell do people not laugh at it when it comes to legal issues?

The fact is, Linux is in a very different position than the one that Jeremy Allison describes for samba. Or the one we were in 20 years ago. We have very consciously tried to make various companies be *part* of our community, and they have been an incredibly powerful resource. They employ a lot of the engineers, but they do so much more too.

Quoted 3 lines

So I seriously believe that we should not see companies as the "enemy" and as a target of lawsuits. We should see the Linux companies as a big part of the community, and as the natural *defender* of the GPL.

Ah. If those companies use the GPL. Sadly a new breed of companies do not use the GPL for upstream contributions when they can now and as such the GPL is not even part of their language other than danger, and if you need to use the GPL you can end up feeling like a caged monkey. The good 'ol days are over, for some companies and if I were you I'd be a bit concerned over what that might mean long term. There surely are companies still using the GPL, and that's great, but its not like the way it was before. I'll admit I am partly to blame for the proliferation of a new age of permissive license proliferation in the kernel, this all started with a joint effort to help the BSDs when we took the openhal for ath5k, then ath9k.. etc... My days of the whole BSD camp - kumbaya are over, as I've seen the danger with that.

Quoted 2 lines

And we already have a really good example of that that people seem to be ignoring.

The good 'ol days are over. Not for all, but some.

Quoted 10 lines

I would really want people to completely change their thinking about this "GPL enforcement" thing.

The great thing about the GPLv2 was how it turned copyright law "against itself" (really just against traditional use of copyrigth) and it has been described as a legal "judo move" - using copyright to *open* software instead of using it as a way to *restrict* software. It's why people call it "copyleft", after all.

THAT is the beauty of the GPLv2.

:D

Quoted 8 lines

But the people who then see proprietary software as "evil", and see companies as being amoral, and as the enemy (and this very much is how rms and the FSF was acting), those people were doing exactly the wrong thing, and I have been fighting that idiocy for as long as I've been using the GPLv2.

The fact that we didnt' see proprietary software as evil, and that we opened our arms to companies made all the difference.

People have the right to feel proprietary software is amoral, its on them, this may be subjective in certain situations. But, from a market perspective proprietary software is also plain stupid.

Quoted 5 lines

Now those same small-minded people are making the SAME MISTAKE, all over again. I do *not* want anybody who talks about "evil" proprietary software to be the seen as the "protector" of the GPL. No, people who talk about how proprietary software is "evil" should be seen as *stupid* people. Because they are. We showed them wrong.

I say proprietary software is just stupid. There are advantages of copyleft, however not many companies tend to see similar gains towards the GPL as perhaps some used to. I'm not saying these companies do not exist, they still do, I'm just saying -- the market has change and some just use Linux permissively.

Quoted 3 lines

And similarly, we should *not* see this as some crazy "community is protecting itself against companies" crap. Again, that's the stupid and wrong-headed FSF thinking. It's bad.

Of course.

Quoted 4 lines

We have a ton of companies that are part of the community, and the same way we're bad at marketing and rely on companies to do that, we should at least _strive_ to work towards companies doing legal enforcement too.

Sure, but many companies don't care about that aspect of the GPL, to a large camp they are fine with Linux being a permissive license dump ground. That's fine for them too, so long as they contribute, we should be happy right?

But I'm pointing out the same logic has slightly changed about approach.

Quoted 5 lines

That's the true "judo" move.

Because quite frankly, I think just by going by existing history, companies are better at lawsuits than the community is anyway. Just look at IBM.

Sure, but there is a new era of companies that do not care. In lack of there being any new need for companies to use the GPL, why would they? That might leave a gap for the community, and then again, should the community have a GPL representation as companies do? What if it was only used as a last resort measure ? That's what is being asked. What due process to follow. Etc.

Luis

#51 lore raw
In reply to James Bottomley
Quoted 2 lines

Given that the names aren't public, that's somewhat of an impossible test.

If SFC does at some point sue, and that action ends up in court, would the names become public? I'm assuming that they would since the first discovery request by the defending company would be to find out which code was at stake, and whether the copyright was really owned by the people that SFC represents.

-Tony

#39 lore raw
In reply to Greg KH
Quoted 20 lines · Greg KH
Quoted 19 lines · Luis R. Rodriguez
Quoted 17 lines · Theodore Ts'o
Quoted 7 lines · Jeremy Allison via Ksummit-discuss

Your opinion on that is clear and I understand why you hold it. There are many other developers who hold the same opinion, but lots of them work on FreeBSD not Linux.

Respectfully, I don't agree with you. Greg and Ted seem to agree with you, Linus (like me) seems to imagine there can be a case for that shiny red button.

For the record, I believe there can be a case for the shiny red button. I just want Linus, and not the SFC (or some --- as admitted by the SFC --- minority set of developers), to be the one who decides when it's appropriate to push it.

I've said it before, and I've said it again. For me, this is much more about a project governance issue. We don't let random pissed off army officers decide when to start World War III.

Quoted 7 lines
Quoted 5 lines

If you are trying to equate "random pissed off officers" with those kernel developers part of the SFC alliance, then I have to say that is perhaps one of the most stupid misrepresentations of members of SFC that I have heard so far. Unless of course your statement is educated, you know all members part of SFC and have asked each one why they joined.

That brings up a question, who exactly is the SFC representing here?

I've come out:

http://www.do-not-panic.com/2016/02/im-part-of-conservancys-gpl-compliance.html

Others have as well. We don't force people to come out though obviously, so its optional. Some folks would prefer their association to remain private. That's a right they should have.

What do you think? Did it ever cross your mind to consider joining ?

Quoted 3 lines

What developers have signed over copyrights to the SFC? Was this done in a "permanent" way? "revoking" copyright assignment isn't exactly a simple thing to do, last I checked, so is this really true?

If this is a concern, perhaps its something SFC can address. Also, would you like a way to participate without signing off copyrights to SFC ? If so that sounds like a type of discussion we could start.

Quoted 5 lines
Quoted 2 lines

If you don't know then please educate yourself on this as reading this type of incoherent nonsense being spouted out is just offending and does nothing to help.

Without knowing the above, it's hard to know what is, or is not, a stupid misrepresentation :)

But the analogy was made so it was rather stupid and simply not contributing anything. What you describe however, sounds like useful feedback.

Luis

#53 lore raw
In reply to James Bottomley
Quoted 28 lines · James Bottomley
Quoted 20 lines · Luis R. Rodriguez
Quoted 10 lines · Theodore Ts'o
Quoted 7 lines · Jeremy Allison via Ksummit-discuss

Your opinion on that is clear and I understand why you hold it. There are many other developers who hold the same opinion, but lots of them work on FreeBSD not Linux.

Respectfully, I don't agree with you. Greg and Ted seem to agree with you, Linus (like me) seems to imagine there can be a case for that shiny red button.

Quoted 8 lines

For the record, I believe there can be a case for the shiny red button. I just want Linus, and not the SFC (or some --- as admitted by the SFC --- minority set of developers), to be the one who decides when it's appropriate to push it.

I've said it before, and I've said it again. For me, this is much more about a project governance issue. We don't let random pissed off army officers decide when to start World War III.

Quoted 6 lines

If you are trying to equate "random pissed off officers" with those kernel developers part of the SFC alliance, then I have to say that is perhaps one of the most stupid misrepresentations of members of SFC that I have heard so far. Unless of course your statement is educated, you know all members part of SFC and have asked each one why they joined.

Quoted 2 lines

Given that the names aren't public, that's somewhat of an impossible test.

Then best not equate them to angry officers. Its no different than trying to equate those opposed to modern responsible community GPL enforcement with corporate lobbyists. I'd be really, really stupid if I used that analogy.

Quoted 3 lines

The problem Ted has is that a tiny minority of the copyright holders can launch a GPL action under the law today with out regard to the opinions of the majority.

This thread seems to reveal that even Linus was aware of the Vmware law suit. Other than this it seems due process, in whatever capacity we have, is being followed. In lack of any process being available, and given the interest of those pestering SFC, what else can be done but to gather folks, discuss, and try to reach some sort of transparent process ? What else can be done better? That's the whole point of the discussion and engagement.

Simply dismissing all the effort possible by assuming Bradley is in charge is IMHO understandable but also doing a huge disservice to Karen's own efforts. Moving past that, if one can trust that he's not, then the next question is -- what due process would we like in place. Linus would prefer a proactive approach, and I'm all for it. Always have been. But that still dismisses any proper due process left in place as last resort which we can settle on for the community.

If a proactive approach can avoid another stupid lingering Vmware type of case, then lets hear it. Why didn't it work and what can we do better ? In fact, other than few key developer having impact at companies, what other effort is there? I'm one of the few that took the plunge into a silicon company and did my best to educate, and I think the company learned the benefits of upstream, but working at silicon companies is *hard* and takes a lot of patience. These days I know more developers that simply prefer to do contract work than work full time or lobby. Then we have things like Linaro. That helps but still leave open to question what proactive measure are in place.

Quoted 4 lines

So could one person try to set up a
permanent fork of linux; What holds it together isn't legal principles, it's sound governance, which is why Ted says this is a governance issue.

I agree with the governance thing obviously. The analogy used was just dumb.

Quoted 2 lines

The analogy is to try to get you to understand, not to insult you by equating members of the SFC coalition with random pissed off generals.

The analogy does nothing to help. The discussion we are having, yes.

Quoted 9 lines
Quoted 3 lines

If you don't know then please educate yourself on this as reading this type of incoherent nonsense being spouted out is just offending and does nothing to help.

OK, so leaving the rhetoric aside, do you understand why we see this as an unsolved governance issue? Solving it correctly is a hard problem, because it involves finding some mechanism for bringing GPL violators into line that everyone (including those in the SFC coalition) can support.

Of course, that's the whole point ! How do we resolve this ?

Luis

#22 lore raw
In reply to Greg KH
Quoted 7 lines · Greg KH
Quoted 4 lines · David Woodhouse

Even though I abhor what Patrick McHardy is doing, I still can't quite find it in my heart to have *sympathy* for his victims. Because it's not as if he's just taking random pot-shots at passers-by on the street. These people defended their actions in court, and lost.

Quoted 5 lines

No, that's not what Patrick did. Whenever he actually took something to court, _he_ lost. Companies paid him off before then because they were scared for foolish reasons, or it was honestly just cheaper to do it than go to court and win. He took the traditional model of patent troll to the next level.

Please bear in mind that public information on what's going on there is very scarce, I suspect most people have only seen the SFLC statement at:

https://sfconservancy.org/blog/2016/jul/19/patrick-mchardy-gpl-enforcement/

(it seems from followups that there may be some confusion even in what I've quoted above).

#52 lore raw
In reply to Luck, Tony
Quoted 8 lines · Tony
Quoted 2 lines

Given that the names aren't public, that's somewhat of an impossible test.

If SFC does at some point sue, and that action ends up in court, would the names become public? I'm assuming that they would since the first discovery request by the defending company would be to find out which code was at stake, and whether the copyright was really owned by the people that SFC represents.

If the law requires it I'm sure the names of those involved would come out. Otherwise its a volunteer option.

Luis

#47 lore raw
In reply to Greg KH
Quoted 5 lines · Greg KH

That brings up a question, who exactly is the SFC representing here? What developers have signed over copyrights to the SFC? Was this done in a "permanent" way? "revoking" copyright assignment isn't exactly a simple thing to do, last I checked, so is this really true?

Ah, this could be a big part of the misapprehensions in this thread !

While it is possible to sign over copyrights to the SFC, this is not commonly done by member projects (I think I'm safe in saying that). It's also not required to assign copyright in order for SFC to represent copyright holders in enforcement actions.

In Samba for example (which I can talk publicly about), *NO* devlopers have assigned any copyrights to the SFC, they are merely acting as an enforcement agent authorized to do so on our behalf - by the wishes of the developers.

The Samba developers can revoke such permission at any time and for any reason. The reason we haven't is that the consensus for Samba is that SFC is doing a good job representing our interests.

#23 lore raw
In reply to Mark Brown
Quoted 8 lines · Mark Brown
Quoted 6 lines · Greg KH
Quoted 4 lines · David Woodhouse

Even though I abhor what Patrick McHardy is doing, I still can't quite find it in my heart to have *sympathy* for his victims. Because it's not as if he's just taking random pot-shots at passers-by on the street. These people defended their actions in court, and lost.

Quoted 8 lines
Quoted 5 lines

No, that's not what Patrick did. Whenever he actually took something to court, _he_ lost. Companies paid him off before then because they were scared for foolish reasons, or it was honestly just cheaper to do it than go to court and win. He took the traditional model of patent troll to the next level.

Please bear in mind that public information on what's going on there is very scarce, I suspect most people have only seen the SFLC statement at:

SFLC != SFC. It will be hard, but try and look at why we have two orgs now. SFLC did do good -- it helped with the upstream openhal efforts and ath5k review. But the org that put out the review below and then published the Principles is SFC, not SFLC.

Quoted 4 lines
   https://sfconservancy.org/blog/2016/jul/19/patrick-mchardy-gpl-enforcement/

(it seems from followups that there may be some confusion even in what I've quoted above).

Agreed, I think more has been revealed in this thread then in that article, sadly most is information learned so far is through the grape vine.

Luis

#40 lore raw
In reply to Luis R. Rodriguez

<fixing Jeremy's email address, Luis, your email client broke it...>

Quoted 29 lines · Luis R. Rodriguez
Quoted 20 lines · Greg KH
Quoted 19 lines · Luis R. Rodriguez
Quoted 17 lines · Theodore Ts'o
Quoted 7 lines · Jeremy Allison via Ksummit-discuss

Your opinion on that is clear and I understand why you hold it. There are many other developers who hold the same opinion, but lots of them work on FreeBSD not Linux.

Respectfully, I don't agree with you. Greg and Ted seem to agree with you, Linus (like me) seems to imagine there can be a case for that shiny red button.

For the record, I believe there can be a case for the shiny red button. I just want Linus, and not the SFC (or some --- as admitted by the SFC --- minority set of developers), to be the one who decides when it's appropriate to push it.

I've said it before, and I've said it again. For me, this is much more about a project governance issue. We don't let random pissed off army officers decide when to start World War III.

Quoted 7 lines
Quoted 5 lines

If you are trying to equate "random pissed off officers" with those kernel developers part of the SFC alliance, then I have to say that is perhaps one of the most stupid misrepresentations of members of SFC that I have heard so far. Unless of course your statement is educated, you know all members part of SFC and have asked each one why they joined.

That brings up a question, who exactly is the SFC representing here?

Quoted 7 lines

I've come out:

http://www.do-not-panic.com/2016/02/im-part-of-conservancys-gpl-compliance.html

Others have as well. We don't force people to come out though obviously, so its optional. Some folks would prefer their association to remain private. That's a right they should have.

It's something you would "loose" if you actually file for something. And for the SFC to approach a company with a vague "we have random copyrights, give us the code!" that message is horrid!

Go back and read my long email about what happens at a company when they are approached by a "representative", and not a developer. Especially one that makes lots and lots and lots of public statements about how companies are evil, how Linux is the GPL's ultimate test case, how they want to use the courts to clarify the GPL's "grey areas". All of these have been stated numerous times by the leadership of the SFC as recently as a few months ago.

Again, that is NOT how to create and sustain a community. That's how you set fire to it and watch it burn. It happened to Busybox and I don't want it to happen here to Linux.

Quoted 1 line

What do you think? Did it ever cross your mind to consider joining ?

Sure, many years ago. And I'm glad I never signed the document that Bradley gave me many years ago at LinuxCon as it would have been a bad idea (not to mention that people giving developers random legal documents to sign at a conference really isn't a wise thing on either parties involved...) As I mentioned my discussion with Bradley last year, at LinuxCon, I did not want him to continue to do this as it is not how you create a community.

Again, the SFC puts the GPL before Linux, and is willing to do things to make Linux fail if it somehow finally answers their unresolved questions about the GPL[1].

For a group of people who had nothing to do with Linux at all in the first place, this seems like a very dangerous thing to let them do to you, or anyone else who has signed up for this. This is _our_ project, not theirs. Why would you ever give the power that you have, and have created, away to others that might not have your project's best interest in mind?

Remember, they approached all of us, shopping around the fact that they knew of companies that were violating, showing us printouts of files that were in the information they had received from their Busybox work at vmware. They were digging and asking and wanting to bring this type of lawsuit forward, it was not brought by us, the developers. Bradley has always been very upfront about this, I'll give him credit for that.

Go and watch their talks! Like Linus, I spent all weekend, reading and watching their talks. It's actually worse than I thought. I have notes somewhere around here when I was going to try to point them all out, but I gave up after a while as it was just crazy...

I can dig them up if you really want, but I suggest you go do it yourself, it's more powerful that way :)

Quoted 7 lines
Quoted 3 lines

What developers have signed over copyrights to the SFC? Was this done in a "permanent" way? "revoking" copyright assignment isn't exactly a simple thing to do, last I checked, so is this really true?

If this is a concern, perhaps its something SFC can address. Also, would you like a way to participate without signing off copyrights to SFC ? If so that sounds like a type of discussion we could start.

How can you participate in something that you are not a part of, and right now, really really want nothing at all to do with?

I'm really sick after watching all of this, and honestly, want nothing to do with the SFC anymore at all. My employment contract at the LF says that I can't tell them what to do, and they can't tell me what to do either, but I'm going to go recommend to them that they not donate any more money to the SFC as I really think they are toxic to the future of Linux, which is the exact opposite of the LF's charter.

Outreachy is a good thing that SFC does though, so I'll still support that for now and recommend that the LF funds that portion (if that's even possible, I have no idea how the LF donates their funds, or if even the SFC accepts earmarked funds). Perhaps the SFC can focus on doing that type of work (outreach and growth, not litigate and destroy).

thanks,

greg k-h

[1] You will note that the FSF and the people who created the GPLv2 are not even involved in this! If anyone actually had any bit of standing for issues like this and how it applied to Linux, it might be them (and even then, we could argue that they don't matter at all, so why would some "random" people who are not developers, and don't have anything "invested" in Linux, really care about us at all?)

#48 lore raw
In reply to Jeremy Allison
Quoted 16 lines · Jeremy Allison
Quoted 5 lines · Greg KH

That brings up a question, who exactly is the SFC representing here? What developers have signed over copyrights to the SFC? Was this done in a "permanent" way? "revoking" copyright assignment isn't exactly a simple thing to do, last I checked, so is this really true?

Ah, this could be a big part of the misapprehensions in this thread !

While it is possible to sign over copyrights to the SFC, this is not commonly done by member projects (I think I'm safe in saying that). It's also not required to assign copyright in order for SFC to represent copyright holders in enforcement actions.

Quoted 4 lines

In Samba for example (which I can talk publicly about), *NO* devlopers have assigned any copyrights to the SFC, they are merely acting as an enforcement agent authorized to do so on our behalf - by the wishes of the developers.

I don't understand, what exactly do you mean by "authorized to do so on your behalf"? Are they your project's legal representation? If you haven't assigned your copyright to them to enforce, how does this all work?

When the SFC approaches a company that seems to not be abiding by the Samba license, who exactly do they say they are and what rights do they have to do so?

thanks,

greg k-h

#49 lore raw
Quoted 9 lines · Greg KH
Quoted 5 lines · Jeremy Allison

In Samba for example (which I can talk publicly about), *NO* devlopers have assigned any copyrights to the SFC, they are merely acting as an enforcement agent authorized to do so on our behalf - by the wishes of the developers.

I don't understand, what exactly do you mean by "authorized to do so on your behalf"? Are they your project's legal representation?

Yes.

Quoted 3 lines

When the SFC approaches a company that seems to not be abiding by the Samba license, who exactly do they say they are and what rights do they have to do so?

They are our legal representation, so they act in the same way any lawyers representing clients do.

#24 lore raw
In reply to Luis R. Rodriguez
Quoted 15 lines · Luis R. Rodriguez
Quoted 14 lines · Mark Brown
Quoted 12 lines · Greg KH
Quoted 4 lines · David Woodhouse

Even though I abhor what Patrick McHardy is doing, I still can't quite find it in my heart to have *sympathy* for his victims. Because it's not as if he's just taking random pot-shots at passers-by on the street. These people defended their actions in court, and lost.

No, that's not what Patrick did. Whenever he actually took something to court, _he_ lost. Companies paid him off before then because they were scared for foolish reasons, or it was honestly just cheaper to do it than go to court and win. He took the traditional model of patent troll to the next level.

Quoted 7 lines
Quoted 2 lines

Please bear in mind that public information on what's going on there is very scarce, I suspect most people have only seen the SFLC statement at:

SFLC != SFC. It will be hard, but try and look at why we have two orgs now. SFLC did do good -- it helped with the upstream openhal efforts and ath5k review. But the org that put out the review below and then published the Principles is SFC, not SFLC.

If it helps, they tend to go by "Conservancy" or "Software Freedom Conservancy", rarely "SFC", to avoid acronym confusion.

#41 lore raw
In reply to Greg KH
Quoted 1 line · Greg KH

<fixing Jeremy's email address, Luis, your email client broke it...>

Stupid mutt, sorry!

Quoted 8 lines · Luis R. Rodriguez
Quoted 7 lines · Greg KH
Quoted 1 line

That brings up a question, who exactly is the SFC representing here?

I've come out:

http://www.do-not-panic.com/2016/02/im-part-of-conservancys-gpl-compliance.html

Quoted 7 lines
Quoted 3 lines

Others have as well. We don't force people to come out though obviously, so its optional. Some folks would prefer their association to remain private. That's a right they should have.

It's something you would "loose" if you actually file for something. And for the SFC to approach a company with a vague "we have random copyrights, give us the code!" that message is horrid!

Growing pains.

Quoted 7 lines

Go back and read my long email about what happens at a company when they are approached by a "representative", and not a developer. Especially one that makes lots and lots and lots of public statements about how companies are evil, how Linux is the GPL's ultimate test case, how they want to use the courts to clarify the GPL's "grey areas". All of these have been stated numerous times by the leadership of the SFC as recently as a few months ago.

I've known Bradley since I was an eager beaver Linux college contributor, and I agree that clearly his background and statements can only send chills to certain companies. But he's also known me, so, I try to what I can to influence him as well with regards to how we work best upstream, and I'm pretty sure he has always appreciated this effort. He's also learned from others and he listens. In fact, it is his job to listen.

He recently noted he's to be held accountable to that.

I will note that despite what he says, when it comes to the kernel actions actually speak more loudly towards advocating permissive licenses than the GPL. In fact he has a Sign-off-by on a driver upstream and that's all ISC licensed. As much as I'm sure it burned his copyleft heart, we did this to help the BSD community as that is what we needed to do. In fact we have this effort to blame for the slew of new permissive licensed practices by a slew of other vendors after that.

Quoted 3 lines

Again, that is NOT how to create and sustain a community. That's how you set fire to it and watch it burn. It happened to Busybox and I don't want it to happen here to Linux.

Understood.

Quoted 11 lines
Quoted 1 line

What do you think? Did it ever cross your mind to consider joining ?

Sure, many years ago. And I'm glad I never signed the document that Bradley gave me many years ago at LinuxCon as it would have been a bad idea (not to mention that people giving developers random legal documents to sign at a conference really isn't a wise thing on either parties involved...) As I mentioned my discussion with Bradley last year, at LinuxCon, I did not want him to continue to do this as it is not how you create a community.

Again, the SFC puts the GPL before Linux,

That's news to me. I think everyone on the alliance would have a fit if this were true. So please stop equating Bradley's own sentiments to that of the alliance's. If that's the message folks get then we need to correct this.

Quoted 3 lines

and is willing to do things to
make Linux fail if it somehow finally answers their unresolved questions about the GPL[1].

We won't allow for that. It is stupid. It should be clear by now the issue has been a proper due process for issues that are long standing and not resolved, last resort issues.

Quoted 6 lines

For a group of people who had nothing to do with Linux at all in the first place, this seems like a very dangerous thing to let them do to you, or anyone else who has signed up for this. This is _our_ project, not theirs. Why would you ever give the power that you have, and have created, away to others that might not have your project's best interest in mind?

You are making an assumption as to what SFC does on behalf of kernel developers, and that we do not discuss things carefully. Obviously that is incorrect.

Quoted 6 lines

Remember, they approached all of us, shopping around the fact that they knew of companies that were violating, showing us printouts of files that were in the information they had received from their Busybox work at vmware. They were digging and asking and wanting to bring this type of lawsuit forward, it was not brought by us, the developers. Bradley has always been very upfront about this, I'll give him credit for that.

Busybox is another one of their members. He has *listened* to their request to try to request more folks involved. It makes sense to dismiss cases where no harm is done or no due process is followed, but if the violation is legit and due process is being followed, it is worth *considering*. Do you not think ?

Quoted 4 lines

Go and watch their talks! Like Linus, I spent all weekend, reading and watching their talks. It's actually worse than I thought. I have notes somewhere around here when I was going to try to point them all out, but I gave up after a while as it was just crazy...

Growing pains. Remember its their job to listen to alliance members. So I voice these concerns ;)

Quoted 2 lines

I can dig them up if you really want, but I suggest you go do it yourself, it's more powerful that way :)

No, I understand. Let me be clear that there is a disconnect between philosophy, engineering and finance. Throw law in the mix and you have a good Mexican Mole sauce. The evolution is painfully slow. As Conservancy gains kernel developers they educate Conservancy on matters and tact for *our* community, just as I'm sure others members (hey git is one) do for their community.

In lack of a better due process, which seems rather implicit and it seems only work for a few, some folks resort to alternatives. If you ask me -- the Principles are a huge win over anything close to represent due process in a responsible way than for instance what seems to have been Patrick's approach. Asking for more feedback openly is another good step. But joining and actively voicing your opinion however is the best strategy, provided of course your concerns are addressed.

Quoted 11 lines
Quoted 7 lines
Quoted 3 lines

What developers have signed over copyrights to the SFC? Was this done in a "permanent" way? "revoking" copyright assignment isn't exactly a simple thing to do, last I checked, so is this really true?

If this is a concern, perhaps its something SFC can address. Also, would you like a way to participate without signing off copyrights to SFC ? If so that sounds like a type of discussion we could start.

How can you participate in something that you are not a part of, and right now, really really want nothing at all to do with?

Quoted 6 lines

I'm really sick after watching all of this, and honestly, want nothing to do with the SFC anymore at all. My employment contract at the LF says that I can't tell them what to do, and they can't tell me what to do either, but I'm going to go recommend to them that they not donate any more money to the SFC as I really think they are toxic to the future of Linux, which is the exact opposite of the LF's charter.

You've made up your mind, and I understand. I'm however in hope other developers who do know folks who are part of the alliance can talk and decide based on these conversations. SFC is simply there to listen to us.

Its sad that misrepresented statements are why you have given up, instead of talking to members of the alliance and what we do, and more importantly the how consensus is reached.

On the other hand I donate and I joined and I voice my opinion, strongly.

Also, by not addressing the last resort measure, or trying to correct SFC's approach, you still leave a gap and I'd hate for more Patrick type of stupid things to happen.

Quoted 5 lines

Outreachy is a good thing that SFC does though, so I'll still support that for now and recommend that the LF funds that portion (if that's even possible, I have no idea how the LF donates their funds, or if even the SFC accepts earmarked funds). Perhaps the SFC can focus on doing that type of work (outreach and growth, not litigate and destroy).

Outreachy is amazing :D

Luis

#82 lore raw
In reply to Guenter Roeck
Quoted 11 lines · Guenter Roeck
Quoted 10 lines · Arnd Bergmann
Quoted 4 lines

Anyway, like I was saying, no one from Linaro ever contributed something meaningful (except some cross-tree patches, and the usual "maintainance" patches).

I'm not surprised at all. Most of the kernel work we do in Linaro is intentionally cross-platform (so it benefits all members equally), or it is done on those platforms that the members decide are important upstream.

Quoted 6 lines

One may wonder how your Linux kernel patches and merges are classified per the above.

Thank you for all your work in the Linux kernel. It is anything but meaningless, and it obviously goes far beyond "some cross-tree patches, and the usual maintenance patches".

I'm sure Maxime was specifically referring to mach-sunxi specific code here, but it's clear how that could be interpreted differently, or taken out of context.

Looking at the commits in mach-sunxi from all Linaro developers, his categorization is completely right:

$ git log --oneline --no-merges --author=linaro --author=arnd --author=robh torvalds/master arch/arm/mach-sunxi/
5c34a4e89c74 ARM: do away with ARCH_[WANT_OPTIONAL|REQUIRE]_GPIOLIB
117d4f59affa cpufreq: sunxi: Use generic platdev driver
e58cf0193c0f ARM: sunxi: allow building without reset controller
1146b600044d ARM: sunxi: fix build for THUMB2_KERNEL
90bc8ac77dc8 ARM: select HAVE_SMP for V7 multi-platform
ddb902cc3459 ARM: centralize common multi-platform kconfig options

However, Linaro also has a number of subsystem maintainers and most of the sunxi specific drivers were reviewed and/or merged by someone in Linaro who is doing that work for all ARM platforms, whether they are made by Linaro member companies or not.

Arnd

#46 lore raw
In reply to Greg KH
Quoted 3 lines · Greg KH

Why would you ever give the power that you have, and have created, away to others that might not have your project's best interest in mind?

Oh and just wanted to confirm, as with Jeremy, I have not given any power up, I hold copyrights, I never signed copyrights away to Conservancy, I joined the alliance and voice my opinion to make sure to help voice my opinion in not only the last resort topics, but also even voice how things might work better for things currently up in the air. Case in point the ZFS crap, the permissive license actually makes sense there [0].

So yet -- more permissive license "agenda" and this coming from SFC! -- jeesh, how copyleft crazy this is, isn't it? These SFC permissive license zealots are just nuts. Crazy I tell you...

So -- if you'd like to voice your opinion and give the conservancy a shot, please note you do not have to sign away copyrights to Conservancy -- so you can join, see we're civil and reach consensus amicably through the list and use fair judgement. Please consider joining the alliance if you want to voice you opinion.

And -- you can always leave, you know -- if it turns out we're bat shit crazy.

[0] http://www.do-not-panic.com/2016/02/zfs-linux-and-illumos-and-isc-license.html

Luis

#42 lore raw
In reply to Luis R. Rodriguez
Quoted 6 lines · Luis R. Rodriguez
Quoted 1 line

Again, the SFC puts the GPL before Linux,

That's news to me. I think everyone on the alliance would have a fit if this were true. So please stop equating Bradley's own sentiments to that of the alliance's. If that's the message folks get then we need to correct this.

Given that the alliance's membership is secret, we only have your word on it. And the governance mechanisms of the alliance have also not been spelled out publically. Do you guys vote? Is it weighted based on the amount of code someone brings to the "alliance"? Or is it just one head, one vote? So if someone with a large amount of code where they own the copyright comes to the project, and Bradley then uses this fact to browbeat a vendor, and that person says, woah, that doesn't seem right? Do they get one vote, or something proportional to what they bring to the table? Sure, they can withdraw from the alliance, so there is _some_ recourse after you've signed on the dotted lines, but only after 30 days, and a lot of threats could be issued in their name in 30 days...

It doesn't help the SFC that there's no transparency in its actions. A similar dynamic is at work when the FBI issues national security letters with gag orders attached. So some kind of regular transparency report where companies have been contacted by the SFC are described in some general way ("a handset vendor", "a consumer electronics product"), the nature of the violation ("lack of apparently otherwise unmodified source code available on the vendor's FTP site", "apparent mixing of GPL code with some incompatible open source license", "out-and-out blatent misuse of Linux code in a completely unrelated commercial virtualization product," etc.) and the steps taken (friendly contact, lawsuit threatened, lawsuit filed, etc.) might be helpful in the long run.

Quoted 3 lines

Its sad that misrepresented statements are why you have given up, instead of talking to members of the alliance and what we do, and more importantly the how consensus is reached.

So I don't believe they are misrepresented, because #1, a few years ago, in a hallway discussion, I've asked Bradley point blank whether the GPL or the long-term health of Linux development was more important to him, and he very candidly said "the GPL". Props for him not dissembling, but this was not a case of my not understanding what he said.

More importantly, #2, if you look at the 2016 linux.conf.au talk, it was quite unambiguous. Trying to claim that there was misunderstanding or misrepresentation going on is roughly the same as Trump surrogates trying to claim that Donald Trump's very clear statements on Mexicans was all a misunderstanding pushed by the mainstream media. But hey, don't take my word for it; listen to the talks for yourself and judge for yourself.

Maybe it was all rhetoric was for fundraising purposes, and wasn't actually meant "for real" (just as the claims that Trump's words about immigration was just to appeal to the Republic base, but it wasn't what he _really_ believes and he _really_ isn't a racist in his heart of hearts) --- but to the extent that Bradley is the face of "The Alliance" when he goes and pays visit to companies, the fact that he was making these statements just a few months ago doesn't help "The Alliance" and it certainly doesn't help Linux since it sows FUD to the companies who could just as easily decide to use a commercial OS like QNX, or another Open Source OS such as FreeBSD instead.

(Never think you are irreplaceable; you aren't. This is true just as much for programmers and employees, as it is for operating systems.)

- Ted

#83 lore raw
In reply to Arnd Bergmann

Hi Arnd,

Quoted 3 lines · Arnd Bergmann

However, Linaro also has a number of subsystem maintainers and most of the sunxi specific drivers were reviewed and/or merged by someone in Linaro who is doing that work for all ARM platforms, whether they

I think "ARM" shouldn't be part of this sentence (e.g. for SPI).

Quoted 1 line

are made by Linaro member companies or not.

Yep. That's assumed by wearing a Linux MAINTAINERS hat...

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

#44 lore raw
In reply to Luis R. Rodriguez
Quoted 17 lines · Luis R. Rodriguez
Quoted 1 line · Greg KH

<fixing Jeremy's email address, Luis, your email client broke it...>

Stupid mutt, sorry!

Quoted 12 lines · Luis R. Rodriguez
Quoted 10 lines · Greg KH
Quoted 1 line

That brings up a question, who exactly is the SFC representing here?

I've come out:

http://www.do-not-panic.com/2016/02/im-part-of-conservancys-gpl-compliance.html

Others have as well. We don't force people to come out though obviously, so its optional. Some folks would prefer their association to remain private. That's a right they should have.

Quoted 5 lines
Quoted 3 lines

It's something you would "loose" if you actually file for something. And for the SFC to approach a company with a vague "we have random copyrights, give us the code!" that message is horrid!

Growing pains.

Huh? What do you mean by this, the SFC has been working on doing this for _years_. They have been doing this for other projects for probably over a decade now. You don't start approaching companies and then go "oops, sorry, still learning how to do this, never mind!" You also don't go around in public saying crap like "corporations are evil!" and then show up on a company's doorstep saying "just kidding, please work with us, we are friendly, trust us."

It's as if you went and hired the law firm of Dewey, Cheetham & Howe, and expected that they _not_ do what they had been doing for years and years before that, just because you were now their client.

That's NOT how you pick someone to be your representative. It looks badly on you, and of course it looks horrid on the community you are a part of.

Again, as Linus said, appearances matter. And you can't just blow off public statements with the "but I said it from my personal, not my corporation which I founded, email account."

As IBM drilled into me many many times when I worked for them, employees of a corporation reflect directly on how the corporation is viewed by others, no matter if you are the president, or an engineer, when you are in public. I think there is even some legal rules about that somewhere as well...

Quoted 6 lines
Quoted 1 line

Again, the SFC puts the GPL before Linux,

That's news to me. I think everyone on the alliance would have a fit if this were true. So please stop equating Bradley's own sentiments to that of the alliance's. If that's the message folks get then we need to correct this.

WHAT???

Bradley has said this to me, and many others, directly! He founded the SFC and is responsible for setting the direction of it and picking and choosing what it will do, as well as deciding who will help him run it. To ignore his public, and private, statements about something like this is folly.

If you want legal representation for kernel license issues, great, but pick someone that doesn't go around publicly saying crap like this, as again, it reflects directly on you!

Luis, I trust you when you say you want Linux to succeed, as it's backed up by years and years of your hard work and dedication and public statements. But I don't trust your representative, as he has explicitly stated that he doesn't care. That's what started this whole long email-thread-from-hell, his statement that we have to "enforce in the courts or give up on the GPL." That's toxic to Linux as both me and Linus have pointed out.

People will tell you who they are if you listen to them. Please listen.

I suggest you get a different representative, there are many out there that I know of that do care about the future of Linux, and have backed that up with years of work toward that goal. I encourage you work with them instead, as it seems that your representative doesn't seem to share the same feelings about the future of _your_ project as you do.

thanks,

greg k-h

#84 lore raw
In reply to Arnd Bergmann
Quoted 15 lines · Arnd Bergmann
Quoted 14 lines · Guenter Roeck
Quoted 10 lines · Arnd Bergmann
Quoted 4 lines

Anyway, like I was saying, no one from Linaro ever contributed something meaningful (except some cross-tree patches, and the usual "maintainance" patches).

I'm not surprised at all. Most of the kernel work we do in Linaro is intentionally cross-platform (so it benefits all members equally), or it is done on those platforms that the members decide are important upstream.

One may wonder how your Linux kernel patches and merges are classified per the above.

Quoted 7 lines
Quoted 3 lines

Thank you for all your work in the Linux kernel. It is anything but meaningless, and it obviously goes far beyond "some cross-tree patches, and the usual maintenance patches".

I'm sure Maxime was specifically referring to mach-sunxi specific code here, but it's clear how that could be interpreted differently, or taken out of context.

Yeah, sorry, I wasn't try to reduce or deny the huge amount of work Linaro is doing on the whole kernel.

My point was just that, on the Allwinner specific code, all the work done was on code that was already there, not on any new code.

Which doesn't prevent us from using a lot of Linaro code everywhere.

Maxime

Signature · 3 lines
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
#43 lore raw
In reply to Theodore Ts'o
Quoted 10 lines · Theodore Ts'o
Quoted 6 lines · Luis R. Rodriguez
Quoted 1 line

Again, the SFC puts the GPL before Linux,

That's news to me. I think everyone on the alliance would have a fit if this were true. So please stop equating Bradley's own sentiments to that of the alliance's. If that's the message folks get then we need to correct this.

Given that the alliance's membership is secret, we only have your word on it.

Its optionally secret so developer's privacies can be respected, which means some folks are willing to say publicly they are part of it and some are not. Why would someone not want to come out ? Well why would they with such hostility going around ? First one needs to understand why the hostility is there and now it seems some clarify is coming up. Is it because companies who use Linux don't want to give developers and users their freedoms, or because of tact? It sounds like its the tact. Can you confirm if that is correct ?

I came out before these clarifications given I have an employer who has built into their DNA FOSS and understands these issues are part of our DNA to resolve and they have the patience to deal with this. It is critical to both understand these issues and resolve them in an amicable way, with the community and developers, as transparently as possible. A concern others face is the chance of being put on a sort of a persona non grata list for employers. Does such a list exist ? I don't know, but such concerns exist. If you have kids to maintain the pressure is even harder. I personally have the luxury to not be concerned over this since I have a supportive employer and do not have children -- nor plan on having any ;) Not only that, if my employer were to start doing crazy things I'm assured I would not be the only one to step out, and worst come to worst, I could just go and hack on Linux from a beach in Costa Rica. That's not a bad thing. I know of some retired developers who go around travelling and contributing when they can to Linux on 802.11 :D There's not many folks in similar situations though, and you cannot rationally expect someone to compromise on this.

If the concerns are not clear for some folks to come out -- please let me know.

Quoted 2 lines

And the governance mechanisms of the alliance have also not been spelled out publically. Do you guys vote?

Like I said before -- no, because we so far have pretty much have had consensus. We should probably consider voting if such consensus were not happening. Its something to discuss in the coalition.

Quoted 7 lines

Is it weighted based
on the amount of code someone brings to the "alliance"? Or is it just one head, one vote? So if someone with a large amount of code where they own the copyright comes to the project, and Bradley then uses this fact to browbeat a vendor, and that person says, woah, that doesn't seem right? Do they get one vote, or something proportional to what they bring to the table?

We have no had to deal with this issue or concern, we so far have had consensus. If the issue comes up then we should talk about it in the coalition, among developers.

Quoted 4 lines

Sure, they can withdraw from the
alliance, so there is _some_ recourse after you've signed on the dotted lines, but only after 30 days, and a lot of threats could be issued in their name in 30 days...

It sounds like these are terms you can discuss with Conservancy and see if its possible to address them. After all -- these are the sorts of things I would have expected from you know, a Q&A which you could get immediate feedback from Karen from.

Quoted 1 line

It doesn't help the SFC that there's no transparency in its actions.

What type of transparency would you like ?

Quoted 2 lines

A similar dynamic is at work when the FBI issues national security letters with gag orders attached.

Seriously Ted... you are comparing FBI gag orders with Conservancy's coalition. Because unless my eyes need LASIK again -- which maybe they do -- this just happened. Let us recall Karen was the one who brought up in the list the idea of *flying out* to KS and let developers, you know, ask questions. Does the FBI does this sort of crap ? Hell no!

Quoted 10 lines

So some kind of regular
transparency report where companies have been contacted by the SFC are described in some general way ("a handset vendor", "a consumer electronics product"), the nature of the violation ("lack of apparently otherwise unmodified source code available on the vendor's FTP site", "apparent mixing of GPL code with some incompatible open source license", "out-and-out blatent misuse of Linux code in a completely unrelated commercial virtualization product," etc.) and the steps taken (friendly contact, lawsuit threatened, lawsuit filed, etc.) might be helpful in the long run.

I am not sure, this seems like it might break confidentiality for companies... but IANAL, so if we had a Q&A perhaps you could have gotten a direct answer, maybe ask Karen in person next time you see her!

Quoted 10 lines
Quoted 3 lines

Its sad that misrepresented statements are why you have given up, instead of talking to members of the alliance and what we do, and more importantly the how consensus is reached.

So I don't believe they are misrepresented, because #1, a few years ago, in a hallway discussion, I've asked Bradley point blank whether the GPL or the long-term health of Linux development was more important to him, and he very candidly said "the GPL". Props for him not dissembling, but this was not a case of my not understanding what he said.

My point was to disregard Bradley as what matters here for Linux is what Linux developers part of the alliance care for and what you need to do is talk to those involved. The Q&A would have been a perfect opportunity you know...

I can only speak for myself so I'll say how I feel.

I care deeply over the long term development and health of the entire Linux ecosystem, and above and beyond all things in the ecosystem I care mostly and deeply about Linux. Since Linux is GPL I've been an advocate for it, since I also care about the license it uses, because it gives both developers and uses certain rights that I think are bad ass. So when it comes to "long-term health of Linux development" -- this is subjective if we do not take into consideration both the practical gains over open collaborative development and the *freedoms* that come with Linux that we grant to both our developers and users. So if you'd like we can get into specifics here. Please let me know if you have any particular questions.

I encourage you to ask others involved similar questions.

Quoted 7 lines

More importantly, #2, if you look at the 2016 linux.conf.au talk, it was quite unambiguous. Trying to claim that there was misunderstanding or misrepresentation going on is roughly the same as Trump surrogates trying to claim that Donald Trump's very clear statements on Mexicans was all a misunderstanding pushed by the mainstream media. But hey, don't take my word for it; listen to the talks for yourself and judge for yourself.

Yeah often, but not always, what Bradley says makes me cringe, so I joined Conservancy to ensure I can voice my concerns and express exactly what I think to him and all other developers.

Quoted 10 lines

Maybe it was all rhetoric was for fundraising purposes, and wasn't actually meant "for real" (just as the claims that Trump's words about immigration was just to appeal to the Republic base, but it wasn't what he _really_ believes and he _really_ isn't a racist in his heart of hearts) --- but to the extent that Bradley is the face of "The Alliance" when he goes and pays visit to companies, the fact that he was making these statements just a few months ago doesn't help "The Alliance" and it certainly doesn't help Linux since it sows FUD to the companies who could just as easily decide to use a commercial OS like QNX, or another Open Source OS such as FreeBSD instead.

Agreed.

Quoted 2 lines

(Never think you are irreplaceable; you aren't. This is true just as much for programmers and employees, as it is for operating systems.)

Agreed.

Luis

#45 lore raw
In reply to Greg KH
Quoted 36 lines · Greg KH
Quoted 17 lines · Luis R. Rodriguez
Quoted 1 line · Greg KH

<fixing Jeremy's email address, Luis, your email client broke it...>

Stupid mutt, sorry!

Quoted 12 lines · Luis R. Rodriguez
Quoted 10 lines · Greg KH
Quoted 1 line

That brings up a question, who exactly is the SFC representing here?

I've come out:

http://www.do-not-panic.com/2016/02/im-part-of-conservancys-gpl-compliance.html

Others have as well. We don't force people to come out though obviously, so its optional. Some folks would prefer their association to remain private. That's a right they should have.

Quoted 5 lines
Quoted 3 lines

It's something you would "loose" if you actually file for something. And for the SFC to approach a company with a vague "we have random copyrights, give us the code!" that message is horrid!

Growing pains.

Huh? What do you mean by this, the SFC has been working on doing this for _years_. They have been doing this for other projects for probably over a decade now. You don't start approaching companies and then go "oops, sorry, still learning how to do this, never mind!" You also don't go around in public saying crap like "corporations are evil!" and then show up on a company's doorstep saying "just kidding, please work with us, we are friendly, trust us."

It's as if you went and hired the law firm of Dewey, Cheetham & Howe, and expected that they _not_ do what they had been doing for years and years before that, just because you were now their client.

Quoted 7 lines

That's NOT how you pick someone to be your representative. It looks badly on you, and of course it looks horrid on the community you are a part of.

Again, as Linus said, appearances matter. And you can't just blow off public statements with the "but I said it from my personal, not my corporation which I founded, email account."

Let's not get into crazy details here...

There's tons of things folks say or do publicly which make companies cringe, even our best of maintainers have quite a lot of pictures on the Internet giving the middle finger to them...

At one point I considered giving up on Linux kernel development because of the actions of *one* developer. But I did not. I decided these are growing pains and I really feel we can overcome these stupid qualms.

So yes, tact. I am saying we learn from these mistakes and move on.

That is what I meant by growing pains.

Quoted 5 lines

As IBM drilled into me many many times when I worked for them, employees of a corporation reflect directly on how the corporation is viewed by others, no matter if you are the president, or an engineer, when you are in public. I think there is even some legal rules about that somewhere as well...

Makes sense.

Quoted 15 lines
Quoted 6 lines
Quoted 1 line

Again, the SFC puts the GPL before Linux,

That's news to me. I think everyone on the alliance would have a fit if this were true. So please stop equating Bradley's own sentiments to that of the alliance's. If that's the message folks get then we need to correct this.

WHAT???

Bradley has said this to me, and many others, directly! He founded the SFC and is responsible for setting the direction of it and picking and choosing what it will do, as well as deciding who will help him run it. To ignore his public, and private, statements about something like this is folly.

Quoted 3 lines

If you want legal representation for kernel license issues, great, but pick someone that doesn't go around publicly saying crap like this, as again, it reflects directly on you!

Since we have a group of like minded folks who care about freedom, given no other alternative existed -- I preferred to join and ask them to tone it down if I saw it fit.

Quoted 7 lines

Luis, I trust you when you say you want Linux to succeed, as it's backed up by years and years of your hard work and dedication and public statements. But I don't trust your representative, as he has explicitly stated that he doesn't care. That's what started this whole long email-thread-from-hell, his statement that we have to "enforce in the courts or give up on the GPL." That's toxic to Linux as both me and Linus have pointed out.

I *completely* understand the concern, and I choose to join to help ensure that no lunacy is done in the name of kernel developers. Although I already trusted the kernel developers that were part of the alliance, I sympathized with other developers and users who were having issues getting source code to products they purchase. I decided it is best to join and voice in my best capacity what I believe is rational for our community.

Quoted 1 line

People will tell you who they are if you listen to them. Please listen.

Sure thing.

Quoted 5 lines

I suggest you get a different representative, there are many out there that I know of that do care about the future of Linux, and have backed that up with years of work toward that goal. I encourage you work with them instead, as it seems that your representative doesn't seem to share the same feelings about the future of _your_ project as you do.

Thanks, so far Conservancy has been *extremely* keen on ensuring they listen to the developers that are part of the alliance so I trust them with what they are doing. I wish I could tell you to what extent Conservancy is serious about this... but then I'd break confidentiality :) If you trust me -- then please trust that they listen and work with our expressed interests and goals.

If they don't -- I'll ask you then for alternative representatives that are out there which might also care not only for Linux but also for both the developer and user freedoms that come with Linux.

Luis