kane mclean - an introduction to the mil-oss community

mil-‐oss.org

An Introduction to the Mil-OSS Community

19 JAN 2012 An Introduc+on to the Mil-‐OSS Community

1

Mil-‐OSS connects and empowers an ac=ve community of civilian and military open source soBware and hardware developers across the United States. This grassroots movement is a collec=on of diverse patriots that work for and with the Department of Defense and believe in adop=ng open technology innova=on philosophies to effec=vely defend our na=on.

mil-‐oss.org

ABOUT OUR COMMUNITY


2

mil-‐oss.org

Our Mission Mil-‐OSS exists to improve technology development and innova=on across the DoD by connec=ng and empowering an ac=ve community of patrio=c developers and solu=on providers, improving use of the taxpayers' funds through thorough requirements extrac=on, wise execu=on, and increasing the speed new technologies enable the Warfighter by leveraging open source and open technology innova=on philosophies.

About Our Community


3

Our Mission

Our Goals

Our Guiding Principles

Steering CommiSee

Who We Are






mil-‐oss.org

About Our Community

Our Goals •  Create new open source solu=ons that are more effec=ve for the Warfighter

•  Increase reuse of code and exis=ng open source projects

•  Increase awareness of exis=ng reusable and open source technologies

•  Ini=ate events and opportuni=es that enable Warfighters to transfer requirements directly to developers

•  Educate developers on how to beSer develop for the Warfighter

•  Improve collabora=on with allies

Our Mission

Our Goals


Steering CommiSee


4

Who We Are

mil-‐oss.org

About Our Community

Our Guiding Principles •  We believe that contribu=ng to OSS in the DoD is a patrio=c contribu=on to our na=onal defense.

•  We believe that as stewards of taxpayer funds, we are responsible to be efficient, cost-‐effec=ve and innova=ve.

•  We believe in the innova=ve power of people, especially in large numbers.

•  We believe in finding and mee=ng challenges—good solu=ons to real problems will find their needed funding.

Our Mission

Our Goals


Steering CommiSee


5

Who We Are

mil-‐oss.org

About Our Community

Steering CommiBee •  Josh Davis, Georgia Tech Research Ins=tute •  John ScoB, Radiant Blue •  Heather Burke, U.S.N. (Civilian at SPAWAR) •  Gunnar Hellekson, Red Hat •  David Wheeler, IDA •  Daniel Risacher, DoD (Civilian at DoD CIO NII) •  Kane McLean, BRTRC

•  Michael Howard, Qine=q •  Winston Messer, Open Source Ins=tute

Our Mission

Our Goals


Steering CommiBee


6

Who We Are

mil-‐oss.org

About Our Community

Defense Professionals Mil-‐OSS is a grass-‐roots organiza=on made up of . . . •  Ac=ve community of civilians and military across the U.S. Dept. of Defense (DoD)

•  Open Source SoBware (OSS) and Open Source Hardware (OSHW) Enthusiasts

•  Patriots who seek to improve soBware security, control development costs and increase innova=on in support of our na=onal defense

Defense Professionals

Na=onal Events

Local Events

Policy Engagement

Online Resources


7

Where We Are

mil-‐oss.org

About Our Community

Na+onal Events •  Annual Mil-‐OSS Working Group •  Mil-‐OSS LANT


Na+onal Events

Local Events

Policy Engagement

Online Resources


8

Where We Are

mil-‐oss.org

About Our Community

Local Events •  Atlanta — Monthly Breakfast •  Boston — Details Being Worked Out

•  Charleston — Launching in May •  San Diego — Monthly Drinks •  Washington, D.C. –  Monthly Lunch –  Quarterly OpenGEO & Mil-‐OSS Meet-‐up

•  Online — Details Being Worked Out


Na=onal Events

Local Events

Policy Engagement

Online Resources


9

Where We Are

mil-‐oss.org

Policy Engagement •  If regula=ons or policy are being discussed, there is a strong chance someone from Mil-‐OSS is at the table

•  Mil-‐OSS members have been part of the most important OSS policy developments

About Our Community


Na=onal Events

Local Events

Policy Engagement

Online Resources


10

Where We Are

mil-‐oss.org

About Our Community

Online Resources •  Google Group -‐ groups.google.com/group/mil-‐oss

•  Facebook -‐ facebook.com/groups/miloss

•  TwiSer -‐ twiBer.com/mil_oss

•  LinkedIn -‐ linkedin.com/groups?gid=3273107

