Open Source Training

821 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
821
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Open Source Training

  1. 1. How and Why to BringOpen Source to Your Agency February 24, 2011 Brought to you by:
  2. 2. Today’s SpeakersSteve ResslerPresident and FounderGovLoopAndrew HoppinFormer CIO NY State SenatePartner, New Amsterdam IdeasJohn ScottSteering Committee MemberOpen Source for AmericaGunnar HelleksonChief Technology StrategistRed Hat Public Sector Group
  3. 3. Housekeeping• Twitter Hash Tag: #gltrain• At any time during the next hour, if you would like to submit a question, just look for the "Ask a question" console. The presenters will field your questions at the end.• If you have any technical difficulties during the Webinar, click on the Help button located below the slide window and you’ll receive technical assistance.• And finally, after this session is complete, we will be e- mailing you a link to the archived version of this Webinar, so you can view it again or share it with a colleague and a GovLoop training certificate.
  4. 4. Doing More With Le$$:Open-Source in New York State Government Andrew Hoppin NY State Senate CIO 1/09-1/11 @ahoppin
  5. 5. Challenge at NYS Senate in 2009:Government 1.965, not Government 2.00x http://flickr.com/photos/rocketqueen/1573565705/
  6. 6. News “Clips” ($1.5MM/year) http://flickr.com/photos/rocketqueen/1573565705/
  7. 7. Constituent Relationship Management (CRM) http://flickr.com/photos/rocketqueen/1573565705/
  8. 8. Senate.State.NY.UShttp://flickr.com/photos/rocketqueen/1573565705/
  9. 9. Better Laws, Governmenthttp://flickr.com/photos/rocketqueen/1573565705/ $ Less
  10. 10. Why An Open-Source CMS?• Needed a true CMS – hundreds of content creators on staff• Preference for Open-Source – avoid license fees – choice of consultants – ability to bring development in-house• Comfort with Open-Source – range of mature platforms in use by large enterprise – availability of professional support• Ability to Collaborate with Government Peers – Share code, roadmap, etc.
  11. 11. Why Drupal?• Considered Joomla, Django, Drupal and Wordpress• Selected Drupal based on: – widespread use in public sector (gov’t & NGOs) – module feature set for constituent use cases – local availability of PHP/MySQL talent – maturity of consultant and developer community – trajectory of the platform since 2004
  12. 12. Development Process• Contracted outside consulting firm for – requirements gathering – design – coding – hosting• *During* external development, hired – one in-house developer – one project manager – existing in-house staff for training & QA• Deployed 3.5 months after project start – one programmer – one project manager – leveraged in-house staff for training – hundreds of bugs and features implemented since
  13. 13. NYSenate.govhttp://flickr.com/photos/rocketqueen/1573565705/
  14. 14. Microsites for Senatorshttp://flickr.com/photos/rocketqueen/1573565705/
  15. 15. Microsites for Committeeshttp://flickr.com/photos/rocketqueen/1573565705/
  16. 16. Open Administrative Data
  17. 17. Calendars
  18. 18. Committee Eventshttp://flickr.com/photos/rocketqueen/1573565705/
  19. 19. …Content to the Cloud http://flickr.com/photos/rocketqueen/1573565705/
  20. 20. NYSenate.govhttp://flickr.com/photos/rocketqueen/1573565705/
  21. 21. Open Legislative Data
  22. 22. News 2.0
  23. 23. New CRMhttp://flickr.com/photos/rocketqueen/1573565705/
  24. 24. NY Senate Mobilehttp://flickr.com/photos/rocketqueen/1573565705/
  25. 25. Releasing Our Code on GitHub http://flickr.com/photos/rocketqueen/1573565705/
  26. 26. Open-Source Distinctions• Software Stack on which we build and host applications • Linux, Apache, MySQL, PHP, Java, Android, Xen, etc.•Tools We Use to Support Building Applications: • Git / Subversion, Redmine / Trac / Bugzilla, Eclipse IDE, etc.•New Applications We Build and Release as Open-Source: • e.g.: NYSenate Open Legislation, SAGE Geo Web Service•Open-Source Platforms We Leverage, Customize and Extend • e.g.: Drupal, MediaWiki, Wordpress, CiviCRM, GeoServer
  27. 27. Open Standards, Formats, APIs for Interoperability, Shared Services• e.g.: XML, JSON, .ODF, .JPG, .CSV, RDF• e.g.: SOAP, REST APIs http://flickr.com/photos/rocketqueen/1573565705/
  28. 28. …Open APIs, Open Standardshttp://flickr.com/photos/rocketqueen/1573565705/
  29. 29. OPEN Data
  30. 30. Open-Source Software for Collaboration & Cost Savings“More and more we are seeing the federal government move towards open sourcedue to its increased security, reduced procurement times, large scalability...reducedcost to the taxpayers, and escape from vendor lock-in…Open source will just continue to grow as the world moves to open storage (low-cost hardware with open-source storage management software that makes itperform as well as high-cost proprietary storage devices), open network (low-costhardware with open-source VoIP, routing, and switching software that make itperform as well as high-cost proprietary network devices) and open-sourcevirtualization (xVM and Xen cloud computing without the cost of proprietaryvirtualization and management software) -Bill Vass, COO Sun Microsystems Federal, former CTO US Pentagon
  31. 31. Recent Press•CIO Magazine: “The Recession will lead CIO’sto move to open source”•eWeek: “10 things IT organizations will doduring the recession… #1 Move to OpenSource”•Government Computer News: DefenseAppropriations language advocates a move toOpen Source”
  32. 32. Social Web Adoption Socialize It: CapitolCamp II, August ‘10http://flickr.com/photos/rocketqueen/1573565705/
  33. 33. Rationale•Cost Savings (no license fees)•Innovation (leverage community-built software)•Speed to Deployment (reduced procurement times,clone product a peer has created, etc.)•No Vendor Lock-In (hire anyone to work on it)•Recruit Talent (top developers like to work with F/OSS)•Leverage Tax Dollars (share our code to benefitothers)•Security: see the source code, fix bugs yourself•Supported: Red Hat, IBM, Sun, Acquia, Kitware, etc.
  34. 34. Social Web Adoption Collaborate Across Virtual Geographies …… Federal Missouri California Vermont Indiana NYSenate Judiciary Executive Assembly Citizens Civil Servants Elected Officials Rochester Businesses Troy NYCInterest Groups http://flickr.com/photos/rocketqueen/1573565705/
  35. 35. Followup Twitter.com/ahoppin Twitter.com/NYSenateCIONYSenate.gov/department/cioHoppin@Senate.State.NY.USCiodesk@Senate.State.NY.US
  36. 36. How & Why to bring Open Source to Your AgencyJohn Scott, RadiantBlue Technologies, Inc.jscott@radiantblue.comjms3rd@gmail.com@johnmscottFebruary 24, 2011
  37. 37. Open Source: Freedom (and Control) Enjoy to Savings RadiantBlue Technologies Inc.25 February 2011 38
  38. 38. UNCLASSIFIED Software becomes a CommodityRef: Commodification of Industrial Software: A Case for Open Source, July/August 2009 IEEE Software RadiantBlue Technologies Inc. Proprietary www.RadiantBlue.com UNCLASSIFIED 39 25 February 2011
  39. 39. UNCLASSIFIED Example SavingsSource: OSDL, Stuart Cohen, GOSCON 2007 RadiantBlue Technologies Inc. Proprietary 40 www.RadiantBlue.com UNCLASSIFIED 40 25 February 2011
  40. 40. 41
  41. 41. 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 different business models, that monetize the software using different strategies. Gartner Group, “Open source going mainstream,” 2006 RadiantBlue Technologies Inc.25 February 2011 42
  42. 42. RadiantBlue Technologies Inc.25 February 2011 43
  43. 43. Open Open Gov DoD: Clarifying Guidance Regarding Open Source Software16 October 2009 RadiantBlue Technologies Inc.25 February 2011 44
  44. 44. OSFA Reportcard RadiantBlue Technologies Inc.25 February 2011 45
  45. 45. RadiantBlue Technologies Inc.25 February 2011 46
  46. 46. Military & Openness Problem Opportunity • DoD „hostage‟ to legacy, proprietary • Agility components  Faster development Time is a significant driver –  Faster deployment: need to have sometimes forced to „re-engineer‟ impact during fight the solution created decades ago  Better transition • Interoperability issues: Services, • Decrease likelihood for vendor lock-in commands and systems • Potentially lower costs • Greater interoperability • Increasing complexity of code • Knowledge capture • We develop code that isn‟t readily accessible or reusable • Communities around capabilities • Software process model • Development/maintenance costs outweigh COTS costs • Timely delivery of new solutions • Keeping up with innovation/change25 February 2011 “The OODA loop for software deployment must decrease” RadiantBlue Technologies Inc. 47 47
  47. 47. RadiantBlue Technologies Inc.25 February 2011 48
  48. 48. www.Mil-OSS.org RadiantBlue Technologies Inc.25 February 2011 49
  49. 49. Open Source OptionOpen 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 RadiantBlue Technologies Inc.25 February 2011 50
  50. 50. Backup RadiantBlue Technologies Inc.25 February 2011 51
  51. 51. RadiantBlue Technologies Inc.25 February 2011 52
  52. 52. Open Source Strategy for Governments Freedom may not be free, but its totally worth it. Gunnar Hellekson Chief Technology Strategist, Red Hat US Public Sector gunnar.hellekson@redhat.com · 202 507 9027 · @ghelleks 24 February 2011
  53. 53. Three PhasesUse.Participate.Create.
  54. 54. Red Hats Packaging Problem
  55. 55. Use.
  56. 56. Participate.
  57. 57. Create.
  58. 58. Use.
  59. 59. Open Source = Commercial Software Its special, but its not that special.In most cases, the existing procurement rules are fine:It must fulfill your needs.You need support.You need an exit strategy.Someone is in charge. Open source must win in a fair fight. http://www.blackducksoftware.com/oss/licenses
  60. 60. The Support Question Dont assume proprietary advantages.You will always have support when you need it.If you report a bug, it will always be fixed promptly.That company will always be in business.They will never change their business model.They will always support the product.The original developer will always work here.You will always have great documentation. – Deb Bryant, OSU Open Source Lab
  61. 61. The Support Question Be aware of open source advantages.You can always pay for support when you need it.If you find a bug, it can be fixed.You dont rely on one company.You dont worry about new business models.You dont need the original developer.Open standards make integration easier.
  62. 62. The Support Question Self-support?Who will support unsupported software?What risks are you willing to assume?When will you require a support contract?Who says yes?
  63. 63. Review the Licenses.What terms are you willing to accept? http://www.blackducksoftware.com/oss/licenses
  64. 64. OMBhttp://www.cio.gov/documents/Technology-Neutrality.pdf “...evaluation processes that promote procurement choices based on performance and value, and free of preconceived preferences based on how the teclmology is developed, licensed or distributed... This allows the Government to pursue the best strategy to meet its particular needs.” “Technology Neutrailty Memo”
  65. 65. SFhttp://www.sfgov.org/site/coit_page.asp?id=115978 “The Software Evaluation Policy will require departments to consider open source alternatives, when available, on an equal basis to commercial software, as these may reduce cost and speed the time needed to bring software applications to production.”
  66. 66. Participate.
  67. 67. How Can I Participate? “Whos in charge here?” Can staff participate on lists? Can they use their work email? Who can submit bug reports? Who can submit feature requests? What does an endorsement looklike? Image: "Working together..." (http://www.flickr.com/photos/lollyman/4424552903/) used under the Creative Commons CC-BY-NC-ND-2.0 license, image from lollymans photostream
  68. 68. SCAP.
  69. 69. Create.
  70. 70. How Can We Release Code? Pitching in.Who decides what will be open source?When does it make sense?What license will you use?What kind of review process is necessary?Whos involved in the review?Whos the maintainer?Where do I track whats been opened? Image: "Lego Construction Worker" (http://www.flickr.com/photos/wannawork/2098315714 /) used under the Creative Commons CC-BY-NC-SA- 2.0 license, image from wannaworks photostream
  71. 71. DODhttp://cio-nii.defense.gov/docs/OpenSourceInDoD.pdf
  72. 72. YOU ARE HERE
  73. 73. Audience Q&A
  74. 74. Today’s SpeakersSteve ResslerPresident and FounderGovLoopAndrew HoppinFormer CIO NY State SenatePartner, New Amsterdam IdeasJohn ScottSteering Committee MemberOpen Source for AmericaGunnar HelleksonChief Technology StrategistRed Hat Public Sector Group
  75. 75. Thank You! To continue the discussion visit theOpen Source Software in Government Group on GovLoop at: http://www.govloop.com/group/OSSinGov

×