Contributing
Very important ways to help
- Answer others' questions on the mailing lists.
- Verify and close out old bugs that have been fixed.
- Submit detailed bug reports when you run into issues.
- Summarize mailing list discussions on the Wiki in Document Mode.
- Rewrite Thread Mode wiki pages into Document Mode.
- Review commits other developers make.
- File bugs on code that doesn't conform to Code Style and Conventions
- Contribute documenation here. Documentation describing configuration file modifications for different databases, ldap configurations, and especially documentation targeted to users is needed.
Ways to contribute code to the Ja-Sig project:
Code Archives
Add your channel to the Clearinghouse and link to an archive with your changes and instructions. You may also email a link to your code in an archive to the mailing list. If you don't have your code hosted somewhere else you may post the patch as an attachment to a page on this wiki, and then email the list with the URL of the Confluence page. This Confluence approach provides a place to comment about and keep a latest version of the patch.
Passing around archives of code have their drawbacks. They are usually only released for a specific version of uPortal and it's pretty likely it's not the one you are running. Putting each project in CVS and managing releases, release notes and tags would help fix this. Also, something like Maven would help us fetch the correct version of each component of uPortal. uPortal would need to be mavenized first though.
JIRA
Create an issue in JIRA and submit your changes as a patch to the current development version of uPortal in CVS.
CVS
Once you have commit access, you may add your code to the uPortal CVS directly.