LWN: Comments on "Bruce Perens: Statement on Busybox Lawsuits"

Bruce Perens: Statement on Busybox Lawsuits

landley — Wed, 23 Dec 2009 22:51:02 +0000

My point was merely that gzip's use of the technique predated busybox.

Otherwise: dead thread, by the editor's request.

Enough, please?

bronson — Wed, 23 Dec 2009 08:54:17 +0000

Cluelessness alert. :(

Enough, please?

BrucePerens — Wed, 23 Dec 2009 04:34:26 +0000

Sock-puppet alert.

Yes, it's like RMS's waiver...

Baylink — Wed, 23 Dec 2009 04:28:34 +0000

I posted a comment earlier tonight that might clarify this for you.

The issue is not individual file licenses, which it's clear you cannot change; it's how you can validly distribute an assembled package, which depends on both the incoming licenses (to you) and the licenses you apply to your changes (since the only time this matters is if you're changing or extending a package *and then distributing it yourself*.

Bruce Perens: Statement on Busybox Lawsuits

Baylink — Wed, 23 Dec 2009 02:53:29 +0000

FWIW, Rob, I've been following open source development since before it was called that; Lance-Taylor UUCP, HylaFAX, and a bunch of other projects few people remember anymore unless they're using them, going back to, oh, 1983 or 4...

and I'm having no trouble following your postings, and it's clear to me that you know what you're talking about.

Not that you *needed* external validation or anything, but... :-)

Bruce Perens: Statement on Busybox Lawsuits

Baylink — Wed, 23 Dec 2009 02:41:04 +0000

Nope, it is in fact subset -- intersection.

Please understand that we're talking about "subset of the granted rights of distribution". Not a subset of the *licenses themselves as objects*.

The alternative would be superset or union, and that could logically never produce the "so you therefore have no legal way to distribute the code at all" situation, which we all know happens.

Bruce Perens: Statement on Busybox Lawsuits

Baylink — Wed, 23 Dec 2009 02:37:27 +0000

It might clarify things if everyone remembered that the license controls *how you distribute the code after you've modified it*, and only that.

And that each person who distributes code is controlled by *the licenses attached to that code*.

So if I receive the code -- it doesn't matter how -- and *all the files say GPLv2+*, then I can distribute it under the terms of any version I like.

Clearly, this means that the only thing which might change the terms under which someone taking *my* distribution can distribute the packge is *the licenses on any files I add*.

If I take a GPLv2+ package, and substantially extend and modify it, and place my changes under a 2-only license, then in practical terms, I've restricted downstream distribution of *the package with my changes* to 2-only, because (as Bruce -- I think -- notes above) in order to use a later license, you'd have to take my work back out... and why bother? You could just go back to my upstream, and use that.

IocANALe.

Bruce Perens: Statement on Busybox Lawsuits

Baylink — Wed, 23 Dec 2009 02:24:24 +0000

Yes, *if* the code was released with the "or any later version" language...

which is *purposefully* optional.

Bruce Perens: Statement on Busybox Lawsuits

Baylink — Wed, 23 Dec 2009 02:21:41 +0000

Bruce is right: "decide which function to perform by looking at argv[0]" predates gzip.

I have here in my hand Kernighan and Pike, _The_UNIX_Programming_Environment_, which suggests the idea on page 85, as "a novel use".

Publication date?

1984.

Anyone wanna go back any further than that?

Enough, please?

syspig — Mon, 21 Dec 2009 06:10:43 +0000

With all due respect, you opened the door when you chose to publish Mr. Perens' ill-advised press release. He's been soundly taken to task with some very informative posts, with cites to historical events that gives much needed clarity into his motives and claims.

While the tone may be somewhat harsher than is typical, this has been one of the most enlightening discussions I've seen here.

Bruce Perens: Statement on Busybox Lawsuits

efexis — Sun, 20 Dec 2009 20:38:27 +0000

" I also pointed out you could maintain your own fork"

With blackjack? And hookers?!!

It was done many times before.

khim — Sun, 20 Dec 2009 07:54:44 +0000

Sounds good, but I'm still confused. Everyone agrees we can convert "V2 Or later" to "V2 Only" but nobody agrees HOW to do it.

Take a look on OpenSSL for example. This package changed licenses 2 or 3 times. You keep copyright notices from old owners around and just add a new one in files where new, "V2 only" code is added. Looks ugly, yes, but it's the only way to do legally it.

The only legal way to remove or change copyright notice without consent of copyright owner is if you remove the file and/or replace it with a brand new one.

I'm still confused. I thought "this License" meant the v2 GPL. The "or later" clause is NOT part of "this License" (because it actually refers to multiple licenses).

License is V2 GPL, but as you've pointed out "or later" clause is NOT part of teh license and it's NOT part of the licensed material. It's COPYRIGHT NOTICE and it's modifications is discussed in GPL separately (as in: it explains how to add the note and makes it impossible to change it).

"you are out" means I get sued, right?

No. You can be sued (since you are distributing the stuff without license), but this is not automatic.

Companies will stick their heads in the sand about the GPL until forced to deal with it. (I know, I've been an engineer telling my boss we should comply with the GPL, and the boss says "we can deal with that later".)

Looks like "the later" is "now". Most companies now publish sources like GPL requires (of course they can not be used as most hardware out there is TiVoized, but that's another story), but few holdouts will probably not change their ways till goods will not be confiscated for copyright violations.

Yes, it's like RMS's waiver...

dmag — Sun, 20 Dec 2009 05:21:52 +0000

> Illegal change of note is violation of GPL:

Sounds good, but I'm still confused. Everyone agrees we can convert "V2 Or later" to "V2 Only" but nobody agrees HOW to do it.

In practice, keeping the "or later" clause at the top of the file after you merge in "v2 only" code is dangerous.

Or the reverse: I've got a "v2 only" file, and merge in a few lines of "or later" code. Do I put "or later" at the top of the file now?

I think both sides would like the FSF to identify exactly how to merge V2+ and V2-only code.

> GPL gives you certain rights, but it does not give you right to change copyright notes (You may copy and distribute... provided that you ... keep intact all the notices that refer to this License and to the absence of any warranty).

I'm still confused. I thought "this License" meant the v2 GPL. The "or later" clause is NOT part of "this License" (because it actually refers to multiple licenses).

> GPLv3 is more forgiving in this regard but GPLv2 is not: minor violation - and you are out.

"you are out" means I get sued, right?

Suing people (after talking to them of course) might be bad in the short-term, but it is a good long term strategy. (reminds me of RMS -- look at the future, not today).

The fact is that companies are pathological. They will gladly make cribs that kill babies until the government makes it unprofitable by making those cribs illegal to sell.

Companies will stick their heads in the sand about the GPL until forced to deal with it. (I know, I've been an engineer telling my boss we should comply with the GPL, and the boss says "we can deal with that later".)

Bruce Perens: Statement on Busybox Lawsuits

landley — Sun, 20 Dec 2009 04:13:36 +0000

It's hard because I'm tired of arguing about it with people who don't bother to do their homework.

And it's not that your selection of terms is unclear, it's that your understanding of copyright law in general (and Title 17 in particular) seems to be unclear.

> And in this case, seeing as the compilation is a mix of v2-only and v2+,
> the compilation licence has to be v2-only.

In the phrase "compilation license" you're confusing at least three distinct concepts: compilation copyright, derived works, and issuing a license to a copyright. (And you're probably unaware that a fourth related concept, joint copyright, even exists.)

Look, if you're really going to care you should talk to a lawyer or take a course in business law or something. But here's a 10,000 foot overview that's worth what you paid for it:

First, let's talk about licensing. One copyright can have multiple, (completely incompatible) licenses granted on it. For example, the QT project lists three:

http://qt.nokia.com/products/licensing

(Although only two actually matter since the second is convertible into the third, they probably just did the third to get the FSF to shut up.)

So QT has a commercial license, and LGPL. If you ship a modified binary without offering source code, you've violated the terms of the LGPL. If you put your source up for download for free to all and sundry, you've violated the terms of your average commercial license. And this is _fine_, because you only need _one_ valid license under which to distribute the code. When there are multiple ones, you can choose the one that best suits your needs and obey the terms of that one.

The fact that everybody who buys the commercial license ALSO gets the code under LGPL means that the code is dual licensed when they get it, and they're intentionally discarding one of those licenses. This is _normal_.

So: one copyright can have multiple licenses, and those licenses can be completely unrelated, of diffent scope, duratinon, requirements, and so on. And some of those licenses may not apply to you. Clear so far?

Now let's look at different _kinds_ of copyright a work can have. Title 17 has a "definitions" section:

http://www.copyright.gov/title17/92chap1.html#101

> A compilation is a work formed by the collection and assembling of
> preexisting materials or of data that are selected, coordinated, or
> arranged in such a way that the resulting work as a whole constitutes an
> original work of authorship. The term compilation includes collective
> works.

What that means is a compilation copyright is a copyright on the selection of elements to include, such as a short story anthology or a CD containing a dozen music tracks from various authors. It mostly becomes relevant when the person who put together the compilation contributed no actual material to the result that could form a derivative work.

Compilation copyright is about "you included substatially the same public domain stories I did in your book, that organization was copied from me". In busybox, you might be able to claim the selection of commands to implement gives you a compilation copyright, except that we implement hundreds more now the selection of commands to implement is "what's in the Single Unix Specification plus the Linux man pages", which falls under scenes a faire:

http://www.ivanhoffman.com/scenes.html

One of the _other_ failings of compilation copyright is that if you cherry-pick out the individual elements and take a significantly different subset of them (or a compile them in a different way), the compilation copyright doesn't apply. Thus if Bruce had a compilation copyright on busybox 0.0.1 or whatever it was he released and somebody grabbed just one command from that (which Bruce didn't write), whatever license terms he decided to apply wouldn't matter unless he had code in that command. It would be entirely based on what the original author had licensed the work as. (See http://www.copyright.gov/title17/92chap2.html#201 part c.)

Because of this, I've never seen a GPL enforcement action based on a compilation copyright, and when I brought it up with the SFLC three years ago they didn't want to go there. Compilation copyright is generally fairly weak and uninteresting unless you're an anthology publisher.

Open source projects such as Linux have always based their legal status on derived works. Again from the definitions section of title 17:

> A derivative work is a work based upon one or more preexisting works,
> such as a translation, musical arrangement, dramatization,
> fictionalization, motion picture version, sound recording, art
> reproduction, abridgment, condensation, or any other form in which a
> work may be recast, transformed, or adapted. A work consisting of
> editorial revisions, annotations, elaborations, or other modifications,
> which, as a whole, represent an original work of authorship, is a
> derivative work.

(For example, somebody takes an existing mozart performance and puts a drum track over it, they've created a derivative work. Now to distribute recordings of the result they need to get a license to the mozart performance _and_ issue their own license on their drum track.)

Note that every compilation copyright is _on_ a derivative work, but not every derivative work has a compilation copyright claimed on it.

The thing about a derivative work is that the copyrights of the contributions remain distinct, and each is licensed separately. The copyrights on each contribution to the derivative work must be licensed under compatible terms in order for the derivative work as a whole to be copied and distributed.

So just as one copyright can have multiple licenses, one derivative work is made up of multiple copyrights, ideally each licensed under the same terms. (Simply put, multiple copyrights, one license.) Ok?

Derivative works are the "boolean and" of copyrights, and it fails closed. Violate the license to one component, and you have infringed that copyright, and the owner of that copyright has standing to sue. This makes the addition of new licenses extremely difficult, and makes dropping licenses in a multi-license scenario easy. Making it hard to add new licenses (such as proprietary commercial ones) is generally what open source projects want (unless they're using BSD licensing where the license itself is "do what you will, just don't sue me"), so it's how open source developers arrange their projects.

For example, if you put together a derived work combining public domain code, code dual licensed under GPL and some other license (such as Perl, which is dual GPL and Artistic), and code that's only under GPLv2, you have a number of different licenses on the _components_, but only one license under which the derived work as a whole can be shipped.

If a recipient of that derived work wants to pick it apart and grab individual chunks and argue that those components are in the public domain or usable under the terms of the Artistic, that's their right to do so. It's also their problem to do the analysis to prove the provenance of that part of the code.

The BusyBox project's git repository currently has 10,866 commits in it. That means Erik Andersen and his successors have created over 10,000 distinct derived works, and if you want to pull any chunk from the current version and go "this was originally BSD licensed, I want to use it in my BSD licensed project" (such as networking/traceroute.c) you have to go through and find all changes to that chunk since it was so licensed and either remove those changes or get permission to use them under BSD from whoever owns that change's copyright (the source control commit messages should record who wrote it).

Of course it's way easier (and more sure) to just go find the older copy before it was modified into a derived work that included changes from authors who only licensed their copyrights under GPlv2. And as I said, those old versions are still there in the downloads directory, and in the repository, and so on.

What open source projects generally try to _avoid_ is a "joint copyright", which is the "boolean or" case. That's where there's one copyright shared by multiple authors. That means each copyright holder has an equal right to the resulting work, and thus each of them individually can issue a license to the whole work all by themselves under any terms they like. (There's just the one copyright to be licensed, so any license covers the whole thing. Who's owed what share of any royaltaies from such licensing is another matter.)

The FSF never wanted to deal with any of this and forced all their contributors to sign over their copyrights (not just grant compatible licenses to them in non-centralied regimes such as Linux). That way FSF code has one copyright owner, which can thus issue new licenses on a whim.

Of course if you remember reading about the SCO/Novell case on Groklaw, signing over copyrights requires a "written instrument of conveyance", I.E. they have to keep actual signed pieces of paper on file in a physical filing cabinet, and that bureaucracy was one of the main limiting factors preventing their development process from scaling. (The other was Richard Stallman's ego, but let's not go there.)

(At least you're not one of the people who try to drag contract law into it. And I've skirted the whole "copyright doesn't cover _use_" morass. Some lawyer somewhere needs to do a "copyright and licensing for open source developers" class. I've arranged a few panels at Penguicon and Linucon, often with Eric Raymond's wife Cathy, who is a Lawyer. But that's just poking at the problem...)

Sigh. Let the SFLC or the Linux Foundation deal with it...

> (imho, but that's only ho, they should have said "we've accidentally
> mixed some v2-only into a v2+ project, so all new code must be v2+ as
> per the original but the project is actually v2-only unless and until
> somebody bothers to do something about it.)

You mean like we publicly discussed doing on the busybox mailing list three years ago, in a number of different threads I pointed to earlier in this discussion?

http://lists.busybox.net/pipermail/busybox/2006-August/05...

So your advice is we should have taken an option we discussed at length, for several months, and decided against months before His Special-ness ever showed up.

Rob

Enough, please?

corbet — Sun, 20 Dec 2009 01:27:32 +0000

On this thread, too, I would like to request that people just stop. The history, I think, has been sufficiently rehashed. LWN seems to have become a place where people go to throw things at each other; suffice to say that's really not part of my vision of the site. Please, let's move on.

Bruce Perens: Statement on Busybox Lawsuits

landley — Sat, 19 Dec 2009 23:58:40 +0000

> if you wanted a GPLv2 clone of busybox you should write it yourself
> instead of relicensing an existing project.

A) You can't relicense an existing project if you aren't the copyright holder. However, each new release is a fresh derivative work, which must be under a compatible license but isn't required to be under the _same_ license. GPLv2-only is a compatible subset of "GPLv2 or later".

It's sad that Bruce didn't understand that, but I don't care.

B) I wasn't the one proposing "relicensing", Bruce was. Busybox had always been distributed under GPLv2 because GPLv3 didn't _exist_. I simply dropped what had up until that point been a purely theoretical dual license, under which the code had never actually been distributed, and made it not apply to future derived works (I.E. the current release I was working on and future releases based on that).

Bruce was the one who wanted to distribute busybox under a new license that hadn't existed up until that point. I declined to allow my code, which I had written, to be licensed under those terms.

C) I did write a new one from scratch: http://landley.net/code/toybox

I wrote far more code in that than Bruce ever did in busybox, but that was pretty much just a hobby working out some leftover design ideas I had (much better underlying infrastructure than BusyBox was using). I wasn't particularly interested in competing with the ten year headstart Erik and I had given BusyBox, or the existing active development community Erik and I had grown around it, nor the energy Denys Vlasenko (the maintainer I recruited to replace me) was putting into it.

These days I have a todo item to push my design changes (and some of the toybox commands I wrote, such as patch and df) upstream into BusyBox, which would be somewhere between the third and the fifth complete rewrite of that infrastructure since Bruce's day (depending on how you want to count the scripts/individual stuff and moving the main.c code into libbb).

You seldom find Bruce arguing about the actual busybox _code_. That's because he's completely unfamiliar with it.

> Regardless of how long ago that project was forked and how little of his
> code remained after so many years, it was indisputedly his project begun
> with his code that all the other coders have hacked on over the years.

Nah, that was pretty disputable actually. I've never even _seen_ a version released by Bruce, the comparisons I did were against the oldest version Erik released (0.25), which was already pretty heavily modified from Bruce's time.

Erik Anderson took various forks of a project bruce had abandoned years earlier and stitched them together into a new project, which he proceeded to replace pretty much all of the existing code of within the first year or two. It probably would have been _easier_ for him to just start over from scratch, but that wasn't his style.

As to what Bruce originally did, he stitched together a dozen or so existing projects he hadn't written. The bulk of the original code was things like gzip, copied verbatim into his "new" project. Other projects (such as Red Hat's nash) did the same thing, but they didn't get turned into important embedded tools because they weren't repurposed and rewritten for seven years by Erik Andersen.

> Arent hackers supposed to have ethical standards and respect for other
> peoples work?

Dunno, ask Bruce. He certainly wasn't respecting the years I'd put into the project (at least twice what he ever had by that point), or the years Erik had (which was over three times as much as Bruce had ever done, without any input from Bruce, and that's just going by duration rather than lines of code which would give us an order of magnitude larger gap).

I made sure Erik Andersen had no problem with me going GPLv2-only, and if Erik had objected I wouldn't have done it, because I had (and still have) enormous respect for him as a developer. (As far as I'm concerned, Erik had veto power because he'd _earned_ it.) I also polled the list and discussed the issue for months publically with the busybox developer community. The fact that Bruce wasn't part of that community and had not been for a full decade, and thus didn't show up to complain until _after_ this process was Bruce's problem, not mine.

Also, Erik got permission from Bruce to relaunch the project way back, which was already a couple years after Bruce's involvement in the project had ended. (I.E. Bruce was long gone as a developer, Erik was just being polite and covering his bases.) Authority passed from Bruce (and a couple other developers who had maintained their own forks after Bruce abandoned the project) to Erik to me to Denys. But once authority has passed, it's passed. Erik never tried to order me around, and I can't order Denys around. (We can make _requests_, but "no" is a prefectly acceptable answer. The new versions are not put out by the old maintainer.)

The reason I have no respect for Bruce's "work" is because I've never seen him do any work for me to respect. In the five years I'd been poking at busybox (by the time I became maintainer and tried to clean up the license mish-mash) I had never interacted with Bruce as a programmer, and his contributions (if any) had never been discussed on the list or on IRC.

I had met Bruce once at a conference (in 2000 or 2001) back when he was working for HP, when I was going around interviewing potential guests for what became Penguicon. That was after he'd abandoned BusyBox and before I'd done more than casually poke at it, and we didn't talk about code. I mostly remember that HP could fly him in to be a speaker for free, which is presumably why he was there.

I think I worked on BusyBox for about three years before becoming aware Bruce had any historical involvement at all. Keep in mind that BusyBox contains code with Linus Torvalds' copyrights on it, and Linus has no personal involvement with BusyBox. Integrating external code and rewriting it to be smaller and simpler is one of the things BusyBox has always done. There were _hundreds_ of copyright notices in the busybox code.

Bruce simply isn't a coder. Hasn't been this decade, that I've noticed. He's an author and politician. (Hint: most people don't need an equivalent of http://perens.org/about/self-promotion/ on their websites.) His claims to fame are things like inheriting Ian Murdock's Debian project and giving it is current culture of hostility to newbies and close ties to the FSF. That isn't code, that's politics.

Other "political" figures in the community earned it. As much as I disagree with Richard Stallman, he's written tons of code that people actually use. I could tell you the projects Erik Raymond contributes to (currently GPSD and Battle for Wesnoth, historically bogofilter and fetchmail and the emacs lisp library and a dozen others.) But what code has Bruce written? Google is unhelpful here, so let's look at his own web page.

If you hunt around a bit on perens.org, you can eventually find http://perens.org/works/software/ (which is link #25 of 36 in the nav bar, obviously a high priority). That page starts by noting that back in the 90's he posted map data to the internet (which isn't coding, wasn't data he collected or created, happened in the floppy drive era, and he's pointing at work somebody else did on their website and somehow taking credit for it).

Next up is "Electric Fence", which is actual code but which the man page at http://linux.die.net/man/3/efence says was from 1987, and that man page ends with a "What's Better" section pointing at two other projects from the mid-90's. Wikipedia currently lists 23 separate projects that do this sort of thing (http://en.wikipedia.org/wiki/Memory_debugger) none of which are gcc's current built-in stuff like libmudflap. The efence implementation is a simple wrapper around malloc and friends that allocates a guard page before and another after each allocation. (Um, I've done that myself, back under OS/2 in 1996. You need a library for it?) Its project page at http://perens.com/FreeSoftware/ElectricFence/ says "a new version will be up shortly", but archive.org's oldest version of that page (from 2004) has it saying the exact same thing and pointing at the exact same version.

The next entry is his claim to busybox. Whatever else you want to say about it, the last actual coding he did on it was over a decade ago.

Then he has a page noting that some media center remote should work out of the box but didn't for him, so he had to tweak a config entry. (This is on his "software" page?). Then some javascript to pan and zoom some camera from firefox, and finally "convert vim outliner to various slide show formats".

That's it. I've seen undergraduates with a better programming portfolio. Heck, when I was an undergraduate I could have pointed you at various bulletin board systems I wrote (my first big C program and my first big C++ program were both bulletin board systems, back before ISPs), the bake build tool for OS/2 (which amazingly is <a href=http://www.os2bbs.com/download/gnu.html>still online</a>), the little mcga game I wrote in 8086 assembly, and all sorts of other stuff I can't even remember today. But I'm not the one claiming to be some great community leader, I just some developer who happened to be doing stuff that Bruce flipped out over.

Bruce did not show up on the busybox list to discuss code. Bruce doesn't seem particularly interested in code. It looks like Bruce _can_ code (although he might be a bit out of practice), but it obviously isn't nearly the priority in his life he makes it out to be. He's an "open source developer" who doesn't seem to _develop_ anything, but loves to order around those who do.

And you say I'm showing him insufficient _respect_?

Rob

(By the way, it's not about age. At Ohio LinuxFest in October, the keynote speaker was Doug McIlroy, the guy who wrote "diff" and "sort" at bell labs back in the 70's and also came up with the original idea for the Unix "pipe". I have enormous respect for him, and his presentation was as current and relevant as anything said at that entire conference, even though he retired from Bell Labs years ago and is currently 77 years old.)

Bruce Perens: Statement on Busybox Lawsuits

Wol — Sat, 19 Dec 2009 22:52:02 +0000

That's a bit harsh ... okay I did muddle my terminology a bit.

But what I was trying to say was that the compilation copyright belongs to the project maintainers, and the licence they apply to that is constrained by the licences applying to the code they've compiled.

And in this case, seeing as the compilation is a mix of v2-only and v2+, the compilation licence has to be v2-only.

(imho, but that's only ho, they should have said "we've accidentally mixed some v2-only into a v2+ project, so all new code must be v2+ as per the original but the project is actually v2-only unless and until somebody bothers to do something about it.)

Cheers,
Wol

Bruce Perens: Statement on Busybox Lawsuits

anton — Sat, 19 Dec 2009 15:28:01 +0000

As I understand it, you as distributor can choose to distribute the software under a subset of the licenses that you received (at least with the GPL2+, GPL3+, and LGPL wordings). Of, course, if you distribute a verbatim copy (or your changes are not significant wrt copyright), then the recipient of your copy can get a copy from the original source to get the additional licenses. So the difference is only relevant in practice if the changes you made are significant.

The Big Questions

paulj — Sat, 19 Dec 2009 12:37:38 +0000

Re free software as a hobby:

Good point. No doubt many enjoy free software (or open-source ;) ) as a hobby. No doubt they would keep enjoying it.

However, hobbies are common-place in many fields, and don't tend to spring up ethical and economic frameworks around them. The idea that free software is a fundamentally better (ethically, economically, whatever) way to build software *generally* must surely therefore encompass more than just hobby programming. So it must surely encompass and *encourage* professional programming too. For if it did not then it would, as you allude to, be a hobbyists manifesto, which makes little sense.

The Big Questions

paulj — Sat, 19 Dec 2009 12:30:22 +0000

You seem to have mixed together 2 different comments in replying to me, e.g. I didn't write:

> meaning that Rob will not
> be named a plaintiff in any of the lawsuits and he will not be entitled
> to any potential recovery that comes from them.

That wasn't me.

Re dotcom boom, I didn't put a time-frame on "new". I was drawing parallels between the early 80s user-hacker ethic that started things off and todays situation. I.e. "new" in the sense that something changed. Perhaps I should have said "changed" instead of "new". :)

I don't have enough information to say whether your stance or the SFLCs is correct. I can though imagine a counter-argument to your stance:

a) Who cares if Cisco no longer use Linux? It's not like they were contributing much back (directly or via whichever embedded Linux developer they outsourced to, including putting pressure on them to release).

And the more persuasive counter:

b) If they can't be bothered complying with the GPL, why should they face no consequences? Imagine 2 companies:

- BigCorp
- GoodCorp

BigCorp uses Linux, cause it's cheap and saves them precious per-unit $$ in royalties. Their upper-management have no great appreciation for free software and/or open-source other than expediency. They will release only as little code and material as they have to. They have a relatively large in-house legal team who are certainly capable of figuring out what their responsibilities are in distributing such software.

GoodCorp is medium-sized. They also use Linux cause it's cheap. However, they still have founder-engineers in their upper-management, who still appreciate some of the ethical aspects of free software. The company doesn't have huge resources, but they are willing to put in a little engineering effort into longer-term issues, like going through the community processes to get code reviewed and integrated upstream, as they can see some longer-term value in doing so. They are meticulous about making sure they comply with the GPL, and they even GPL some (or, in the case of AngelCorp, all) of their device/function specific code.

Now, the argument is, if BigCorp fails to meet its obligations, again and again, and NO action is ever taken against it, you are effectively punishing GoodCorp. GoodCorp is spending resources on complying with the GPL and engaging with the community, which BigCorp is not. So GoodCorp is at a competitive disadvantage. The rational thing for GoodCorp to do is to emulate BigCorp and free up those resources and lower its costs. And eventually one of the more businessy types in GoodCorps' management will prevail in this argument over the founder-engineer.

It sounds, from what you say that, if the SFLCs' case is sound, that Cisco are a serial offender who intend to milk free software for as much as they can. They surely have the resources and expertise to ensure they discharge all their GPL responsibilities, yet they have (it is alleged) failed to do so, even several years after a previous dispute.

Why do you think the softly-softly approach is justified, given the adverse economic incentives it provides to companies like GoodCorp and AngelCorp?

Bruce Perens: Statement on Busybox Lawsuits

landley — Sat, 19 Dec 2009 09:36:00 +0000

> IMO, you have no standing to the change of licence on the project as a
> whole. That's a compilation copyright "owned" by the project maintainer

Wake me when you've learned the difference between a license and a copyright.

Rob

Bruce Perens: Statement on Busybox Lawsuits

Arker — Sat, 19 Dec 2009 08:33:57 +0000

1) The old releases still exist, from before we dropped the dual license. If he wants to cherry pick clean versions from source control that can still have the other license applied to them, from before GPLv2-only code got merged in, he's welcome to do so. (We told him this, but he remained in hysterical chicken-little mode.)

