Brunei-Smarter-Cities

Seminar in University of Brunei Darulsalaam about Smarter Cities. Talk is about Open Source in Government and about Open Data.

Transcript

1. OPEN SOURCE IN GOVERNMENT DEFAULT TO OPEN Harish Pillay Head, Community Architecture and Leadership @harishpillay • +65.9636.9253 • hpillay@redhat.com November 2014 https://speakerdeck.com/harishpillay/brunei-smarter-cities
2. PRESENTATION OBJECTIVES • Give you a comfort level that Open Source Solutions have become a game changer for: • Radically driving cost out of Government
3. PRESENTATION OBJECTIVES • Give you a comfort level that Open Source Solutions have become a game changer for: • Radically driving cost out of Government • Providing government the platform to deliver innovation and to be more agile in delivering new services to constituents
4. PRESENTATION OBJECTIVES • Give you a comfort level that Open Source Solutions have become a game changer for: • Radically driving cost out of Government • Providing government the platform to deliver innovation and to be more agile in delivering new services to constituents • Educate you on the overall open source objectives and provide you strategies to leverage Open Source safely in your organizations
5. PRESENTATION OBJECTIVES • Give you a comfort level that Open Source Solutions have become a game changer for: • Radically driving cost out of Government • Providing government the platform to deliver innovation and to be more agile in delivering new services to constituents • Educate you on the overall open source objectives and provide you strategies to leverage Open Source safely in your organizations • Point you to some resources where you can learn more
6. “In production and development, open source as a development model promotes a universal access via a free license to a product's design or blueprint, and universal redistribution of that design or blueprint, including subsequent improvements to it by anyone.”
7. “Open source software is software that can be freely used, changed, and shared (in modified or unmodified form) by anyone. Open source software is made by many people, and distributed under licenses that comply with the Open Source Definition.”
8. THE OPEN SOURCE WAY • Create. • When we are free to collaborate, we create and solve problems that no one person may be able to solve on their own
9. THE OPEN SOURCE WAY • Create. • When we are free to collaborate, we create and solve problems that no one person may be able to solve on their own • Share. • We learn more from each other when information is open
10. THE OPEN SOURCE WAY • Create. • When we are free to collaborate, we create and solve problems that no one person may be able to solve on their own • Share. • We learn more from each other when information is open • Collaborate. • Through “meritocracy”, the best ideas win • Through Communities formed around a common purpose
11. THE OPEN SOURCE WAY • Create. • When we are free to collaborate, we create and solve problems that no one person may be able to solve on their own • Share. • We learn more from each other when information is open • Collaborate. • Through “meritocracy”, the best ideas win • Through Communities formed around a common purpose • Let everyone else do the same. Source: https://opensource.com/open-source-way
13. OPEN SOURCE IS EATING THE SOFTWARE WORLD* http://www.slideshare.net/blackducksoftware/the-2013-future-of-open-source-survey-results
14. IT STARTS WITH AN IDEA Community Project Idea 1M +
15. HOW THE COMMUNITY WORKS
16. THE TOOLS CODE REPOSITORY MAILING LIST One for developers. One for users. One for casual watchers. The heart of the project. A complete history of all changes. Anyone can read, only committers can write. The to-do list. Where users and developers interact. Where you’ll learn why a change was made. ISSUE TRACKER
17. THE WORKFLOW Large Communities will have Governance Policies posted on their website
18. LICENSING IS CRUCIAL • Licensing creates the community • It tells how contributions are handled
19. LICENSING IS CRUCIAL • Licensing creates the community • It tells how contributions are handled • Licensing determines the business model • If you compel source distribution, how do you build a business?
20. LICENSING IS CRUCIAL • Licensing creates the community • It tells how contributions are handled • Licensing determines the business model • If you compel source distribution, how do you build a business? • Licensing should be easy • If it’s too complicated, you lose contributors
21. LICENSING IS CRUCIAL • Licensing creates the community • It tells how contributions are handled • Licensing determines the business model • If you compel source distribution, how do you build a business? • Licensing should be easy • If it’s too complicated, you lose contributors • Most Open Source software is delivered under the GPL (GNU Public License) • You may copy, distribute, and modify the software as long as you track changes in source files and keep modifications under GPL. • You can distribute your application using a GPL Library commercially, but you must open source/disclose the source code
22. OPEN SOURCE LICENSING MUST BE FLEXIBLE
23. WHO PARTICIPATES IN PROJECTS? EXAMPLE: LINUX KERNEL Source: The Linux Foundation Linux Kernel Development March 2012 (Pages 10-11) RED HAT INTEL NOVELL IBM TEXAS INSTRUMENTS CONSULTANTS BROADCOM NOKIA SAMSUNG ORACLE GOOGLE WOLFSON MICROELECTRONICS AMD FUJITSU PENGUTRONIX ATHEROS COMMUNICATIONS FREESCALE MICROSOFT ST ERICSSON WIND RIVER MITAC SFR ANALOG DEVICES TGLX PITA LINARO QLOGIC MARVELL Corporate Contributions to Linux (SINCE KERNEL 2.6.36) 0% 2% 4% 6% 8% 10% 12% COMPANY / ORGANIZATION * * the developers who are known to be doing this work on their own, with no financial contribution happening from any company' are not grouped together as 'None' and instead are considered part of the 'long tail,' as are contributors of academic or unknown sponsorship. 'LONG TAIL' OF CONTRIBUTORS
24. WHO PARTICIPATES IN PROJECTS? EXAMPLE: OPENSTACK Source: Bitergia http://activity.openstack.org/dash/releases/index.html?data_dir=data/icehouse Top Contributors to Icehouse Release 0 500 1000 1500 2000 2500 3000 3500 Red Hat IBM HP Rackspace Mirantis SUSE OpenStack Foundation eNovance Intel 0 50 100 150 200 250 300 350 400 Red Hat Others HP Mirantis IBM Rackspace Canonical OpenStack Foundation Dreamhost • Overall commits per company (aggregated) • Closed Tickets per company (aggregated) Learn more about projects, communities, and contributors - Check out: https://www.openhub.net/
25. THE FARM TEAM: USING THE LONG TAIL OF DEVELOPERS
26. BENEFITS OF OPEN SOURCE TO AN ORGANIZATION • Shared development = accelerated innovation • Open collaboration = products that meet customer needs • Themes: • Better price/performance (the bits are free!) • Faster technology innovation • Better quality & reliability
27. CHALLENGES OPEN COLLABORATION IS SOLVING Security & Quality Reduce Costs Deliver Cloud Deliver Big Data Interoperability
28. PRIORITIZING OPEN SOURCE PROJECTS Operating System 1 Development Tools 2 Cloud 3 Content Management 4 Mobile 5 Database 6 Big Data 7 Source: 2013 The Future of Open Source Conference – Black Duck
29. HOW DO YOU GET AN ENTERPRISE CLASS SUPPORTED OPEN SOURCE SOLUTION?
30. OPEN SOURCE IS RAPID INNOVATION
31. MODULARITY DRIVES INNOVATION "a change to one element in Mozilla is likely to impact three times as many other elements as a similar change in Linux. We conclude that the first version of Mozilla was much less modular than a comparable version of Linux." MacCormack, Rusnak, and Baldwin. “Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary Code” http://opensource.mit.edu/papers/maccormackrusnakbaldwin2.pdf
32. MODULARITY DRIVES INNOVATION “Mozilla, after its release as open source, was rapidly and successfully redesigned to become much more modular - at least as modular as Linux, in fact.... the differences in code appear to result from differences in organization.” Nick Carr, http://www.roughtype.com/archives/2006/01/open_sources_du.php
33. OPEN SOURCE: COMMUNITIES vs. COMPANIES Community  Innovation  Rapid Development  Embracing Risk  Money is Scarce  Highly Collaborative  Exciting Companies  Stability  Change Management  Mitigating Risk  Time is Scarce  Somewhat Collaborative  Not as Exciting
34. COMPANY PRODUCT PROCESS UP AND DOWNSTREAM INVOLVMENT We enable software & hardware partners, customers, and academia to participate at every stage of development. 100,000+ PROJECTS Participate in & create community- powered upstream projects. PARTICIPATE INTEGRATE STABILIZE (upstream projects) (community platforms) (supported products platforms, & solutions) Integrate upstream projects, fostering open community platforms. Commercialize these platforms together with a rich ecosystem of services & certifications.
35. WHAT TO LOOK FOR FROM AN OPEN SOURCE PROVIDER 1. Multiple levels of technical support - based on your needs 2. Government certifications (e.g. NIAP/Common Criteria, FIPS 140-2, etc.) 3. Product support and stability for many years (7-10 minimum) 4. Best practices for life cycle management (for major/minor releases) 5. Timely delivery of: Updates, Patches, Security Fixes, Upgrades 6. Security Response Team 7. Training and Implementation Services 8. Software Assurance 9. Size and scale of the ISV/IHV ecosystem 10.Asset Management/Tracking
36. FORKS AND DERIVATIVES CAN BE CHALLENGING FOR THE UNINITIATED
37. FOR EXTERNAL USE | PAUL PINKNEY 27 OPEN SOURCE EVERYWHERE
38. PUBLIC MATERIAL | GUNNAR HELLEKSON 28
39. PUBLIC MATERIAL | GUNNAR HELLEKSON 29
40. PUBLIC MATERIAL | GUNNAR HELLEKSON 30
41. MOBILE PHONES
42. STOCK EXCHANGES
43. AUTOMOBILES
44. WEATHER
45. AIRPLANES
46. RESOURCES: OPEN SOURCE STRATEGY FOR GOVERNMENT ORGANIZATIONS • Open Source for America • http://opensourceforamerica.org/ • Helps government and industry use and make open source together.
47. RESOURCES: OPEN SOURCE STRATEGY FOR GOVERNMENT ORGANIZATIONS • Open Source for America • http://opensourceforamerica.org/ • Helps government and industry use and make open source together. • CivicCommons • http://civiccommons.org/ • Building an open source government stack.
48. RESOURCES: OPEN SOURCE STRATEGY FOR GOVERNMENT ORGANIZATIONS • Open Source for America • http://opensourceforamerica.org/ • Helps government and industry use and make open source together. • CivicCommons • http://civiccommons.org/ • Building an open source government stack. • Mil-OSS • http://mil-oss.org/ • DoD and intelligence open source advocates.
49. RESOURCES: OPEN SOURCE STRATEGY FOR GOVERNMENT ORGANIZATIONS • Stormy's Policy Guide • http://olex.openlogic.com/wazi/2009/create-open-source-policy/ • A great walk through of policy creation.
50. RESOURCES: OPEN SOURCE STRATEGY FOR GOVERNMENT ORGANIZATIONS • Stormy's Policy Guide • http://olex.openlogic.com/wazi/2009/create-open-source-policy/ • A great walk through of policy creation. • Linux Foundation and Foss Bazaar • http://www.linuxfoundation.org/programs/legal/compliance • https://fossbazaar.org/ • http://fossology.org • A project to simplify open source policies.
51. RESOURCES: OPEN SOURCE STRATEGY FOR GOVERNMENT ORGANIZATIONS • Stormy's Policy Guide • http://olex.openlogic.com/wazi/2009/create-open-source-policy/ • A great walk through of policy creation. • Linux Foundation and Foss Bazaar • http://www.linuxfoundation.org/programs/legal/compliance • https://fossbazaar.org/ • http://fossology.org • A project to simplify open source policies. • Code for America • http://codeforamerica.org
52. RESOURCES: OPEN SOURCE STRATEGY FOR GOVERNMENT ORGANIZATIONS • Stormy's Policy Guide • http://olex.openlogic.com/wazi/2009/create-open-source-policy/ • A great walk through of policy creation. • Linux Foundation and Foss Bazaar • http://www.linuxfoundation.org/programs/legal/compliance • https://fossbazaar.org/ • http://fossology.org • A project to simplify open source policies. • Code for America • http://codeforamerica.org • BarCamp – unconference bringing developers together • http://barcamp.org
53. CLOSING • Open Source Software can help Government lower costs and deliver innovation to constituents • Cloud, Big Data, Application Integration/Development Tools to name a few...
54. CLOSING • Open Source Software can help Government lower costs and deliver innovation to constituents • Cloud, Big Data, Application Integration/Development Tools to name a few... • Government and Enterprise will need support from Open Source Providers – Consider all the factors
55. CLOSING • Open Source Software can help Government lower costs and deliver innovation to constituents • Cloud, Big Data, Application Integration/Development Tools to name a few... • Government and Enterprise will need support from Open Source Providers – Consider all the factors • How will you embrace Open Source? • Do you have an Open Source Strategy & Policy?
56. CLOSING • Open Source Software can help Government lower costs and deliver innovation to constituents • Cloud, Big Data, Application Integration/Development Tools to name a few... • Government and Enterprise will need support from Open Source Providers – Consider all the factors • How will you embrace Open Source? • Do you have an Open Source Strategy & Policy? • The successful adoption of any technology relies on skilled people and appropriate process • Open Source solutions can help Government be more agile
57. Replace slide headline here Comments? Harish Pillay hpillay@redhat.com @harishpillay
58. MYTHS OF OPEN SOURCE 1. It's a Linux-vs-Windows thing. 2. Open source is not reliable or supported. 3. Big companies don't use open source. 4. Open source is hostile to intellectual property. 5. Open source is all about licenses. 6. If I give away my software to the open source community, thousands of developers will suddenly start working for me for nothing. 7. Open source only matters to programmers, since most users never look under the hood anyway. 8. The open source movement is not sustainable, since people will stop developing free software once they see others making lots of money from their efforts. 9. Open source is playing catch-up to Microsoft and the commercial world. MYTHS BUSTED