<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p><b><span style='font-size:9.0pt;font-family:"Trebuchet MS","sans-serif";color:#AAAAAA'>Dell - Internal Use - Confidential </span></b><o:p></o:p></p><p class=MsoNormal>The link from cinder page to Cinder review inbox (<a href="https://review.openstack.org/#/dashboard/">https://review.openstack.org/#/dashboard/</a>) from <a href="https://wiki.openstack.org/wiki/Cinder#Resources">https://wiki.openstack.org/wiki/Cinder#Resources</a> is empty.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Link to bugs does work.<o:p></o:p></p><p>-----Original Message-----<br>From: Mike Perez [mailto:thingee@gmail.com]<br>Sent: Tuesday, March 24, 2015 3:49 PM<br>To: OpenStack Development Mailing List (not for usage questions)<br>Subject: Re: [openstack-dev] Cinder Review Inbox Was RE: Cinder Third-Party CI: what next? (was Re: [cinder] Request exemption for removal of NetApp FC drivers (no voting CI))<br><br>On 19:38 Tue 24 Mar , Asselin, Ramy wrote:<br>> Changing the topic.<br>> <br>> Mike Perez did include a Cinder Review Inbox link on the main Cinder <br>> Wiki page.<br>> https://wiki.openstack.org/wiki/Cinder#Resources<br>> <br>> Not sure how many people/cores use that link but that could be a step <br>> towards what you’re asking for.<br>> The query should probably be proposed to <br>> http://git.openstack.org/cgit/stackforge/gerrit-dash-creator/tree/dash<br>> boards<br>> <br>> Ramy<br>> <br>> <br>>> From: Rochelle Grober [mailto:rochelle.grober@huawei.com]<br>>> Sent: Tuesday, March 24, 2015 12:02 PM<br>>> To: OpenStack Development Mailing List (not for usage questions)<br>>> Subject: Re: [openstack-dev] Cinder Third-Party CI: what next? (was<br>>> Re: [cinder] Request exemption for removal of NetApp FC drivers (no <br>>> voting CI))<br>>> <br>>> One other item I’d like to bring up.<br>>> <br>>> While Nova and Neutron are well distributed around the globe and have Core Reviewers on IRC in the Asia daytime, some other projects are not so well distributed as yet. A problem I noticed a number of times is that an Asia based developer will post to the mailing list to get some attention for his/her patch. This is frowned upon in the community, but when there are few to no Core Reviewers in IRC, getting that first core review can be difficult. Emailing the PTL is something I’m sure the PTLs would like to limit as they are already swamped. So, how do we get timely first core review of patches in areas of the world where Core presence in IRC is slim to none?<br>>> <br>>> I can think of a few options but they don’t seem great:<br>>> <br>>> · A filter for dashboards that flags reviews with multiple +1s and no core along with a commitment of the Core team to perform a review within x number of days<br>>> <br>>> · A separate mailing list for project review requests<br>>> <br>>> · Somehow queueing requests in the IRC channel so that offline developers can easily find review requests when looking at channel logs<br>>> <br>>> · ???<br>>> <br>>> Solving this issue could help not just Third Party developers, but all of OpenStack and make the community more inviting to Asian and Australian (and maybe European and African) developers.<br>>> <br>>> --Rocky<br><br>Yes thanks Ramy. That's exactly what this dashboard helps with and has existed since January. I brought it up at the Cinder midcycle meetup, multiple times in meetings, reviewathons, etc. I was letting it sit and have people try it out before proposing to see if anyone had feedback. Since it has been sitting for a while without feedback, I'll go ahead and propose it.<br><br>--<br>Mike Perez<br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<o:p></o:p></p></div></body></html>