|
|
(75 intermediate revisions by 3 users not shown) |
Line 1: |
Line 1: |
| Here are some project ideas for the [http://code.google.com/soc/ Summer of Code 2006] ...
| | The Jabber-related Summer of Code projects have been selected. We had ~100 applications and it was very difficult to select from among them. The accepted projects are listed below. |
|
| |
|
| === Distributed monitoring of the Jabber network ===
| | * [[Encrypted Sessions and XMPP support for SIM-IM]] (student: Jan Å embera; mentor: Ian Paterson) |
| (proposed by Lucas Nussbaum - xmpp:lucas@nussbaum.fr) | | * [[HTTP-Auth suite]] (student: [[User:Machekku|Maciej Niedzielski]]; mentor: Jacek Konieczny) |
| | * [[Instant Syndicating]] (student: Nick Vidal; mentor: Remko Tronçon) |
| | * [[Java Jingle]] (student: [[User:AlNorth|Alasdair North]]; mentor: Matt Tucker) |
| | * [[Psi JFT|Jingle File Transfer for Psi]] (student: [[User:Murilo|Murilo Belluzzo]]; mentor: Justin Karneges) |
| | * [[Psi Link-local messaging|Link-local messaging support for Psi]] (student: [[User:JasonMcC|Jason McCandless]]; mentor: Justin Karneges) |
| | * [[Psi Plugins Soc 2006|Plugin and scripting support for Psi]] (student: [[User:kevin|Kevin Smith]]; mentor: Peter Saint-Andre) |
| | * [[Gajim PubSub|PubSub for Gajim]] (student: Tomasz Melcer; mentor: Yann Le Boulanger) |
| | * [[Real-time wiki]] (student: Grzegorz Grasza; mentor: Mickaël Rémond) |
| | * [[Psi Whiteboarding|Whiteboarding support for Psi]] (student: Joonas Govenius; mentor: Remko Tronçon) |
|
| |
|
| The Jabber network isn't really known for its reliability, and administrators don't always have the necessary tools to monitor their server correctly. The data provided by http://public.jabbernet.dk/mrtg/ is not enough. The goal of this project is to build a testing framework to be able to monitor the public servers and answer those questions :
| | And some Jabber-related projects for other teams include: |
| * do client connections using SASL, TLS or SSL currently work on server S1 ? (not only checking if the TCP port is open, but full login) | | * [http://code.google.com/soc/inkscape/about.html Inkboard Protocol Spec and Lib Conversion] |
| * do server-to-server works between server S1 and S2 (by exchanging ping messages on XMPP) ?
| | * [http://www.adiumx.com/blog/2006/05/huzzah.php Jingle support in Adium] |
| This would allow to build a more detailed status of the Jabber network. Additionally, it would be nice to be able to add a contact email, so the administrator can get informed of his server's problems.
| |
|
| |
|
| (addendum by [[Stpeter]])
| | You can still view the [[Summer of Code 2006 Project Ideas]], too. |
|
| |
|
| Integrating this into the [http://www.xmpp.net/ XMPP Federation] database and website would be super.
| | [[Category:Summer of Code 2006]] |
| | |
| === Jabber authentication to CMS and blogs ===
| |
| (proposed by [[Halr9000]])
| |
| | |
| See my [http://halr9000.com/ideas/xmpp-and-cms/ XMPP and CMS] post on the topic.
| |
| | |
| === ejabberd features ===
| |
| (proposed by [[Stpeter]])
| |
| | |
| It would be great if the [http://ejabberd.jabber.ru/ ejabberd] server (written in Erlang) supported the latest version of [http://www.jabber.org/jeps/jep-0060.html Publish-Subscribe] including the [http://www.jabber.org/jeps/jep-0163.html Personal Eventing] subset.
| |
| | |
| Support for the [http://www.jabber.org/jeps/jeps-0124.html HTTP Binding] would be great but I think the folks at [http://www.mabber.com/ mabber] have written this and just need to contribute their code.
| |
| | |
| (proposed by [[mremond]])
| |
| | |
| File transfer [http://www.jabber.org/jeps/jep-0065.html SOCKS5 proxy] integration.
| |
| | |
| === Create a Vandal Fighter for Wikipedia based on XMPP ===
| |
| | |
| http://en.wikipedia.org/wiki/User:Henna/VF/Feature_requests#XMPP_and_Especially_Publish-Subscribe
| |
| | |
| === Hack a client to support some basic features ===
| |
| | |
| (proposed by [[Zion]])
| |
| | |
| Two big things that very very very few clients support
| |
| * muc
| |
| * xdata
| |
| | |
| Pick a client, and implement the full muc spec or add decent xdata where appropriate.
| |
| | |
| Also, anyone suggesting a new client should be thwapped.
| |
| | |
| === Write a XMPP-compliance test suite ===
| |
| | |
| (proposed by [[Astro]])
| |
| | |
| A lot of servers claim XMPP-compliance, thus following the RFCs strictly. A test suite for interoperability between clients and servers can ratify these claims.
| |