Mickaël Rémond for Board 2009

Revision as of 20:09, 24 July 2010 by Neustradamus (talk | contribs) (Mickael Remond for Board 2009 moved to Mickaël Rémond for Board 2009)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Small introduction about me

I am the founder of ProcessOne ([1]) and developer on ejabberd ([2]), an open source XMPP server implementation, and several other related XMPP projects.

Here are some facts about myself:

  • Job: I am doing lots of various things at ProcessOne ranging from marketing and sales to helping the development team do a good job.
  • Open source: I have been active in the Open Source community since 1993, both working on open source development and in French Linux non-profit organisations. I am still involved in several projects and non-profit organisation on Free Software (like April). I am heavily involved in Erlang development and several other Erlang related projects.
  • XMPP: My interest for Jabber gets back to 2000, when I was working for a company developing a clustering and scalability layer around Jabberd (in Erlang already at this time). I am also involved in work relating to XMPP like Google Wave protocol.
  • XSF: I have been an XSF member (JSF member previously) since 2005. I have been in the XSF board since 2006.
  • Family: Yes :-) Three beautiful children
  • Hobbies: I dive, play the guitar and play poker with friends.
  • Books: I have written the French Erlang book, for the main reason of being able to say that I wrote it. That's why I am mentioning it here ;-)
  • Conference: Advocacy on technical topic I love is a hobby for me. I have made tens of conference all over the world.
  • Other: I am Erlang user of the year (in 2004). Most likely the only one in the XSF Board :-)

Note: If you are interested in my whole academic and professional cursus description, you can check my profile on LinkedIn: [3]

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 servers, 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 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.

We have also large number of customers that send us feedback on XMPP, the protocol and where they would like to see it heading. I would be glad to share those view as well.

Projects I have been involved in

I have been involved in the past on many Erlang and/or XMPP projects:

  • ejabberd
  • Yaws web server
  • BTT (ticket tracker)
  • Manderlbot (IRC bot).
  • J-EAI (logical data bus based on XMPP)
  • exmpp (Erlang library for XMPP)
  • Oneteam Firefox based XMPP client
  • OneTeam for iPhone
  • TeamLeader supervision console for ejabberd
  • ...and various contributions that are too numerous to remember :-)

These days I am involved in new projects that we are preparing to launch at ProcessOne, but also most of our large scale XMPP deployment projects. It means I have a good vision on what the XMPP users need for large industrial deployments, from a technical and organisational perspective.

I have designed several new products and services at ProcessOne that we are about to launch.

My goals: Why I'm reapplying

My goals are the following:

  • 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.
  • to convince more people to participate to the XSF (we need volunteers), more companies to become sponsor and more people to use XMPP. I feel the XSF is different from other standard oriented organisations as it rely on a passionate community. My view is that this is what makes the XSF successfull. I would like to make sure that we emphasizes on openeness and community as much as standards.
  • to represent the XMPP businesses in the XSF, as more and more companies are relying on XMPP to make a living. This is a good way to make sure the protocol has the required traction to push it further.
  • to help tackling hard and controversial topics such as *interop*, next protocol to add or relation with between the XSF and other companies. I am for example personnaly involved in testing framework work and would really like to push the interop testing framework operation (can I say certification ? ;-).

XMPP is now acknowledged as one of the major protocol, adopted by Internet players and large traditional company. It serves as a basis for many services, from the "internet of things" to news distribution and collaboration.

We need to have a strong vision on what its future should be and how we can improve and protect this common good. This debate has to be lead by the board.


My IM ID: mremond @ process-one.net