Open source optionsOpen source software implementations creates options for the government:Don’t have to be locked into single technology vendor with forced license requirements (per seat, CPU, etc. )Open source can be a powerful negotiating point with vendors to decrease costs
John Scott: Mil-OSS
WHY THE GOVERNMENT IS EVOLVING TO ‘OPEN’ Content.gov 2013 Conference March 5, 2013 John Scott firstname.lastname@example.org @johnmscott
1. Why is the gov opening? § People § Technology § Process
Trends: People Employees & Citizens: § Impatient (generational) § Raised on open and free development tools/ sites/portals Developers: § Good ones are lazy § Good ones don’t want to resolve completed problems
Trends: Technology § Need for Speed ú Software development & change § Tooling ú Best software development tools mainly OSS ú OSS easiest available § Commoditization / maturity of OSS
Gartner predicts that within 2010 25% of the overall software market will be Free Software-‐based, with roughly 12% of it “internal” to companies and administrations that adopt Free Software. The remaining market, still substantial, is based on several diﬀerent business models, that monetize the software using diﬀerent strategies. Gartner Group, “Open source going mainstream,” 2006
Example Savings 10 Source: OSDL, Stuart Cohen, GOSCON 2007
2. Where is the Gov? § 3 stages: Use, modify & create § Open data: shock troops of openness § OSS the logistics/supply train
Open Continuum Gov Data DATA about here Full Access ACCESS INTERACT COMBINE & Open Closed USE MODIFY CREATE TO RELEASE Gov Tech about here TECHNOLOGY
People & Tech Gov Employees § Workforce aging/retiring and not being replaced at same rate due to costs Technology § Lots of Legacy systems and code
Process (the bigger problem) § Policy, Regulations, Law § Hardware vs. Software & Acquisitions ú WW2 & software development and tools
Key Issues in Technology Acquisitions Key Point # 1: Measure Twice, Cut Once Acquisitions Processes based on one premise -‐ Measure Twice, Cut Once -‐ Industrial vs. Digital / Steel vs. Bits / Land Warfare vs. Cyber Key Point #2: Knowledge Monopolies Hardware: Enabling industry to have commercial rights to hardware technologies (which requires factories, etc.) works Software: enabling a knowledge monopoly limits the dissemination of knowledge about defense systems Gov Intellectual Property Regime based in 20th (19th?) Century
Government Software IP Knot Tactical IP: Good at tactical management of intellectual property on a programs basis Strategic IP: Bad: No DoD strategic policy on how the software ecosystem should function for us: i.e., how (as an enterprise) should software IP rights be exercised in DoD
* USER CANNOT CLEAN, FIX, MODIFY, OR UPGRADE *Non-starter for the military, but we allow in software?
LAW § House: Issa IT Reform Bill § Senate 2012 Bill ú Supported use of OSS
POLICY § DOD CIO, OMB, NASA, CFPB… § New @ NIH ! ú NCIP’s Open-‐Development Strategy Enables Community-‐Driven Cancer Informatics Software Development ú http://ncip.nci.nih.gov/blog/2013/02/20/ncips-‐open-‐development-‐ strategy-‐enables-‐community-‐driven-‐cancer-‐informatics-‐ software-‐development/
Open Source Software! =! "software for which the human-readable source code is available for use, study, re-use,modification, enhancement, and re-distribution by the users of that software"*! *Reference: 16 October 2009 memorandum from the DoD CIO, "Clarifying Guidance Regarding Open Source Software (OSS)"
Open Open Gov DoD: Clarifying Guidance Regarding Open Source Software16 October 2009
Other .gov/.mil efforts § Dept of State: Tech@State on Open Source § NASA Open Source Software Day ú http://www.slideshare.net/skytland/nasa-‐open-‐source-‐proceedings § SPAWAR/Atlantic: Open Source Day § Veterans Aﬀairs Vista
How to help? Strategy § CIOs: Focus on ú Increasing enterprise options ú Enterprise automation § Educating COTRs § Require review of OSS solutions ú Already a req, but ignored ú At least use to negotiate
Key Points § Open Source is not FREE § Must (somehow) fund and sponsor development to keep the technology fresh, evolving and up-‐to-‐ date § Either through subscriptions or services
Software is a Renewable Civilian/Military Resource (and we paid for it) § Software has become central to how the government conducts missions § For reliance on software to be a strength, the government must pursue an active strategy to manage its software portfolio and foster an internal culture of open interfaces, modularity and reuse 40
How to Build a Capability Running Open Technology DevelopmentProjectsStep 1: Determine reuse optionsStep 2: Identify the Projects to be EstablishedStep 3: Choose and Apply a Common LicenseStep 4: Establish GovernanceStep 5: Establish CollaborationStep 6: Create Project Technical DirectionStep 7: AnnouncingContinuously Review Steps 1-7 Rules of the Road: 1. Don’t Fork OSS Solely for Government Use 2. Open Standards 3. Continuous Delivery 4. Simplify Intellectual Rights Management
OSS Winning… Its just not evenly distributed (across government)
Thanks! OSS Maturity: Certiﬁed to DoD 5015.02 standard for records management
MILITARY OPEN SOURCE SOFTWARE(MIL-OSS)HTTP://MIL-OSS.ORGJohn Scott, RadiantBlue Tech. Inc.email@example.com@gmail.com, 240.401.6574
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.