I am imagining (and Bruce will surely correct me) that his counteroffer was that if you wanted a GPLv2 clone of busybox you should write it yourself instead of relicensing an existing project. It seems very reasonable to me. Regardless of how long ago that project was forked and how little of his code remained after so many years, it was indisputedly his project begun with his code that all the other coders have hacked on over the years. Why not respect his license?

IIRC he fairly early on made the mistake of accepting submissions licensed GPL v2 only? If that is correct, it might limit his legal ability to enforce his license here, but so what? Arent hackers supposed to have ethical standards and respect for other peoples work?

The Big Questions

landley — Sat, 19 Dec 2009 08:22:52 +0000

> There's a new dynamic in play with Free Software.

New? (Where were you during the dot-com boom?)

> E.g. in this particular case both Bruce and Rob Landley have explicitly
> stated that they have revenue-generating relations with various
> organisations that are adversely affected by this law suit.

Actually, I made more off the SFLC's various lawsuits than I did off of Cisco. (Despite never asking the SFLC for a dime.) The SFLC guys actually raised the money angle when I was breaking up with them, ala:

> meaning that Rob will not
> be named a plaintiff in any of the lawsuits and he will not be entitled
> to any potential recovery that comes from them.

(Gee thanks, hadn't noticed those were connected. Good to have that cleared up.)

Sticking with the SFLC would probably have been in my financial best interest, but obviously that's not what I did. (Anybody who goes into open source for the money is missing the _point_.)

Also, I kept working with Cisco for months after the suit was filed. (They understood that a lawfirm I'd worked with was taking action on behalf of another client, _I_ wasn't the one suing them.) I just wasn't _accomplishing_ anything anymore from an open source perspective due to management going into some sort of panic lockdown when lawyers were invoked, and Linux in general being massively de-prioritized within the company to limit their legal exposure to who knows what future lawsuits.

The thing was, they'd already been sued over the original Linksys router by the busybox developers (Erik Andersen's father's a lawyer) back in 2002 or so. That was the legal action that had gotten them to release their Linksys source code in the first place, from which OpenWRT and friends emerged. (Yes, Linksys responded to that first lawsuit by ceasing all Linux development and doing vxworks-based routers instead, and it took them about five years to get over it. But in that case the code release was worth it, as evidenced by OpenWRT and similar projects it allowed to happen.)

In that original lawsuit, the busybox developers hadn't _asked_ for the source code to the toolchain (because they didn't _need_ it, it was bog standard mips or arm depending on variant), so Linksys hadn't tracked it down back then. Now a _second_ group came around five years later and started rehashing the same old issues they thought were settled, and Cisco's management started going "if we settle with them, who _else_ is going to come out of left field and sue us?" And thus they started "limiting the company's exposure to Linux"...

