Lunch talk at ASTAR

Lunch talk at ASTAR about open source and how best the researchers etc t ASTAR can participate.

Transcript

1. How Open Source Collaboration is Innovating the Future Harish Pillay Head, Community Architecture and Leadership Red Hat, hpillay@redhat.com September 19, 2014 A*STAR ITSS Lunchtime Seminar
2. How Open Source Collaboration is Innovating the Future – Now.
3. 3 <1>
4. 4 Why are you attending this session?
5. 5 What do you want out of this session?
6. 6 How Open are you?
7. 7 Open ____________
8. 8 Open Collaboration
9. 9 Open Communication
10. 10 Open Data
11. 11 Open Government
12. 12 Open Knowledge
13. 13 Open Mind
14. 14 Open Research
15. 15 Open Science
16. 16 Open Standards
17. 17 Open Source
18. 18 Open Parachute
19. 19 Huh?
20. 20 Parachutes are useful ONLY when OPEN
21. 21 What's keeping you from being OPEN?
22. 22 Default to Open* *http://tinyurl.com/ms9cuv6 - 26 minute video
23. 23 Truth Happens Video https://www.youtube.com/watch?v=5EkkMfjetEY
24. 24 What then is the magic of being OPEN?
25. 25 Simple: when things are open and inviting, people gather
26. 26 How Does Red Hat achieve OPEN?
27. 27 To be the catalyst in communities
28. 28 To be the catalyst in communities of customers, contributors, and
29. 29 To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way.
30. 30 To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. Red Hat's Mission Statement
31. 31 To be the catalyst in communities of customers, contributors, and partners creating better technology the open source way. Red Hat's Mission Statement
32. 32 TheOpenSourceWay.org
33. 33 The Open Source Connection Open source/free(dom) software happens because people are motivated by: - “scratch your own itch”
34. 34 The Open Source Connection Open source/free(dom) software happens because people are motivated by: - “scratch your own itch” - “I can do that”
35. 35 How Open Source Trumps Others ✔ Open source ensures the adoption of open standards
36. 36 How Open Source Trumps Others ✔ Open source ensures the adoption of open standards ✔ Open standards in turn ensure that when systems need to be fixed, it can be done
37. 37 How Open Source Trumps Others ✔ Open source ensures the adoption of open standards ✔ Open standards in turn ensure that when systems need to be fixed, it can be done ✔ This alone mitigates interoperability issues
38. 38 The Key Ideas ✔ Open Source
39. 39 The Key Ideas ✔ Open Source ✔ Open Standards
40. 40 The Key Ideas ✔ Open Source ✔ Open Standards ✔ Interoperability
41. 41 The Key Ideas ✔ Open Source ✔ Open Standards ✔ Interoperability ✔ Three essential conditions to ensure no lock-in and maximum choice
42. 42 A short story about security
43. 43 Security through obscurity
44. 44 Security through obscurity - your guarantee of #FAIL
45. 45 Content Scrambling System
46. 46 Over a couple of months in 1999, the DVD Association's “secure” code “Content Scrambling System” was broken
47. 47 for DVDs in Linux screw the MPAA and ; do dig $DVDs.z.zoy.org ; done | \ perl -ne 's/\.//g; print pack("H224", $1) if(/^x([^z]*)/)' | gunzip Source: http://decss.zoy.org/
48. 48 Many eyes make bugs shallow Linus Torvalds
49. 49 </1>
50. 50 <2>
51. 51 What Tools Should You Use?
52. 52 Collaborative Tools - git (gitlab/gitosis)
53. 53 Collaborative Tools - git (gitlab/gitosis) - wikis/markdown
54. 54 Collaborative Tools - git (gitlab/gitosis) - wikis/markdown - bugzilla
55. 55 Collaborative Tools - git (gitlab/gitosis) - wikis/markdown - bugzilla - irc/waartaa
56. 56 Collaborative Tools - git (gitlab/gitosis) - wikis/markdown - bugzilla - irc/waartaa - etherpad
57. 57 Collaborative Tools 100% Open Source Tools - git (gitlab/gitosis) - wikis/markdown - bugzilla - irc/waartaa - etherpad
58. 58 What do these offer you?
59. 59 Reproducibility of Research
60. 60 Is Publishing Papers a KPI?
61. 61 How would your work be assessed?
62. 62 How would your work be assessed? Independently?
63. 63 Ideas - Use tools whose code you can check - Digital Science www.digital-science.com - Run My Code www.runmycode.org - OpenShift www.openshift.com - Project Atomic www.projectatomic.io - PLOS www.plos.org - OpenSource.com www.opensource.com
64. 64 </2>
65. 65 <3>
66. 66 What about “Intellectual Property”?
67. 67 What about it?
68. 68 Copyrights, Patents and Trademarks
69. 69 Trademarks - by and large, no issue
70. 70 Copyrights - Use CreativeCommons.org
71. 71 Copyrights - Use CreativeCommons.org - General Public License etc for code
72. 72 Copyrights - Use CreativeCommons.org - General Public License etc for code - Check opensource.org for license options
73. 73 Patents - Patenting SOFTWARE is a HUGE problem https://www.eff.org/patent
74. 74 Patents - Patenting SOFTWARE is a HUGE problem https://www.eff.org/patent - Patents Stifle Innovation https://www.forbes.com/sites/danielfisher /2014/06/18/13633/
75. 75 Patents - Patenting SOFTWARE is a HUGE problem https://www.eff.org/patent - Patents Stifle Innovation https://www.forbes.com/sites/danielfisher /2014/06/18/13633/ - Beware of patent trolls http://www.thisamericanlife.org/radio- archives/episode/441/when-patents-attack
76. 76 What You Can Do Now - Set up an A-STAR wide: git repo and OpenShift PaaS - Encourage use of GPL and Creative Commons licenses - Release Early, Release Often - Fail Early, Fail Fast - Share like there's no tomorrow
77. 77 </3>
78. Agreements, Disagreements, Comments, Questions?
79. Thank you! Harish Pillay hpillay@redhat.com @harishpillay
80. 80 Go Have Your Lunch!