Contributing to the Gluster community
Are you itching to send in patches and participate as a developer in the Gluster community? Here are a number of starting points for getting involved. We don't require a signed contributor license agreement or copyright assignment, but we do require a "signed-off-by" line on each code check-in.
- Simplified Developer Workflow
- A simpler and faster intro to developing with GlusterFS, than the doc below.
- Developer Workflow - this tells you about our patch requirements, tools we use, and more. Required reading if you want to contribute code.
- Compiling RPMS - Step by step instructions for compiling Gluster RPMS
- Building GlusterFS - How to compile Gluster from source code. Including instructions for Ubuntu.
- Projects - Ideas for projects you could create
- EasyFix Bugs - Easy to fix bugs of GlusterFS. One of the best place to start contributing to GlusterFS.
- Fixing issues reported by tools for static code
- This is a good starting point for developers to fix bugs in GlusterFS project.
- Backport Wishlist - Problems fixed in the master branch might need to get fixed in stable release branches too.
- Backport Guidelines describe the steps that branches too.
- Our Jenkins Infrastructure - A braindump of the Jenkins infrastructure we have in place for automated testing
- Manual steps for setting up a Jenkins slave VM in Rackspace - Steps for setting up a slave VM in Rackspace
Other Gluster Developer documentation can be found here