Ian Paterson for Council 2006

History
I have been interested in Jabber since 1999 (thanks to Celso Martinho) and developing software for over twenty years (Jabber applications full-time since 2001). I became a member of the JSF Council in 2005.

JEPs
I am the primary author of the following "Draft" and "Experimental" JEPs: JEP-0059, JEP-0116 "Encrypted Sessions", JEP-0124 "HTTP Binding", JEP-0136 "Message Archiving", JEP-0158, JEP-0159, JEP-0187, JEP-0188 and JEP-0189.

I contribute to the development of many other protocols as a member of the JSF Council and by posting to the Standards-JIG mailing list (and occasionally to other lists).

Current Software Development Activities

 * Chatterbox fully-featured Web-client (I've pioneered AJAX applications since 1998)
 * BreakThru HTTP proxy server

I also manage a public Jabber server.

Qualifications

 * Experience (current council member)
 * Broad knowledge of JEPs, broad experience implementing (more than 30) and authoring (9) JEPs
 * Constant attention and regular contribution to the Standards-JIG mailing list (the community that guides such successful protocol development)
 * I'm prepared to disagree nicely, to challenge... but to stay open minded, and then accept consensus
 * Motivated to keep up the real momentum from last year
 * OCD ;)

Sixth Council Priorities and Ideas
Council members have very few extra powers to promote their priorities and ideas. The formal role of council members does not include deciding where protocol or software development efforts will be spent. The JSF rightly leaves that up to the authors. Most of the time the council simply guides protocol authors (like the Standards-JIG does, but with the added responsability for quality control).

In case you're interested, I would especially like to see authors/implementors (including myself) rapidly advancing:


 * e2e security
 * PEP service implementations (an essential building block for many protocols)
 * VoIP and video integration
 * Multi-user real-time XML document editing (including sync and whiteboard protocols)
 * Server-side message-archiving
 * Integration of Email functionality (so when users stop using email clients they won't loose features)
 * Private key availability (Aunt Tillie only)

General Emphasis

 * Pragmatic real-world (an advocate for users and developers)
 * Keep it simple and generally reusable
 * Do everything we can to encourage code development
 * Defend constrained clients (without compromising desktop clients)
 * Look after Aunt Tillie
 * Efficiency
 * Privacy/Security

Why I'm Running
I believe our developer community is lucky to have such an easy-to-follow and quickly-evolving set of protocol documentation. Through membership of the council, and in other (more significant) ways, I believe I've successfully contributed to that. If the JSF members would like me to, I am keen to continue that work.

Contact
If you'd like to discuss this application or anything else about Jabber with me, feel free to contact me. (JID: ian at zoofy.com)