Difference between revisions of "Summer of Code 2006"
| Line 9: | Line 9: | ||
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. | 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 [[ | (addendum by [[Stpeter]]) | ||
Integrating this into the [http://www.xmpp.net/ XMPP Federation] database and website would be super. | Integrating this into the [http://www.xmpp.net/ XMPP Federation] database and website would be super. | ||
=== Jabber authentication to CMS and blogs === | === Jabber authentication to CMS and blogs === | ||
(proposed by [[ | (proposed by [[Halr9000]]) | ||
See my [http://halr9000.com/ideas/xmpp-and-cms/ XMPP and CMS] post on the topic. | See my [http://halr9000.com/ideas/xmpp-and-cms/ XMPP and CMS] post on the topic. | ||
=== ejabberd features === | === ejabberd features === | ||
(proposed by [[ | (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. | 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. | ||
| Line 25: | Line 25: | ||
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. | 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 [[ | (proposed by [[mremond]]) | ||
File transfer [http://www.jabber.org/jeps/jep-0065.html SOCKS5 proxy] integration. | File transfer [http://www.jabber.org/jeps/jep-0065.html SOCKS5 proxy] integration. | ||
| Line 35: | Line 35: | ||
=== Hack a client to support some basic features === | === Hack a client to support some basic features === | ||
(proposed by [[ | (proposed by [[Zion]]) | ||
Two big things that very very very few clients support | Two big things that very very very few clients support | ||
| Line 47: | Line 47: | ||
=== Write a XMPP-compliance test suite === | === Write a XMPP-compliance test suite === | ||
(proposed by [[ | (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. | 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. | ||
Revision as of 22:47, 21 April 2006
Here are some project ideas for the Summer of Code 2006 ...
Distributed monitoring of the Jabber network
(proposed by Lucas Nussbaum - xmpp:lucas@nussbaum.fr)
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 :
- 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)
- do server-to-server works between server S1 and S2 (by exchanging ping messages on XMPP) ?
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)
Integrating this into the XMPP Federation database and website would be super.
Jabber authentication to CMS and blogs
(proposed by Halr9000)
See my XMPP and CMS post on the topic.
ejabberd features
(proposed by Stpeter)
It would be great if the ejabberd server (written in Erlang) supported the latest version of Publish-Subscribe including the Personal Eventing subset.
Support for the HTTP Binding would be great but I think the folks at mabber have written this and just need to contribute their code.
(proposed by mremond)
File transfer 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.