So ENTIRELY PREDICTABLY the lawsuit drives Cisco away from Linux for at least another five years (possibly longer, twice may be considered a pattern), but this time we don't get valuable code and new open source projects on the order of OpenWRT and the half-dozen other projects that spun off from it. No, we get _nothing_ other than the FSF going "I'm still relevant, I'm still relevant, look I can file a me-too lawsuit five years late that accomplishes nothing!"

> However, I have several devices (routers, laser printers, etc.) which
> contain sizeable amounts of free software, to an extent the product's
> functionality is dependent on it, yet I can not rebuild the software.
> Sure, I get the source to the Linux kernel and various generic
> utilities, but it's nearly missing the device and/or function specific
> stuff. Often there isn't even a working build system to create the
> firmware image format.

You know what I considered the single most important thing I was trying to accomplish while I was at Cisco? The thing the SFLC's actions _really_ screwed up? Hobbyist access to serial adapters for their routers:

http://landley.net/notes-2008.html#05-12-2008

Cisco's engineers have a little dongle circuit that gives a serial console on an unmodified router. The one I got for the WRT610n hooks under one of the ethernet ports (the ethernet cable holds it in place), where it connects to some extra pins and translates the result into a serial port. (It's not just wiring, there an actual chip in the thing converting the TTL signals into rs232, I took one apart to see why it wasn't working and it turns out to be a nontrivial piece of equipment.)

