Page History

...

• Source code and fixes contributionsDocumentation assistance
• New and better Documentation
• New blog theme and Admin UI designs
• Product and feature suggestions
• Detailed and constructive feedback
• Articles and white-papersConstructive feedback

Contributing to Roller should be easy and if it's not, please stop by the Roller mailing lists and tell us how we can make it easier. This document is a short guide to help contributors get started.

...

Join the developer mailing list, ask questions and help with those asked by others. Tell us how you use Roller, what you like and dislike. Discuss ideas you have for improving any aspect of the Roller project from the website to the documentation and code.

Fork our GitHub repo

If you are a GitHub user, get started by forking our GitHub repo: https://github.com/apache/roller.

Get your fixes and improvements in

If you've used Roller, you probably made small fixes and perhaps even add some new features. Getting these fixes and improvements helps Roller and it helps you because, once you get your fixes in you don't have to worry about adding them again when new versions of Roller come out.

• Download the Roller code from SVN and get setup to build it. There are instructions for this on the Roller Source Code page and in the in How to build Roller.

• Learn the code-base. Install a Maven plugin into your IDE so you can easily explore the Roller modules and source code base. Check out the Developer Resources page for documents and presentations that introduce the Roller architecture. Study the parts of the code you'd like to change, enhance, add to, etc. Subscribe to the Roller dev mailing list so you can ask the experts.

• Before you contribute a patch you must send in your individual contributor agreement make any big contributions you must sign an Individual Contributor License Agreement (ICLA) to the Apache Software Foundation via mail or FAX. See: http://www.apache.org/licenses/icla.txt

...