81
edits
Line 1: | Line 1: | ||
== History == | == History == | ||
I've been involved with the Jabber community since late 1999. I've been the [http://www.jabber.org/jeps/editor.shtml JEP Editor] since the JSF was founded in 2001 | I've been involved with the Jabber community since late 1999. I've been the [http://www.jabber.org/jeps/editor.shtml JEP Editor] since the JSF was founded in 2001, the JSF's Executive Director since 2002, and Chair of the Jabber Council for 2004-2005 and 2005-2006. | ||
== Contributions == | == Contributions == | ||
Line 9: | Line 9: | ||
== Sixth Council Priorities == | == Sixth Council Priorities == | ||
I think the Fifth Council (2005-2006) did a pretty good job. We didn't publish a lot of new protocols, but that's not necessarily a bad thing given the traditional cry of "too many JEPs". We still haven't replaced vcard-temp or finalized a protocol for end-to-end encryption (as described in my [http://wiki.jabber.org/index.php/Peter_Saint_Andre_for_Council_2005#Fifth_Council_Priorities 2005 priorities] but I think we're getting closer with our work on PEP. I'm confident we can finish many PEP payload formats this year, make good progress on the end-to-end encryption technology (JEP-0116), complete revisions to the XMPP RFCs at the IETF, and advance more JEPs from Draft to Final (e.g., JEP-0045 and JEP-0060). These efforts will provide strong foundations for further work. Also I would like to deprecate JEPs that people are not using (e.g., JEP-0013). | |||
== Why I'm Running Again == | == Why I'm Running Again == | ||
Once again I think it's important for the Council to publish and advance the right JEPs, not necessarily more JEPs. I'm running for Council again because I think I've done a good job of pushing the Council in 2004-2005 and 2005-2006, and I think I can do that again for 2006-2007. |
edits