The problem is, they only ordered a small number of them as debug adapters for in-house use during development, and at such low volume each of the suckers cost more than the router it connects to.

I convinced the CTO I spoke to that something he could do to make the open source guys happy was sell those adapters to the community cheaply through a web page. That way hobbyists could get a serial console on their routers without needing to soldier their own chips to the board, which most hobbyists aren't up for. (He suggested giving some away at OLS, which was nice, but I wanted to make sure _everybody_ could order them. It's important to ask how people are supposed to develop an interest in fiddling with these devices in the first place: barrier to entry must be low for people who have not previously expressed interest. And you must be prepared for demand for development tools to scale up.)

Unfortunately, end-user access to the debug adapters went out the window when the SFLC sued 'em and everything went "under review". (Making the open source community happy ceased being a priority overnight.) And thus if you want to reflash your router today, you have a way harder time of it than necessary thanks to the SFLC and the FSF.

The _sad_ part is the community already had working toolchains built from source that targeted all these boards, and had for years, so the SFLC's suit served no possible pragmatic purpose. Just as none of the lawsuits I was involved with ever resulted in a single line of code merged into the busybox source control repository. It was all ivory tower idealism with a _negative_ pragmatic result.

> It's not bad that people make money from free software and indeed it's a
> *requirement*, if free software is to be sustainable.

