On 06/12/2012 07:45 PM, Will Chan wrote:
I've taken all the feedback so far and extended the CloudStack Maintainers
Guide written by John and added all the maintainers so far. There are probably
more missing but that's what we have today. If we want this list to be its own
page, we can cer
Will
From: John Kinsella [j...@stratosec.co]
Sent: Tuesday, June 12, 2012 5:44 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: Maintainer/committer model for CloudStack
Thanks Will, I was thinking of doing similar.
I haven't raised a hand to be a maint
---
>> From: David Nalley [mailto:da...@gnsa.us]
>> Sent: Friday, June 01, 2012 7:57 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: Maintainer/committer model for CloudStack
>>
>> So it seems we have some consensus around trying this maintainer mo
>
> Will
>
> > -Original Message-
> > From: David Nalley [mailto:da...@gnsa.us]
> > Sent: Friday, June 01, 2012 7:57 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Re: Maintainer/committer model for CloudStack
> >
> > So it seems we ha
Friday, June 01, 2012 7:57 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Maintainer/committer model for CloudStack
>
> So it seems we have some consensus around trying this maintainer model out -
> so now we need the existing committers to step up for some of these
>To: cloudstack-dev@incubator.apache.org
>Subject: RE: Maintainer/committer model for CloudStack
>
>I'll take VMware and console proxy
>Kelven
>
>> -Original Message-
>> From: Anthony Xu [mailto:xuefei...@citrix.com]
>> Sent: Monday, June 11, 2012 6:21
I'll take VMware and console proxy
Kelven
> -Original Message-
> From: Anthony Xu [mailto:xuefei...@citrix.com]
> Sent: Monday, June 11, 2012 6:21 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Maintainer/committer model for CloudStack
>
> I'
I'll take XenServer and snapshot parts.
Regards,
Anthony
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Friday, June 01, 2012 7:57 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Maintainer/committer model for CloudStack
>
>
I can take up KVM part.
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Friday, June 01, 2012 7:57 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Maintainer/committer model for CloudStack
>
> So it seems we have some consens
Sorry for late reply.
I'll take OVM/Baremetal and setup now.
> -Original Message-
> From: Jessica Tomechak [mailto:jessica.tomec...@citrix.com]
> Sent: Monday, June 04, 2012 1:33 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Maintainer/committer model f
I can maintain documentation.
Jessica T.
CloudStack Tech Pubs
-Original Message-
From: David Nalley [mailto:da...@gnsa.us]
Sent: Friday, June 01, 2012 7:57 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: Maintainer/committer model for CloudStack
So it seems we have some
I can take up the Deployment Planners/Allocator components, EC2 API (awsapi).
-Prachi
-Original Message-
From: David Nalley [mailto:da...@gnsa.us]
Sent: Friday, June 01, 2012 7:57 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: Maintainer/committer model for CloudStack
So it
On Fri, Jun 1, 2012 at 10:19 PM, Alena Prokharchyk
wrote:
> On 6/1/12 7:57 PM, "David Nalley" wrote:
>
>>So it seems we have some consensus around trying this maintainer model
>>out - so now we need the existing committers to step up for some of
>>these 'modules'. I am happy to step up for packag
We can use http://jenkins.cloudstack.org/ for the same.
> -Original Message-
> From: Wido den Hollander [mailto:w...@widodh.nl]
> Sent: Saturday, June 02, 2012 5:37 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: David Nalley
> Subject: Re: Maintainer/committer mo
On 06/02/2012 04:57 AM, David Nalley wrote:
So it seems we have some consensus around trying this maintainer model
out - so now we need the existing committers to step up for some of
these 'modules'. I am happy to step up for packaging stuff (debs and
rpms) and some of the related things around
On 6/1/12 7:57 PM, "David Nalley" wrote:
>So it seems we have some consensus around trying this maintainer model
>out - so now we need the existing committers to step up for some of
>these 'modules'. I am happy to step up for packaging stuff (debs and
>rpms) and some of the related things around
So it seems we have some consensus around trying this maintainer model
out - so now we need the existing committers to step up for some of
these 'modules'. I am happy to step up for packaging stuff (debs and
rpms) and some of the related things around this such as initscripts.
I'd like to get to th
On Thu, May 17, 2012 at 2:08 AM, Chiradeep Vittal
wrote:
>
>
> On 5/16/12 11:33 AM, "John Kinsella" wrote:
>
>>On May 16, 2012, at 5:33 AM, Robert Schweikert wrote:
>>> On 05/15/2012 10:08 PM, John Kinsella wrote:
OK - took a little longer than intended, but I've got a draft put
together
On 5/16/12 11:33 AM, "John Kinsella" wrote:
>On May 16, 2012, at 5:33 AM, Robert Schweikert wrote:
>> On 05/15/2012 10:08 PM, John Kinsella wrote:
>>> OK - took a little longer than intended, but I've got a draft put
>>>together. I can keep adding to this, but wanted to get it out for
>>>commen
On Wed, May 16, 2012 at 2:31 PM, John Kinsella wrote:
> On May 15, 2012, at 9:21 PM, David Nalley wrote:
>> This is a discussion still - no need to move it away from this list IMO.
>>
>> John - thanks for writing this up.
>>
>> So there's a mixture of our own terminology and ASF terminology - and
On May 16, 2012, at 5:33 AM, Robert Schweikert wrote:
> On 05/15/2012 10:08 PM, John Kinsella wrote:
>> OK - took a little longer than intended, but I've got a draft put together.
>> I can keep adding to this, but wanted to get it out for comments on what's
>> written so far.
>>
>> One question
On May 15, 2012, at 9:21 PM, David Nalley wrote:
> This is a discussion still - no need to move it away from this list IMO.
>
> John - thanks for writing this up.
>
> So there's a mixture of our own terminology and ASF terminology - and
> I propose that we start with a lexicon, and here's what I'
On May 15, 2012, at 9:38 PM, Alex Huang wrote:
>> Contributors - people who contribute in one way or another to the project
>> Committers - people who have commit access to the project's repo(s)
>> Maintainers - volunteers from the pool of committers who have stepped
>> forward to shepherd a single
On Wed, May 16, 2012 at 1:09 PM, Chiradeep Vittal
wrote:
>
>
> On 5/15/12 11:39 PM, "David Nalley" wrote:
>
>>On Wed, May 16, 2012 at 12:38 AM, Alex Huang
>>wrote:
Contributors - people who contribute in one way or another to the
project
Committers - people who have commit access t
On 5/15/12 11:39 PM, "David Nalley" wrote:
>On Wed, May 16, 2012 at 12:38 AM, Alex Huang
>wrote:
>>> Contributors - people who contribute in one way or another to the
>>>project
>>> Committers - people who have commit access to the project's repo(s)
>>> Maintainers - volunteers from the pool o
I believe the worst person to perform quality assurance on code is the
person who wrote the code. It would be best to have someone else who
didn't write the code to test and make sure the application and new code
are functional because they are going to be approaching it with fresh eyes.
Matth
On 05/15/2012 10:08 PM, John Kinsella wrote:
OK - took a little longer than intended, but I've got a draft put together. I
can keep adding to this, but wanted to get it out for comments on what's
written so far.
One question - we seem to have "committers" as well as "maintainers." What's
the
On 05/16/2012 12:38 AM, Alex Huang wrote:
Contributors - people who contribute in one way or another to the project
Committers - people who have commit access to the project's repo(s)
Maintainers - volunteers from the pool of committers who have stepped
forward to shepherd a single module. This i
On Wed, May 16, 2012 at 12:38 AM, Alex Huang wrote:
>> Contributors - people who contribute in one way or another to the project
>> Committers - people who have commit access to the project's repo(s)
>> Maintainers - volunteers from the pool of committers who have stepped
>> forward to shepherd a
> Contributors - people who contribute in one way or another to the project
> Committers - people who have commit access to the project's repo(s)
> Maintainers - volunteers from the pool of committers who have stepped
> forward to shepherd a single module. This is not a position of authority - but
On Tue, May 15, 2012 at 10:14 PM, Alex Huang wrote:
> John,
>
> Should we comment by replying to this email or by adding comments to your
> page?
>
> Also,
>
>> One question - we seem to have "committers" as well as "maintainers."
>> What's the difference between the two?
>
> To me, committers ar
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Wednesday, May 16, 2012 7:45 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Maintainer/committer model for CloudStack
>
> John,
>
> Should we comment by replying
John,
Should we comment by replying to this email or by adding comments to your page?
Also,
> One question - we seem to have "committers" as well as "maintainers."
> What's the difference between the two?
To me, committers are contributors. Maintainers are gatekeepers to make sure
the process
OK - took a little longer than intended, but I've got a draft put together. I
can keep adding to this, but wanted to get it out for comments on what's
written so far.
One question - we seem to have "committers" as well as "maintainers." What's
the difference between the two?
I'm trying to rea
On May 7, 2012, at 11:06 AM, Frank Zhang wrote:
>>
>> On May 4, 2012, at 8:37 AM, David Nalley wrote:
>>> On Fri, May 4, 2012 at 12:24 AM, John Kinsella wrote:
Guys - during the developer on-ramp this week, we held a group
>> discussion around the topics of reviewing patch submissions, cod
On Fri, May 4, 2012 at 9:52 AM, Robert Schweikert wrote:
> On 05/04/2012 12:24 AM, John Kinsella wrote:
>>
>> Guys - during the developer on-ramp this week, we held a group discussion
>> around the topics of reviewing patch submissions, code maintainers, voting,
>> and overall care and management
>
> On May 4, 2012, at 8:37 AM, David Nalley wrote:
> > On Fri, May 4, 2012 at 12:24 AM, John Kinsella wrote:
> >> Guys - during the developer on-ramp this week, we held a group
> discussion around the topics of reviewing patch submissions, code
> maintainers, voting, and overall care and managem
On Fri, May 04, 2012 at 10:37:10AM -0500, David Nalley wrote:
> On Fri, May 4, 2012 at 12:24 AM, John Kinsella wrote:
> > I'm going to list out some of the points and goals we discussed, but this
> > probably isn't a complete list of things we should be considering:
> >
> > Goals:
> > * Responsi
On May 4, 2012, at 8:37 AM, David Nalley wrote:
> On Fri, May 4, 2012 at 12:24 AM, John Kinsella wrote:
>> Guys - during the developer on-ramp this week, we held a group discussion
>> around the topics of reviewing patch submissions, code maintainers, voting,
>> and overall care and management o
On 05/04/2012 12:24 AM, John Kinsella wrote:
Guys - during the developer on-ramp this week, we held a group discussion
around the topics of reviewing patch submissions, code maintainers, voting, and
overall care and management of the official source tree. We wanted to continue
the discussion o
On Fri, May 4, 2012 at 12:24 AM, John Kinsella wrote:
> Guys - during the developer on-ramp this week, we held a group discussion
> around the topics of reviewing patch submissions, code maintainers, voting,
> and overall care and management of the official source tree. We wanted to
> continue
Guys - during the developer on-ramp this week, we held a group discussion
around the topics of reviewing patch submissions, code maintainers, voting, and
overall care and management of the official source tree. We wanted to continue
the discussion on the developer list to look for the best way t
42 matches
Mail list logo
