Good point Amar.. Noted.
Avati
On Fri, Sep 6, 2013 at 1:40 AM, Amar Tumballi wrote:
> One of the other things we missed in this thread is how to handle bugs in
> bugzilla, and who should own the triage for high/urgent priority bugs.
>
> -Amar
>
>
> On Fri, Jul 26, 2013 at 10:56 PM, Anand Avati
One of the other things we missed in this thread is how to handle bugs in
bugzilla, and who should own the triage for high/urgent priority bugs.
-Amar
On Fri, Jul 26, 2013 at 10:56 PM, Anand Avati wrote:
> Hello everyone,
>
> We are in the process of formalizing the governance model of the
>
Hi
it seems the message below was written some time ago but was stuck in my
mailbox. Here is it released:
Anand Avati wrote:
> Please do. I'm curious to know how releases happen (release engineer?
> team?) and how new committers are added in the NetBSD project (votes? by
> who? are there quanti
On Wed, July 31, 2013 9:12 pm, Bharata B Rao wrote:
> On Fri, Jul 26, 2013 at 10:56 PM, Anand Avati
wrote:
>>
>> Looking forward to hearing from you!
>
> Hi Avati,
>
> As many said on the thread, frequent releases will be good.
>
> Another aspect which we felt could be improved is the timely revie
On Fri, Jul 26, 2013 at 10:56 PM, Anand Avati wrote:
>
> Looking forward to hearing from you!
Hi Avati,
As many said on the thread, frequent releases will be good.
Another aspect which we felt could be improved is the timely review
for the patches. Though this is the responsibility of the commu
On Sun, Jul 28, 2013 at 11:32 PM, Bryan Whitehead wrote:
> Weekend activities kept me away from watching this thread, wanted to
> add in more of my 2 cents... :)
>
> Major releases would be great to happen more often - but keeping
> current releases "more current" is really what I was talking abou
On 07/29/2013 12:02 PM, Bryan Whitehead wrote:
Weekend activities kept me away from watching this thread, wanted to
add in more of my 2 cents... :)
Major releases would be great to happen more often - but keeping
current releases "more current" is really what I was talking about.
Example, 3.3.0
Weekend activities kept me away from watching this thread, wanted to
add in more of my 2 cents... :)
Major releases would be great to happen more often - but keeping
current releases "more current" is really what I was talking about.
Example, 3.3.0 was a pretty solid release but some annoying bugs
Harshavardhana wrote:
> What is good for GlusterFS as a whole is highly debatable - since there
> are no module owners/subsystem maintainers as of yet at-least on paper.
Just my two cents on that: you need to make clear if a module maintainer
is a dictator or a steward for the module: does he ha
On Sun, Jul 28, 2013 at 9:23 AM, Emmanuel Dreyfus wrote:
> Anand Avati wrote:
>
> > We are in the process of formalizing the governance model of the
> > GlusterFS project. Historically, the governance of the project has been
> > loosely structured. This is an invitation to all of you to partic
Anand Avati wrote:
> We are in the process of formalizing the governance model of the
> GlusterFS project. Historically, the governance of the project has been
> loosely structured. This is an invitation to all of you to participate in
> this discussion and provide your feedback and suggestions
Avati,
Glad that such a discussion came up :-)
Few comments inline.
>
> Here are some specific topics to seed the discussion:
>
> - Core team formation
> - what are the qualifications for membership (e.g contributions of code,
> doc, packaging, support on irc/lists, how to quantify?)
> -
12 matches
Mail list logo