Just like it's a requirement for all those bloggers to be paid to continue blogging. And all those deviantart accounts will close if people don't make money off of their drawings. Webcomic artists must get syndication deals for the artform to remain viable. People posting video to youtube are all in it for the money. Gold farmers are the only _true_ World of Warcraft players.

That would be a "no". Being able to make a living off of your hobby is a good thing, but it's not actually required for the continued existence of the hobby.

Some of us actually enjoy programming.

> Indeed, it seems that goal has mostly been abandoned by many free
> software hackers.

I'm an open source developer, not a free software developer. (GPLv2, not v3.) Perhaps this is why I continue to do it even when I'm not paid to.

Rob

Bruce Perens: Statement on Busybox Lawsuits

BrucePerens — Sat, 19 Dec 2009 01:15:37 +0000

Bruce: you were not involved with the project at that time.

This is correct. It's important to delegate.

The hall of shame languished for years without your interest.

Actually, I was OK with the shame-with-publicity strategy. Bringing suit did have a cost for us, as you are well aware given your collateral damage from the Cisco suit. The main reason that the Software Freedom Conservancy is interested in Busybox is that the Linux kernel copyright holders aren't making use of the Conservancy.

Shortly before your Triumphant Return To BusyBox, I spent a couple years focusing on defending the Linux community from SCO.

