openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #00737
Re: Review days for nova-core members
"Also, good point to keep in mind: Membership to nova-core isn't a
privilege or even any fun. It's a responsibility and a duty to your
fellow contributors :)"
well said!
On Thu, Feb 17, 2011 at 9:59 AM, Jay Pipes <jaypipes@xxxxxxxxx> wrote:
> On Thu, Feb 17, 2011 at 9:26 AM, Thierry Carrez <thierry@xxxxxxxxxxxxx>
> wrote:
> > That said that shouldn't prevent anyone from also reviewing stuff that
> > they care about any day.
>
> This is EXTREMELY important. Remember that anyone can (and is
> encourage to) review anyone else's branches. IMHO, the best way to
> "get into nova-core" is to regularly review code for other people and
> participate in the various debates on merge proposals.
>
> There are a number of folks that already do this, and are not in
> nova-core. Sandy Walsh and Ed Leafe both come to mind. And there are a
> few folks that don't do reviews on Nova stuff much at all anymore.
> Monty Taylor (blessed he be in all things build-related) and Chris
> Macgown (blessed he be in all things earthquake related) are two that
> likely can be replaced in my opinion.
>
> Also, good point to keep in mind: Membership to nova-core isn't a
> privilege or even any fun. It's a responsibility and a duty to your
> fellow contributors :)
>
> -jay
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@xxxxxxxxxxxxx, and delete the original message.
Your cooperation is appreciated.
References