Slashdot Mirror
The Credibility Issues of MS's CodePlex Foundation
alphadogg writes 'Microsoft's new CodePlex Foundation has serious flaws to correct if it wants to become a credible force in the open source industry, and attract a diverse collection of developers and participants, according to an expert in forming consortia and foundations. Andy Updegrove, a lawyer and founder of ConsortiumInfo.org, says Microsoft has created with CodePlex a rigid foundation that has almost no wiggle room and a poorly crafted governance structure that concentrates authority at the top and leaves little power to others who might join the foundation.' Here is Andy's detailed analysis of CodePlex's structure: "Over the past 22 years, I've helped structure scores of open, consensus based consortia and foundations, and represented over 100 in all... In this blog entry, I'll show where I think the legal and governance structure of CodePlex has wandered off the open path, and offer specific recommendations for how the structure could be changed to give people (other than Microsoft business partners) confidence that CodePlex will be an organization worth joining."
Needs more lawyer.
Be you Admins? nay, we are but lusers!
Because I'm sure my Linux on [insert device here] port will look just fine on CodePlex.
But it almost perfectly captures Microsoft's view on the software market.
extern warranty;
main()
{
(void)warranty;
}
This looks like a poor attempt at Google Code, but with a lot more politics, beaurocracy and legal problems involved.
Doesn't look like it captures the OSS development spirit, to me...
That's probably because it isn't supposed to. It's supposed to allow Microsoft and any other companies who sign on to support it the ability to say "We like open source. We're spending eleventy-billion dollars on supporting an independent open source foundation." By calling it "open source" even if it's not, it succeeds at its PR purpose.
Remember the Halloween Documents? I don't think we have any reason to think that Microsoft has suddenly decided that they should become the next Red Hat.
I am officially gone from
Not only that, but why put what appears to be a boardroom discussion on your blog unless Microsoft's made it clear they won't play ball. Sounds like "It's a Trap!" which now has a big glowing neon sign over the top of it.
http://www.beanleafpress.com
Why, the article might lead one to think that Codeplex was set up as an entirely self-serving initiative under Microsoft's firm control! Who could imagine such a thing?!
From FTA:
Q: Is that good or bad?
A: In my view, itâ(TM)s bad, because it means that the Board of Directors not only has complete control, but the Board is also self-perpetuating (i.e., the directors elect their own successors). Moreover, there are no term limits on how long a Board member can serve. In this kind of organization, the Board is not answerable to the participants, and the participants have no say or control at all over how the organization is managed or evolves.
The author of the article points out that Microsoft has created a self-controlling organization without industry partners and given it complete control of itself. The implication is that CodePlex will fail because participants will be backed into a corner if they want to do anything that the Board of Directors opposes. It seems like the term "Microsoft Open Source" is still an oxymoron.
"...a poorly crafted governance structure that concentrates authority at the top and leaves little power to others who might join the foundation." Doesn't look like it captures the OSS development spirit, to me...
The article is well-thought and well written. Though Andy uses longer, politer phrases to beat around the bush, M$ Code Pox, is a scam and misrepresentation. Even though we're not surprised by that behavior from M$ and its minions, we shouldn't put up with it. After all, ten years ago tech people laughed at M$, M$ products, M$ users and M$ boosters. however, they did nothing to stop the spread and now look at the big cleanup job before us.
There are just too many barriers to it ever becoming credible. Look at any of the required changes Andy mentions. This one in particular stands out:
No way that one can be overcome. M$ has long been using it's tactic of panel stacking to carry out its jihad. M$ representatives include those by proxy, such as those from sock-puppets and political action groups like Black Dork Software, Novell and others.
Then you have all the activists M$ has placed inside other companies. Juniper Networks, NComputing, Yahoo (especially via the board), Xensource are now saddled with M$ moles. That is just a sample, and each of those companies turned and started to toe the M$ party line after taking on one or more moles.
Now, you may ask, how is all this getting financed and who is underwriting it? The answer: each and every bastard who in any way is helping build or maintain M$ marketshare, that's who.
Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
It should just give the Mono group carte blanche to reimplement all of their .NET APIs under any OSS license. A full, iron clad legal agreement with them would do more than enough.
You know, I really wonder why MS even bothers getting into open source.
If Microsoft tries to get into open source, it's seen as a move to stranglehold OSS Development and software.
If Microsoft closes the door and goes completely proprietary, it's seen as a move to stranglehold OSS Development and software.
Ballmer should say screw it and just go back to the 90's and steamroll all over the competition. If the government gets involved, split all the divisions into separate companies, get them all to join some consortium group, and keep on steamrolling away.
At least the M$ moniker would have meaning again.
In Soviet Russia, Trojan exploits YOU!
First, keep in mind, the provisional board of the CodePlex Foundation is only half Microsoft, and they have a mandate to setup a new board within a certain time frame. Second, they've also said the default license will actually be the Modified BSD license, so none of that untrusted MS-PL stuff going on. Thirdly, I've caught word from the inside that one of the effects this could have will be Microsoft employees being allowed to use open-source software internally, along with the ability to contribute to said projects under this CodePlex Foundation. With current issues like Microsoft programmers not being allowed to use superior open-source tools over inferior Microsoft ones (for example, Entity Framework versus NHibernate) - this will definitely result in Microsoft's own position changing for the better.
The whole reason d'atre of The CodePlex Foundation is that it isn't the Free Software Foundation or the Open Inventions Network. Microsoft could have just have easily one of these or similar organizations. But then again they wouldn't be so easy to control - which is the whole point of the exercise. Pollute, extend and embrace Microsoft control of 'open source', and by extension Open Standards. And here's what one of the current members of the board of TCF has to say about his time at the FSF.
..
.. "There's an old game in politics. If some group is giving you trouble, launch a competing group under your control"
... :)
"I hope that I can last more on this foundation than I lasted at the FSF, where I was removed by RMS after refusing to be an active part of the campaign to rename Linux as GNU/Linux", Miguel de Icaza
Lets see who else is on the 'open source' CodePlex board: Sam Ramji (Microsoft), Bill Staples (Microsoft), Stephanie Davies Boesch (Microsoft), Miguel de Icaza (Novell), D. Britton Johnston (Microsoft), Shaun Bruce Walker (DotNetNuke)
This blog sure has it figured out already
So there you have it, what could be more 'open' than that
The "crime", if you want to call it that, is that after years of scuzzball tactics, FUD, lawsuits, smears, and namecalling ("linux is a cancer" ... remember that?), a true blue, died-in-the-wool authoritarian software vendor is posing as a "look-at-me-I'm-hip-now" open source software vendor, likely while trying to find yet another way to screw the real open source community. Judging by the way they structured their "open source" (to use the term veeeerrryy loosely) initiative, they seem to think that open source means "will do what we tell them for free", proving that they still don't get it.
RICO should cover most of M$ business models, past and present.
While you're at it, add up the total damage from the Windows malware per quarter. It's got the late Osama Bin Laden beat, hands down. There may well be a business case for air strikes against Redmond. Obviously that would be preceded by naval bombardment and followed by after-action mop up by ground units.
Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
It's crafted exactly like Microsoft wants it to look and behave.
GNU is just a toolchain. An IMPORTANT toolchain, but a tollchain nonetheless. You don't name your OS or your system distribution after the toolchain, no matter how badly RMS tries to rationalize it.
The operating system layer itself is Linux. Period. Unless there's actual GNU modules or drivers alongside the Linux kernel in kernel-space I don't know about.
And the name of the system distribution is whatever the fuck the maker wants to call it: Ubuntu, RHEL, SuSE, since it's THEIR creation by way of assembling the parts themselves into a distribution.
Stallman wants us to think that by having the GNU toolchain the entire system magically becomes GNU.
It's Linux. It is not GNU/Linux.
I am beginning to think that maybe Darl McBride was attacked viciously by a penguin as a child.
A little hint: Don't complain about use M$ in our posts or no one will take you seriously, especially when you fail to make a good point.
Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.