jabberd project

Jabber® is a registered trademark of Jabber Inc., and its use is licensed through the Jabber Software Foundation.

Thanks to JabberStudio for hosting.

© 1999-2004 The jabberd project.

jabberd Development

This is the central site for development of the jabberd server. Currently, development effort is focused on the jabberd 2 code branch.

The project leader is Justin Kirby. He can be contacted via Jabber at xmpp:zion@openaether.org. or his i-name =justin.kirby

The project coordinator is Stephen Marquard. He can be contacted via Jabber at xmpp:scm@jabberafrica.org

The original project creator, developer, genius was Rob Norris. Thanks Rob

Getting the code

The code is stored in JabberStudio CVS, and can be obtained using either the pserver interface or the web interface.

Occassionally we release CVS snapshots for people who don't want to deal with the potentially broken and bleeding CVS code. These are available from the main jabberd 2 page.

If you would like commit access to the CVS repository, please contact the project leader. Basically, you need to prove that you can be trusted - writing patches and contributing on the mailing list is a good way to show this.

Mailing list

Development issues are discussed on the jabberd development mailing list. This list is open for all to subscribe and post to. If you're doing anything with development code (including testing), you're encouraged to join and contribute.

Documentation

The following developer documentation is available:

Contributing

There are a number of ways you can contribute to jabberd 2:

  • Code - there's still a number of things that need to be implemented, though that list gets smaller every day. The wiki is always a good place to start, or ask on the list. You don't need to be a code hero to help - some C is all thats required.
  • Test - You could install and use the server locally, do load testing with JabberTest (or some other test suite). Do protocol compliance testing (and join the Compliance JIG). Make sure that the documentation matches with what actually happens. You don't need code knowledge to help out in this area.
  • Document - Will Kamishlian is heading up the jabberd 2 documentation project, which aims to provide a complete installation and administration guide for jabberd 2. You can help by reading the drafts and contributing to the wiki.

And if none of these suit you, but you'd still like to help in some other way, please contact the project leader or the list - there's almost certainly something you can do!