Fork ahead...?

Posted Jul 10, 2007 15:19 UTC (Tue) by sepreece (subscriber, #19270) [Link]

I agree that there are few examples of projects that have forked and succeeded. However, subcommunities do exist and there is nothing inherently wrong with a group of developers (or companies) deciding to form a new community with slightly-but-significantly different principles. The viability of that community would depend on whether enough people were interested and whether they were the right people.

The current situation is interesting from that perspective. It's quite possible to be willing to share openly within an open community, but NOT to feel the need for the GPLv3's additional restrictions. I think there is the potential for certain key projects to end up with two lively communities around them, based on different licenses. Or, it could be that communities with enough internal disagreement about licensing will simply elect to remain "GPLv2 or any later" and avoid the fight.

We'll see...

Posted Jul 12, 2007 14:54 UTC (Thu) by emk (subscriber, #1128) [Link]

Well, the scenario you describe would almost certainly run afoul of the GPLv2, because your patent would restrict the rights of downstream users of the software. There has been quite a bit of discussion on this topic, and there's also explicit patent-related language in GPLv2 that covers other cases. Really, the only change in GPLv3 is that a couple of tricky loopholes dreamt up by Microsoft have been fixed, and that everything is much more explicit.

Posted Jul 12, 2007 14:55 UTC (Thu) by drag (subscriber, #31333) [Link]

You snipped some pretty important things out of your quotes there.

When you cliped "non-exclusive, worldwide, royalty-free patent license" you realy ment "Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.", right?

Because there is a huge difference.

Anyways your mythical hardware patent has nothing to do with the software. Hardware is hardware and software is software; seperate things. Your granting license to use that software, not to anything else. The hardware your providing is unaffected by the software license, so your patent is safe.

That's also assuming that the Chinese give a crap about patents, which they don't.

What they will do is take your patented ideas, violate your patents. They will sell the hardware in countries that do not honor U.S. patents, and thus are completely isolated from any U.S. patent law. Because of the lack of need to pay for patents and such they will undercut competing hardware coming out of the USA.

Then they will use the profits from these sales to then turn around and hire lawyers in the U.S. to setup a legal entities (aka patent trolls) to buy new patents from the government, which you would have to pay for, since your based out of the U.S.

This, combined with the legal overhead you have to deal with on a day to day basis related to all this crap, will have considurably higher expenses then your chinese friends, who are happily putting you out of business.

Good luck trying to get the government to risk billions in dollars worth of agricultural exports with China, and the livelihoods of hundreds of thousands of (very politically active) midwest farmers, as well as other billions of dollars in trade in order to get in a trade dispute with China to help defend your little NAS business from that evil (mostly state-owned, mind you) chinese corporation (who probably already makes the majority of the parts you use in your product anyways).