fighting forks

20
Fighting Forks When Open Source Disappears into the Pentagon and What We Can Do About It Gunnar Hellekson Chief Technology Strategist, Red Hat US Public Sector gu[email protected] · 202 507 9027 · @ghelleks 3 August 2010

Upload: gunnar-hellekson

Post on 13-Dec-2014

527 views

Category:

Technology


1 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Fighting Forks

Fighting ForksWhen Open Source Disappears into the Pentagon

and What We Can Do About It

Gunnar HelleksonChief Technology Strategist, Red Hat US Public [email protected] · 202 507 9027 · @ghelleks

3 August 2010

Page 2: Fighting Forks

Licenses keep open software open.That's all we have.

Page 3: Fighting Forks

Licenses keep open software open.That's all we have.

Our process keeps software closed.The world conspires against us.

Page 4: Fighting Forks

Licenses keep open software open.That's all we have.

Tivo-ization.Which is a fancy word for free-riding.

Page 5: Fighting Forks

Licenses keep open software open.That's all we have.

Secret Open Source.If my lawyer finds out I used GPL code, he's gonna kill me.

Page 6: Fighting Forks

Licenses keep open software open.That's all we have.

Tweakers.I just added this one teeny-weeny patch...

Page 7: Fighting Forks

Licenses keep open software open.That's all we have.

Government is Government.No code distribution requirements: it's all Government.

Page 8: Fighting Forks

Licenses keep open software open.That's all we have.

Government Forges.Roach motels for code.

Page 9: Fighting Forks

Licenses keep open software open.That's all we have.Security.

DSS > GPL. And don't forget ITAR.

Page 10: Fighting Forks

Licenses keep open software open.That's all we have.

What can we do?Hack the process. Get our act together.

Page 11: Fighting Forks

Design for evolution.Open a dialogue between inside and outside perspectives. Invite different levels of participation. Develop both public and private community spaces.Focus on value.Combine familiarity and excitement.Create a rhythm for the community.

Etienne Wenger, Richard McDermott, and William M. SnyderCultivating Communities of Practice, 1st ed. (Harvard Business Press, 2002)

What do we want from the process?Let's ask an expert.

Page 12: Fighting Forks

Licenses keep open software open.That's all we have.

Design for EvolutionInclude upstream contributions in contracts.

Page 13: Fighting Forks

Invite different levels of participation. Operationalize Dave Wheeler and Dan Risacher.

Page 14: Fighting Forks

Develop public and private spaces.Forges are for secrets. Unclassified work should be public.

Page 15: Fighting Forks

Open a dialogue.Talk to your PMs, your lawyers, your engineers.

Page 16: Fighting Forks

Focus on value.Less talking. More doing. Perfect is the enemy of the good, etc.

“Democracy is the enemy of useful work.” - Clay Johnson

Page 17: Fighting Forks

Combine familiarity with excitement.Tools are important.

Page 18: Fighting Forks

Create a rythym.Stay vocal and stay visible.

Page 19: Fighting Forks

Do these three things.

Understand the contribution process in your patch. Make sure everyone knows they can come to you with questions. We have your back.

Shout your success.We're winning every day, but nobody knows about it.

Find one patch, one script you can free.These little guys are whithering. Get them out into the sunlight, where they can grow.

Page 20: Fighting Forks

20