26
ISO/IEC JTC 1 This work is licensed under a Creative 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

Forget about-e committees

Embed Size (px)

DESCRIPTION

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

Citation preview

Page 1: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Forget about eCommittees

Harish PillayISO ITAG/JTC 1/Red Hat/ITSC Singapore

ISO IT ForumNov 29 - Dec 1 2011

Geneva

Page 2: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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 – 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)

Page 3: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

How does the Free and Open Source community collaborate?

Page 4: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Caveat:My suggestions and ideas might

annoy people

Page 5: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

A parachute works best when open – just as a mind and an organiza-

tion works best when open

Page 6: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

How does the Free and Open Source community collaborate?

➲ Default to open

Page 7: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

How does the Free and Open Source community collaborate?

➲ Default to open➲ Transparency is central

Page 8: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

How does the Free and Open Source community collaborate?

➲ Default to open➲ Transparency is central➲ Document everything

Page 9: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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 – IRC, etherpads, emails, wikis, blogs, bugzilla, git

Page 10: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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 – IRC, etherpads, emails, wikis, blogs, bugzilla, git

➲ Expect chaos initially – take baby-steps to build a community

Page 11: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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 – 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

Page 12: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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 – 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 governance

Page 13: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

The eCommittee

➲ Disclosure: I've not used it.

Page 14: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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.

Page 15: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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?

Page 16: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Obvious Questions

Page 17: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Obvious Questions

➲ Should the ISO be using technologies that are not open source?

Page 18: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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 ecosys-tem of technologies that are 100% open source that can be proliferated globally for the greater benefit of society?

Page 19: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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 ecosys-tem of technologies that are 100% open source that can be proliferated globally for the greater benefit of society?

➲ Aren't distributed and federated systems better than centralized (as proposed by an audience member this morning)?

Page 20: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Suggestions for 2015

➲ Create data.iso.org

Page 21: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Suggestions for 2015

➲ Create data.iso.org➲ Remove logins for people to get and mash up

standards

Page 22: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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

Page 23: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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

Page 24: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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.

Page 25: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative 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

Page 26: Forget about-e committees

ISO/IEC JTC 1This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Thank you.

[email protected]@redhat.com

@harishpillayharishpillay.wordpress.com