Contributing to Ivy RoundUp is easy and helps Ivy users everywhere

The main work required is adding new modules and new revisions of existing modules. All that is required for a new revision is an ivy.xml file and a packager.xml file. The format of packager.xml files is documented here.

If the module already exists (i.e., you're just adding a new revision), typically all you need to do is copy the files from the previous revision and update the release timestamp and resource SHA1 checksums.

For new modules, there are plenty of examples to work from. But you should always start with an SVN copy of the boilerplate files.

Please create issues in the issue tracker to submit new or updated modules.

Please follow these guidelines when creating issues for new revisions:

1. Read and understand the ModuleMaintainerGuidelines.
2. Make sure that running ant repo with your new files in place under src/modules doesn't generate any (new) warnings or errors.
3. Make sure that running ant -Dresolve.mod=foo doesn't generate any errors (where "foo" is the name of your module; you can also use resolve.org and/or resolve.rev)
4. Don't forget to set the "publication" attribute to the release date of the module.
5. Include your new modules as a subversion patch file attached to the issue:
• If the module is new, the patch should be against an "svn copy" of the boilerplate files
• If the revision is new but the module already exists, the patch should be against the previous revision

If you're interested in developing the Ivy RoundUp infrastructure, or becoming a regular contributor with SVN commit access, join us on the mailing list.

Thanks!