-
Notifications
You must be signed in to change notification settings - Fork 12
Project: ejabberd
- Website: http://www.process-one.net/en/ejabberd
- Responsible: Mickaël Rémond (mremond at process-one)
- Possible mentors: Mickaël Rémond (experienced mentor, since 2006) Alexey Shchepin, Badlop, Evgenyi Khramtsov, Jérôme Sautret, Christophe Romain
- If you have any questions, send an e-mail to beam-community AT googlegroups DOT com
- You can add Mickaël Rémond on XMPP: mremond AT process-one DOT net
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.
Ahead of the Summer of code, we have prepared a way to automatically setup for ejabberd development environment ejabberd-vagrant-dev
As a student, you can select the language you prefer to contribute to ejabberd, between Erlang and Elixir.
Here is a page to help you get started working with ejabberd community as a GSoC student: A quick introduction to ejabberd for GSoC hopefuls
Ideas are listed in no particular order. Students providing their own ideas are also welcome!
Brief explanation: There is plenty of room for improvements in both ejabberd configuration, extensions and plugins writing. The idea would be to built a new configuration DSL (Domain Specific Language) for ejabberd that would both allow to configure it and enhance its feature set through hooks.
It would make both an easier to understand config file and a more easily extensible server for casual developers. The project will requires to review the existing ejabberd hooks and extend the list to make it suitable for the new DSL. Elixir language would be a good candidate for the Domain Specific Language.
Expected results: Elixir powered ejabberd version.
Knowledge prerequisites: Knowledge of Erlang and possibly ejabberd.
Mentor: Alexey Shchepin, Mickaël Rémond
Brief explanation: ejabberd comes with a web console to manage the server. However, many administration features are only available from XMPP clients from users with admin rights or from ejabberdctl command-line tools. For example, managing chat rooms would be more efficiently performed using a web front-end. To spread the use of ejabberd as an easy to use corporate chat services, it is important to make it more manageable through a web browser.
Expected results: Revamp ejabberd management web interface with extended features, with a focus on managing users, MUC Room and shared rosters.
Knowledge prerequisites: Knowledge of Erlang, XMPP and web developments.
Mentor: Alexey Shchepin, Mickaël Rémond
Brief explanation: XMPP is a difficult protocol for web developer. It is a connected stateless protocol. However, it is possible to map a lot of the operation, semantic of XMPP on top of HTTP using traditional ReST semantic.. You could for example browse chat rooms, pubsub nodes, etc using a rest interface. If the session can be separated from the routing of the XMPP protocol, it is even possible to send and receive XMPP stanzas through the HTTP protocol. 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: ejabberd version that can be controlled either through XMPP or a pure HTTP interface to simplify XMPP usage for web developers.
Knowledge prerequisites: Erlang or a functional language and web development.
Mentor: Mickaël Rémond