Difference between revisions of "Mickaël Rémond for Board 2008"

From XMPP WIKI
Jump to navigation Jump to search
(New page: ==About== I am the founder of ProcessOne (http://www.process-one.net/) and developer on ejabberd (http://www.process-one.net/en/ejabberd/), an open source XMPP server implementation, and ...)
 
Line 2: Line 2:


I am the founder of ProcessOne (http://www.process-one.net/) and developer on ejabberd (http://www.process-one.net/en/ejabberd/), an open source XMPP server implementation, and several other related Jabber projects.
I am the founder of ProcessOne (http://www.process-one.net/) and developer on ejabberd (http://www.process-one.net/en/ejabberd/), an open source XMPP server implementation, and several other related Jabber projects.
I have been active in the Open Source community since 1993, mainly in French Linux non-profit organisations.  My interest for Jabber gets back to 2000, when I was working for a company developing a clustering and scalability layer around Jabberd.
I have been active in the Open Source community since 1993, both working on open source development and in French Linux non-profit organisations.  My interest for Jabber gets back to 2000, when I was working for a company developing a clustering and scalability layer around Jabberd.
Since then, I have been doing mainly XMPP and Erlang activities. I have worked on an XML-based EAI (Enterprise Application Integration platform), that is nowadays known as J-EAI (XMPP based integration platform).
 
Since then, I have been doing mainly XMPP and Erlang activities.
I have been a member of the XSF since 5 years now.
I have been a member of the XSF since 5 years now.
My main focus is to push XMPP to its limit in term of reliability and scalabity to make a good business case for the protocol.
My main focus is to push XMPP to its limit in term of scope, reliability and scalabity to make a good business case for the protocol.


==Why I'm reapplying==
==Why I'm reapplying==


The XMPP protocol is an IETF standard. The XEP process have produce a fair amount of good and ready to implement extensions to the protocol. However, we have reach a point where we both have a strong technical asset and a growing adoption of the protocol. However, the protocol is still not spread largely enough, in accordance to its technical merits and its standard status.
The XMPP protocol is currently booming and the original vision is currently on its way to be achieved. It is not only anymore a chat protocol, but it is used as an event based protocol.
We probably also need to layer the protocol. It is hard for implementor to know what to implement first, what is stable and what is moving etc.
It is now at the heart of some new highly innovative applications: XMPP as a way to coordinate a cluster of server, XMPP as a web service platform, XMPP as a news distribution mechanism, XMPP as a channel to mobile phones. XMPP is a glue between users, applications and devices. The whole idea of XMPP application server now makes sense.


My goal in reapplying is to try helping the standardisation process by making it compliant with industry rules and mid term stability.
My goal is to help making sure that the dream of an ubiquitous XMPP stays on its track and that the XSF is doing the right thing to share the vision and make it possible.


My second goal is to get more big companies involved in the XSF and to have cross domain discussions with other technologies (Adobe with Flash technologies, SIP companies, etc).
From a business perspective, this means convince more people to participate to the XSF (we need volunteers), more companies to become sponsor and more people to use XMPP.


I also wants to represent the XMPP businesses in the XSF, as more and more companies are relying on XMPP to make a living.


This target are obviously long term effort. I will primarily focus on helping the XSF and the community behind it in defining and walking through the first steps on the road, by asking the right questions.
This target are obviously long term effort. I will primarily focus on helping the XSF and the community behind it in defining and walking through the first steps on the road, by asking the right questions, and by participating to conference around the world to promote the protocol.


==Contact==
==Contact==


My IM ID: mremond @ process-one.net
My IM ID: mremond @ process-one.net

Revision as of 10:38, 2 September 2008

About

I am the founder of ProcessOne (http://www.process-one.net/) and developer on ejabberd (http://www.process-one.net/en/ejabberd/), an open source XMPP server implementation, and several other related Jabber projects. I have been active in the Open Source community since 1993, both working on open source development and in French Linux non-profit organisations. My interest for Jabber gets back to 2000, when I was working for a company developing a clustering and scalability layer around Jabberd.

Since then, I have been doing mainly XMPP and Erlang activities. I have been a member of the XSF since 5 years now. My main focus is to push XMPP to its limit in term of scope, reliability and scalabity to make a good business case for the protocol.

Why I'm reapplying

The XMPP protocol is currently booming and the original vision is currently on its way to be achieved. It is not only anymore a chat protocol, but it is used as an event based protocol. It is now at the heart of some new highly innovative applications: XMPP as a way to coordinate a cluster of server, XMPP as a web service platform, XMPP as a news distribution mechanism, XMPP as a channel to mobile phones. XMPP is a glue between users, applications and devices. The whole idea of XMPP application server now makes sense.

My goal is to help making sure that the dream of an ubiquitous XMPP stays on its track and that the XSF is doing the right thing to share the vision and make it possible.

From a business perspective, this means convince more people to participate to the XSF (we need volunteers), more companies to become sponsor and more people to use XMPP.

I also wants to represent the XMPP businesses in the XSF, as more and more companies are relying on XMPP to make a living.

This target are obviously long term effort. I will primarily focus on helping the XSF and the community behind it in defining and walking through the first steps on the road, by asking the right questions, and by participating to conference around the world to promote the protocol.

Contact

My IM ID: mremond @ process-one.net