Joshua Davis - Intro to Mil-OSS


Published on

Listen to Josh Davis, Research Scientist II & Manager at Georgia Tech Research Institute and Co-Founder at Military Open Source Software (Mil-OSS) as he provides a brief overview of the US Military and Government's adoption of open source software.  This session also includes an introduction the Military Open Source Software community.

Published in: Technology, News & Politics
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Joshua Davis - Intro to Mil-OSS

  1. 1. An Introduction to Military Open Source Software 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.       An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   1  
  2. 2. ABOUT OPEN SOURCE An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   2  
  3. 3. mil-­‐   3  
  5. 5. mil-­‐   Reference:  h*p://   5  
  6. 6. USER CANNOT CLEAN, FIX, MODIFY, OR UPGRADEmil-­‐   Reference:  h*p://   6  
  7. 7. mil-­‐  
  8. 8. Remember to think of! “free” as in “free speech,” not as in “free beer”! ! Richard M. Stallman! (1996)!mil-­‐  
  9. 9. mil-­‐  
  10. 10. mil-­‐  
  11. 11. 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,   What Is OSS reuse,  modifica=on,  enhancement,  and  redistribu=on  by   the  users  of  that  soBware.  In  other  words,  OSS  is  soBware   Defini+on   for  which  the  source  code  is  open."   Abundance   Licensing     Community  Structure                   Clarifying  Guidance  Regarding  OSS  (2009)   An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   11  
  12. 12. About Open Source Abundance  of  OSS     •  Over  half  a  million  projects   •  Over  5,000  sites  for  projects   What Is OSS •  Over  2,000  licenses   Defini=on   •  Approx.  20%  of  all  code  is  Open  Source   Abundance   •  Approx.  95%  of  code  bases  contain  undisclosed  OSS  code   Licensing   •  Over  50%  of  code  bases  contain  unknown  or  reciprocal  (or   Community  Structure   protec=ve)  licenses                   Black  Duck  SoBware   An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   12  
  13. 13. About Open Source OSS  Licensing  Overview   •  OSS  Licensing  is  designed  to  protect  the  open   What Is OSS distributability  of  the  soBware.   Defini=on   •  Licenses  classified  as  Restric=ve  or  Permissive   Abundance   •  Common  aspects  of  OSS  licensing  include:     Licensing   –  Encourage  uncontrolled  combina=on  and  reuse   Community  Structure   –  Typically  have  no  acceptance  procedures     –  OBen  impose  sharing  obliga=ons  on  users   An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   13  
  14. 14. About Open Source Community   •  Low  barriers  to  entry  (for  a  majority  of  projects)   What Is OSS •  "The  Commons"  to  specific  problems  &  technologies   Defini=on   •  Collabora=ve  innova=on   Abundance   Licensing   Community  Structure     An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   14  
  15. 15. About Open Source Exis+ng  Projects   •  Many  solu=ons  already  exist,  don’t  reinvent  wheels   Why OSS •  Discover  previous  success  and  failures   Exis+ng  Projects   •  Find  poten=al  partners  with  similar  needs  and  ideas   New  Projects   Highly  Adaptable   Cost-­‐Effec=ve  Solu=ons   Security  Model     An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   15  
  16. 16. About Open Source New  Projects   •  OSS  new  projects  to  increase  innova=on,  reuse,  etc.   Why OSS •  A  primary  tool  to  establish  a  community   Exis=ng  Projects   •  Can  steer  innova=on  to  a  higher-­‐level  of  compe==on   New  Projects   (infrastructure  vs.  applica=on  layer)   Highly  Adaptable   •  Low  barrier  to  start  -­‐  licensing  choice  one  of  the  most   Cost-­‐Effec=ve  Solu=ons   important  decisions   Security  Model     An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   16  
  17. 17. About Open Source Highly  Adaptable   •  Time  becer  spent  on  innova=on  than  re-­‐establishing   Why OSS the  baseline   Exis=ng  Projects   •  Create  and  expand  pluggable  pladorms   New  Projects   Highly  Adaptable   Cost-­‐Effec=ve  Solu=ons   Security  Model     An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   17  
  18. 18. About Open Source Cost-­‐Effec+ve  Solu+ons   •  Redundant  problems  should  never  be  met  with   Why OSS redundant  problem  solving   Exis=ng  Projects   •  U=lizes  the  r3  Principle   New  Projects   –  Reuse  when  Possible   Highly  Adaptable   –  Repurpose  when  Prac=cal   Cost-­‐Effec+ve  Solu+ons   –  Recycle  when  Plausible   Security  Model     An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   18  
  19. 19. About Open Source Security  Model   •  Built  On  Actual  Hardening  Rather  Than  Obfusca=on   Why OSS •  Wide  Peer  Review   Exis=ng  Projects   •  The  Naked  Truth   New  Projects   "If  we  all  had  to  walk  around  naked  wed  all  spend  more  8me  in   Highly  Adaptable   the  gym.“    -­‐  Jim  Whitehurst,  Red  Hat  CEO   Cost-­‐Effec=ve  Solu=ons   Security  Model     An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   19  
  20. 20. 20  
  22. 22. OPEN SOURCE IN THE DEPARTMENT OF DEFENSE An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   22  
  23. 23. Open Source in the DoD FAR  &  DFARS  Regula+ons   •  OSS  is  considered  “commercial  computer  soBware”  and   therefore  allowable  under    the  United  States  Code,  the   OSS in the DoD Federal  Acquisi=on  Regula=ons  (FAR),  and  the  Defense   Federal  Acquisi=on  Supplement  (DFARS)     FAR/DFARS  Regula+ons   DoD  Policy   •  OSS  oBen  considered  “commercial     off-­‐the-­‐shelf”  (COTS)  per  41USC403   The  ‘Value  Added’   •  OSS  is  preferred  as  commercial  and     Inter-­‐Agency  Sharing     nondevelopmental  items  (NDI)     Re-­‐Deployable  Solu=ons   “to  the  maximum  extent     prac=cable”  under  10  USC  2377     Vendor-­‐Neutral     Obstacles  for  DoD               41  USC  403;    FAR  2.101,  FAR  12;    DFARS  212.212,  DFARS  252   An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   23  
  24. 24. Open Source in the DoD Military  Policy  Governing  OSS   •  DoD  Policy   OSS in the DoD –  2003  OSS  in  the  DoD  (Stenbit  Memo)   FAR/DFARS  Regula=ons   –  2006  Open  Technology  Development  Roadmap   DoD  Policy   –  2009  Clarifying  Guidance  Regarding  Open  Source   The  ‘Value  Added’   –  2010  Becer  Buying  Power  (Carter  Memo)   Inter-­‐Agency  Sharing     •  U.S.  Army   Re-­‐Deployable  Solu=ons   Vendor-­‐Neutral   –  AR  25-­‐2  p4-­‐6   Obstacles  for  DoD   •  U.S.  Navy     –  2007  Open  Source  SoBware  Guidance       An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   24  
  25. 25. Open Source in the DoD The  “Value  Added”   •  Cost-­‐Effec=ve  Development   OSS in the DoD •  Highly  Efficient   FAR/DFARS  Regula=ons   •  Increased  produc=vity   DoD  Policy   •  Increased  innova=on   The  ‘Value  Added’   Inter-­‐Agency  Sharing     •  Increased  collabora=on   Re-­‐Deployable  Solu=ons   Vendor-­‐Neutral   Obstacles  for  DoD         An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   25  
  26. 26. Open Source in the DoD Inter-­‐Agency  Sharing   •  Without  communi=es  of  interest  around  Defense-­‐ OSS in the DoD related  OSS  projects,  they  too  oBen  go  unknown  and   unused   FAR/DFARS  Regula=ons   •  Improve  the  project  by  involving  other-­‐agency  input   DoD  Policy   and  collabora=on   The  ‘Value  Added’   •  NASA  found  it  is  easier  to  share  agency-­‐to-­‐agency   Inter-­‐Agency  Sharing     under  OSS  license  than  under  government  re-­‐use   Re-­‐Deployable  Solu=ons   regula=ons   Vendor-­‐Neutral   Obstacles  for  DoD         An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   26  
  27. 27. Open Source in the DoD Re-­‐Deployable  Solu+ons   •  The  military  lends  itself  to  redundant  problems     OSS in the DoD •  Redundant  problems  should  never  be  met  with   FAR/DFARS  Regula=ons   redundant  problem  solving.     DoD  Policy   •  Open  Source  enables  the  reuse  of  solu=ons  to  common   The  ‘Value  Added’   problems   Inter-­‐Agency  Sharing     •  Adaptability  to  expand  from  a  basic  problem  into  a  new   Re-­‐Deployable  Solu+ons   solu=on  or  service.   Vendor-­‐Neutral   Obstacles  for  DoD         An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   27  
  28. 28. Open Source in the DoD Vendor-­‐Neutral   •  Readable  source  code  makes  it  impossible  to  become   OSS in the DoD locked-­‐in  with  a  specific  vendor     FAR/DFARS  Regula=ons   •  Future  vendor  compe==on   DoD  Policy   •  Rapid  deployment  is  a  strong  case  in  the  DoD   The  ‘Value  Added’   •  IT  tools  for  evolving  mission  solu=ons.   Inter-­‐Agency  Sharing     Re-­‐Deployable  Solu=ons   Vendor-­‐Neutral   Obstacles  for  DoD         An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   28  
  29. 29. Open Source in the DoD Obstacles  for  DoD   •  Ensure  OSS  fairly  considered  in  acquisi+ons   –  Some  acquisi=on  processes/policies  not  updated  for  OSS   OSS in the DoD –  Many  PMs  unfamiliar  with  OSS:  don’t  consider  it   FAR/DFARS  Regula=ons   –  Many  OSS  projects  ignore  solicita=ons  &  RFPs   DoD  Policy   •  Different  economics:  Pay-­‐up-­‐front  for  improvements   The  ‘Value  Added’   –  Some  policies  presume  proprietary  COTS’  pay-­‐per-­‐use  model   Inter-­‐Agency  Sharing     –  Can  pay  in  $  or  =me,  can  compete,  can  cost-­‐share  with  others   Re-­‐Deployable  Solu=ons   •  Transi+on  costs  of  pre-­‐exis+ng  systems   Vendor-­‐Neutral   –  Especially  if  dependent  on  proprietary  formats/protocols/APIs   Obstacles  for  DoD   –  Use  open  standards  so  can  switch  (mul=-­‐vendor,  no  ‘RAND’   patents)     •  Emphasize  web-­‐based  apps/SOA/plaborm-­‐neutral       –  test  it!     –  Vendor  lock-­‐in  oBen  increases  TCO;  transi=on  may  be   worthwhile   An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   29  
  30. 30. ABOUT OUR COMMUNITY An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   30  
  31. 31. About Our Community Our  Mission   Mil-­‐OSS  exists  to  improve  technology  development  and   Who We Are innova=on  across  the  DoD  by  connec=ng  and  empowering   an  ac=ve  community  of  patrio=c  developers  and  solu=on   Our  Mission   providers,  improving  use  of  the  taxpayers  funds  through   Our  Goals   thorough  requirements  extrac=on,  wise  execu=on,  and   increasing  the  speed  new  technologies  enable  the   Our  Guiding  Principles   Warfighter  by  leveraging  open  source  and  open   Steering  Commicee   technology  innova=on  philosophies.     An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   31  
  32. 32. About Our Community Our  Goals   •  Create  new  open  source  solu=ons  that  are  more   Who We Are effec=ve  for  the  Warfighter   Our  Mission   •  Increase  reuse  of  code  and  exis=ng  open  source   projects   Our  Goals   Our  Guiding  Principles   •  Increase  awareness  of  exis=ng  reusable  and  open   source  technologies   Steering  Commicee     •  Ini=ate  events  and  opportuni=es  that  enable   Warfighters  to  transfer  requirements  directly  to   developers   •  Educate  developers  on  how  to  becer  develop  for  the   Warfighter   •  Improve  collabora=on  with  allies     An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   32  
  33. 33. About Our Community Our  Guiding  Principles   •  We  believe  that  contribu=ng  to  OSS  in  the  DoD  is  a   Who We Are patrio=c  contribu=on  to  our  na=onal  defense.   Our  Mission   •  We  believe  that  as  stewards  of  taxpayer  funds,  we  are   responsible  to  be  efficient,  cost-­‐effec=ve  and   Our  Goals   innova=ve.   Our  Guiding  Principles   •  We  believe  in  the  innova=ve  power  of  people,   Steering  Commicee   especially  in  large  numbers.     •  We  believe  in  finding  and  mee=ng  challenges—good   solu=ons  to  real  problems  will  find  their  needed   funding.   An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   33  
  34. 34. About Our Community Steering  Commidee   •  Joshua  L.  Davis,  Georgia  Tech  Research  Ins=tute   Who We Are •  John  Scod,  Radiant  Blue   Our  Mission   •  Heather  Burke,  U.S.N.  (Civilian  at  SPAWAR)   Our  Goals   •  Gunnar  Hellekson,  Red  Hat   Our  Guiding  Principles   Steering  Commidee   •  David  Wheeler,  IDA     •  Daniel  Risacher,  DoD  (Civilian  at  DoD  CIO  NII)   •  Kane  McLean,  BRTRC   •  Michael  Howard,  Qine=q     •  Winston  Messer,  Open  Source  SoBware  Ins=tute   An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   34  
  35. 35. About Our Community Defense  Professionals   Mil-­‐OSS  is  a  grass-­‐roots  organiza=on  made  up  of  .  .  .   Where We Are •  Ac=ve  community  of  civilians  and  military  across  the   Defense  Professionals     U.S.  Dept.  of  Defense  (DoD)   Na=onal  Events   •  Open  Source  SoBware  (OSS)  and  Open  Source   Local  Events   Hardware  (OSHW)  Enthusiasts   Policy  Engagement   •  Patriots  who  seek  to  improve  soBware     Online  Resources   security,  control  development  costs     and  increase  innova=on  in  support     of  our  na=onal  defense   An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   35  
  36. 36. About Our Community Na+onal  Events   •  Annual  Mil-­‐OSS  Working  Group   Where We Are •  Mil-­‐OSS  LANT   Defense  Professionals     Na+onal  Events   Local  Events   Policy  Engagement   Online  Resources     An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   36  
  37. 37. About Our Community Local  Events   •  Atlanta  —  Monthly  Breakfast   Where We Are •  Boston  —  Details  Being  Worked  Out   Defense  Professionals     •  Charleston  —  Launching  in  May   Na=onal  Events   •  San  Diego  —  Monthly  Drinks   Local  Events   Policy  Engagement   •  Washington,  D.C.     Online  Resources   –  Monthly  Lunch     –  Quarterly  OpenGEO  &  Mil-­‐OSS  Meet-­‐up   •  Online  —  Details  Being  Worked  Out   An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   37  
  38. 38. About Our Community Policy  Engagement   •  If  regula=ons  or  policy  are  being  discussed,  there  is  a   Where We Are strong  chance  someone  from  Mil-­‐OSS  is  at  the  table   Defense  Professionals     •  Mil-­‐OSS  members  have  been  part  of  the  most   important  OSS  policy  developments   Na=onal  Events   Local  Events   Policy  Engagement   Online  Resources     An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   38  
  39. 39. About Our Community Online  Resources   •  Google  Group  -­‐­‐oss     Where We Are •  Facebook  -­‐     Defense  Professionals     •  Twicer  -­‐   Na=onal  Events   •  LinkedIn  -­‐   Local  Events   Policy  Engagement   •  SlideShare  -­‐­‐open-­‐source-­‐somware     Online  Resources   •  Vimeo  -­‐       •  Flickr  -­‐­‐oss   •  RSS  Feed  -­‐  mil-­‐   An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   39  
  40. 40. GETTING INVOLVED An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   40  
  41. 41. Getting Involved Adend  Events   •  Local  Events   Getting Involved –  Meet-­‐ups   Adend  Events   –  Breakfasts  /  Lunches  /  Drinks   Engage  the  Community   •  Na=onal  Events   Collaborate  and  Share     –  Mil-­‐OSS  LANT  (Charleston,  May  2012)     –  Mil-­‐OSS  WG4  (Orlando,  October  2012)     •  Start  Another  One     –  If  you  have  idea  there  are  many  within  the   community  to  help  make  it  happen   An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   41  
  42. 42. Getting Involved Engage  the  Community   •  Subscribe  to  and  post     Getting Involved in  the  Google  Group   Acend  Events   •  Engage  on  Facebook     &  Twicer   Engage  the  Community   Collaborate  and  Share   •  Chat  with  members     at  local  events           An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   42  
  43. 43. Getting Involved Collaborate  and  Share   •  Start  new  projects   Getting Involved •  Recruit  Mil-­‐OSS  members  to  par=cipate   Acend  Events   •  Help  others  understand  OSS   Engage  the  Community   •  See  OSS  happening  in  the  Government,  tell  others   Collaborate  and  Share     •  When  you  see  something,  say  something.         An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   43  
  44. 44.        Contact  Informa+on  Joshua  L.  Davis      Website  mil-­‐    Phone  202.455.8089    General  Email  contact@mil-­‐    Media  Inquiries  publicaffairs@mil-­‐     An  Introduc+on  to  the  Mil-­‐OSS  Community  mil-­‐   19  JAN  2012   44  
  45. 45. An  Introduc+on  to  the  Mil-­‐OSS  Community   19  JAN  2012   45