Busybox is the exception. The SFC actively enforces the license for busybox. In addition, once you lose your right to use busybox as a consequence of a license violation, the SFL will let you ship it again only if you come into compliance on for all of the GPL code you ship.
So they are making their own busybox as a way to continue to violate all the non-busybox GPL code they use.
If you comply with the busybox licence, you can continue to violate the licence on all the other GPL code. But violating busybox means you have to comply with all of your GPL code.
You never have to release your non GPL code.
The fact that a Sony guy wants to build a non-GPL Busybox is not evidence of any Sony violations of the GPL, now or earlier. There is some radical jumping to conclusions here.
I'm suggesting that some companies would not want to let you analyze their trade secret modules on principle even when they aren't GPL-derived. I'd say that concern is unreasonable, but that doesn't mean some companies don't have it.
Let me put this another way: Do you think the developers behind editline wrote it because they wanted to violate the GPL? Or did they write it for some other reason?
Personally, I read the Sony post very differently. It sounds to me Sony, in part because of the aggressive stance SFC takes with busybox GPL violations, isn't happy with the business costs of using busybox (e.g. concerns among chip vendors and suppliers). They could easily be wrong in their assessment of the business costs (e.g. concerns from chip vendors and suppliers should not be taken seriously), but given that assessment, it seems to me that writing a busybox replacement is a reasonable response.
I would hardly call enforcing their license an "aggressive stance". When a company enforces their right against those that violate the terms of their proprietary license it's considered "normal" but if a Free Software developer does the same thing it's considered being "aggressive"?
Sony never originally intended to comply with the requirements of the GPL. They did violate the terms of the GPL. That isn't speculation. The reason they ever complied is because they were forced to.
For those saying that there isn't a problem as long as the original authors are not willing to go to court over the violation. Think about what you are saying for a minute. You are basically saying "it's OK to pirate someones work as long as they don't enforce their license on me personally". Yes it's "piracy" as the same companies have defined it -copyright infringement-.
Let me try an analogy: Suppose that, as part of a BSA settlement, they didn't just require you to come to terms with any BSA members whose licenses you were violating, but also with any non-BSA members whose licenses they judged you were violating. Having never had dealings with the BSA they may well do this (in the interests of drumming up new members or something). Nevertheless, I would characterize that in exactly the same way: not wrong, or even unreasonable, just aggressive.
They're not asking for this because they dislike Busybox'es GPL license. They're asking for it because they know Busybox actually goes to court to enforce it, and asks for the other GPL products to have their license respected too.
I'll spell it out more clearer: they want to get rid of Busybox, because its one of the only things whose license they cannot violate with impunity.
On one hand, if the license holders of the other infringing software don't care to enforce the license, why should anybody care? It makes no sense to me, but it's up to them.
On the other hand, if Sony would rather write it themselves than abide by the GPL then I'm not seeing the problem there, either. Again, it makes no sense, but it's their decision.
Believe it or not, most free software developers aren't dying to spend their time and money to start a copyright lawsuit against Sony. That doesn't mean they're actually OK with their copyright and licenses being violated. Public shaming is often much more cost-effective. But if there's one company that doesn't give a rats ass, it's Sony.
Most free software developers also don't register their copyright (unlike Sony) and so aren't entitled to those fantastically high statutory damages. They have to prove actual damages. For free software.
Good luck.
Basically, Sony is admitting that they are doing this so that they can avoid complying with the GPL, meaning that it is their intent to violate copyright law, knowing that they probably won't get sued over it. Isn't this a criminal act on the part of Sony?
I realize that it isn't as cut and dry, but I do see some strong parallels.
Further, why are these companies so stupid as to not release the source for their BusyBox implementation without being sued? It seems like it would be much, much simpler than trying to hold onto it and then be forced into a situation of releasing the source for everything that's covered.
Sony aside, I wondr if it is legally feasible for there to beaclass action suit against a large serial gpl violator, the class being developers only related by the license they chose to use.... copyright violation is illegal, after all, right?
On the other hand, more software that is not infected with a proprietary or copyleft license is always good.
Nobody has a problem with Sony writing their own version of BusyBox - good for them if they can do it. But, if the reason they are writing their own version, is so they can, without worry, violate _everyone else's_ copyright - then that's somewhat shady behavior.
Ironically - from a "Game Theoretic" position, Sony's approach is entirely rational. Take out the opponent who can stand up against you, and crush those who can't.
So - I'm simultaneously impressed by their strategy while offended by their attitude.
Why is this a bad thing, other than that it weakens the importance of the GPL?
They want to switch to a mostly-GPL stack, except for the one component that causes them to have to live up to their GPL obligations.
If its your work and you hold the copyright, how you license, distribute, and enforce it are all up to you.
> If its your work and you hold the copyright, how you license, distribute, and enforce it are all up to you.
Your ability to do this also depends on the legal system, which makes it hard for the little guy with respect to a big corporation. This is why we have mechanisms like SFC.
If they're placing too high a monetary value on non-compliance with the license, then you could easily see why these companies would push back and seek these types of alternatives; or flat out deny the use of (L)GPL software in their products entirely. In the end, this is probably the opposite of what the SFC intended and may result in the loss of their greatest legal tool.
The companies who habitually violate the GPL contribute approximately nothing back to the wider ecosystem. The best you can say is that they gain brand awareness for Linux, but that's it. People release code under copyleft licenses because they want people to provide source to their downstream recipients. If they were more interested in brand awareness than source, they'd have used a liberal BSD-style license instead. Having vendors refuse to use GPLed code because they don't want to ship source is arguably a perfectly reasonable outcome.
It's sad, really. I can see a future where a terminal program or command is embedded in the linux kernel and cannot be removed, only to force companies to stay honest.
And the point is that the people who wrote Busybox don't want money if you're infringing their copyright - they just want to see exactly what you've done with their code, and get the chance to play with it. Which is pretty reasonable when you think about it.
https://products.sel.sony.com/opensource/
you'll see other products such as webkit with updates in 2011
Note that busybox is only used to obtain the source code of parts of the product for which source code is already required to be provided by the GPL or similar licenses. It's not used to get code which isn't covered by the GPL (although it could in principle be, or at least force the company in violation to choose between that and coming into compliance by removing all use of busybox)
This is based on one interpretation of the GPL: That if you violate the license, you lose the license to that software forever, including new versions of it, until you get explicit permission from the author. The SFC then made a condition of granting permission to BusyBox, that the violator come into compliance regarding all other GPLed projects.
But that interpretation is not a legal fact. Another interpretation - which seems much more reasonable to me, and was certainly the intention I had when I released GPL code myself - is that you lose the license when you violate it. But as the GPL states, you get a license when you download a new version of the software anyhow, so the problem goes away - unless you violate the GPL again. In other words, if you violate the GPL, you have no license to the code, but once you comply with it, you are fine.
The former interpretation always struck me as bizarre: If you lost the license when you violated the GPL, surely you lost that license to that particular software. But how can that prevent you from getting a new license to a new version of the software? How are those connected? Or how about a new version of the software that was rewritten from scratch, and has no code shared with the one you were temporarily in violation from? Is the mere name enough? How about forks of the project? If any of this were what the GPL originally intended, you would think it would have been specified in some way. The much more reasonable interpretation is the second one: You lose the license to the concrete software you were given a license to before. Download a new version, get a new license. Stop violating the license, and you are ok.
The FSF has stated that the additional wording in the GPL3 was to avoid confusion from other possible interpretations in the past. So I don't think the GPL3 wording proves either previous interpretation is right - it has been used to argue that either of the two is, actually - all it shows is that there was some lack of clarity.
They're connected because some of the originally licensed copyrighted material still exists in the new version. You would get a clear license to any new material that you hadn't previously licensed (and hence hadn't violated the license of), but that's not very helpful.
Or how about a new version of the software that was rewritten from scratch, and has no code shared with the one you were temporarily in violation from?
If it doesn't contain any material that you'd previously violated the license of, then you would seem to be in the clear.
They are connected in the way that the same people whose license you violated are the ones granting you the new license. And I'd say they have reasonable doubt as to whether you will comply with the new license, since you didn't before. They don't have to grant you a license to use it, you know. Using someone else's IP is a privilege, not a right.
I don't see where it says that the license being given is not to people that violated the license on previous software being released. Again, if you argue that, then you get into the problems with "is this the same as the software from before" that I mentioned.
Sony wants to write a BusyBox that doesn't use BusyBox's license? What exactly is the problem? If they don't like the license isn't that the best approach they can take?
"A couple of weeks ago, this page appeared on the elinux.org wiki. It's written by an engineer at Sony, and it's calling for contributions to rewriting Busybox. This would be entirely reasonable if it were for technical reasons, but it's not - it's explicitly stated that companies are afraid that Busybox copyright holders may force them to comply with the licenses of software they ship. If you ship this Busybox replacement instead of the original Busybox you'll be safe from the SFC. You'll be able to violate licenses with impunity."
Wait, didn't GNU and the GPL start off for the completely non-technical reason that Stallman didn't like the original license?
I'm also not sure I like the idea of using BusyBox as a backdoor to examine the rest of a product's source code. I didn't realize that was a condition of the GPL, but it makes me glad I've switched most of my projects over to the BSD and ISC licenses.