Re: [Gluster-devel] Maintainers 2.0 Proposal

Do we also plan to publish similar guidelines for deciding on Project maintainer? On Fri, Mar 24, 2017 at 2:24 AM, Michael Scherer wrote: > Le samedi 18 mars 2017 à 16:47 +0530, Pranith Kumar Karampuri a écrit : > > On Sat, Mar 18, 2017 at 1:20 AM, Amar Tumballi

Re: [Gluster-devel] Maintainers 2.0 Proposal

Le samedi 18 mars 2017 à 16:47 +0530, Pranith Kumar Karampuri a écrit : > On Sat, Mar 18, 2017 at 1:20 AM, Amar Tumballi wrote: > > > I don't want to take the discussions in another direction, but want > > clarity on few things: > > > > 1. Does maintainers means they are

Re: [Gluster-devel] Maintainers 2.0 Proposal

On Sat, Mar 18, 2017 at 01:20:31AM +0530, Amar Tumballi wrote: > I don't want to take the discussions in another direction, but want clarity > on few things: > > 1. Does maintainers means they are only reviewing/ merging patches? > 2. Should maintainers be responsible for answering ML / IRC

Re: [Gluster-devel] Maintainers 2.0 Proposal

On Sat, Mar 18, 2017 at 1:20 AM, Amar Tumballi wrote: > I don't want to take the discussions in another direction, but want > clarity on few things: > > 1. Does maintainers means they are only reviewing/ merging patches? > 2. Should maintainers be responsible for answering

Re: [Gluster-devel] Maintainers 2.0 Proposal

Posting in line, but it may be pretty hard to follow. Apologies if I miss something. On Fri, Mar 17, 2017 at 11:06 AM, Niels de Vos wrote: > On Wed, Mar 15, 2017 at 10:12:18PM -0400, Vijay Bellur wrote: > > Hi All, > > > > We have been working on a proposal [1] to make the

[Gluster-devel] Maintainers 2.0 Proposal

Hi All, We have been working on a proposal [1] to make the lifecycle management of Gluster maintainers more structured. We intend to make the proposal effective around 3.11 (May 2016). Please review the proposal and let us know your feedback. If you need clarity on any existing aspect or