There are checks and balances in our system of government. There are checks and balances in open source governance as well.
The latter checks aren't spelled out explicitly as in the Constitution. But it's very clear from recent events that governance is not a one-way street, and there are levers that can be pulled by the community, against a project's reputation, which will force a rational project manager to moderate their demands or lose everything.
These checks include the fork, the boycott and the strike. The threat to do any of these things against a project are powerful incentives for management to come to the table.
All three weapons were used against Oracle's management of Openoffice.org, and Oracle now seems to have thrown in its hand . That's the Oracle way. Rather than play out a losing hand they make a decision to toss it aside and move on.
Despite its efforts to isolate the community in Libre Office, to force that fork, and to stand alongside IBM with a fully corporate strategy, Oracle finally saw that its reputation was suffering from the dispute, and the marketplace implications of this forced it to act.
The hope had been to do with Openoffice.org what IBM has been doing for years with Symphony, to offer the code for a free download while restricting support to paying customers. It didn't work, in part because Oracle wasn't set up to do things that way, but also because Openoffice.org wasn't set up to have things that way, in the way that Symphony is.
Symphony's modest success as IBM's commercial open source office suite took years of quiet hard work to achieve. Oracle's attempt to match it was being done in full view of the public. Symphony users know the deal, and prefer it to the alternative. Oracle was trying to re-make the deal, reneging on the software's past commitments.
Open is not something you can really take back.
Recent Comments