Your SlideShare is downloading. ×
Forget about-e committees
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Forget about-e committees

520

Published on

Presentation at the ISO IT Forum in Geneva on November 29, 2011

Presentation at the ISO IT Forum in Geneva on November 29, 2011

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

  • Be the first to like this

No Downloads
Views
Total Views
520
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Forget about eCommittees Harish Pillay ISO ITAG/JTC 1/Red Hat/ITSC Singapore ISO IT Forum Nov 29 - Dec 1 2011 GenevaISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 2. About me ➲ Member of ISO IT Advisory Group (ITAG) on behalf of JTC 1 ➲ $DayJob with Red Hat, based in Singapore ➲ $DayJob – Global Head, Community Archi- tecture and Leadership – looking at the greater Free and Open Source community globally to encourage & nurture their growth ➲ Been in the IT industry for over 20 years ➲ Member of the Singapore IT Standards Committee (www.itsc.org.sg)ISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 3. How does the Free and Open Source community collaborate?ISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 4. Caveat: My suggestions and ideas might annoy peopleISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 5. A parachute works best when open – just as a mind and an organiza- tion works best when openISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 6. How does the Free and Open Source community collaborate? ➲ Default to openISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 7. How does the Free and Open Source community collaborate? ➲ Default to open ➲ Transparency is centralISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 8. How does the Free and Open Source community collaborate? ➲ Default to open ➲ Transparency is central ➲ Document everythingISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 9. How does the Free and Open Source community collaborate? ➲ Default to open ➲ Transparency is central ➲ Document everything ➲ Use only standards based tools to collabo- rate – IRC, etherpads, emails, wikis, blogs, bugzilla, gitISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 10. How does the Free and Open Source community collaborate? ➲ Default to open ➲ Transparency is central ➲ Document everything ➲ Use only standards based tools to collabo- rate – IRC, etherpads, emails, wikis, blogs, bugzilla, git ➲ Expect chaos initially – take baby-steps to build a communityISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 11. How does the Free and Open Source community collaborate? ➲ Default to open ➲ Transparency is central ➲ Document everything ➲ Use only standards based tools to collabo- rate – IRC, etherpads, emails, wikis, blogs, bugzilla, git ➲ Expect chaos initially – take baby-steps to build a community ➲ Do not be afraid to invite people to partici- pateISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 12. How does the Free and Open Source community collaborate? ➲ Default to open ➲ Transparency is central ➲ Document everything ➲ Use only standards based tools to collabo- rate – IRC, etherpads, emails, wikis, blogs, bugzilla, git ➲ Expect chaos initially – take baby-steps to build a community ➲ Do not be afraid to invite people to partici- pate ➲ Build on concensus and good governanceISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 13. The eCommittee ➲ Disclosure: Ive not used it.ISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 14. The eCommittee ➲ Disclosure: Ive not used it. ➲ Are there alternatives to OpenText? Yes, plenty. And a lot of them are free & open source versions like Drupal.org for example.ISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 15. The eCommittee ➲ Disclosure: Ive not used it. ➲ Are there alternatives to OpenText? Yes, plenty. And a lot of them are free & open source versions like Drupal.org for example. ➲ How does the FOSS world collaborate to build technology that powers todays super- computers, stock exchanges, wifi routers, smart phones, smart TVs?ISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 16. Obvious QuestionsISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 17. Obvious Questions ➲ Should the ISO be using technologies that are not open source?ISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 18. Obvious Questions ➲ Should the ISO be using technologies that are not open source? ➲ Would ISO be interested in creating an ecosys- tem of technologies that are 100% open source that can be proliferated globally for the greater benefit of society?ISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 19. Obvious Questions ➲ Should the ISO be using technologies that are not open source? ➲ Would ISO be interested in creating an ecosys- tem of technologies that are 100% open source that can be proliferated globally for the greater benefit of society? ➲ Arent distributed and federated systems better than centralized (as proposed by an audience member this morning)?ISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 20. Suggestions for 2015 ➲ Create data.iso.orgISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 21. Suggestions for 2015 ➲ Create data.iso.org ➲ Remove logins for people to get and mash up standardsISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 22. Suggestions for 2015 ➲ Create data.iso.org ➲ Remove logins for people to get and mash up standards ➲ If ISO is to remain relevant, it has to drastically change the business model and let “citizen-led standards making” take rootISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 23. Suggestions for 2015 ➲ Create data.iso.org ➲ Remove logins for people to get and mash up standards ➲ If ISO is to remain relevant, it has to drastically change the business model and let “citizen-led standards making” take root ➲ Does not negate need for national standards bodies or the very important role of experts – cf. success and accuracy of wikipediaISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 24. Suggestions for 2015 ➲ Create data.iso.org ➲ Remove logins for people to get and mash up standards ➲ If ISO is to remain relevant, it has to drastically change the business model and let “citizen-led standards making” take root ➲ Does not negate need for national standards bodies or the very important role of experts – cf. success and accuracy of wikipedia ➲ Adopt Creative Commons licensing as the standard, i.e., dont say “IP” if all thats meant is copyright.ISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 25. Some observations II ➲ Multi-lingual: transifex.net ➲ Standard wiki with locking – available today al- ready – perhaps etherpad and drupal ➲ Can OpenText be run on a federated/distributed manner? ➲ Using the Cloud – Google Docs/Calendar. Note the lack of distributed environments – single point of failureISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
  • 26. Thank you. h.pillay@ieee.org hpillay@redhat.com @harishpillay harishpillay.wordpress.comISO/IEC JTC 1 This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

×