• On The Insider: Britney's Bikini-Clad Top 10
June 5, 2008 3:00 PM PDT

Microsoft's non-open source attempt at open source

by Matt Asay
  • Font size
  • Print
  • 2 comments

Microsoft has evolved in its stance toward open source, but its current hiccup with the Sandcastle project calls into question just how well it understands the obligations open source imposes. Microsoft created its CodePlex site to host open-source software, and has been careful to abide by open-source rules, submitting its licenses to the Open Source Initiative for approval.

Yet as Sandcastle demonstrates, Microsoft still has a long ways to go before it demonstrates that it understands and is willing to stand behind the obligations of open source. The Sandcastle project went live on January 8. Several months later, it still isn't providing source code, a key tenet of the CodePlex hosting requirements.

This isn't a matter of holding Microsoft to a third-party standard. It's a matter of holding Microsoft to its own standards. Microsoft declares CodePlex to be an open-source project hosting site:

(Credit: Microsoft)

The CodePlex terms of use require the following conditions for CodePlex-hosted projects:

  1. You must choose a license for your project (license resources: Open Source License page on Wikipedia)
  2. It must be an ongoing project (no "abandoned" projects)
  3. It must have source code (no non-software projects)

In the case of Sandcastle, it fails items one and three. No source, at least as of 2:54 PM PDT today, and therefore not open.

Does Microsoft care? Well, the CodePlex front page declares:

Microsoft does not control, review, revise, endorse or distribute the third party projects on [CodePlex]. Microsoft is hosting the CodePlex site solely as a web storage site as a service to the developer community.

Fine. But why then stipulate requirements for the site that are apparently meaningless? And why pretend that it's an open-source code repository if, in fact, it may not be?

Microsoft built CodePlex. It can do with it what it wants. But what it can't do is borrow the term "open source" for marketing purposes and then fail to live up to the Open Source Definition. I thought the company understood that. Sandcastle makes me wonder....

So, Microsoft, your options are clear: 1) Request the site owner to provide source code or 2) Properly label CodePlex as a code repository, but not necessarily as an open-source code repository.

Matt Asay brings a decade of in-the-trenches open-source business and legal experience to The Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure. You can follow Matt on Twitter @mjasay.
Recent posts from The Open Road
Why is Google Android beating Symbian?
The convenient fiction that Microsoft is evil
Apache: 'No jerks allowed'
Cloud to suck money out of market, report says
When open source isn't (open enough)
SAP wants an open Java process (pot, meet kettle)
Google shifts software value to operations, away from IP
Mobile: Still waiting to see what sticks
Add a Comment (Log in or register)
by jmcannon June 6, 2008 9:19 AM PDT
Matt, your concerns are valid. I looked into this and we're working with the project owner to understand their plans for source code publishing. If it's not fully OSD compliant, it'll be removed from Codeplex and moved to a more appropriate home.

-Jamie (jcannon@microsoft.com)
Reply to this comment
by PJonDevelopment June 7, 2008 1:43 PM PDT
It's really sad to know that SandCastle was removed from CodePlex.

I've contacted Eric Woodruf and he was kind enough to send me the May 2008 release of SandCastle.

If anyone needs it I've mirrored it here: http://pjondevelopment.50webs.com/blog/2008/06/sandcastle-may-2008-binaries.html

Regards,

Paulo Santos
http://pjondevelopment.50webs.com
Reply to this comment

A CNET Conversation with Eric Schmidt

CNET's Tom Krazit and Molly Wood sit down with Google CEO Eric Schmidt to discuss the future of Android, the Chrome OS, the problem of real-time search indexing, and more.

Verizon tests sending RIAA copyright notices

The No. 2 phone company, known for its reluctance to intervene in antipiracy cases, strikes an agreement to forward copyright notices on behalf of the music industry.

advertisement

About The Open Road

Matt Asay brings a decade of in-the-trenches open-source business and legal experience to the Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is general manager of the Americas division and vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.

Add this feed to your online news reader

The Open Road topics

advertisement
advertisement

Inside CNET News

Scroll Left Scroll Right