After beginning my journey with [[!gluster]] some months ago
and my recent blog about
[[How to access gluster from multiple networks|how-to-access-gluster-from-multiple-networks]],
I have made a great experience with glusterfs yesterday:
After [mentioning that I have the same problem](http://www.gluster.org/pipermail/gluster-users/2015-March/020945.html) as [何亦](http://www.gluster.org/pipermail/gluster-users/2015-March/020939.html)
and [suggesting a patch](http://www.gluster.org/pipermail/gluster-users/2015-March/020948.html),
1. Someone ([[!twitter nixpanic]] aka Niels) suggested to prepare it for inclusion
1. GlusterFS has [an organic process for development and testing](http://www.gluster.org/community/documentation/index.php/Simplified_dev_workflow) - seeing the patch going through this process gives me the impression someone cares about code quality
1. After creating the [bugreport](https://bugzilla.redhat.com/show_bug.cgi?id=1199577), the process smoothly started
1. The patch was reviewed within hours
1. And finally merged into the master branch as well as [included for glusterfs 3.6.3](http://www.gluster.org/pipermail/gluster-users/2015-March/020955.html)