Even Westvang: Open developments (Webdagene 2014)
•
1 like•786 views
This document discusses the benefits of using APIs and open source software in government projects. It argues that APIs allow flexibility, reduce costs by enabling modular development, and improve user experiences by integrating services across platforms. Open source is also advocated for to facilitate collaboration, avoid vendor lock-in, and enable other governments to reuse solutions. The document provides examples from the US and Norway and recommends that new government software retain rights to code, apply open source licensing, and publish reusable components.
Report
Share
Even Westvang: Open developments (Webdagene 2014)
- 1. Open developments a short talk in 2 parts EVEN WESTVANG BENGLER.NO @even *
- 2. pt.1 “my software has something to discuss with your software” EVEN WESTVANG BENGLER.NO @even
- 6. Public Agency Even Service
- 7. Even Public Agency Even Service
- 8. And then next year… Even Public Agency Even Service
- 9. Even
- 11. Dude. It works like this _inside_ the public sector too.
- 12. Dude. It works like this _inside_ the public sector too. Public Agency Public Agency Public Agency Service
- 13. Depressingly, more often like this… $$$$ Even & Public agency Consultant
- 14. This is not how you save resources with ICTs. ! This is just nuts.
- 15. You fix stuff like this by building APIs
- 16. API? Application programming interface – Computers talking to each other WEB API? Computers talking to each other on the internet !
- 17. APIs allows an organization to contribute value wherever it is most useful ! Without necessarily knowing about it
- 18. API Internet People + +
- 20. Why APIs ! example #1 flexibility & cost
- 21. Portal Desktop
- 22. Portal Desktop Mobile App ? WOT
- 23. API + Portal Desktop Mobile App + Other systems
- 24. Why APIs ! example #2 User Experience
- 25. “USER CENTERED” SERVICES WITHOUT APIs PORTAL PORTAL PORTAL
- 26. “USER CENTERED” SERVICES WITHOUT APIs PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL
- 27. PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL Oh right, I only need to go over here to do this.
- 28. ÆÆÆÆ #FAIL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL PORTAL Oh right, I only need to go over here to do this.
- 29. Apps for parents - Avtaler med sykehus - Barnemat-oppskrifter - Levering av skjemaer til NAV - Avtaler med helsestasjon - Finn & Søk barnehager - Symptomkartlegning av barnesykdommer - Klovneutleie ! API API API API
- 30. SIMPLE, FOCUSED SERVICES API API API API
- 32. OPEN DATA OPEN ARCHITECTURE
- 33. USA Mai 2009 Data.gov – inspiration for data.norge.no April 2011 Executive Order 13571 – Streamlining Service Delivery and Improving Customer Service ! HTTP://WWW.GPO.GOV/FDSYS/PKG/FR-2011-05-02/PDF/2011-10732.PDF HTTP://WWW.WHITEHOUSE.GOV/SITES/DEFAULT/FILES/OMB/EGOV/DIGITAL-GOVERNMENT/DIGITAL-GOVERNMENT-STRATEGY.PDF To establish a “new default,” the policy will require that newly developed IT systems are architected for openness and expose high-value data and content as web APIs …
- 34. So when you build new infrastructure Expose high-value data as APIs Document your APIs Make public APIs available without paperwork Implement own website on top of APIs MUST MUST MUST SHOULD
- 35. pt.2 why, oh why, build the same wheel over and over again? EVEN WESTVANG BENGLER.NO @even
- 36. The curious perception of OPEN SOURCE in the public sector
- 38. In 2014…
- 48. So why do private companies share their source code?
- 49. To be nice?
- 51. No. Facebook’s value is not tied to the software components that make up facebook.com ! It’s simply a win for Facebook if anyone uses their software and helps make it better.
- 52. WHY SHOULD THE PUBLIC SECTOR CARE? • Lots of shared concerns • Accelerated development • Collaborate with others while preserving local concerns • Escape vendor lock-in • Save on licenses • Public enrichment
- 56. Just wonderful • No open process • No reusable solutions • No open source • 124m should deliver a bunch of open technologies that other Norwegian municipalities could reuse
- 65. So when you build new software Retain rights to code Publish and apply FOSS licensing to it Publish components as FOSS SHOULD SHOULD MUST
- 66. Two principles, both multipliers Architecture Reuse APIs Open Source
- 67. developments * Open EVEN WESTVANG BENGLER.NO @even