Code Conversations - Chris DiBona on Google's Open Source Programs

-- Contents --
0:00 - Introduction
0:20 - Chris in the Chrome Comic
0:44 - Release of Chrome source code
1:20 - Throwing code over the wall...
2:18 - Developing Chrome in the open
5:02 - What won't be released as OSS
5:55 - Not all OSS helps the web
-- End --

"Code Conversations" is a new series of videos intended to film casual conversations with notable Google developers and legends in the technology fields. No agenda, no topic... just thoughts. This video is the first episode of this series, in which Chris DiBona, our intrepid open source programs manager talks to Stephanie Liu of the Developer Team about his "sweet goatee" in the Chrome Comic. He also explains why Google open sourced Chrome and Android and why we didn't do it sooner. He also touches on why much of Google's software isn't open sourced.

Intros:

Chris DiBona is the open source programs manager at Google, where his team oversees license compliance and supports the open source developer community through the release of open source software projects and programs such as the Google Summer of Code. Before joining Google, Chris was an editor at Slashdot, has edited the books Open Sources: Voices from the Open Source Revolution and Open Sources 2.0: The Continuing Evolution and formerly co-hosted the FLOSS weekly with Leo Laporte. His personal blog is called Ego Food.

Stephanie Liu is a Programs Manager on the Developer Team here at Google.

We'll be checking your comments on this post for feedback and ideas for future Code Conversations.

Category:

Science & Technology

Tags:

• gcvcodeconv
• google
• code
• conversations
• chris
• dibona
• stephanie
• liu
• videos
• chrome
• comic
• android
• open
• source
• programs
• developer
• video
• series
• plid633DD2FE10E46955

[motters2001]

So, why is there still no Linux version? If you're a software engineer you should know that it's perfectly possible to write software which runs on multiple platforms if you plan to do that from the outset - which then governs your technical decisions.

[tbaskan]

Yes, the audio is too bad.

[VondaFoni]

Google has a lot of Opensource programs i think.

[wingedspycat4]

thats my uncle by the way

[computertricks911]

um im prety sure that google can afford a wireless mic our somhting right come on

[MadSmokerBBQ]

crappy audio would kill ya to plug in a mic

[JeReL19]

Turn the volume up.

[acereroycementero]

Excellent idea this Code Conversations, I really enjoyed it and I found it very useful, I'm looking forward for more CCs!!

[eeanm]

So big successful open source projects aren't the norm, but the normal open source developer is working on a big successful project since that's where all the developers are.

I've heard people talk about how many small unsuccessful open source projects (by which they mean, some crap on sourceforge), but I really don't think its a very relevant metric. Open source is about DEVELOPERS DEVELOPERS DEVELOPERS (as a wise man once said :P) so its better to look at what they are doing.

[fcmonnard]

casual conversations is a great idea. Professional mic is even better. ;-)

[yourstudio]

good interview thanks for the casual conversation .. i've actually read some of his books.. its cool to hear some current perspectives from open source experts