Don’t Just Use It
     Build It!
Building Open Source Software in the DoD
                        Or

          A rapid do...
DoD is coming to grips
 with Open Source
      Software.

       Today...
It’s like COTS, It Even
    Comes in a Box
Photo creative commons licensed from http://www.flickr.com/photo_zoom.gne?id=432710571&size=l




                         ...
But, imagine this...
Welcome to www.SOSCOE.org
Project
Documentation
                     SOSCOE is the glue that holds FCS together...
Source
...
Or...
 www.open-cjmtk.org
 www.falconview.org
  www.webcop.org
www.open-disa.org/necc
You mean “corporate
   source” right?
      Right??
Q: Assuming a Normal distribution, how
      many developers must have the
opportunity to self select for your project
in ...
A: More open is better
Community Process:
 Gate the commit
  not the source

     Linus
 “the dictator”


                  http://www.flickr.com/...
So, you mean
 something like
“SHARE” right?
A Brief Aside:

Three ways (that I can think
of) to make source funded
 by government “open”* in
         the DoD
     * N...
• Government asserts rights (unlimited,
  or gov purpose) and shares the code
• Government Owned (they wrote it)
  and rel...
“SHARE” is this
                       one
•   Government asserts rights
    (unlimited, or gov purpose) and
    shares th...
But, if you’re a
 contractor you don’t
 have to wait for your
customer to make you
        SHARE.
You’re customer is sick
 of the Proprietary Lock In
 Model (and doesn’t it make
you feel kind of crappy too?).

Maybe ther...
If you are     Proprietary
 standing        Lock In


   here...

             ... go ahead
                   and
       ...
•   Government asserts rights
    (unlimited, or gov purpose) and
    shares the code

•   Government Owned (they wrote it...
Huh, Why?
Delight your customer
To do more with less!
Hire, retain, and excite great
         developers.
Obtain Great
  Karma




                                                                    Get free
                    ...
We decided to try it
What we got:
• A seat at the standards table
• Energized developers who are contributing
  and are known
• A broad communi...
rVooz.org
A few quick questions:
Q: Do you think the
     “open source
community” owes you
 process compliance
    (and ear tags)?
Q: Have you ever
attended an OSCON?
BarCamp? Heck, even a
 Gartner open source
     conference?
Q: Do you think there is a
 moral / ethical dimension to
   the adoption of OSS in
    government? Are you
prepared to wor...
Q: Now that Gen Justice got
you fired up about the value of
community, where the heck are
      the communities?
Q: Are you prepared for the
moment when open software,
developed under government
  contract, is forked by the
    Chinese...
Thanks!


      Jim Stogdill
jstogdill@gestalt-llc.com
    www.limnthis.com
Open Source in the DoD; Build It
Open Source in the DoD; Build It
Upcoming SlideShare
Loading in …5
×

Open Source in the DoD; Build It

3,996 views

Published on

Presented at AFEI DoD Open Technology Conference 12/12/07 www.afei.org

Published in: Business, Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,996
On SlideShare
0
From Embeds
0
Number of Embeds
146
Actions
Shares
0
Downloads
60
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Open Source in the DoD; Build It

  1. 1. Don’t Just Use It Build It! Building Open Source Software in the DoD Or A rapid dose of wishful thinking
  2. 2. DoD is coming to grips with Open Source Software. Today...
  3. 3. It’s like COTS, It Even Comes in a Box
  4. 4. Photo creative commons licensed from http://www.flickr.com/photo_zoom.gne?id=432710571&size=l Yawn
  5. 5. But, imagine this...
  6. 6. Welcome to www.SOSCOE.org Project Documentation SOSCOE is the glue that holds FCS together... Source Wiki Distributed Peer to Peer Get Started! Open Get SOSCOE Join Buy a Tee shirt! ... and is an open source project funded by the U.S. Army to develop a next generation real time distributed platform. You are free to use, modify, and distribute SOSCOE. Don’t worry, we aren’t sharing the super secret squirrel stuff.
  7. 7. Or... www.open-cjmtk.org www.falconview.org www.webcop.org www.open-disa.org/necc
  8. 8. You mean “corporate source” right? Right??
  9. 9. Q: Assuming a Normal distribution, how many developers must have the opportunity to self select for your project in order to have a 90% confidence that at least 1% of the actual participants will be 5 σ above the mean? You know, the crazy smart ones. The ones you want
  10. 10. A: More open is better
  11. 11. Community Process: Gate the commit not the source Linus “the dictator” http://www.flickr.com/photos/dunechaser/134671996/
  12. 12. So, you mean something like “SHARE” right?
  13. 13. A Brief Aside: Three ways (that I can think of) to make source funded by government “open”* in the DoD * No attempt here to conform to OSF definition
  14. 14. • Government asserts rights (unlimited, or gov purpose) and shares the code • Government Owned (they wrote it) and released via PAO • Contractor copyright released to open source community
  15. 15. “SHARE” is this one • Government asserts rights (unlimited, or gov purpose) and shares the code • Government Owned (they wrote it) and released via PAO • Contractor copyright released to open source community
  16. 16. But, if you’re a contractor you don’t have to wait for your customer to make you SHARE.
  17. 17. You’re customer is sick of the Proprietary Lock In Model (and doesn’t it make you feel kind of crappy too?). Maybe there is a Tipping Point?
  18. 18. If you are Proprietary standing Lock In here... ... go ahead and push!
  19. 19. • Government asserts rights (unlimited, or gov purpose) and shares the code • Government Owned (they wrote it) and released via PAO • Contractor copyright released to open source community So, do this one
  20. 20. Huh, Why?
  21. 21. Delight your customer
  22. 22. To do more with less!
  23. 23. Hire, retain, and excite great developers.
  24. 24. Obtain Great Karma Get free beer http://www.flickr.com/photos/pete4ducks/1364334188/
  25. 25. We decided to try it
  26. 26. What we got: • A seat at the standards table • Energized developers who are contributing and are known • A broad community to critique and help fix our stuff • Sun testing and marketing our stuff • Visibility for our brand • An intentionally commoditized, easy to adopt stack
  27. 27. rVooz.org
  28. 28. A few quick questions:
  29. 29. Q: Do you think the “open source community” owes you process compliance (and ear tags)?
  30. 30. Q: Have you ever attended an OSCON? BarCamp? Heck, even a Gartner open source conference?
  31. 31. Q: Do you think there is a moral / ethical dimension to the adoption of OSS in government? Are you prepared to work with people who do?
  32. 32. Q: Now that Gen Justice got you fired up about the value of community, where the heck are the communities?
  33. 33. Q: Are you prepared for the moment when open software, developed under government contract, is forked by the Chinese for their use?
  34. 34. Thanks! Jim Stogdill jstogdill@gestalt-llc.com www.limnthis.com

×