Third-party patches are essential for keeping RichFaces great. Contributing to the project helps to deliver functionality you need and allows you to share your code with other contributors and users. We want to keep it as easy as possible to contribute changes you made and we will work hard to deliver your contributions in upcoming releases. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
- Follow instructions in Contributor Getting Started Guide
- Check-list:
- Make sure you have a JBoss account
- Make sure you have a GitHub account
- Submit a issue report, assuming one does not already exist.
- Clearly describe the issue including steps to reproduce when it is a bug.
- Make sure you fill in the earliest version that you know has the issue.
- Fork the repository on GitHub
- Follow First-Time Contributor Workflow
- and subsequent Contributor Workflow
- Make sure the code is properly formatted
- common mistake is changed original line-endings (DOS/unix) - make sure the patch can be clearly applied (particular line changes are clearly visible when using
git diff HEAD^or in GitHub commits history)
- common mistake is changed original line-endings (DOS/unix) - make sure the patch can be clearly applied (particular line changes are clearly visible when using
- More information on contributing
- Bug tracker (JIRA)
- Contributor License Agreement
- General GitHub documentation
- GitHub pull request documentation
- #richfaces IRC channel on irc.freenode.org
Hmm... I assumed that I would be able to do some kind of pull request after forking a Gist. That feature isn't there, so I am not exactly sure what the point forking a Gist is...
Anyway, the JBoss account link goes to github.com.