Bagel Belly Blog

On Google Chrome OS and OSS

So, Google have just announced a new operating system for devices like netbooks. From the announcement:

Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks. Later this year we will open-source its code, and netbooks running Google Chrome OS will be available for consumers in the second half of 2010. Because we're already talking to partners about the project, and we'll soon be working with the open source community, we wanted to share our vision now so everyone understands what we are trying to achieve.

Firstly, this is great news. We already have moblin , maemo, and various netbook remixes, but any big company deciding to invest in building open source platforms is likely to stimulate the ecosystem, provide competition that leads to innovation, and bring valuable eyeballs and marketing to the open source world.

Unfortunately, Google have done it again - started down the path to another "throw it over the wall" open source project, missing out on the key benefits of the open development model and skipping that most important step of all - building a community from inception to ensure the community develops and matures in line with the code.

That announcement quote again, with some emphasis added:

Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks. Later this year we will open-source its code, and netbooks running Google Chrome OS will be available for consumers in the second half of 2010. Because we're already talking to partners about the project, and we'll soon be working with the open source community, we wanted to share our vision now so everyone understands what we are trying to achieve.

Now, I know many people at Google, I know they have a lot of smart folk there, and I know that some parts of the organisation really understand what open source is and how it works. But how is it that there is this continuous disconnect at a fundamental level when it comes to new initiatives? We saw it with Android and we saw it with Chrome: Google do the bulk of the work behind closed doors, then dump the code out there and simply expect everyone to pick it up and run with it. If you're moving to open from a proprietary codebase, such as in Symbian's case, this approach is understandable. But if you're starting from scratch, it makes no sense at all.

Here's the thing. Either you believe in the open source model - and the open development that goes with it - or you're a cynical company using it for marketing and to leverage some free bug fixes. Which is it to be, Google? Are you going to start the conversation around code from inception, giving every motivated developer an opportunity to collaborate and contribute, accepting not just the rewards of community development but also the risks? Or are you going to do your own thing yet again, and hope no-one calls you on it?