This was a presentation encouraging the ISO to consider using open source tools and techniques of collaboration to help with standards making globally.
Commons Attribution-ShareAlike 3.0 Unported License. Forget about eCommittees Harish Pillay ISO ITAG/JTC 1/Red Hat/ITSC Singapore ISO IT Forum Nov 29 - Dec 1 2011 Geneva
Commons Attribution-ShareAlike 3.0 Unported License. About me ➲ Member of ISO IT Advisory Group (ITAG) on behalf of JTC 1 ➲ $DayJob with Red Hat, based in Singapore ➲ $DayJob – Head, Community Architecture and Leadership – looking at the greater Free and Open Source community globally to encourage & nurture their growth ➲ Been in the IT industry for over 25 years ➲ Member of the Singapore IT Standards Committee (www.itsc.org.sg)
Commons Attribution-ShareAlike 3.0 Unported License. How does the Free and Open Source community collaborate? ➲ Default to open ➲ Transparency is central
Commons Attribution-ShareAlike 3.0 Unported License. How does the Free and Open Source community collaborate? ➲ Default to open ➲ Transparency is central ➲ Document everything
Commons Attribution-ShareAlike 3.0 Unported License. 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 – (like, but not only) IRC, etherpads, emails, wikis, blogs, bugzilla, git
Commons Attribution-ShareAlike 3.0 Unported License. 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 – (like, but not only) IRC, etherpads, emails, wikis, blogs, bugzilla, git ➲ Expect chaos initially – take baby-steps to build a community
Commons Attribution-ShareAlike 3.0 Unported License. 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 – (like, but not only) 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
Commons Attribution-ShareAlike 3.0 Unported License. The eCommittee ➲ Disclosure: I've 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.
Commons Attribution-ShareAlike 3.0 Unported License. The eCommittee ➲ Disclosure: I've 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 today's super- computers, stock exchanges, wifi routers, smart phones, smart TVs?
Commons Attribution-ShareAlike 3.0 Unported License. Obvious Questions ➲ Should the ISO be using technologies that are not open source? ➲ Would ISO be interested in creating an ecosystem of technologies that are 100% open source that can be proliferated globally for the greater benefit of society?
Commons Attribution-ShareAlike 3.0 Unported License. Obvious Questions ➲ Should the ISO be using technologies that are not open source? ➲ Would ISO be interested in creating an ecosystem of technologies that are 100% open source that can be proliferated globally for the greater benefit of society? ➲ Aren't distributed and federated systems bet- ter than centralized (as proposed by an audi- ence member this morning)?
Commons Attribution-ShareAlike 3.0 Unported License. Suggestions for 2015 ➲ Create data.iso.org ➲ Remove logins for people to get and mash up standards
Commons Attribution-ShareAlike 3.0 Unported License. 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
Commons Attribution-ShareAlike 3.0 Unported License. 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
Commons Attribution-ShareAlike 3.0 Unported License. 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., don't say “IP” if all that's meant is copyright.
Commons Attribution-ShareAlike 3.0 Unported License. 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 failure.