That you are lecturing me on this might indicate a bit of near-sightedness, also the fact that you had no idea of the involvement of the Linux Router Project in Busybox, or the fact that you didn't realize that GZIP does not contain the invention of argv zero switching. I understand that you have ESR as a neighbor, but it is a really big world out there whose contributions you don't seem to even have been aware of.

Your positions reminded me strongly and uncomfortably of SCO's

SCO really did believe that Linux was directly derivative of their work. They thought so because they had the evidence of BPF being duplicated in Linux, but they didn't realize that they hadn't written BPF because the information in Legal's file cabinet hadn't stayed with the software when the company was sold. IMO, once I published the analysis of their press slide-show demonstrating that they had not written BPF, their case was essentially over, the death throes just took a long time.

USG v. BSD is the other similar case. Today, USG would have won. Back then, the laws were different and their work was not copyrighted by default.

And that brings us to Busybox. Busybox really is derivative of my earlier work on Busybox. Every exact line that I have written could be removed and it would still be derivative. The reason this is different from SCO is that Linux really did not start with SGO's code base, Busybox really did start with mine. You might not like that, but it's the way it is.

which took all the fun out of my _volunteer_ work for the BusyBox project.

I just can't help but smile when I read this. Sorry, but if you're going to have a dispute with someone, it's fun to have that dispute with someone who is this visibly self-limiting.

I try to change things by _writing_code_, not by arguing about what _other_ people should be doing in a volunteer organization like you do, Bruce.

Writing code is very important. But not to the exclusion of the painful discussions around charting our course. One big problem with Free Software and Open Source is that too many of us are more comfortable in our cubes hacking than dealing with the big issues. We get taken advantage of because of it.

I never knew David Dawes, but my impression was that he wasn't a significant contributor to the X server development. Unlike David, I am not the one attempting to change the license - you were.

There was at the time a reasonably long list of people urging me to fork the project and pledging help - I don't even know why, and hope that Dennis has addressed whatever the problem was at the time. I had bigger fish to fry.

The "or later" clause

Wol — Sat, 19 Dec 2009 00:34:17 +0000

You *can* choose?

No! Before v3 came out it was "you MUST choose *version*2*".

YOU need a licence to distribute. The grant of licence allows YOU to choose which licence applies to YOU. It does NOT allow you to choose which licence applies downstream from you.

If your argument is valid, then the "or later" wording is worthless, because as soon as the first recipient distributes they have to choose which licence they are going to distribute under (this is just a practical/legal necessity), and if choosing a licence negates the choice for the next person in line, then the only people with the right to choose the "or later" licence will be those people who got it directly from the copyright holder.

So if you're right, pretty much all code initially distributed as "v2 or later" is in practice "v2 only" because it was distributed under v2 in the past and the recipients today can't choose v3 because the recipients "yesterday" didn't (couldn't) choose v3.

Cheers,
Wol

Bruce Perens: Statement on Busybox Lawsuits

docwhat — Fri, 18 Dec 2009 21:38:11 +0000

http://www.somethingpositive.net/sp03032009.jpg

Bruce Perens: Statement on Busybox Lawsuits

Wol — Fri, 18 Dec 2009 19:37:09 +0000

IMO, you have no standing to the change of licence on the project as a whole. That's a compilation copyright "owned" by the project maintainer and (within legal limits) they can do what they like. And if they decide to mix your 2+ code with 2-only code from someone else, then "legal limits" mean they HAVE to change the licence to "2 only".

As for tampering with the licence ON YOUR CODE - that is a NO NO NO.

Cheers,
Wol

Bruce Perens: Statement on Busybox Lawsuits

Wol — Fri, 18 Dec 2009 19:31:42 +0000

If it's derivative of yours, then you have copyrightable code ...

If EVERY LINE of what you wrote has gone, then whether the original was yours or not is irrelevant, there's nothing of yours left so you have no copyright.

Cheers,
Wol

Bruce Perens: Statement on Busybox Lawsuits

Wol — Fri, 18 Dec 2009 19:28:22 +0000

Yabbut ...

The GPL gives the user the right to choose which licence *he* wants to apply to *him*. That's fine. If I'm given some GPLv2+ code *I* can choose to use v2, or v3, or v4(when it exists) etc etc.

What that clause does NOT GIVE ME is the right to tell the next guy in line what licence HE can choose.

It CANNOT mean that. Because if I receive v2+ code, I *HAVE* to choose *ONE* licence to apply to me. If that then strips the next guy of the right to choose, what's the point of having the "+" option?

Cheers,
Wol

The Big Questions

paulj — Fri, 18 Dec 2009 14:15:00 +0000

There's a new dynamic in play with Free Software.

It may have arisen out of an end-user-hacker ethic, typified by RMS being unable to fix a bug in his printer. However, today, now that many corporates have adopted free software for their products, many free software hackers see the corporates as *customers* or *employers* (potential or actual). No longer is the end-user's freedom to hack the concern, but the self-interest of maintaining good relations with those who pay your wages. E.g. in this particular case both Bruce and Rob Landley have explicitly stated that they have revenue-generating relations with various organisations that are adversely affected by this law suit.

I'm not trying to make any great value judgements here. It's not bad that people make money from free software and indeed it's a *requirement*, if free software is to be sustainable. Bruce and Rob both argue, as you note, that these suits affect adoption - and that could result in fewer jobs in free software down the line, which would hurt free software.

However, I have several devices (routers, laser printers, etc.) which contain sizeable amounts of free software, to an extent the product's functionality is dependent on it, yet I can not rebuild the software. Sure, I get the source to the Linux kernel and various generic utilities, but it's nearly missing the device and/or function specific stuff. Often there isn't even a working build system to create the firmware image format.

So it seems to me that, though free software has made progress in terms of jobs for engineers and re-use of code, it has not made much progress on the original end-user-hacker-freedom goal. Indeed, it seems that goal has mostly been abandoned by many free software hackers. This is perhaps a shame.

The Big Questions

pboddie — Fri, 18 Dec 2009 13:38:51 +0000

The blog entry raises a few interesting questions:

If Cisco got their toolchain from Broadcom and got sued by the SFLC, what does that say about Cisco's understanding of the licensing? If some bloke gives you a CD with some executables on it, do you not have this nagging doubt about it being legitimate? Thus, is it completely beyond the legal department of a major corporation to figure out whether they can distribute something or not?
Why didn't Cisco turn round and sue Broadcom over the same licence violation? (Probably because it would interfere with a game of "spot the cartel", I imagine.)
Is some corporation putting the Linux badge on their product more important than the whole freedom aspect: the expectation that contributors to such projects often have that end-users will finish up with the same opportunities instead of staring at blinking LEDs and wondering why the product doesn't work any more?
How is suing someone over actual copyright infringement the "equivalent of patent trolling"?

