You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Alex Huang <Al...@citrix.com> on 2013/02/22 01:52:12 UTC
[DISCUSS] Animesh Chaturvedi as a committer
Hi,
I like to discuss nominating Animesh as a committer. Animesh joined back in December time frame and quickly became an advocate for CloudStack. He has quickly come up to speed on CloudStack and on how it should work in Apache. He's handled the difficult IP clearance issues and helped minimize its problems. He's arranged for meetups for CloudStack. He's working with everyone to come up with better processes. He's basically everywhere on mailing list. I think he will make for a great committer.
--Alex
RE: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Frank Zhang <Fr...@citrix.com>.
+1
> -----Original Message-----
> From: Alex Huang [mailto:Alex.Huang@citrix.com]
> Sent: Thursday, February 21, 2013 4:52 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: [DISCUSS] Animesh Chaturvedi as a committer
>
> Hi,
>
> I like to discuss nominating Animesh as a committer. Animesh joined back in
> December time frame and quickly became an advocate for CloudStack. He
> has quickly come up to speed on CloudStack and on how it should work in
> Apache. He's handled the difficult IP clearance issues and helped minimize
> its problems. He's arranged for meetups for CloudStack. He's working with
> everyone to come up with better processes. He's basically everywhere on
> mailing list. I think he will make for a great committer.
>
> --Alex
>
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Mice Xia <we...@gmail.com>.
+1
-Mice
2013/2/22 Gavin Lee <ga...@gmail.com>:
> +1
>
> On Fri, Feb 22, 2013 at 10:14 AM, Min Chen <mi...@citrix.com> wrote:
>> +1, well deserved.
>>
>> -min
>>
>> On 2/21/13 5:54 PM, "Vijayendra Bhamidipati"
>> <vi...@citrix.com> wrote:
>>
>>>+1
>>>
>>>-----Original Message-----
>>>From: Ahmad Emneina [mailto:aemneina@gmail.com]
>>>Sent: Thursday, February 21, 2013 5:45 PM
>>>To: cloudstack-dev@incubator.apache.org
>>>Subject: Re: [DISCUSS] Animesh Chaturvedi as a committer
>>>
>>>+1... couldnt refrain.
>>>
>>>
>>>On Thu, Feb 21, 2013 at 5:35 PM, Sonny Chhen <So...@citrix.com>
>>>wrote:
>>>
>>>> +1
>>>>
>>>> Sent from my iPhone
>>>>
>>>> Thank You and Best Regards,
>>>>
>>>> Sonny H. Chhen
>>>> www.SChhen.com
>>>>
>>>> On Feb 21, 2013, at 4:52 PM, "Alex Huang" <Al...@citrix.com> wrote:
>>>>
>>>> > Hi,
>>>> >
>>>> > I like to discuss nominating Animesh as a committer. Animesh joined
>>>> back in December time frame and quickly became an advocate for
>>>>CloudStack.
>>>> He has quickly come up to speed on CloudStack and on how it should
>>>> work in Apache. He's handled the difficult IP clearance issues and
>>>> helped minimize its problems. He's arranged for meetups for
>>>> CloudStack. He's working with everyone to come up with better
>>>> processes. He's basically everywhere on mailing list. I think he will
>>>>make for a great committer.
>>>> >
>>>> > --Alex
>>>> >
>>>> >
>>>>
>>
>
>
>
> --
> Gavin
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Gavin Lee <ga...@gmail.com>.
+1
On Fri, Feb 22, 2013 at 10:14 AM, Min Chen <mi...@citrix.com> wrote:
> +1, well deserved.
>
> -min
>
> On 2/21/13 5:54 PM, "Vijayendra Bhamidipati"
> <vi...@citrix.com> wrote:
>
>>+1
>>
>>-----Original Message-----
>>From: Ahmad Emneina [mailto:aemneina@gmail.com]
>>Sent: Thursday, February 21, 2013 5:45 PM
>>To: cloudstack-dev@incubator.apache.org
>>Subject: Re: [DISCUSS] Animesh Chaturvedi as a committer
>>
>>+1... couldnt refrain.
>>
>>
>>On Thu, Feb 21, 2013 at 5:35 PM, Sonny Chhen <So...@citrix.com>
>>wrote:
>>
>>> +1
>>>
>>> Sent from my iPhone
>>>
>>> Thank You and Best Regards,
>>>
>>> Sonny H. Chhen
>>> www.SChhen.com
>>>
>>> On Feb 21, 2013, at 4:52 PM, "Alex Huang" <Al...@citrix.com> wrote:
>>>
>>> > Hi,
>>> >
>>> > I like to discuss nominating Animesh as a committer. Animesh joined
>>> back in December time frame and quickly became an advocate for
>>>CloudStack.
>>> He has quickly come up to speed on CloudStack and on how it should
>>> work in Apache. He's handled the difficult IP clearance issues and
>>> helped minimize its problems. He's arranged for meetups for
>>> CloudStack. He's working with everyone to come up with better
>>> processes. He's basically everywhere on mailing list. I think he will
>>>make for a great committer.
>>> >
>>> > --Alex
>>> >
>>> >
>>>
>
--
Gavin
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Min Chen <mi...@citrix.com>.
+1, well deserved.
-min
On 2/21/13 5:54 PM, "Vijayendra Bhamidipati"
<vi...@citrix.com> wrote:
>+1
>
>-----Original Message-----
>From: Ahmad Emneina [mailto:aemneina@gmail.com]
>Sent: Thursday, February 21, 2013 5:45 PM
>To: cloudstack-dev@incubator.apache.org
>Subject: Re: [DISCUSS] Animesh Chaturvedi as a committer
>
>+1... couldnt refrain.
>
>
>On Thu, Feb 21, 2013 at 5:35 PM, Sonny Chhen <So...@citrix.com>
>wrote:
>
>> +1
>>
>> Sent from my iPhone
>>
>> Thank You and Best Regards,
>>
>> Sonny H. Chhen
>> www.SChhen.com
>>
>> On Feb 21, 2013, at 4:52 PM, "Alex Huang" <Al...@citrix.com> wrote:
>>
>> > Hi,
>> >
>> > I like to discuss nominating Animesh as a committer. Animesh joined
>> back in December time frame and quickly became an advocate for
>>CloudStack.
>> He has quickly come up to speed on CloudStack and on how it should
>> work in Apache. He's handled the difficult IP clearance issues and
>> helped minimize its problems. He's arranged for meetups for
>> CloudStack. He's working with everyone to come up with better
>> processes. He's basically everywhere on mailing list. I think he will
>>make for a great committer.
>> >
>> > --Alex
>> >
>> >
>>
RE: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Vijayendra Bhamidipati <vi...@citrix.com>.
+1
-----Original Message-----
From: Ahmad Emneina [mailto:aemneina@gmail.com]
Sent: Thursday, February 21, 2013 5:45 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] Animesh Chaturvedi as a committer
+1... couldnt refrain.
On Thu, Feb 21, 2013 at 5:35 PM, Sonny Chhen <So...@citrix.com> wrote:
> +1
>
> Sent from my iPhone
>
> Thank You and Best Regards,
>
> Sonny H. Chhen
> www.SChhen.com
>
> On Feb 21, 2013, at 4:52 PM, "Alex Huang" <Al...@citrix.com> wrote:
>
> > Hi,
> >
> > I like to discuss nominating Animesh as a committer. Animesh joined
> back in December time frame and quickly became an advocate for CloudStack.
> He has quickly come up to speed on CloudStack and on how it should
> work in Apache. He's handled the difficult IP clearance issues and
> helped minimize its problems. He's arranged for meetups for
> CloudStack. He's working with everyone to come up with better
> processes. He's basically everywhere on mailing list. I think he will make for a great committer.
> >
> > --Alex
> >
> >
>
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Ahmad Emneina <ae...@gmail.com>.
+1... couldnt refrain.
On Thu, Feb 21, 2013 at 5:35 PM, Sonny Chhen <So...@citrix.com> wrote:
> +1
>
> Sent from my iPhone
>
> Thank You and Best Regards,
>
> Sonny H. Chhen
> www.SChhen.com
>
> On Feb 21, 2013, at 4:52 PM, "Alex Huang" <Al...@citrix.com> wrote:
>
> > Hi,
> >
> > I like to discuss nominating Animesh as a committer. Animesh joined
> back in December time frame and quickly became an advocate for CloudStack.
> He has quickly come up to speed on CloudStack and on how it should work in
> Apache. He's handled the difficult IP clearance issues and helped minimize
> its problems. He's arranged for meetups for CloudStack. He's working
> with everyone to come up with better processes. He's basically everywhere
> on mailing list. I think he will make for a great committer.
> >
> > --Alex
> >
> >
>
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Sonny Chhen <So...@citrix.com>.
+1
Sent from my iPhone
Thank You and Best Regards,
Sonny H. Chhen
www.SChhen.com
On Feb 21, 2013, at 4:52 PM, "Alex Huang" <Al...@citrix.com> wrote:
> Hi,
>
> I like to discuss nominating Animesh as a committer. Animesh joined back in December time frame and quickly became an advocate for CloudStack. He has quickly come up to speed on CloudStack and on how it should work in Apache. He's handled the difficult IP clearance issues and helped minimize its problems. He's arranged for meetups for CloudStack. He's working with everyone to come up with better processes. He's basically everywhere on mailing list. I think he will make for a great committer.
>
> --Alex
>
>
RE: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Sateesh Chodapuneedi <sa...@citrix.com>.
> -----Original Message-----
> From: Alex Huang [mailto:Alex.Huang@citrix.com]
> Sent: 22 February 2013 06:22
> To: cloudstack-dev@incubator.apache.org
> Subject: [DISCUSS] Animesh Chaturvedi as a committer
>
> Hi,
>
> I like to discuss nominating Animesh as a committer. Animesh joined back in
> December time frame and quickly became an advocate for CloudStack. He has
> quickly come up to speed on CloudStack and on how it should work in Apache.
> He's handled the difficult IP clearance issues and helped minimize its problems.
> He's arranged for meetups for CloudStack. He's working with everyone to
> come up with better processes. He's basically everywhere on mailing list. I think
> he will make for a great committer.
+1
>
> --Alex
>
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Prasanna Santhanam <ts...@apache.org>.
On Fri, Feb 22, 2013 at 02:56:30PM +0530, Rohit Yadav wrote:
> >
> > You can rant, but I hope you didn't imply that the others on this thread
> > were "brainlessly following".
>
> I can rant, but out of all the things I've to say it's sad the only
> thing that got attention was this:
> " +1 also because follow everyone on this thread brainlessly!"
>
> The statement just implies that the author (me :) is voting a +1 to
> follow brainlessly with everyone else. And why not because who cares
> about giving committership to contributors, QA, doc guys whose lives
> will become easier and they reviews won't have to depend on mercy of
> some other committer, let's give it to the guy who works the emailz :P
>
My 2 cents:
Various QA and doc folks have worked tirelessly putting through bug
reports, fixing doc issues when "pressed" in to action. I for one
don't like (hate, loath, any other superlatives) the idea of people in
a position to mobilize a team get credit before individuals. Let's
please show what we are made up of instead of standing on the
shoulders of giants. All of that goes against the idea of an apache
meritocracy.
It's the lack of transparency that shook the 'foundations' of a
project that is not named here. Let's avoid running into that wall in
the future.
--
Prasanna.,
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Rohit Yadav <bh...@apache.org>.
>
> You can rant, but I hope you didn't imply that the others on this thread
> were "brainlessly following".
I can rant, but out of all the things I've to say it's sad the only
thing that got attention was this:
" +1 also because follow everyone on this thread brainlessly!"
The statement just implies that the author (me :) is voting a +1 to
follow brainlessly with everyone else. And why not because who cares
about giving committership to contributors, QA, doc guys whose lives
will become easier and they reviews won't have to depend on mercy of
some other committer, let's give it to the guy who works the emailz :P
Regards.
>
> Other than that, +1 to all the folks mentioned :)
> --
> Chiradeep
>
RE: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Donal Lafferty <do...@citrix.com>.
Rohit's evidence is that we're slowing down our best dev contributors by not nominating them for committer status.
Referring to concrete measures of performance is also a more inclusive approach to committer nomination. At least among developers.
Can we not do this on a monthly or quarterly basis? It gives participants something interesting to strive towards.
DL
Disclaimers... My git rank is quite low, so this move would make no difference to me :)
> -----Original Message-----
> From: Chiradeep Vittal [mailto:Chiradeep.Vittal@citrix.com]
> Sent: 22 February 2013 07:16
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Animesh Chaturvedi as a committer
>
>
>
> On 2/21/13 11:01 PM, "Rohit Yadav" <bh...@apache.org> wrote:
>
> >On Fri, Feb 22, 2013 at 6:29 AM, Alex Huang <Al...@citrix.com>
> wrote:
> >> This was not meant for cloudstack-dev....I'm sure I will get a ton of
> >>+1 replies but please refrain from replying to this.
> >
> >While this is the first time a proposal was made public, I had to rant,
> >the toughest email I had to write, but anyway you should ignore
> >it:
> >
> >Should we have transparency on committer proposals and votes? It's
> >because I feel we're not proposing people based on pure merits. For
> >example, my git rank (git shortlog -sn) and ML participating tells me
> >the following folks were participating since many months, they have
> >good commits and their patches only fall behind due to their review not
> >getting love on time:
> > 21 Sateesh Chodapuneedi
> > 20 Devdeep Singh
> > 16 Sanjay Tripathi
> > 14 James Martin
> > 12 Gavin Lee
> >
> >While not denying or taking away anything but I'm actually
> >acknowledging and appreciating the good work Animesh did.
> >Since I signed the ICLA and think I understand the apache culture [1][2]:
> >
> >Wearing my daily job hat:
> >+1 also because follow everyone on this thread brainlessly!
> >
> >Wearing my opensource hippie aka apache hat:
> >-1 because I think there are other folks here for months who are not
> >receiving love. Animesh's work is more like ppmc folks, he could mature
> >into one later, but what about people who have made good commits, their
> >contributors should be made easier by providing them commit access,
> >they are already committed to the community.
> >
> >Regards.
> >
> >[1] https://www.youtube.com/watch?v=fiDchgAmIBw
> >[2] http://www.apache.org/foundation/how-it-works.html
> >
> >Your truly,
> >Just another apache committer.
>
> You can rant, but I hope you didn't imply that the others on this thread were
> "brainlessly following".
>
> Other than that, +1 to all the folks mentioned :)
> --
> Chiradeep
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Joe Brockmeier <jz...@zonker.net>.
On Fri, Feb 22, 2013, at 05:51 AM, Rohit Yadav wrote:
> Jzb, I think ASF allows people to discuss things as an individual if
> that has to mean ask questions, or raise concerns. IMHO I spoke for
> the community, asking PPMC about what they would do for the community
> folks who're putting their efforts for months but may have been
> overlooked. And if you think I was "holding other folks feet to the
> fire", sure so does that mean I cannot ask questions or raise
> concerns, doubts? I'm sorry about that then, I was honest and
> opinions, words were mine alone.
>
We all discuss things *as* individuals, but it's not considered a good
practice to discuss individuals on a public list. As Hugo said, there's
no delete key for the Internet. It also puts people in an awkward
position to say "hey, give me your opinion of Mary right here in public.
Explain why you think she should or shouldn't be a committer, right here
where everyone else can see it."
If you want "brainless" +1's that's the way to do it, because who wants
to be the one saying "no, I don't think Mary is a good candidate and
here's why"? It's bad enough to have to do that in private, who wants to
do that to someone's face *and* have it archived on a public list?
By and large, I believe very strongly that we should conduct business in
the open. We should review code in the open. We should make decisions
about processes in the open. The few times I've been contacted
privately/off-list about decisions that need to be taken on the list,
I've always steered those back to the list.
Discussing individuals (or legal matters) is the exception to that, for
the reasons I've already expressed and many others.
Best,
jzb
--
Joe Brockmeier
jzb@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Rohit Yadav <bh...@apache.org>.
On Fri, Feb 22, 2013 at 5:01 PM, Hugo Trippaers
<HT...@schubergphilis.com> wrote:
>
>
>> -----Original Message-----
>> From: rohityadav89@gmail.com [mailto:rohityadav89@gmail.com] On Behalf
>> Of Rohit Yadav
>> Sent: vrijdag 22 februari 2013 12:24
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [DISCUSS] Animesh Chaturvedi as a committer
>>
>> On Fri, Feb 22, 2013 at 4:03 PM, Joe Brockmeier <jz...@zonker.net> wrote:
>> > On Fri, Feb 22, 2013, at 01:01 AM, Rohit Yadav wrote:
>> >> On Fri, Feb 22, 2013 at 6:29 AM, Alex Huang <Al...@citrix.com>
>> >> wrote:
>> >> > This was not meant for cloudstack-dev....I'm sure I will get a ton of +1
>> replies but please refrain from replying to this.
>> >>
>> >> While this is the first time a proposal was made public, I had to
>> >> rant, the toughest email I had to write, but anyway you should ignore
>> >> it:
>> >>
>> >> Should we have transparency on committer proposals and votes? It's
>> >
>> > No. When we have a discussion/vote about a committer, we should be
>> > able to have a frank conversation about that person's contributions -
>> > which may or may not be something an individual would want aired in a
>> > public forum, and a public forum is not the best way to get honest
>> > feedback about an individual.
>> >
>> > I don't have any problem publicly saying "I don't think your idea /
>> > patch is good" but that's a far cry from saying - on a publicly
>> > archived list, mind you - "Bob Q. Contributor is not someone I'd like
>> > to give commit access to."
>>
>> There were no personal remarks about anybody's abilities or skills in my
>> email so I don't see why you're saying this, neither I'm blaming the PPMC or
>> questioning the proposal.
>> In fact I'm saying that there are folks whose contributions and skills may have
>> been overlooked.
>>
>> >
>> >> because I feel we're not proposing people based on pure merits.
>> >
>> > I think you're mistaking merits for metrics below. That's not to say
>> > no one below has merit, but how many messages are sent to the mailing
>> > list or the number of patches are not, strictly speaking, the only
>> > things that we should look at.
>> >
>> > - Does a person submit a good patch that should have gone in
>> > immediately, or does it require guidance before being put in?
>> > - Are they following good community practices?
>> > - Have they been doing this consistently over time?
>> >
>>
>> So, these things may not be measurable, ppmc should be in a better position
>> to do that.
>> Okay so how does a non-ppmc member in this project propose for a
>> committer?
>
> Send a mail to cloudstack-private@incubator.apache.org with whom you like to nominate and why. Or catch one of us on IRC, meetups or any other way like joe put in his email below. The main thing > is that we want to discuss those things in private to ensure privacy for the individuals concerned. The internet has no delete button ;-)
Thanks Hugo will do.
Jzb, I think ASF allows people to discuss things as an individual if
that has to mean ask questions, or raise concerns. IMHO I spoke for
the community, asking PPMC about what they would do for the community
folks who're putting their efforts for months but may have been
overlooked. And if you think I was "holding other folks feet to the
fire", sure so does that mean I cannot ask questions or raise
concerns, doubts? I'm sorry about that then, I was honest and
opinions, words were mine alone.
Regards.
PS. I should just become a codemonkey
>
>
>>
>> Regards.
>>
>> >> example, my git rank (git shortlog -sn) and ML participating tells me
>> >> the following folks were participating since many months, they have
>> >> good commits and their patches only fall behind due to their review
>> >> not getting love on time:
>> >> 21 Sateesh Chodapuneedi
>> >> 20 Devdeep Singh
>> >> 16 Sanjay Tripathi
>> >> 14 James Martin
>> >> 12 Gavin Lee
>> >
>> > Actually, Gavin is already a committer.
>> >
>> > Anyway - if you feel someone is deserving of committer status, and
>> > you're not on the PPMC, I'd encourage you to speak up (privately) to
>> > someone on the PPMC if you feel they're being overlooked. But
>> > discussing specific individuals on -dev is unfair to those people and
>> > puts the PPMC in a bad position.
>> >
>> > Best,
>> >
>> > jzb
>> > --
>> > Joe Brockmeier
>> > jzb@zonker.net
>> > Twitter: @jzb
>> > http://www.dissociatedpress.net/
RE: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Hugo Trippaers <HT...@schubergphilis.com>.
> -----Original Message-----
> From: rohityadav89@gmail.com [mailto:rohityadav89@gmail.com] On Behalf
> Of Rohit Yadav
> Sent: vrijdag 22 februari 2013 12:24
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Animesh Chaturvedi as a committer
>
> On Fri, Feb 22, 2013 at 4:03 PM, Joe Brockmeier <jz...@zonker.net> wrote:
> > On Fri, Feb 22, 2013, at 01:01 AM, Rohit Yadav wrote:
> >> On Fri, Feb 22, 2013 at 6:29 AM, Alex Huang <Al...@citrix.com>
> >> wrote:
> >> > This was not meant for cloudstack-dev....I'm sure I will get a ton of +1
> replies but please refrain from replying to this.
> >>
> >> While this is the first time a proposal was made public, I had to
> >> rant, the toughest email I had to write, but anyway you should ignore
> >> it:
> >>
> >> Should we have transparency on committer proposals and votes? It's
> >
> > No. When we have a discussion/vote about a committer, we should be
> > able to have a frank conversation about that person's contributions -
> > which may or may not be something an individual would want aired in a
> > public forum, and a public forum is not the best way to get honest
> > feedback about an individual.
> >
> > I don't have any problem publicly saying "I don't think your idea /
> > patch is good" but that's a far cry from saying - on a publicly
> > archived list, mind you - "Bob Q. Contributor is not someone I'd like
> > to give commit access to."
>
> There were no personal remarks about anybody's abilities or skills in my
> email so I don't see why you're saying this, neither I'm blaming the PPMC or
> questioning the proposal.
> In fact I'm saying that there are folks whose contributions and skills may have
> been overlooked.
>
> >
> >> because I feel we're not proposing people based on pure merits.
> >
> > I think you're mistaking merits for metrics below. That's not to say
> > no one below has merit, but how many messages are sent to the mailing
> > list or the number of patches are not, strictly speaking, the only
> > things that we should look at.
> >
> > - Does a person submit a good patch that should have gone in
> > immediately, or does it require guidance before being put in?
> > - Are they following good community practices?
> > - Have they been doing this consistently over time?
> >
>
> So, these things may not be measurable, ppmc should be in a better position
> to do that.
> Okay so how does a non-ppmc member in this project propose for a
> committer?
Send a mail to cloudstack-private@incubator.apache.org with whom you like to nominate and why. Or catch one of us on IRC, meetups or any other way like joe put in his email below. The main thing is that we want to discuss those things in private to ensure privacy for the individuals concerned. The internet has no delete button ;-)
>
> Regards.
>
> >> example, my git rank (git shortlog -sn) and ML participating tells me
> >> the following folks were participating since many months, they have
> >> good commits and their patches only fall behind due to their review
> >> not getting love on time:
> >> 21 Sateesh Chodapuneedi
> >> 20 Devdeep Singh
> >> 16 Sanjay Tripathi
> >> 14 James Martin
> >> 12 Gavin Lee
> >
> > Actually, Gavin is already a committer.
> >
> > Anyway - if you feel someone is deserving of committer status, and
> > you're not on the PPMC, I'd encourage you to speak up (privately) to
> > someone on the PPMC if you feel they're being overlooked. But
> > discussing specific individuals on -dev is unfair to those people and
> > puts the PPMC in a bad position.
> >
> > Best,
> >
> > jzb
> > --
> > Joe Brockmeier
> > jzb@zonker.net
> > Twitter: @jzb
> > http://www.dissociatedpress.net/
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Rohit Yadav <bh...@apache.org>.
On Fri, Feb 22, 2013 at 4:03 PM, Joe Brockmeier <jz...@zonker.net> wrote:
> On Fri, Feb 22, 2013, at 01:01 AM, Rohit Yadav wrote:
>> On Fri, Feb 22, 2013 at 6:29 AM, Alex Huang <Al...@citrix.com>
>> wrote:
>> > This was not meant for cloudstack-dev....I'm sure I will get a ton of +1 replies but please refrain from replying to this.
>>
>> While this is the first time a proposal was made public, I had to
>> rant, the toughest email I had to write, but anyway you should ignore
>> it:
>>
>> Should we have transparency on committer proposals and votes? It's
>
> No. When we have a discussion/vote about a committer, we should be able
> to have a frank conversation about that person's contributions - which
> may or may not be something an individual would want aired in a public
> forum, and a public forum is not the best way to get honest feedback
> about an individual.
>
> I don't have any problem publicly saying "I don't think your idea /
> patch is good" but that's a far cry from saying - on a publicly archived
> list, mind you - "Bob Q. Contributor is not someone I'd like to give
> commit access to."
There were no personal remarks about anybody's abilities or skills in
my email so I don't see why you're saying this, neither I'm blaming
the PPMC or questioning the proposal.
In fact I'm saying that there are folks whose contributions and skills
may have been overlooked.
>
>> because I feel we're not proposing people based on pure merits.
>
> I think you're mistaking merits for metrics below. That's not to say no
> one below has merit, but how many messages are sent to the mailing list
> or the number of patches are not, strictly speaking, the only things
> that we should look at.
>
> - Does a person submit a good patch that should have gone in
> immediately, or does it require guidance before being put in?
> - Are they following good community practices?
> - Have they been doing this consistently over time?
>
So, these things may not be measurable, ppmc should be in a better
position to do that.
Okay so how does a non-ppmc member in this project propose for a committer?
Regards.
>> example, my git rank (git shortlog -sn) and ML participating tells me
>> the following folks were participating since many months, they have
>> good commits and their patches only fall behind due to their review
>> not getting love on time:
>> 21 Sateesh Chodapuneedi
>> 20 Devdeep Singh
>> 16 Sanjay Tripathi
>> 14 James Martin
>> 12 Gavin Lee
>
> Actually, Gavin is already a committer.
>
> Anyway - if you feel someone is deserving of committer status, and
> you're not on the PPMC, I'd encourage you to speak up (privately) to
> someone on the PPMC if you feel they're being overlooked. But discussing
> specific individuals on -dev is unfair to those people and puts the PPMC
> in a bad position.
>
> Best,
>
> jzb
> --
> Joe Brockmeier
> jzb@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Joe Brockmeier <jz...@zonker.net>.
On Fri, Feb 22, 2013, at 01:01 AM, Rohit Yadav wrote:
> On Fri, Feb 22, 2013 at 6:29 AM, Alex Huang <Al...@citrix.com>
> wrote:
> > This was not meant for cloudstack-dev....I'm sure I will get a ton of +1 replies but please refrain from replying to this.
>
> While this is the first time a proposal was made public, I had to
> rant, the toughest email I had to write, but anyway you should ignore
> it:
>
> Should we have transparency on committer proposals and votes? It's
No. When we have a discussion/vote about a committer, we should be able
to have a frank conversation about that person's contributions - which
may or may not be something an individual would want aired in a public
forum, and a public forum is not the best way to get honest feedback
about an individual.
I don't have any problem publicly saying "I don't think your idea /
patch is good" but that's a far cry from saying - on a publicly archived
list, mind you - "Bob Q. Contributor is not someone I'd like to give
commit access to."
> because I feel we're not proposing people based on pure merits.
I think you're mistaking merits for metrics below. That's not to say no
one below has merit, but how many messages are sent to the mailing list
or the number of patches are not, strictly speaking, the only things
that we should look at.
- Does a person submit a good patch that should have gone in
immediately, or does it require guidance before being put in?
- Are they following good community practices?
- Have they been doing this consistently over time?
> example, my git rank (git shortlog -sn) and ML participating tells me
> the following folks were participating since many months, they have
> good commits and their patches only fall behind due to their review
> not getting love on time:
> 21 Sateesh Chodapuneedi
> 20 Devdeep Singh
> 16 Sanjay Tripathi
> 14 James Martin
> 12 Gavin Lee
Actually, Gavin is already a committer.
Anyway - if you feel someone is deserving of committer status, and
you're not on the PPMC, I'd encourage you to speak up (privately) to
someone on the PPMC if you feel they're being overlooked. But discussing
specific individuals on -dev is unfair to those people and puts the PPMC
in a bad position.
Best,
jzb
--
Joe Brockmeier
jzb@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Noah Slater <ns...@apache.org>.
Comittership is a bestowal of trust on an individual on behalf of the
project. It is awarded to people who have shown sustained positive
contributions to the project, code or no code. Don't get too hung up on the
code aspect.
On 22 February 2013 22:30, Jessica Tomechak <je...@gmail.com>wrote:
> On Fri, Feb 22, 2013 at 2:45 AM, Joe Brockmeier <jz...@zonker.net> wrote:
>
> > On Fri, Feb 22, 2013, at 01:01 AM, Rohit Yadav wrote:
> >
> > > While this is the first time a proposal was made public, I had to
> > > rant, the toughest email I had to write, but anyway you should ignore
> > > it:
> >
> > I'd also point out, this isn't something that we dreamed up specifically
> > for CloudStack - we're following Apache practices here. It's worth
> > researching whether something is CloudStack-specific or an Apache
> > process before holding other folks feet to the fire about the way
> > they're doing things.
> >
> > These are the Apache guidelines for voting on committers:
> > http://community.apache.org/newcommitter.html
> >
> > AFAIK, individual projects (and certainly not incubating projects) are
> > not free to disregard these practices.
> >
> > Best,
> >
> > jzb
> > --
> > Joe Brockmeier
> > jzb@zonker.net
> > Twitter: @jzb
> > http://www.dissociatedpress.net/
> >
>
>
> Totally agreed about all Animesh's awesome contributions. But I have a
> "this is my first open-source project" question.
>
> I searched Reviewboard and don't see any patches from Animesh. Why would
> someone who doesn't write code need to be a committer?
>
> I read the Apache "committers" docs [1][2] and they mention a few
> "back-office" things committers can do, but they pretty much assume that
> writing code is the main reason to be a committer.
>
> Again: totally agreed about Animesh's awesome contributions. Maybe Animesh
> has written tons of code for the project which I've overlooked, in which
> case I apologize. I'm still curious about what else committers can do.
>
> [1] http://community.apache.org/committers/index.html
> [2] http://www.apache.org/dev/new-committers-guide.html
>
> Jessica T.
>
--
NS
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Noah Slater <ns...@apache.org>.
The functions and responsibilities of a committer are up to each project.
Typically, they are expected to have more scope for managing JIRA, the
wiki, moderating mailing lists, social media, etc.
On 27 February 2013 01:18, Jessica Tomechak <je...@gmail.com>wrote:
> On Sat, Feb 23, 2013 at 10:25 AM, Sebastien Goasguen <runseb@gmail.com
> >wrote:
>
> >
> > On Feb 22, 2013, at 11:30 PM, Jessica Tomechak <
> jessica.tomechak@gmail.com>
> > wrote:
> >
> > > On Fri, Feb 22, 2013 at 2:45 AM, Joe Brockmeier <jz...@zonker.net>
> wrote:
> > >
> > >> On Fri, Feb 22, 2013, at 01:01 AM, Rohit Yadav wrote:
> > >>
> > >>> While this is the first time a proposal was made public, I had to
> > >>> rant, the toughest email I had to write, but anyway you should ignore
> > >>> it:
> > >>
> > >> I'd also point out, this isn't something that we dreamed up
> specifically
> > >> for CloudStack - we're following Apache practices here. It's worth
> > >> researching whether something is CloudStack-specific or an Apache
> > >> process before holding other folks feet to the fire about the way
> > >> they're doing things.
> > >>
> > >> These are the Apache guidelines for voting on committers:
> > >> http://community.apache.org/newcommitter.html
> > >>
> > >> AFAIK, individual projects (and certainly not incubating projects) are
> > >> not free to disregard these practices.
> > >>
> > >> Best,
> > >>
> > >> jzb
> > >> --
> > >> Joe Brockmeier
> > >> jzb@zonker.net
> > >> Twitter: @jzb
> > >> http://www.dissociatedpress.net/
> > >>
> > >
> > >
> > > Totally agreed about all Animesh's awesome contributions. But I have a
> > > "this is my first open-source project" question.
> > >
> > > I searched Reviewboard and don't see any patches from Animesh. Why
> would
> > > someone who doesn't write code need to be a committer?
> > >
> > > I read the Apache "committers" docs [1][2] and they mention a few
> > > "back-office" things committers can do, but they pretty much assume
> that
> > > writing code is the main reason to be a committer.
> > >
> > > Again: totally agreed about Animesh's awesome contributions. Maybe
> > Animesh
> > > has written tons of code for the project which I've overlooked, in
> which
> > > case I apologize. I'm still curious about what else committers can do.
> >
> > We have voted and posted bylaws for the community:
> >
> >
> https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
> >
> > They define a contributor as:
> >
> > "Contributors are all of the volunteers who are contributing time, code,
> > documentation, or resources to the CloudStack Project. Contributions are
> > not
> > just code, but can be any combination of documentation, testing, user
> > support,
> > code, code reviews, bug reporting, community organizing, project
> > marketing, or
> > numerous other activities that help promote and improve the Apache
> > CloudStack
> > project and community."
> >
> > And explain that:
> >
> > "A Contributor that makes sustained, welcome contributions to the project
> > may be
> > invited to become a Committer by the PMC. The invitation will be at the
> > discretion of a supporting PMC member."
> >
> > To summarize, it's not just code.
> >
> > -Sebastien
> >
> >
> > >
> > > [1] http://community.apache.org/committers/index.html
> > > [2] http://www.apache.org/dev/new-committers-guide.html
> > >
> > > Jessica T.
> >
> >
> OK, thanks for the replies. This clarifies that Committer may be more of a
> vote-of-confidence than anything related to committing code.
>
> Still wondering: aside from gaining direct commit permissions on the code
> repo, what other permissions does an Apache Committer have, if any? This
> was more the point of my question, "curious about what else committers can
> do."
>
> For example, maybe only Committers can edit certain blogs, or do certain
> types of configuration on other infrastructure. As I mentioned, the Apache
> docs refer to some "back-office" tasks that committers can do that
> non-committers can't, but they do not go into much detail about this.
> That's the point on which I'm still curious. Maybe, for example, it takes a
> Committer to update those Apache docs about being a Committer?
>
> If this is a question for a different Apache list, please let me know.
>
> Jessica T.
>
--
NS
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Jessica Tomechak <je...@gmail.com>.
On Sat, Feb 23, 2013 at 10:25 AM, Sebastien Goasguen <ru...@gmail.com>wrote:
>
> On Feb 22, 2013, at 11:30 PM, Jessica Tomechak <je...@gmail.com>
> wrote:
>
> > On Fri, Feb 22, 2013 at 2:45 AM, Joe Brockmeier <jz...@zonker.net> wrote:
> >
> >> On Fri, Feb 22, 2013, at 01:01 AM, Rohit Yadav wrote:
> >>
> >>> While this is the first time a proposal was made public, I had to
> >>> rant, the toughest email I had to write, but anyway you should ignore
> >>> it:
> >>
> >> I'd also point out, this isn't something that we dreamed up specifically
> >> for CloudStack - we're following Apache practices here. It's worth
> >> researching whether something is CloudStack-specific or an Apache
> >> process before holding other folks feet to the fire about the way
> >> they're doing things.
> >>
> >> These are the Apache guidelines for voting on committers:
> >> http://community.apache.org/newcommitter.html
> >>
> >> AFAIK, individual projects (and certainly not incubating projects) are
> >> not free to disregard these practices.
> >>
> >> Best,
> >>
> >> jzb
> >> --
> >> Joe Brockmeier
> >> jzb@zonker.net
> >> Twitter: @jzb
> >> http://www.dissociatedpress.net/
> >>
> >
> >
> > Totally agreed about all Animesh's awesome contributions. But I have a
> > "this is my first open-source project" question.
> >
> > I searched Reviewboard and don't see any patches from Animesh. Why would
> > someone who doesn't write code need to be a committer?
> >
> > I read the Apache "committers" docs [1][2] and they mention a few
> > "back-office" things committers can do, but they pretty much assume that
> > writing code is the main reason to be a committer.
> >
> > Again: totally agreed about Animesh's awesome contributions. Maybe
> Animesh
> > has written tons of code for the project which I've overlooked, in which
> > case I apologize. I'm still curious about what else committers can do.
>
> We have voted and posted bylaws for the community:
>
> https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
>
> They define a contributor as:
>
> "Contributors are all of the volunteers who are contributing time, code,
> documentation, or resources to the CloudStack Project. Contributions are
> not
> just code, but can be any combination of documentation, testing, user
> support,
> code, code reviews, bug reporting, community organizing, project
> marketing, or
> numerous other activities that help promote and improve the Apache
> CloudStack
> project and community."
>
> And explain that:
>
> "A Contributor that makes sustained, welcome contributions to the project
> may be
> invited to become a Committer by the PMC. The invitation will be at the
> discretion of a supporting PMC member."
>
> To summarize, it's not just code.
>
> -Sebastien
>
>
> >
> > [1] http://community.apache.org/committers/index.html
> > [2] http://www.apache.org/dev/new-committers-guide.html
> >
> > Jessica T.
>
>
OK, thanks for the replies. This clarifies that Committer may be more of a
vote-of-confidence than anything related to committing code.
Still wondering: aside from gaining direct commit permissions on the code
repo, what other permissions does an Apache Committer have, if any? This
was more the point of my question, "curious about what else committers can
do."
For example, maybe only Committers can edit certain blogs, or do certain
types of configuration on other infrastructure. As I mentioned, the Apache
docs refer to some "back-office" tasks that committers can do that
non-committers can't, but they do not go into much detail about this.
That's the point on which I'm still curious. Maybe, for example, it takes a
Committer to update those Apache docs about being a Committer?
If this is a question for a different Apache list, please let me know.
Jessica T.
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Sebastien Goasguen <ru...@gmail.com>.
On Feb 22, 2013, at 11:30 PM, Jessica Tomechak <je...@gmail.com> wrote:
> On Fri, Feb 22, 2013 at 2:45 AM, Joe Brockmeier <jz...@zonker.net> wrote:
>
>> On Fri, Feb 22, 2013, at 01:01 AM, Rohit Yadav wrote:
>>
>>> While this is the first time a proposal was made public, I had to
>>> rant, the toughest email I had to write, but anyway you should ignore
>>> it:
>>
>> I'd also point out, this isn't something that we dreamed up specifically
>> for CloudStack - we're following Apache practices here. It's worth
>> researching whether something is CloudStack-specific or an Apache
>> process before holding other folks feet to the fire about the way
>> they're doing things.
>>
>> These are the Apache guidelines for voting on committers:
>> http://community.apache.org/newcommitter.html
>>
>> AFAIK, individual projects (and certainly not incubating projects) are
>> not free to disregard these practices.
>>
>> Best,
>>
>> jzb
>> --
>> Joe Brockmeier
>> jzb@zonker.net
>> Twitter: @jzb
>> http://www.dissociatedpress.net/
>>
>
>
> Totally agreed about all Animesh's awesome contributions. But I have a
> "this is my first open-source project" question.
>
> I searched Reviewboard and don't see any patches from Animesh. Why would
> someone who doesn't write code need to be a committer?
>
> I read the Apache "committers" docs [1][2] and they mention a few
> "back-office" things committers can do, but they pretty much assume that
> writing code is the main reason to be a committer.
>
> Again: totally agreed about Animesh's awesome contributions. Maybe Animesh
> has written tons of code for the project which I've overlooked, in which
> case I apologize. I'm still curious about what else committers can do.
We have voted and posted bylaws for the community:
https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html
They define a contributor as:
"Contributors are all of the volunteers who are contributing time, code,
documentation, or resources to the CloudStack Project. Contributions are not
just code, but can be any combination of documentation, testing, user support,
code, code reviews, bug reporting, community organizing, project marketing, or
numerous other activities that help promote and improve the Apache CloudStack
project and community."
And explain that:
"A Contributor that makes sustained, welcome contributions to the project may be
invited to become a Committer by the PMC. The invitation will be at the
discretion of a supporting PMC member."
To summarize, it's not just code.
-Sebastien
>
> [1] http://community.apache.org/committers/index.html
> [2] http://www.apache.org/dev/new-committers-guide.html
>
> Jessica T.
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Jessica Tomechak <je...@gmail.com>.
On Fri, Feb 22, 2013 at 2:45 AM, Joe Brockmeier <jz...@zonker.net> wrote:
> On Fri, Feb 22, 2013, at 01:01 AM, Rohit Yadav wrote:
>
> > While this is the first time a proposal was made public, I had to
> > rant, the toughest email I had to write, but anyway you should ignore
> > it:
>
> I'd also point out, this isn't something that we dreamed up specifically
> for CloudStack - we're following Apache practices here. It's worth
> researching whether something is CloudStack-specific or an Apache
> process before holding other folks feet to the fire about the way
> they're doing things.
>
> These are the Apache guidelines for voting on committers:
> http://community.apache.org/newcommitter.html
>
> AFAIK, individual projects (and certainly not incubating projects) are
> not free to disregard these practices.
>
> Best,
>
> jzb
> --
> Joe Brockmeier
> jzb@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>
Totally agreed about all Animesh's awesome contributions. But I have a
"this is my first open-source project" question.
I searched Reviewboard and don't see any patches from Animesh. Why would
someone who doesn't write code need to be a committer?
I read the Apache "committers" docs [1][2] and they mention a few
"back-office" things committers can do, but they pretty much assume that
writing code is the main reason to be a committer.
Again: totally agreed about Animesh's awesome contributions. Maybe Animesh
has written tons of code for the project which I've overlooked, in which
case I apologize. I'm still curious about what else committers can do.
[1] http://community.apache.org/committers/index.html
[2] http://www.apache.org/dev/new-committers-guide.html
Jessica T.
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Joe Brockmeier <jz...@zonker.net>.
On Fri, Feb 22, 2013, at 01:01 AM, Rohit Yadav wrote:
> While this is the first time a proposal was made public, I had to
> rant, the toughest email I had to write, but anyway you should ignore
> it:
I'd also point out, this isn't something that we dreamed up specifically
for CloudStack - we're following Apache practices here. It's worth
researching whether something is CloudStack-specific or an Apache
process before holding other folks feet to the fire about the way
they're doing things.
These are the Apache guidelines for voting on committers:
http://community.apache.org/newcommitter.html
AFAIK, individual projects (and certainly not incubating projects) are
not free to disregard these practices.
Best,
jzb
--
Joe Brockmeier
jzb@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Chiradeep Vittal <Ch...@citrix.com>.
On 2/21/13 11:01 PM, "Rohit Yadav" <bh...@apache.org> wrote:
>On Fri, Feb 22, 2013 at 6:29 AM, Alex Huang <Al...@citrix.com> wrote:
>> This was not meant for cloudstack-dev....I'm sure I will get a ton of
>>+1 replies but please refrain from replying to this.
>
>While this is the first time a proposal was made public, I had to
>rant, the toughest email I had to write, but anyway you should ignore
>it:
>
>Should we have transparency on committer proposals and votes? It's
>because I feel we're not proposing people based on pure merits. For
>example, my git rank (git shortlog -sn) and ML participating tells me
>the following folks were participating since many months, they have
>good commits and their patches only fall behind due to their review
>not getting love on time:
> 21 Sateesh Chodapuneedi
> 20 Devdeep Singh
> 16 Sanjay Tripathi
> 14 James Martin
> 12 Gavin Lee
>
>While not denying or taking away anything but I'm actually
>acknowledging and appreciating the good work Animesh did.
>Since I signed the ICLA and think I understand the apache culture [1][2]:
>
>Wearing my daily job hat:
>+1 also because follow everyone on this thread brainlessly!
>
>Wearing my opensource hippie aka apache hat:
>-1 because I think there are other folks here for months who are not
>receiving love. Animesh's work is more like ppmc folks, he could
>mature into one later, but what about people who have made good
>commits, their contributors should be made easier by providing them
>commit access, they are already committed to the community.
>
>Regards.
>
>[1] https://www.youtube.com/watch?v=fiDchgAmIBw
>[2] http://www.apache.org/foundation/how-it-works.html
>
>Your truly,
>Just another apache committer.
You can rant, but I hope you didn't imply that the others on this thread
were "brainlessly following".
Other than that, +1 to all the folks mentioned :)
--
Chiradeep
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Rohit Yadav <bh...@apache.org>.
On Fri, Feb 22, 2013 at 6:29 AM, Alex Huang <Al...@citrix.com> wrote:
> This was not meant for cloudstack-dev....I'm sure I will get a ton of +1 replies but please refrain from replying to this.
While this is the first time a proposal was made public, I had to
rant, the toughest email I had to write, but anyway you should ignore
it:
Should we have transparency on committer proposals and votes? It's
because I feel we're not proposing people based on pure merits. For
example, my git rank (git shortlog -sn) and ML participating tells me
the following folks were participating since many months, they have
good commits and their patches only fall behind due to their review
not getting love on time:
21 Sateesh Chodapuneedi
20 Devdeep Singh
16 Sanjay Tripathi
14 James Martin
12 Gavin Lee
While not denying or taking away anything but I'm actually
acknowledging and appreciating the good work Animesh did.
Since I signed the ICLA and think I understand the apache culture [1][2]:
Wearing my daily job hat:
+1 also because follow everyone on this thread brainlessly!
Wearing my opensource hippie aka apache hat:
-1 because I think there are other folks here for months who are not
receiving love. Animesh's work is more like ppmc folks, he could
mature into one later, but what about people who have made good
commits, their contributors should be made easier by providing them
commit access, they are already committed to the community.
Regards.
[1] https://www.youtube.com/watch?v=fiDchgAmIBw
[2] http://www.apache.org/foundation/how-it-works.html
Your truly,
Just another apache committer.
>
> --Alex
>
>> -----Original Message-----
>> From: Alex Huang [mailto:Alex.Huang@citrix.com]
>> Sent: Thursday, February 21, 2013 4:52 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: [DISCUSS] Animesh Chaturvedi as a committer
>>
>> Hi,
>>
>> I like to discuss nominating Animesh as a committer. Animesh joined back in
>> December time frame and quickly became an advocate for CloudStack. He
>> has quickly come up to speed on CloudStack and on how it should work in
>> Apache. He's handled the difficult IP clearance issues and helped minimize
>> its problems. He's arranged for meetups for CloudStack. He's working with
>> everyone to come up with better processes. He's basically everywhere on
>> mailing list. I think he will make for a great committer.
>>
>> --Alex
>>
>
RE: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Alex Huang <Al...@citrix.com>.
This was not meant for cloudstack-dev....I'm sure I will get a ton of +1 replies but please refrain from replying to this.
--Alex
> -----Original Message-----
> From: Alex Huang [mailto:Alex.Huang@citrix.com]
> Sent: Thursday, February 21, 2013 4:52 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: [DISCUSS] Animesh Chaturvedi as a committer
>
> Hi,
>
> I like to discuss nominating Animesh as a committer. Animesh joined back in
> December time frame and quickly became an advocate for CloudStack. He
> has quickly come up to speed on CloudStack and on how it should work in
> Apache. He's handled the difficult IP clearance issues and helped minimize
> its problems. He's arranged for meetups for CloudStack. He's working with
> everyone to come up with better processes. He's basically everywhere on
> mailing list. I think he will make for a great committer.
>
> --Alex
>
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by Chip Childers <ch...@sungard.com>.
On Feb 21, 2013, at 7:52 PM, Alex Huang <Al...@citrix.com> wrote:
> Hi,
>
> I like to discuss nominating Animesh as a committer. Animesh joined back in December time frame and quickly became an advocate for CloudStack. He has quickly come up to speed on CloudStack and on how it should work in Apache. He's handled the difficult IP clearance issues and helped minimize its problems. He's arranged for meetups for CloudStack. He's working with everyone to come up with better processes. He's basically everywhere on mailing list. I think he will make for a great committer.
>
> --Alex
I think you said it well. I'd be a +1.
Re: [DISCUSS] Animesh Chaturvedi as a committer
Posted by John Kinsella <jl...@stratosec.co>.
+1
On Feb 21, 2013, at 4:52 PM, Alex Huang <Al...@citrix.com> wrote:
> Hi,
>
> I like to discuss nominating Animesh as a committer. Animesh joined back in December time frame and quickly became an advocate for CloudStack. He has quickly come up to speed on CloudStack and on how it should work in Apache. He's handled the difficult IP clearance issues and helped minimize its problems. He's arranged for meetups for CloudStack. He's working with everyone to come up with better processes. He's basically everywhere on mailing list. I think he will make for a great committer.
>
> --Alex
>
>
>
Stratosec - Secure Infrastructure as a Service
o: 415.315.9385
@johnlkinsella