CherryOS and OSS

cherry osJust about everyone saw that CherryOS went "open source" the other day, but I didn't write about it because I was waiting for the other shoe to drop, I'm working on something larger, and I was dealing with the ponce Brad Gibson over at MacObserver yet again.

Eweek and EPN caught the other shoe, where they basically say to ignore the GNU logo, they'll be releasing CherryOS under an open source license they've created themselves and charging $14.95. Oh, and all the evidence is a pack of lies.

This story is such a non-starter that I'm really kind of bored by this aspect of it. It should be obvious we're in for another round of rhyming history.

Here's how it will go:

  1. Eventually, CherryOS vOSS will be released... the source will probably be delayed, but it'll be coming eventually.

  2. Since they're claiming they weren't stealing code, people will be all over it. The source will be a gnarled, tangled mess of stripped out copyrights and obfuscation.

  3. It'll be obvious they're infringing in multiple ways to anyone with the critical thinking skills above the level of a toaster (or MacObserver).

  4. The discussion is going to degenerate in a big way over the open source aspect of things, and everyone will be more confused regarding the GPL and other OSS licenses than they were before.

  5. Brad Gibson, through MacObserver, will continue to be a hack (Let me put it this way; this is a tech 'journalist' who doesn't realize WHOIS data can be false)

If you can't tell, they're becoming really annoying to write about, and really getting up my craw the more I do have to write about them, partly because their immediately bizarre behavior is interrupting my writing about their long-term and continuously bizarre behavior, let alone other things.

Apple should be watching this closely; I'm close to hating hearing about anything that has a fruit in it's name, and I doubt I'm the only one.

One thing I did latch onto over the last few days was the idea of CherryOS opening up their source code at all. There's an idea floating about -- that even I had in my head -- that if someone like Maui-X takes, and then violently violates, GPL code, that they've given up their right to the license and opening it up is now not an option.

Specifically, the GPL says:

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

It's a bit of a moot point when it comes to CherryOS because if they do have GPL'd code in their product, just throwing it under another license -- especially one that is more limited than the licenses of the code they're using -- is horrifyingly infringing.

However, it's not as though we won't run into this situation again, so I picked up the red phone and asked a lawyer.

When asked whether someone who was found to be infringing the GPL would then be prevented from further using the code, even to include it in an OSS product, Kurt Opsahl of the Electronic Frontier Foundation had this to say:

In a typical license agreement, after termination, one has to negotiate again for the license - for example, if I got a license from you to republish your photo, and you terminated the license because I didn't pay the license fee, we would have to reach another license for the photo before I could publish it.

However, the fact that the earlier license terminated would not prevent us from reaching a new license agreement.

Here, however, the GPL license is not individually negotiated. Rather "Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions."

So the question would be, whether this provides a license to replace the earlier terminated license.

Basically, it's not a cut-and-dried situation in the hypothetical sense, but in CherryOS's case it probably will be.

yummy alcohol posted button Posted by drunkenbatman
    April 08, 2005, at 01:36 AM


Comments (18)




Post a comment



Anonymous comments are allowed, but please enter something for a name.

And do endeavor to appear sane.









Remember personal info?