The SFLC can't act on these matters without doing so in the interest of at least one copyright holder, and the only reasonable argument I can think of against such apparently uncoordinated actions is either the potential uncertainty of further lawsuits on behalf of other contributors, or such actions taking on a "class action" label without legitimately representing the interests of those other contributors. Regardless of all this, however, it should be possible to contribute code to a project with the expectation that people honour the licence, without other contributors waving away licence violations because they are personally OK with such stuff.

Maybe this does make the average Free Software project a bit like a hedgehog/porcupine for careless licence violators - after getting pricked once, there's no guarantee that they won't get pricked again until they either put the animal down or learn how to handle it properly, but that's not an argument against Free Software: it's an argument for respecting software licensing regardless of the nature of the licence. Failing to respect the licence of a different kind of project or a differently licensed project could be the equivalent of putting one's arm into a tiger's mouth and then complaining about what happened next.

Changing the notices (or adding new ones)

pboddie — Fri, 18 Dec 2009 12:46:58 +0000

Well, as the creator of the derived work, you could add a new notice saying that your code is GPLv2 only and thus recipients have to disregard the "or later" in all the other notices. I'd rather advocate that than start editing licensing notices.

In fact, according to the SFLC, when contributing GPL-licensed code to a BSD-licensed project, thus making the derived work GPL-licensed, the original notices should be left in place (which is actually stipulated in those notices). So, to do the same with GPL-licensed code is consistent with that. What people are missing is something in the GPL instructions which says that one can edit the licensing notices to make a licensing change easier to follow.

I've developed stuff under a copyleft licence that originally had a permissive licence, and as well as preserving the original notices intact, I also pointed out where the original work came from, and I've also preserved the licensing on individual files which I didn't change. I'm not likely to pin any flexible version GPL-licensed code to a particular version - I think those insisting on precise versions of the GPL are misguided - but I'd do the same with the licensing notices in such a situation. It's safer to keep everything as transparent as possible.

Bruce Perens: Statement on Busybox Lawsuits

landley — Fri, 18 Dec 2009 07:44:43 +0000

This whole SFLC thing was fallout from something I did while maintainer, securing proper legal representation to replace the old "hall of shame" which never worked. See the March 27, 2006 entry at
http://busybox.net/oldnews.html for details.

That's why I was still involved for a while after I stepped down as maintainer: because I'd set it up in the first place (and got Erik on board). The point was to clean up after the old "Hall of Shame", which as maintainer I felt it was my duty to handle, so I did. Three years later, I've moved on, and am not involved with the current round of lawsuits. (I think Denys Vlasenko probably should be, on general principles, or it's not really representing the busybox project. But that's just my opinion.)

Bruce: you were not involved with the project at that time. The hall of shame languished for years without your interest. (Similarly Denys Vlasenko hasn't been a party to any of these suits because he wasn't maintainer _yet_ when we contacted the SFLC.) You're _stunned_ that a project you hadn't interacted with for almost a full decade didn't bother to track you down.

You're also amazed that we didn't welcome you with open arms when your first posts to the busybox.net mailing list _ever_ were not about code, but about belated license trolling over an issue we'd already discussed for _months_ and come to a final conclusion on before you ever _noticed_.

Examples of the topic intermittently reared its head for a long time (there's more, and both of these are the start of long threads):

http://lists.busybox.net/pipermail/busybox/2006-April/054...
http://lists.busybox.net/pipermail/busybox/2006-July/0571...

The topic was explicitly raised for actual decision August 18th 2006:

http://lists.busybox.net/pipermail/busybox/2006-August/05...

I started looking at the status of some of the existing busybox code already marked GPLv2-only on September 8th:

http://lists.busybox.net/pipermail/busybox/2006-September...

And then your first post to the list ever, in the entire history of the list archive, was on September 13th, and was titled "Please tone down the GPLv3 paranoia":

http://lists.busybox.net/pipermail/busybox/2006-September...

Well hail the conquering hero. (Shortly thereafter, someone taught me the word "Schlamiel" when attempting to describe your behavior.)

> My objection was to 1) the license change for the overall project

GPLv2 was a valid license to distribute it under when it started, and GPLv2 is the valid license to distribute it under today. The old versions from back when you were relevant are still available in the archive. You're objecting that new work done by volunteers isn't what you would have done, and are attempting to steer the volunteers "from the grave", without actually participating.

You're also rehashing an argument you lost in 2006.

> 2) the license change regarding any stuff of mine which is still in
> there.

Nobody ever said you couldn't grab your bits and use them elsewhere, you just had to be sure they were _just_ your bits, and not tangled up with other people's bits under different licenses. Easiest way to do that was to grab old versions before other people's code got merged in. (When other people's code gets merged in, dual licenses often get dropped.)

BusyBox developers merged GPLv2-only code into the project years before we _acknowledged_ it. Thus the project as a whole could only be distributed under the terms of GPLv2. Some upstream sources may have had additional dual licenses, and some code we incorporated may even have come from public domain sources. But that doesn't mean you can distribute the releases of the modern BusyBox project under any license terms _other_ than GPLv2.

As a courtesy, I offered (back in 2006) to replace any code that had your copyright notice with a fresh implementation, even though legally we weren't required to do this. You got all offended and changed the subject.

> It seems I still have code in the latest version, and stuff derivative
> of my previous work. My objection still stands.

I covered that in 2006. I offered to volunteer my time to remove code you objected to, if you would just identify it, but you weren't interested. I also pointed out you could maintain your own fork, and you did the "well maybe I will, mister!" flounce but never followed through.

Actually, there was no "maybe" about it. You said, and I quote, you "feel that a fork is necessary and will put in the work to make one":

http://lists.busybox.net/pipermail/busybox/2006-September...

And then you didn't.

Meanwhile I did my own restart for _fun_ at http://landley.net/code/toybox and fed bits of that into busybox once I got over my visceral reaction to your SCO-like claims. (I need to push more code into busybox, but at this point it's structural and design changes which require convincing the busybox community that http://landley.net/code/toybox/code.html is a better design than having to touch five different files to add each new command.) But since it's a mature project where all new development is optional (modulo susv4 coming out), it's hard to prioritize proposing major design changes.

So I responded by writing code, you told other people what to do and then flounced off in a huff. Wake me when you do your promised fork. I should stop feeding the troll on this issue.

I think that's enough rehashing of ancient history, though. (Those laurels comfy? Seems like they started to smell a bit ten years ago.)

> My favorite part of the whole thing, though, is when you said you
> couldn't participate any longer because whenever you looked at my code
> you saw my face. IMO this qualified as divine punishment. And I don't
> even believe in the divine.

Punishment?

