Difference between revisions of "Remko Tronçon for Council 2008"

From XMPP WIKI
Jump to navigation Jump to search
Line 7: Line 7:


== Jabber/XMPP Activities ==
== Jabber/XMPP Activities ==
I am 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 also joined the XMPP Software Foundation (in the good old days when it still was called the JSF). Besides development for Psi, 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 am 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 also joined the XMPP Software Foundation (in the good old days when it still was called the JSF).  
 
Besides development for Psi, 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 mentor of several Google Summer of Code Projects for the XSF in the past years.


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 13: Line 20:
* [http://www.xmpp.org/extensions/xep-0146.html XEP-0146: Remote Controlling Clients]
* [http://www.xmpp.org/extensions/xep-0146.html XEP-0146: Remote Controlling Clients]
* [http://www.xmpp.org/extensions/xep-0209.html XEP-0209: Metacontacts]
* [http://www.xmpp.org/extensions/xep-0209.html XEP-0209: Metacontacts]
Together with Peter Saint-Andre and Kevin Smith, I'm [http://el-tramo.be/blog/xmppbook-intro writing a book] for O'Reilly on XMPP.


Finally, I try to attend as many XMPP meetings as my (personal) budget allows me. So far, this has brought me to EuroOSCON and to 2 XMPP summits.
Finally, I try to attend as many XMPP meetings as my (personal) budget allows me. So far, this has brought me to EuroOSCON and to 2 XMPP summits.

Revision as of 05:57, 4 September 2008

Personal Trivia

  • My name is Remko
  • I live in Leuven, Belgium.
  • After finishing my Master in Computer Science at the Catholic University of Leuven in 2001, I stuck around and did a PhD in Engineering at the same university.
  • Since early 2007, I am employed as a software engineer at CoWare, an EDA company designing tools targeted towards embedded system chip designers.
  • I have been an active free software developer and contributor ever since I learned to write my first few lines of code in a language that didn't end with the letters 'BASIC', and will probably be so for the rest of my life.

Jabber/XMPP Activities

I am a member of the lead development team of Psi since early 2004, after having contributed regularly since 2003.

In 2004, I also joined the XMPP Software Foundation (in the good old days when it still was called the JSF).

Besides development for Psi, I also contribute to various other Jabber OSS projects, including Openfire and PyMSN-t.

I have been a mentor of several Google Summer of Code Projects for the XSF in the past years.

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:

Together with Peter Saint-Andre and Kevin Smith, I'm writing a book for O'Reilly on XMPP.

Finally, I try to attend as many XMPP meetings as my (personal) budget allows me. So far, this has brought me to EuroOSCON and to 2 XMPP summits.

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 take my involvement on defining and documenting XMPP to the next level by joining the council, both as a personal challenge and as a favor to the community.

Plan

Here is a list of the things I would like the council to spend time on during the next year:

  • Jingle: A lot of progress has been done in the past years on this front, we just need to bite the bullet and polish off the last few bits.
  • Security: After having investigated several approaches to allow secure communications (OpenPGP, ESessions, ...), the time has come to formalize some final protocols for secure end-to-end communication, based on proven secure technologies.
  • Emerging technologies: XMPP is being considered and used in several emerging hip technologies, including microblogging and social networking. We should make sure that we have the facilities to become the de facto standard for these technologies.

Contact

If you're interested in discussing my application with me, feel free to have a chat with me.