•  SlideShare -‐ slideshare.net/group/military-‐open-‐source-‐so\ware

•  Vimeo -‐ vimeo.com/channels/miloss

•  Flickr -‐ flickr.com/groups/mil-‐oss

•  RSS Feed -‐ mil-‐oss.org/index.php?format=feed&type=rss


Na=onal Events

Local Events

Policy Engagement

Online Resources


11

Where We Are

mil-‐oss.org

ABOUT OPEN SOURCE


12

mil-‐oss.org

About Open Source

The DoD Defini+on "Open Source SoBware (OSS) is soBware for which the human-‐readable source code is available for use, study, reuse, modifica=on, enhancement, and redistribu=on by the users of that soBware. In other words, OSS is soBware for which the source code is 'open'."

Clarifying Guidance Regarding OSS (2009)

Defini+on

Abundance

Licensing

Community Structure


13

What Is OSS

mil-‐oss.org

About Open Source

Abundance of OSS •  Over half a million projects •  Over 5,000 sites for projects •  Over 2,000 licenses •  Approx. 20% of all code is Open Source •  Approx. 95% of code bases contain undisclosed OSS code •  Over 50% of code bases contain unknown or reciprocal (or protec=ve) licenses

Black Duck SoBware

Defini=on

Abundance

Licensing

Community Structure


14

What Is OSS

mil-‐oss.org

About Open Source

OSS Licensing Overview •  OSS Licensing is designed to protect the open distributability of the soBware.

•  Licenses classified as Restric=ve or Permissive •  Common aspects of OSS licensing include: –  Encourage uncontrolled combina=on and reuse –  Typically have no acceptance procedures –  OBen impose sharing obliga=ons on users

Defini=on

Abundance

Licensing

Community Structure


15

What Is OSS

mil-‐oss.org

About Open Source

Community •  Low barriers to entry (for a majority of projects) •  "The Commons" to specific problems & technologies

•  Collabora=ve innova=on Defini=on

Abundance

Licensing

Community Structure


16

What Is OSS

mil-‐oss.org

About Open Source

Exis+ng Projects •  Many solu=ons already exist, don’t reinvent wheels •  Discover previous success and failures •  Find poten=al partners with similar needs and ideas Exis+ng Projects

New Projects

Highly Adaptable

Cost-‐Effec=ve Solu=ons

Security Model


17

Why OSS

mil-‐oss.org

About Open Source

New Projects •  OSS new projects to increase innova=on, reuse, etc. •  A primary tool to establish a community

•  Can steer innova=on to a higher-‐level of compe==on (infrastructure vs. applica=on layer)

•  Low barrier to start -‐ licensing choice one of the most important decisions

Exis=ng Projects

New Projects

Highly Adaptable


Security Model


18

Why OSS

mil-‐oss.org

About Open Source

Highly Adaptable •  Time beSer spent on innova=on than re-‐establishing the baseline

•  Create and expand pluggable plaiorms Exis=ng Projects

New Projects

Highly Adaptable


Security Model


19

Why OSS

mil-‐oss.org

About Open Source

Cost-‐Effec+ve Solu+ons •  Redundant problems should never be met with redundant problem solving

•  U=lizes the r3 Principle –  Reuse when Possible

–  Repurpose when Prac=cal

–  Recycle when Plausible

Exis=ng Projects

New Projects

Highly Adaptable

Cost-‐Effec+ve Solu+ons

Security Model


20

Why OSS

mil-‐oss.org

About Open Source

Security Model •  Built On Actual Hardening Rather Than Obfusca=on •  Wide Peer Review

•  The Naked Truth "If we all had to walk around naked we'd all spend more ;me in the gym.“ -‐ Jim Whitehurst, Red Hat CEO

Exis=ng Projects

New Projects

Highly Adaptable


Security Model


21

Why OSS

mil-‐oss.org

OPEN SOURCE IN THE DEPARTMENT OF DEFENSE


22

mil-‐oss.org

Open Source in the DoD

FAR & DFARS Regula+ons •  OSS is considered “commercial computer soBware” and therefore allowable under the United States Code, the Federal Acquisi=on Regula=ons (FAR), and the Defense Federal Acquisi=on Supplement (DFARS)

•  OSS oBen considered “commercial off-‐the-‐shelf” (COTS) per 41USC403

•  OSS is preferred as commercial and nondevelopmental items (NDI) “to the maximum extent prac=cable” under 10 USC 2377

41 USC 403; FAR 2.101, FAR 12; DFARS 212.212, DFARS 252

