<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Not sure what the etiquette is for removing someone. Michael Gundlach is still listed but is no longer participating. </div>
<div><br>
</div>
<div>pvo</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Joshua McKenty <<a href="mailto:josh@piston.cc">josh@piston.cc</a>><br>
<span style="font-weight:bold">Date: </span>Wed, 16 Feb 2011 16:51:56 -0800<br>
<span style="font-weight:bold">To: </span>Paul Voccio <<a href="mailto:paul.voccio@rackspace.com">paul.voccio@rackspace.com</a>><br>
<span style="font-weight:bold">Cc: </span>Soren Hansen <<a href="mailto:soren@ubuntu.com">soren@ubuntu.com</a>>, Jay Pipes <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>>, "<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>"
<<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack] Review days for nova-core members<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
Yup - we approved a new process for adding team members to core a few weeks ago, I haven't seen any applications yet but I may have missed one.
<div><br>
</div>
<div>Joshua<br>
<br>
<div class="gmail_quote">On Wed, Feb 16, 2011 at 4:28 PM, Paul Voccio <span dir="ltr">
<<a href="mailto:paul.voccio@rackspace.com">paul.voccio@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Have we considered pruning and expanding the core team to help speed the<br>
reviews along? There are some people who are no longer day-to-day active<br>
in Nova and some that are that could help in this process.<br>
<div>
<div></div>
<div class="h5"><br>
On 2/16/11 3:54 PM, "Soren Hansen" <<a href="mailto:soren@ubuntu.com">soren@ubuntu.com</a>> wrote:<br>
<br>
>2011/2/16 Jay Pipes <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>>:<br>
>> Lots of coding and bug fixing has been done in the past weeks. As a<br>
>> result, we've got a big backlog of code reviews to do.<br>
>><br>
>> If you have some cycles, please do participate:<br>
>><br>
>> <a href="https://code.launchpad.net/nova/+activereviews" target="_blank">https://code.launchpad.net/nova/+activereviews</a><br>
>><br>
>> Nova-core members, remember, it's you responsibility to do code<br>
>>reviews! :)<br>
><br>
>Yes!<br>
><br>
>I've considered if nova-core people should take turns in having a review<br>
>day.<br>
>Their top priority for the day should be doing branch reviews and bug<br>
>triaging. Anything else that day would be second to this. Every member<br>
>of<br>
>the team should be part of the rotation. The only member of nova-core<br>
>exempt from this responsibility would be Jenkins. :) f you cannot accept<br>
>this<br>
>responsibility, you don't get to be a member of the team. Of course<br>
>there has to be room for holiday and being ill, but every day, people<br>
>should know who they can bug for reviews and members of the team should<br>
>generally be available for this rotation.<br>
><br>
>The goal is to ensure that we don't drop good work on the floor due to<br>
>bitrot and to distribute the review load better than we do now.<br>
><br>
><br>
>--<br>
>Soren Hansen<br>
>Ubuntu Developer <a href="http://www.ubuntu.com/" target="_blank">http://www.ubuntu.com/</a><br>
>OpenStack Developer <a href="http://www.openstack.org/" target="_blank">http://www.openstack.org/</a><br>
><br>
>_______________________________________________<br>
>Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
>Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
>More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
<br>
<br>
</div>
</div>
Confidentiality Notice: This e-mail message (including any attached or<br>
embedded documents) is intended for the exclusive and confidential use of the<br>
individual or entity to which this message is addressed, and unless otherwise<br>
expressly indicated, is confidential and privileged information of Rackspace.<br>
Any dissemination, distribution or copying of the enclosed material is prohibited.<br>
If you receive this transmission in error, please notify us immediately by e-mail<br>
at <a href="mailto:abuse@rackspace.com">abuse@rackspace.com</a>, and delete the original message.<br>
Your cooperation is appreciated.<br>
<div>
<div></div>
<div class="h5"><br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</span>
<PRE>
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@rackspace.com, and delete the original message.
Your cooperation is appreciated.
</PRE></body>
</html>