July 16, 2008 11:15 AM PDT

Google's Android: Open source, closed doors

by Matt Asay
  • Font size
  • Print
  • 2 comments

It's not new to wrap open-source software in closed contracts. This is what Red Hat and others have done for years, and generally for very good reasons.

In similar manner, news has hit that while Google remains committed to open source with its mobile Android platform, it hasn't exactly been committed to an open process. To wit, Google has been providing its open-source Android SDK to a select few under non-disclosure agreements.

While most of the Android community was forced to use an outdated version of the SDK from February and were left to wonder if they would ever see another SDK release at all, a small assortment of 50 gagged developers were given priority access to much-needed improvements and bug fixes that Google has apparently been keeping secret. This revelation has compelled some to question the search giant's motives and wonder whether Google is really committed to making Android an equal-opportunity platform for enthusiast developers.

Mike Gunderloy is right to question Google's commitment to openness on the Android project, but this really is a matter of process, not open source. By making a splash around the open-source nature of Android, Google set the openness bar high. There's an expectation that process will follow source-code access.

I don't think Google should be accused of holding back from its community here. I just think the company needs to be much more transparent about why it's doing what it does. There are very good reasons to do a limited SDK release before releasing the code to a wider distribution. Google just needs to state what those are.

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.
Add a Comment (Log in or register)
by Michael-Martin July 16, 2008 5:07 PM PDT
I believe should have an Android engineer communicator / spokesman similar to what Matt Cutts does for Google's webspam awareness - speaking at conferences and on a public blog.

I spoke further about this at http://www.googleandblog.com/google-android-engineer-speaks-out/313/
Reply to this comment
by joelwest July 16, 2008 10:29 PM PDT
I think someday Android could be open, but to assume they will be open soon is taking a lot on faith, and to act as though they are open is foolish.

http://blog.openitstrategies.com/2008/07/perhaps-someday-android-will-be-open.html
Reply to this comment
advertisement

15 sites that went kaput in 2009

Web sites launch all the time, but they also shut their doors. We highlight 15 that bit the dust this year.

Top 10 news stories of the decade

Let the debate begin: Was the iPhone more important than iTunes? Was anything bigger than Google finding a great business model? CNET offers its list of the 10 most important stories of the '00s.

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