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

From XMPP WIKI
Jump to navigation Jump to search
m
 
(3 intermediate revisions by 2 users not shown)
Line 3: Line 3:
  
 
== Jabber ==
 
== Jabber ==
I am a member of the core development team of [http://psi-im.org Psi] since early 2005, after having contributed regularly since 2003. Most of my free time is spent on developing for Psi, and has recently resulted in implementations of MUC, PEP, Avatars, Remote Controlling ([http://www.jabber.org/jeps/jep-0146.html JEP-0146], of which i am (co-)author). Besides development for Psi, i also contribute to various other Jabber OSS projects, including [http://jivesoftware.org/wildfire/ Wildfire] and [http://msn-transport.jabberstudio.org/ PyMSN-t]. This year, I am mentoring two Google Summer of Code projects ([http://wiki.jabber.org/index.php/Instant_Syndicating Instant Syndicating] and [http://wiki.jabber.org/index.php/Psi_Whiteboarding Psi Whiteboarding]). I always hang around on the Jabber mailing list, trying to contribute as much as i can to the various discussions and questions brought up.
+
I am a member of the core development team of [http://psi-im.org Psi] since early 2005, after having contributed regularly since 2003. Most of my free time is spent on developing for Psi, and has recently resulted in implementations of MUC, PEP, Avatars, Remote Controlling ([http://www.jabber.org/jeps/jep-0146.html JEP-0146], of which i am (co-)author), Stream Compression, and libjingle integration. Besides development for Psi, i also contribute to various other Jabber OSS projects, including [http://jivesoftware.org/wildfire/ Wildfire] and [http://msn-transport.jabberstudio.org/ PyMSN-t]. This year, I am mentoring two Google Summer of Code projects ([[Instant Syndicating]] and [[Psi Whiteboarding]]). I always hang around on the Jabber mailing list, trying to contribute as much as i can to the various discussions and questions brought up.
  
 
== Plan ==
 
== Plan ==
Line 9: Line 9:
 
mainly from the point of view of IM clients. Although XMPP isn't strictly an IM protocol anymore, and is used for many different interesting tasks, I feel it is important that IM is not forgotten. Of course, I will not always be wearing the IM hat, and am very dedicated to develop and promote XMPP in general, which is the job of a true JSF council member.
 
mainly from the point of view of IM clients. Although XMPP isn't strictly an IM protocol anymore, and is used for many different interesting tasks, I feel it is important that IM is not forgotten. Of course, I will not always be wearing the IM hat, and am very dedicated to develop and promote XMPP in general, which is the job of a true JSF council member.
  
It has been stated that the main task of the next council will be to finalize all the standards currently in development. As an active developer from the IM world, I am able to provide feedback from the battlefield, which is required to ensure good quality and easy to deploy standards.
+
It has been stated that the main task of the next council will be to finalize all the standards currently in development (PEP, Jingle, ...). As an active developer from the IM world, I am able to provide feedback from the battlefield, which is required to ensure good quality and easy to deploy standards.
  
 
Besides the finalization of the current standards, new standards need to be defined as well. One of the heaviest shortcomings in XMPP is probably the lack of reliability in communications, which I feel should be addressed by the next council.
 
Besides the finalization of the current standards, new standards need to be defined as well. One of the heaviest shortcomings in XMPP is probably the lack of reliability in communications, which I feel should be addressed by the next council.

Latest revision as of 02:41, 17 December 2020

About

I'm a PhD student, and am currently finishing my PhD at the K.U.Leuven, Belgium. I have been an OSS developer for many years, both as an author and a contributor.

Jabber

I am a member of the core development team of Psi since early 2005, after having contributed regularly since 2003. Most of my free time is spent on developing for Psi, and has recently resulted in implementations of MUC, PEP, Avatars, Remote Controlling (JEP-0146, of which i am (co-)author), Stream Compression, and libjingle integration. Besides development for Psi, i also contribute to various other Jabber OSS projects, including Wildfire and PyMSN-t. This year, I am mentoring two Google Summer of Code projects (Instant Syndicating and Psi Whiteboarding). I always hang around on the Jabber mailing list, trying to contribute as much as i can to the various discussions and questions brought up.

Plan

My job as a council member will be to actively participate and contribute to discussions and developments, mainly from the point of view of IM clients. Although XMPP isn't strictly an IM protocol anymore, and is used for many different interesting tasks, I feel it is important that IM is not forgotten. Of course, I will not always be wearing the IM hat, and am very dedicated to develop and promote XMPP in general, which is the job of a true JSF council member.

It has been stated that the main task of the next council will be to finalize all the standards currently in development (PEP, Jingle, ...). As an active developer from the IM world, I am able to provide feedback from the battlefield, which is required to ensure good quality and easy to deploy standards.

Besides the finalization of the current standards, new standards need to be defined as well. One of the heaviest shortcomings in XMPP is probably the lack of reliability in communications, which I feel should be addressed by the next council.

Contact

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