Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Shipping code from the White House: First steps into open source collaboration<br />Rob Winikates  —  @rob_w<br />White Ho...
Hands up if you use:<br />Open Atrium<br />
Hands up if you use:<br />Open Atrium<br />GovDelivery<br />
Hands up if you use:<br />Open Atrium<br />GovDelivery<br />Akamai<br />
Hands up if you use:<br />Open Atrium<br />GovDelivery<br />Akamai<br />urlshorteners<br />
Hands up if you use:<br />Open Atrium<br />GovDelivery<br />Akamai<br />urlshorteners<br />Drupal<br />
Cool. Us too. Plus, we support them with code contributions.<br />
Open source @WhiteHouse<br />Whitehouse.gov family powered by Drupal<br />Video player – JW player<br />Search – Apache So...
Clearly, value extracted from open source communities<br />
What about value added?<br />In house Drupal modules<br />Node Embed<br />Akamai<br />Context HTTP headers<br />GovDeliver...
Five (short) thoughts on releasing code<br />
1. Don’t do it alone. Partner, improve, extend.<br />
2. Plan to release from Day 1. Include it in the RFP, contract, technical requirements, everything.<br />
3. Keep it usable & generic. Build to standards. Seek external feedback.<br />
4. Promote your work.<br />
5. Don’t complain, maintain.<br />
Recap<br />Try to work with the community.<br />Preparing to release from the beginning is just better.<br />You don’t alw...
Thank you, Feedback welcome.<br /> @rob_w<br />rwinikates@who.eop.gov<br />
Upcoming SlideShare
Loading in …5
×

Shipping code from the White House: First steps into open source collaboration

1,356 views

Published on

  • Be the first to comment

  • Be the first to like this

Shipping code from the White House: First steps into open source collaboration

  1. 1. Shipping code from the White House: First steps into open source collaboration<br />Rob Winikates — @rob_w<br />White House Office of Digital Strategy <br />(aka New Media)<br />
  2. 2. Hands up if you use:<br />Open Atrium<br />
  3. 3. Hands up if you use:<br />Open Atrium<br />GovDelivery<br />
  4. 4. Hands up if you use:<br />Open Atrium<br />GovDelivery<br />Akamai<br />
  5. 5. Hands up if you use:<br />Open Atrium<br />GovDelivery<br />Akamai<br />urlshorteners<br />
  6. 6. Hands up if you use:<br />Open Atrium<br />GovDelivery<br />Akamai<br />urlshorteners<br />Drupal<br />
  7. 7. Cool. Us too. Plus, we support them with code contributions.<br />
  8. 8. Open source @WhiteHouse<br />Whitehouse.gov family powered by Drupal<br />Video player – JW player<br />Search – Apache Solr<br />Data visualization – JavaScript InfoVis Toolkit<br />Intranet Analytics – Open Web Analytics<br />Mapping tiles – MapBox and OpenStreetMap<br />
  9. 9. Clearly, value extracted from open source communities<br />
  10. 10. What about value added?<br />In house Drupal modules<br />Node Embed<br />Akamai<br />Context HTTP headers<br />GovDelivery<br />IMCE tools<br />Sponsored development<br />Beta round of Open Atrium suite<br />OpenCalais module<br />ShortURL module<br />
  11. 11. Five (short) thoughts on releasing code<br />
  12. 12. 1. Don’t do it alone. Partner, improve, extend.<br />
  13. 13. 2. Plan to release from Day 1. Include it in the RFP, contract, technical requirements, everything.<br />
  14. 14. 3. Keep it usable & generic. Build to standards. Seek external feedback.<br />
  15. 15. 4. Promote your work.<br />
  16. 16. 5. Don’t complain, maintain.<br />
  17. 17. Recap<br />Try to work with the community.<br />Preparing to release from the beginning is just better.<br />You don’t always know best. Make your code reusableand applicable. Validate your work early and often.<br />Promote your work.<br />Be a good steward of your release.<br />
  18. 18. Thank you, Feedback welcome.<br /> @rob_w<br />rwinikates@who.eop.gov<br />

×