How to contribute to Roller
The Apache Roller project is being built by the open source community for the open source community - we welcome your input and contributions!
What we are looking for:
- Source code and fixes contributions
- New and better Documentation
- New blog theme and Admin UI designs
- Product and feature suggestions
- Constructive 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.
Anybody can contribute to Roller and anybody can join the project, it's an all-volunteer effort. The way to join the project is to subscribe to the development mailing list and start acting like a member of the project: asking questions, making suggestions, responding to question, proposing changes and submitting fixes and patches. If you get along well with others, do quality work and show some commitment to the project somebody will most likely nominate you to be a committer.
Join the developer mailing list
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 and build from the Roller source code. There are instructions for this in How to build Roller.
- Learn the code-base. Check out the Developer Resources page for more information.
- Before you make any big contributions you:
- MUST sign an Individual Contributor License Agreement (ICLA) form http://www.apache.org/licenses/icla.pdf and email a scan of the signed copy to email@example.com.
- MAY want to discuss your changes on the Roller developer mailing list
- MAY want to create a JIRA issue for your changes. Our JIRA is here: https://issues.apache.org/jira/browse/ROL
- Implement your changes and once you've got them working you can:
- Submit a GitHub Pull Request (PR) here: https://github.com/apache/roller.
- Create a new issue in our JIRA https://issues.apache.org/jira/browse/ROL and attach your patch to that.
- Please prepare patches as described here: http://www.apache.org/dev/contributors.html#patches
Propose and develop cool new features
If you're a Roller user already, you probably have ideas for some cool new features. If you're new to Roller, a student or teacher looking for project ideas then ask on the mailing list for ideas. Another way to find project ideas is to help triage Roller bug reports and RFEs in our issue tracking system (https://issues.apache.org/jira/browse/ROL). You'll definitely find ideas for fixes, improvements and new features that way.