process. • The open source collaboration model is still primary based on the notion of scratching your own itch. (Think Apache and Linux) • Less work has been done on a models that include subject matter experts (who are not also writing the code themselves) esp. within government. • Government is awash in shareable technology more relevance to fulfilling its mission, than providing highly technical infrastructure. to Thursday, June 21, 12
problems requires the collaboration of people who may not naturally work together • In government, this includes turning disruptive technology and new models in to a sound, defensible strategy. Thursday, June 21, 12
interesting to give, than to receive • gov 2.0 bling shiny object distraction • rock star behavior • a love of technology and a dread of documentation (= process and policy in government) Thursday, June 21, 12
right. • Continue to move the Community up the Stack • The most open initiatives will develop diverse ecosystems and vital communities. Thursday, June 21, 12
one • Build a community that includes your practitioners. • Create a Community of Practice for personnel and others creating and refining agency policies for open source • NASA, VA, CFPB, DoD, HHS, DHS • Embrace technology, but love the benefits more. Thursday, June 21, 12
community advice. • Use a standard OSI approved license. • Allows for greater participation. • Bigger community. • More diverse ecosystem. • Plus Bonus Points for Sustainability. Thursday, June 21, 12
• NASA world wind for setting the community free. • HHS Connect for lessons learned on moving a federal project to include the private industry. • VA Vista for moving a legacy project outside the agency Thursday, June 21, 12