Skip to content
This repository was archived by the owner on Feb 5, 2020. It is now read-only.

Project: ejabberd

Jump to bottom
mremond edited this page Mar 18, 2013 · 32 revisions
  • Website: http://www.process-one.net/en/ejabberd
  • Responsible: Mickaël Rémond (mremond at process-one), Alexey Shchepin, Jérôme Sautret, Christophe Romain.
  • Notes: Prior knowledge of Erlang (or a functional language) is a good start to begin with the project. We are also open to student proposals.

ejabberd is one of the most known Erlang project, developed since 2002 by ProcessOne. As a student, you will have the opportunity to work with the ejabberd historical lead developers directly and work on projects that can have a huge impact given the number of worldwide users.

Ideas are listed in no particular orders.

Idea #1: XMPP and HTTP convergence

Brief explanation: the ability to offer access to ejabberd feature through HTTP. It is possible to map a lot of the operation, semantic of XMPP on top of HTTP. You could for example browser chat rooms, pubsub nodes, etc using a rest interface. A lot could be done that way and it would open up a whole new range of use case of ejabberd to traditional web developers or to environnement where using XMPP directly is difficult.

Expected results:

Knowledge prerequisites:

Mentor: Mickaël Rémond

Idea #2: Social networking meets chat with Buddycloud protocol

Brief explanation: implement the buddycloud protocol in ejabberd. Buddycloud is an XMPP extension for building social networks. Having worked a lot on concept of federated social networks, I would be very interested in participating in such effort, adding another feature set that would be More details here:

Expected results:

Knowledge prerequisites:

Mentor: Alexey Shchepin, Mickaël Rémond

Idea #3: Improve ejabberd configuration and extensibility

Brief explanation: I am a big fan of elixir and I am a big believer that making ejabberd extensible more easily would be something very valuable. There is plenty of room for improvements. The first that comes to mind is allow writing extensions and plugin using elixir. We would work together to make an even better / clearer API and make it easy to write very powerful modules using elixir. Another area were Elixir + ejabberd could make sense is building a DSL for ejabberd configuration that would replace the existing and difficult to grap configuration file. Maybe mixing the two is even possible, making ejabberd directly extensible from the configuration file with a proper mix of DSL granting both access to configuration patterns and behaviour oriented hooks.

Expected results:

Knowledge prerequisites:

Mentor: Alexey Shchepin, Mickaël Rémond

Idea #4: Multi-User chat module scale and robustness

Brief explanation:

Expected results:

Knowledge prerequisites:

Mentor: Alexey Shchepin, Mickaël Rémond

Clone this wiki locally