Fighting Forks


Published on

Published in: Technology
1 Comment
1 Like
  • Ignite @ Mil-OSS WG2: Fighting Forks from Joshua L. Davis on Vimeo.<br /><object type="application/x-shockwave-flash" data=";;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=&amp;fullscreen=1&amp;autoplay=0&amp;loop=0" width="350" height="288"><param name="movie" value=";;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=&amp;fullscreen=1&amp;autoplay=0&amp;loop=0"></param><embed src=";;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=&amp;fullscreen=1&amp;autoplay=0&amp;loop=0" width="350" height="288" type="application/x-shockwave-flash"></embed></object>
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Fighting Forks

  1. 1. 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 · 202 507 9027 · @ghelleks 3 August 2010
  2. 2. Licenses keep open software open. That's all we have.
  3. 3. Our process keeps software closed. Licenses keep open software open. That's all we have. The world conspires against us.
  4. 4. Licenses keep open software open. Tivo-ization. Which is a fancy all we have. free-riding. That's word for
  5. 5. Licenses keep Open software open. Secret open Source. If my lawyer finds out That's allGPL code, he's gonna kill me. I used we have.
  6. 6. Licenses keep open software open. Tweakers. That's all we have. I just added this one teeny-weeny patch...
  7. 7. Licenses keep open software open. Government is Government. No code distribution That's all we have. it's all Government. requirements:
  8. 8. Licenses keep open software open. Government Forges. That's all we have. Roach motels for code.
  9. 9. Licenses keep open software open. Security. DSS > GPL. Andall we have. That's don't forget ITAR.
  10. 10. Licenses What openwe do? keep can software open. Hack the process.all we our act together. That's Get have.
  11. 11. What do we want from the process? Let's ask an expert. 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. Snyder Cultivating Communities of Practice, 1st ed. (Harvard Business Press, 2002)
  12. 12. Licenses keep for Evolution open. Design open software That's all we have. Include upstream contributions in contracts.
  13. 13. Invite different levels of participation. Operationalize Dave Wheeler and Dan Risacher.
  14. 14. Develop public and private spaces. Forges are for secrets. Unclassified work should be public.
  15. 15. Open a dialogue. Talk to your PMs, your lawyers, your engineers.
  16. 16. Focus on value. Less talking. More doing. Perfect is the enemy of the good, etc. “Democracy is the enemy of useful work.” - Clay Johnson
  17. 17. Combine familiarity with excitement. Tools are important.
  18. 18. Create a rythym. Stay vocal and stay visible.
  19. 19. 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.
  20. 20. 20