FAR/DFARS Regula+ons

DoD Policy

The ‘Value Added’

Inter-‐Agency Sharing

Re-‐Deployable Solu=ons

Vendor-‐Neutral

Obstacles for DoD


23

OSS in the DoD

mil-‐oss.org


Military Policy Governing OSS •  DoD Policy –  2003 OSS in the DoD (Stenbit Memo) –  2006 Open Technology Development Roadmap –  2009 Clarifying Guidance Regarding Open Source –  2010 BeSer Buying Power (Carter Memo)

•  U.S. Army –  AR 25-‐2 p4-‐6

•  U.S. Navy –  2007 Open Source SoBware Guidance

FAR/DFARS Regula=ons

DoD Policy




Vendor-‐Neutral

Obstacles for DoD


24

OSS in the DoD

mil-‐oss.org


The “Value Added” •  Cost-‐Effec=ve Development •  Highly Efficient

•  Increased produc=vity •  Increased innova=on •  Increased collabora=on


DoD Policy




Vendor-‐Neutral

Obstacles for DoD


25

OSS in the DoD

mil-‐oss.org


Inter-‐Agency Sharing •  With out communi=es of interest around Defense-‐related OSS projects, they too oBen go unknown and unused

•  Improve the project by involving other-‐agency input and collabora=on

•  NASA found it is easier to share agency-‐to-‐agency under OSS license than under government re-‐use regula=ons


DoD Policy




Vendor-‐Neutral

Obstacles for DoD


26

OSS in the DoD

mil-‐oss.org


Re-‐Deployable Solu+ons •  The military lends itself to redundant problems •  Redundant problems should never be met with redundant problem solving.

•  Open Source enables the re-‐use of solu=ons to common problems

•  Adaptability to expand from a basic problem into a new solu=on or service.


DoD Policy



Re-‐Deployable Solu+ons

Vendor-‐Neutral

Obstacles for DoD


27

OSS in the DoD

mil-‐oss.org


Vendor-‐Neutral •  Readable source code makes it impossible to become locked-‐in with a specific vendor

•  Future vendor compe==on •  Rapid deployment is a strong case in the DoD •  IT tools for evolving mission solu=ons.


DoD Policy




Vendor-‐Neutral

Obstacles for DoD


28

OSS in the DoD

mil-‐oss.org


Obstacles for DoD •  Ensure OSS fairly considered in acquisi+ons

–  Some acquisi=on processes/policies not updated for OSS –  Many PMs unfamiliar with OSS: don’t consider it –  Many OSS projects ignore solicita=ons & RFPs

•  Different economics: Pay-‐up-‐front for improvements –  Some policies presume proprietary COTS’ pay-‐per-‐use model –  Can pay in $ or =me, can compete, can cost-‐share with others

•  Transi+on costs of pre-‐exis+ng systems –  Especially if dependent on proprietary formats/protocols/APIs –  Use open standards so can switch (mul=-‐vendor, no ‘RAND’

patents)

•  Emphasize web-‐based apps/SOA/planorm-‐neutral –  test it! –  Vendor lock-‐in oBen increases TCO; transi=on may be

worthwhile


DoD Policy




Vendor-‐Neutral

Obstacles for DoD


29

OSS in the DoD

mil-‐oss.org


ABend Events •  Local Events –  Meet-‐ups

–  Breakfasts / Lunches / Drinks •  Na=onal Events –  Mil-‐OSS LANT (Charleston, May 2012) –  Mil-‐OSS WG4 (Orland, October 2012)

•  Start Another One –  If you have idea there are many within the

community to help make it happen

ABend Events

Engage the Community

OSS Evangelism


30

Getting Involved

mil-‐oss.org


Engage the Community •  Subscribe to and post in the Google Group

•  Engage on Facebook & TwiSer

•  Chat with members at local events

ASend Events


OSS Evangelism


31

Getting Involved

mil-‐oss.org


Collaborate and Share •  Start new projects •  Recruit Mil-‐OSS members to par=cipate

•  Help others understand OSS •  See OSS happening in the Government, tell others •  When you see something, say something.

ASend Events


OSS Evangelism


32

Getting Involved

mil-‐oss.org

Contact Informa+on

Website mil-‐oss.org Phone 202.455.8089

General Email contact@mil-‐oss.org Media Inquiries publicaffairs@mil-‐oss.org

Presenta+on Informa+on Version 1.0

Revised 22 JAN 2012


33