All,
Thanks for participating actively in the discussions. With all your
co-operation we now have a update on maintainers 2.0 proposal. Vijay Bellur
sent a patch last week [1] capturing all the discussions.
Please go through the patch and see if you have any more concerns. There
are many new
On Mon, Apr 17, 2017 at 04:53:55PM -0700, Amye Scavarda wrote:
> On Fri, Apr 14, 2017 at 2:40 AM, Michael Scherer
> wrote:
>
> > Le jeudi 13 avril 2017 à 18:01 -0700, Amye Scavarda a écrit :
> > > In light of community conversations, I've put some revisions on the
> > >
On Fri, Apr 14, 2017 at 2:40 AM, Michael Scherer
wrote:
> Le jeudi 13 avril 2017 à 18:01 -0700, Amye Scavarda a écrit :
> > In light of community conversations, I've put some revisions on the
> > Maintainers changes, outlined in the hackmd pad:
> >
On Fri, Apr 14, 2017 at 11:40:35AM +0200, Michael Scherer wrote:
> Le jeudi 13 avril 2017 à 18:01 -0700, Amye Scavarda a écrit :
> > In light of community conversations, I've put some revisions on the
> > Maintainers changes, outlined in the hackmd pad:
> > https://hackmd.io/s/SkwiZd4qe
> >
> >
Le jeudi 13 avril 2017 à 18:01 -0700, Amye Scavarda a écrit :
> In light of community conversations, I've put some revisions on the
> Maintainers changes, outlined in the hackmd pad:
> https://hackmd.io/s/SkwiZd4qe
>
> Feedback welcomed!
>
> Note that the goals of this are to expand out our
;
> > Cc: "Amar Tumballi" <atumb...@redhat.com>, "GlusterFS Maintainers" <
> maintainers@gluster.org>, "Gluster Devel"
> > <gluster-de...@gluster.org>, "Michael Scherer" <msche...@redhat.com>
> > Sent: Saturday, Ma
ers@gluster.org>, "Gluster Devel"
> <gluster-de...@gluster.org>, "Michael Scherer" <msche...@redhat.com>
> Sent: Saturday, March 25, 2017 5:22:44 PM
> Subject: Re: [Gluster-Maintainers] [Gluster-devel] Maintainers 2.0 Proposal
>
>
>
> - Origin
luster.org>, "Gluster Devel"
> <gluster-de...@gluster.org>
> Sent: Friday, March 24, 2017 7:12:32 PM
> Subject: Re: [Gluster-Maintainers] [Gluster-devel] Maintainers 2.0 Proposal
>
> Do we also plan to publish similar guidelines for deciding on Project
> maintainer
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
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
On Sat, Mar 18, 2017 at 7:17 AM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
>
>
> 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
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
On Sat, Mar 18, 2017 at 4:47 PM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
>
>
> 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
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
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 questions
(well, they should focus more on documentation IMO).
3. Who's
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
On Fri, Mar 17, 2017 at 07:06:53PM +0100, 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 lifecycle management of
> > Gluster maintainers more structured. We intend to make the proposal
> >
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 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
18 matches
Mail list logo