In keeping with the open development model, we’ve made the process of participation a bit easier to learn. Check out our developers home on the Gluster Community Forge. We now have a patch review system, with the requirement that any submitted patch must build and pass a battery of tests before acceptance into the main source tree. Read about the development process in the development workflow document.
After every new release, we take time to plan out the next release. The last time we got together, we planned out GlusterFS 3.4, which is now nearing release. You can see the features that went into this release here.
The next planning session will be for GlusterFS 3.5. You can see the beginning sketch of what features we are considering here. If you want to see other features included, or if you have ideas for a feature you would like to work on, add it to the list.