2001-04-18
How to submit code and documentation to the Jabber.org project.
This is the quick-and-dirty guide to contributing your code and documentation to the Jabber.org project. A more detailed guide will follow, and maybe we'll even improve the process at some point! :)
The basic steps for contributing code are as follows:
FTP your code (tarballs are best) to download.jabber.org/contrib using a username and password of jabber-contrib.
Upload a file.README explaining the code you're contributing, and don't forget to include some information about the author (i.e., you!).
Notify the JDEV mailing list and/or contact someone with commit access (see below).
The following people have commit access to the CVS tree. If you're going to be submitting lots of patches or want to maintain them directly, simply ask any of these folks for access.
We're always looking for a few good docs. :) One way you can contribute is to add a link to your document from the docs.jabber.org links page. HTML is fine, although we use DocBook SGML for all the core docs so we can easily convert them into HTML, PostScript, PDF, and RTF (see the Quick Guide to DocBook for more info, it really is pretty easy!).
Alternatively, you can follow the same basic steps as those for contributing code:
FTP your doc (including author identification) to download.jabber.org/contrib using a username and password of jabber-contrib.
Notify the docs-dev mailing list and/or contact stpeter, who can also give you commit access to the docs.jabber.org module if you would like to get your document into CVS.
Right now the docs in CVS are not automatically deployed to the docs.jabber.org website, so there's an extra deployment step involved, but if you follow step 2 above then stpeter will be happy to make sure your doc makes it to the web (at least until we improve the process)!