Hi All,
To supplement our ongoing effort of better patch management, I am
proposing the addition of more maintainers for various components. The
rationale behind this proposal & the responsibilities of maintainers
continue to be the same as discussed in these lists a while ago [1] [2].
Here is the proposed list:
Jeff Darcy: Overall Maintainer across various components.
Bitrot - Venky Shankar & Raghavendra Bhat
Erasure Coding - Xavier Hernandez & Pranith Karampuri
Fuse - Niels de Vos & Raghavendra Bhat
Glusterd - Atin Mukherjee
libglusterfs - Pranith Karampuri & Niels de Vos
Snapshot - Rajesh Joseph
Tiering & libgfdb - Dan Lambright
Upcall infrastructure - Niels de Vos
I think it is very appropriate for us to now consider tests as a core
component. In view of that, I propose the following maintainers for
tests to help us build our overall test strategy and improve test
coverage across the project.
Tests & distaf - Raghavendra Talur & Vishwanath Bhat
(for the uninitiated distaf is the regression test framework where we
will be plugging in more tests)
In addition, given how glusterd & cli code is structured it seems more
appropriate that respective component maintainers manage their part of
code in these directories. The existing glusterd & cli maintainers will
continue to manage the core framework.
We intend to roll ahead with these changes by 10th of June. Please let
us know if you have objections, concerns or feedback on any of these
proposals by then.
Thanks,
Vijay
[1] http://gluster.org/pipermail/gluster-devel/2014-April/025425.html
[2] http://www.gluster.org/pipermail/gluster-devel/2015-March/044176.html
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
