Tuesday, April 8, 2008

Last week during the Skunkworks Tuesday meeting at OPENWORLD we had a discussion around Technical Committees (TC) that are formed at KEBS to discuss various IT standards.

Special reference was made to the OOXML TC that was involved in the OOXML standard process in Kenya. What was clear from the discussion is that it is important to have more participation within these TCs from across the board. Some key advantages from this is that:

Kenya can begin to grow a IT standards professionals base, this is very critical

More objective review of various proposed standards from a local perspective which will limit unbalanced interference from big international vendors and interest

Kenya can define local standards (of course conforming to international standards where possible) for various things such a PCs, various software and hardware, etc. We stand a chance to thrive in international markets in terms of competitiveness and market penetration is we can base our products and services on verified and recognized standards. How can ensure that our local system builders/computer assemblers package standard PCs for example that meet government and corporate procurement standards..etc

Great opportunity for students/universities to link up with industry through active student engagement in the TCs with support from their professors; i must mention that there is always a sitting allowance of KES. 1,000 which is quite attractive if i were a student. But most importantly, one has the opportunity to gain indepth knowledge of various technology specifications. It is worth noting that students from other emerging parts of the world such as Western Europe, East Asia and Latin America are actively engaged in standard processes and are instrumental in these processes.

This will open up participation of Kenyan professionals to other standard creations processes such as IETF which hosts RFC development processes. Our own Michuki Mwangi has been part of this before and it would be great to have more guys joining RFC working groups.