Gluster users - Jun 2015 - Proposal for addition of maintainers and more...

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

I would like to propose Aravinda (avishwan at redhat.com) as a maintainer
for Geo-replication. I can act as a backup maintainer in his absence.

Hope it's not too late for this proposal.

-Venky

On Wed, Jun 3, 2015 at 5:20 PM, Vijay Bellur <vbellur at redhat.com>
wrote:
> 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-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel

On 06/03/2015 05:20 PM, Vijay Bellur wrote:
> 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.

These proposals are now live. To summarize:

1. The proposed new maintainers are now official and have been added to 
the glusterfs-maintainers group in gerrit. This should enable new 
maintainers to merge patches in gerrit. I will be sending a patch to 
update MAINTAINERS file in the code repository.

2. cli & glusterd code changes pertaining to specific components will be 
managed by respective component maintainers.

Regards,
Vijay