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.

• License Change - we recently changed the client library code to a dual license under the GPL v2 and the LGPL v3 or later

• GlusterFS Coding Standards

• If you are not sure of where to start, and what to do, we have a small write-up on what you can pick. Check it out

• Steps to be followed when adding a new FOP to GlusterFS

• Cluster/afr translator
• History of Locking in AFR
• Self heal Daemon

• inode data structure
• iobuf data structure
• mem-pool data structure

Find the gfapi symbol versions here

• How to introduce new daemons using daemon management framework

• Performance/write-Behind Translator
• Translator Development
• Storage/posix Translator

• Brick mux resource reduction

• Interrupt handling

• Unit Tests in GlusterFS
• Using the Gluster Test Framework - Step by step instructions for running the Gluster Test Framework
• Coredump Analysis - Steps to analize coredumps generated by regression machines.
• Identifying Resource Leaks

• Versioning