Changes

Jump to navigation Jump to search
m
Line 7: Line 7:     
== Jabber/XMPP Activities ==
 
== Jabber/XMPP Activities ==
I have been a member of the lead development team of [http://psi-im.org Psi] since early 2004, after having contributed regularly since 2003. In 2004, I joined the XMPP Software Foundation (in the good old days when it still was called the JSF). Together with Kevin Smith, I'm currently working on the [http://swift.im Swift] Jabber/XMPP client and C++ library. Besides Swift development, I also contribute to various other Jabber OSS projects, including [http://www.igniterealtime.org/projects/openfire/ Openfire] and [http://msn-transport.jabberstudio.org/ PyMSN-t].
+
I have been a member of the lead development team of [http://psi-im.org Psi] since early 2004, after having contributed regularly since 2003. In 2004, I joined the XMPP Software Foundation (in the good old days when it still was called the JSF). Together with Kevin Smith, I'm currently working on the [http://swift.im Swift] Jabber/XMPP client and C++ library. Next to Swift development, I also contribute to various other Jabber OSS projects, including [http://www.igniterealtime.org/projects/openfire/ Openfire], [http://msn-transport.jabberstudio.org/ PyMSN-t], and [http://code.google.com/p/sleekxmpp/ SleekXMPP].
    
Besides coding, I like to do some writing now and then too. Together with Peter Saint-Andre and Kevin Smith, we wrote the O'Reilly book [http://oreilly.com/catalog/9780596521264/ XMPP: The Definitive Guide]. I also wrote a chapter on XMPP in O'Reilly's upcoming title [http://oreilly.com/catalog/9780596159818/ Beautiful Testing], promoting XMPP in other circles as well.
 
Besides coding, I like to do some writing now and then too. Together with Peter Saint-Andre and Kevin Smith, we wrote the O'Reilly book [http://oreilly.com/catalog/9780596521264/ XMPP: The Definitive Guide]. I also wrote a chapter on XMPP in O'Reilly's upcoming title [http://oreilly.com/catalog/9780596159818/ Beautiful Testing], promoting XMPP in other circles as well.
 +
 +
Another thing I fancy doing is talking in public about XMPP, such as giving introductions like [http://www.slideshare.net/remko.troncon/xmpp-101 XMPP 101] (which I presented at [http://el-tramo.be/blog/xmpp-101-fosdem FOSDEM], and which was later reused at OSCON).
    
Although I hang around on the XMPP mailing lists and do my best to contribute constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:
 
Although I hang around on the XMPP mailing lists and do my best to contribute constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:
Line 19: Line 21:     
== Motivation ==
 
== Motivation ==
I have always been very passionate about (protocol) standardization. XMPP is probably the greatest place to be for working on protocols, not only because of its potential, but because the community is extremely open to anybody who wants to contribute. I would like to continue my involvement in the community, and even take it to the next step as an XSF council member.
+
I have always been very passionate about (protocol) standardization. XMPP is probably the greatest place to be for working on protocols, not only because of its potential, but because the community is extremely open to anybody who wants to contribute. I would very much like to take my involvement in the XMPP community to the next step as an XSF council member.
    
== Plan ==
 
== Plan ==
 
As a council member, I want to focus the XSF on the following topics during the following year:
 
As a council member, I want to focus the XSF on the following topics during the following year:
* Improving user experience: Some 'flows' used in todays XMPP clients form big usability problems, and require changes in the protocol in order to fix them. These changes include the roster management of gateways/components, presence/priority handling in clients, secure and reliable communication, ...
+
* Improving user experience: Some 'flows' used in todays XMPP clients form big usability problems, and require changes in the protocol in order to fix them. These changes include the roster management of gateways/components, presence/priority handling in clients, secure and reliable communication, ... Working on usability problems will expand XMPP's potential user base to a much broader audience
 
* Secure & reliable communications: XMPP has the name of being the 'solid' choice for IM. We should make sure we live up to that name, and focus on providing good, usable protocols for secure and reliable communications
 
* Secure & reliable communications: XMPP has the name of being the 'solid' choice for IM. We should make sure we live up to that name, and focus on providing good, usable protocols for secure and reliable communications
 
* Embedded XMPP: XMPP needs some work to be attractive to the restricted environment that mobile devices work in.
 
* Embedded XMPP: XMPP needs some work to be attractive to the restricted environment that mobile devices work in.
190

edits

Navigation menu