Making The GPL Easier For Companies To Swallow

stupidNewbie writes "There is a new GPL "wrapper" gaining momentum on Capitol Hill. Dubbed O-STEP, the Open Source Threshold Escrow Program allows vendors to license their products until so many millions are made, then agree to release the code under GPL. This sounds like a good bridge for companies looking to tap into the strengths of open source distribution." Starting from zero, it can certainly gain momentum quickly -- sounds like a good idea though.

Comments

Great Idea!

[TerryAtWork]

I can think of a few legacy projects I'd like to see released like that - Clipper for one.

misses the point

[LMCBoy]

One of the big strengths of Free Software is that you can leverage the community for rapid development and bugfixing. If you've already developed the code under a closed-source, proprietary model, and it's been released long enough to sell 10^6 units, then much of the development is (presumably) already done. Plus, if development was open from day 1, the final codebase would tend to be less messy and obfuscated, IMHO.

Not that I don't welcome such a "late release" model for proprietary code, just thinking out loud...

They'll never reach the threshold.

[jridley]

I have a friend who used to (years ago) be an accountant in the record industry. Their books were set up to NEVER show a profit. It wasn't illegal, and if you didn't know about it and agreed to a percentage of profit, you were just screwed.

Unless they're very careful with wording on this, companies will just set things up so that the threshold is never reached.

If they ARE careful enough that no legal loophole is available, I suspect that companies will consider this a time bomb and avoid it anyway.

Good idea, but needs some work

[RodgerDodger]

The first point, of course, is some agreed means of tracing the sales or revenue. After all, if a company sets the mark fairly low, and then finds out they've got a killer product, they would have to be tempted to fudge the figures to keep the revenue coming in.

The second is that you'd probably want a nominated "end-of-life" date. At that point, the source should be released anyway, regardless of how much money has been raised. 5 years after release would be a suitable point, probably.

You could probably combine them, so that you can have a reducing threshold of revenue vs time.

What I would really like to see, however, is a legal requirement that companies either support software they've sold basically forever (either through patches or free upgrades to more recent releases), or release the source so that somebody else can do the support. There's a lot of machines still running Win95 out there that have major bugs, but MS will never lift a finger to help those people out. I have no problem with companies wanting to sell software, but if there's a bug that causes things to break in a product I've paid cash for, then I want it fixed, dammit!