10
edits
Difference between revisions of "Summer of Code 2008"
Jump to navigation
Jump to search
→Servers
(→New) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 108: | Line 108: | ||
= Servers = | = Servers = | ||
== ejabberd == | |||
We will develop more exciting things on ejabberd this year again. | |||
===Contacts=== | |||
Mentor: Mickaël Rémond (email: mremond@process-one.net / jid: mremond@process-one.net). | |||
== Openfire == | |||
Here are some nice features that would be nice to have in Openfire. We are still working on the list which should be ready for early next week (March 25th). If you have other ideas not listed here feel free to send us an email to discuss it or post it [http://www.igniterealtime.org/community/community/developers/gsoc08?view=discussions here]. | |||
* File Repository and Sharing (including WebDAV) | |||
* File transfers for gateways | |||
* Group Chat for Gateways | |||
* Update and improve BOSH support | |||
For more details, visit the [http://www.igniterealtime.org/community/docs/DOC-1490 Summer of Code 2008 Projects]. | |||
===Contacts=== | |||
Mentor: Gaston Dombiak (email: gaston@jivesoftware.com / jid: gato@jivesoftware.com). | |||
== PJS == | == PJS == | ||
The PJS project aims to create a reliable, correct and highly scalable XMPP server framework in Python, not unlike what ejabberd is to Erlang. It was started as an undergrad project at the University of Toronto in February 2008. By the start of GSOC, the server should have the following components: | The PJS project aims to create a reliable, correct and highly scalable XMPP server framework in Python, not unlike what ejabberd is to Erlang. It was started as an undergrad project at the University of Toronto in February 2008. By the start of GSOC, the server should have the following components: | ||
| Line 136: | Line 155: | ||
Also see [http://wiki.python.org/moin/SummerOfCode Python's SOC page] (under Dr.Project) | Also see [http://wiki.python.org/moin/SummerOfCode Python's SOC page] (under Dr.Project) | ||
= Components = | = Components = | ||
| Line 175: | Line 181: | ||
= Libraries = | = Libraries = | ||
== gloox == | |||
=== Serverless Messaging aka Local-Link === | |||
==== Project description ==== | |||
Write up a platform independent implementation of XEP-0174 for gloox. Platforms supported should be *NIX (including Mac OS X), linux and windows. | |||
http://www.xmpp.org/extensions/xep-0174.html | |||
= Other = | = Other = | ||
| Line 248: | Line 260: | ||
Some information about link-local chatting (biased towards Psi) can be found [http://psi-im.org/wiki/Bonjour here]. | Some information about link-local chatting (biased towards Psi) can be found [http://psi-im.org/wiki/Bonjour here]. | ||
== Client-Independent D-Bus Service for Jingle Audio == | |||
Many Jabber clients will want to implement the Jingle Audio protocol (and eventually other Jingle protocols as well), but may lack the technical possibility to keep an internal implementation. (or just the will to reinvent the wheel ☺) [http://emacs-jabber.cvs.sourceforge.net/emacs-jabber/tox/ Tox] (Talk Over XMPP) is a D-Bus service meant to provide Jingle functionality to a Jabber client able to communicate over D-Bus. It uses the Farsight library. | |||
The goals of this project are: | |||
* Beat Tox into good enough shape to perform audio conversations | |||
* Make at least one Jabber client implement the Jingle protocol through Tox (possibly jabber.el, which is the current development platform) | |||
* (optional) In said client(s), support the protocol used by the Google Talk client for audio conversations | |||
* (optional) Jingle Video | |||
* (optional) Jingle File Transfer | |||
This project needs a mentor, as [[User:Legoscia]] will be offline during great parts of the summer. | |||