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

Jump to navigation Jump to search
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.
20

edits

Navigation menu