More CVS information can be found here.

WebCVS access to the repository.

Or, download the full source distribution containing the latest snapshot of the CVS.

Use SourceForge for bug tracking.

The source code, documentation and libraries are available for anonymous access from the SourceForge CVS server.

The CVS is updated regularly and may contain an unstable version when you check it out. We commit working code to the CVS immediately prior to putting out a release.

The CVS root is :pserver:anonymous@cvs.tyrex.sourceforge.net:/cvsroot/tyrex and hit enter when prompted for a password.

To login to CVS from the command line and checkout a version of Tyrex use the following commands:

  $ cvs -d 
     :pserver:anonymous@cvs.tyrex.sourceforge.net:/cvsroot/tyrex
     login
  password: <hit enter>
  $ cvs -d 
     :pserver:anonymous@cvs.tyrex.sourceforge.net:/cvsroot/tyrex
     checkout tyrex
      

All code contributions must be under the license and copyright of the project to which you contribute. By contributing code you agree that we can distribute the contribution under the terms of the license, that it can be distributed without any royalties, copyright, trademark, patent or other legal lock ups. Open source means no discrimination against any group or individual that may wish to use the code.

When making a contribution you are granting us a world wide, royalty free, unlimited in time license to re-distribute the code under the license. In case you wonder, you remain the original author and copyright holder of the contribution, you just give other people a license to use it as well. Thank you.

It's perfectly ok to put your name and e-mail address in the code.

When sending patches, diff files with context (3 lines before, 3 lines after) work best:

  cvs diff -c <file>
or
  diff -c <file>

Familiarize yourself. Take some time to understand the directory structure, build environment, interaction between components, coding and commenting style. Nothing out of the ordinary, but still not all projects are identical.

Before starting to work please advertise. It's pointless to have two people working on the same feature. Send an e-mail to the developer mailing list and announce what and how. If you don't get a reply within a day, you can assume the coast is clear.

Test before you commit. Before committing any changes run a cvs update to make sure you have the latest code base. Run the test cases to make sure nothing is broken.

Commit all at once. If the change involves more than a single file, make sure to commit all the changes together. A partially committed CVS tree is not a pretty sight. No lunch breaks, meetings or sleep during commits.

Be ready to receive complaints. Hopefully all works fine, but if changes to break existing code, people will complain. Be ready to answer their e-mails and apply the proper fixes. No going on vacation five minutes after a commit.

Put your name so people know who to credit. (Also who to blame). Initials work just fine, your full name and e-mail address are already on the main page. If you've added a new file, feel free to put your name and e-mail address as the author. If you're fixing a file, put your initials on the comment.

Observe release time. We're going to announce a new release five hours prior to making it. That gives you four hours to commit any changes, make sure nothing breaks. Don't leave the computer before the release is done. If you can't make it, there's alway the next release.

Document what you've done. In-code documentation, CVS commit messages, and the changelog. Major changes should always be recorded in the changelog.

Use the document DTD. When adding new documentation use the document DTD. Specify the proper document URL, properties, body and section. Everything inside the body/header/section is XHTML. That means well formed HTML. If it's not, you won't be able to build the docs.

We don't have a particular style for documentation, and we do appreciate a sense of humor, sarcasm and literary expression. Just don't overdue it, and please, no cliche.

We have a simple policy regarding distributable code. Either it's open source and compatible in license, or it's an API that is freely distributable.

BSD-like and MPL-like licenses are compatible and can be mixed in the same code base. Liberal licenses and public domain are also fine.

APIs need not be open source, but they must be freely distributable. As a policy we like to stick with standard APIs and never modify them, so the license has little affect. We do favor public domains APIs like SAX over tightly controlled APIs, and hopefully we can all do something about that.

Pay special attention to pre-release availability and trademark issues. Several committees and companies require proper trademark acknowledgement in the documentation. Some of them are available for distribution only once they have been formally released. This policy applies to all APIs coming from Sun.