Um, dude, it really wasn't _about_ you. "You caused the problem" and "it's about you" are two different things, please get that through your head _one_ of these days. (If you knocked a bookcase over on somebody and they were bleeding, the focus of interest would be helping the person who was bleeding. There might be a secondary interest in making you go away or otherwise preventing you from causing more damage, but it wouldn't be _about_ you.)

I certainly wasn't intending to "punish" you, I was trying to get _away_ from you, because I got burned out on SCO and you started acting like SCO. You're confusing "this isn't fun anymore" with "that'll show Bruce!"

Shortly before your Triumphant Return To BusyBox, I spent a couple years focusing on defending the Linux community from SCO. (Lead author on http://www.catb.org/~esr/halloween/halloween9.html and co-author on http://catb.org/~esr/hackerlore/sco-vs-ibm.html were some of the more public parts, but I put a lot of other work into that topic way back when.) These guys were nasty and evil and the most frustrating part was that whenever you pinned them down they claimed that wasn't what they'd been arguing about and changed the subject. They had a theory of ownership I referred to as "sco disease", under which code that had touched code they had touched had their ownership transmitted to it by osmosis, so that their code could never be detected and removed.

Your positions reminded me strongly and uncomfortably of SCO's, which took all the fun out of my _volunteer_ work for the BusyBox project. I said so explicitly at the time:

http://lwn.net/Articles/202120/

But before I left, I found somebody else with energy and drive who would take good care of the project, and handed it off to a new maintainer. I felt I had an obligation to do this for the good of the project. You apparently never felt such obligation.

This wasn't about "showing bruce", and it wasn't "taking my ball and going home". I no longer had enthusiasm for the project, so it was in the best interests of the _project_ (not necessarily best for me personally) to make sure it was in good hands before going off to do other things.

(I note that Erik Andersen advised me to take a few months off and see if I felt better first, but I didn't want to stall BusyBox development even that long.)

BusyBox is Denys's baby now, and I respect that. Are there elements of his maintainership that I disagree with? Sure, he's not me and thus not doing everything I would do exactly the way I'd do it. (The code is turning into an #ifdef forest again, for example.) But I'm not going to tell him how to do his job, and if I really wanted to clean it up I would _contribute_. I could submit patches to the existing project like any other developer, I could maintain my own fork, or I could write a new version from scratch (ala toybox).

I try to change things by _writing_code_, not by arguing about what _other_ people should be doing in a volunteer organization like you do, Bruce.

By the way, these days, I no longer think of you as SCO. I think of you as David Dawes of xfree86.org: irrelevant through your own actions.

And that's about the duration of my interest in the topic.

Bruce Perens: Statement on Busybox Lawsuits

landley — Fri, 18 Dec 2009 05:19:05 +0000

> Is there not a conflict of interest if you are testifying as an expert
> witness in one case involving compilation copyright, when you are
> involved in a separate dispute that hinges on validity of such copyright?

I'm not involved in the current case. (I posted a link to my December 15 blog entry explaining why.) All the SFLC cases I was involved in were resolved a year or more ago.

Also, Bruce is not a party to any current busybox-related case I am aware of. (That's what he's upset about, the SFLC's total lack of interest in him. They seem to think he's irrelevant too.) I'm just saying that if he was, I would be opposed to his participation, to the extent of testifying against him if asked.

That's not news, either: http://lwn.net/Articles/202106/

Bruce Perens: Statement on Busybox Lawsuits

BrucePerens — Fri, 18 Dec 2009 01:55:57 +0000

It's all derivative of code that was under "any later version".

Bruce Perens: Statement on Busybox Lawsuits

BrucePerens — Fri, 18 Dec 2009 00:27:37 +0000

Is there not a conflict of interest if you are testifying as an expert witness in one case involving compilation copyright, when you are involved in a separate dispute that hinges on validity of such copyright? I.e. would you have the opportunity to influence case law in the one case favourably towards your interests in the other case in which you have a direct stake?

As it happens I probably won't have this particular conflict. But I would think it happens all of the time, in that a plaintiff can bring multiple cases regarding something of theirs which has been infringed, and can cite the previous cases in the pleadings of the later ones.

I think this is the way that the court intends it to work.

Thanks

Bruce

Bruce Perens: Statement on Busybox Lawsuits

paulj — Fri, 18 Dec 2009 00:23:41 +0000

This is not meant in a disrespectful manner, but I have to ask:

Is there not a conflict of interest if you are testifying as an expert witness in one case involving compilation copyright, when you are involved in a separate dispute that hinges on validity of such copyright? I.e. would you have the opportunity to influence case law in the one case favourably towards your interests in the other case in which you have a direct stake?

I do not mean to impugn your reputation with this question. Rather, this question arises from what you've written, in the mind of at least one LWN reader, and I just wanted to highlight that for you so that you could clarify it (this theoretical conflict of interest may matter not a jot to a court with an adversial system - I guess, but I don't know).

--paulj

Bruce Perens: Statement on Busybox Lawsuits

BrucePerens — Thu, 17 Dec 2009 22:52:34 +0000

My objection was to 1) the license change for the overall project and 2) the license change regarding any stuff of mine which is still in there. It seems I still have code in the latest version, and stuff derivative of my previous work. My objection still stands.

My favorite part of the whole thing, though, is when you said you couldn't participate any longer because whenever you looked at my code you saw my face. IMO this qualified as divine punishment. And I don't even believe in the divine.

Bruce Perens: Statement on Busybox Lawsuits

landley — Thu, 17 Dec 2009 22:30:41 +0000

The SFLC's work isn't helping the BusyBox community at all as far as I can tell. And it's certainly not helping the BusyBox project, current maintainer Denys Vlasenko isn't a party either, and I'm unaware of a single line of usable code BusyBox was able to merge as a result out of any of the SFLC's previous actions. The SFLC is doing this for their own reasons, I'd say BusyBox is just an excuse.

I declined to be involved in this round of lawsuits, and thus can't see the new terms either. I blogged about all this before I ever saw your screed (which I still can't bring myself to read). Said blog entry is at:

http://landley.net/notes-2009.html#15-12-2009

I'm aware you believe you deserve special privilege here. More so than the project's current maintainer, apparently. The thing is, I don't care, and I don't HAVE to care. And I'm glad I don't. Go be "special" somewhere else, please.

I'm going to go do something productive now. Bye.

Bruce Perens: Statement on Busybox Lawsuits

BrucePerens — Thu, 17 Dec 2009 22:26:08 +0000

(Remember, Bruce never addressed the embedded space at all. That was Erik Anderson launching a _new_ BusyBox project.)

This is totally ignoring the role of Dave Cinege in the Linux Router project. He maintained Busybox for two years in that context.

Also, the one-floppy Debian installer had all of the qualifications of an embedded system - very limited resources, etc., - with one difference which was that it was ephemeral. Which as far as I can tell doesn't disqualify it.

For that project, I also made a program to cut down shared libraries to only the functions that were actually called for in a given set of executables. This allowed us to have an embedded-sized C library without new development.