<div dir="ltr"><div><span style="font-size:12.8000001907349px">Sylvain, </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:12.8000001907349px">Are you sure your tone is appropriate once you read again your email ?</span></blockquote><div> </div><div>I don't see anything wrong in tone & email at all. </div><div>I just summarize for Rally team results of that thread. So they won't need to read it.</div><div>And explain why we won't have sub cores and need trust model. </div><div>That's all. </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:12.8000001907349px">How can we help you understand that opinions help us to think about us and how we can be better ?</span></blockquote><div><br></div><div>Some members from community can avoid doing things from list that I wrote. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">Do you think you have to apologize for such this email ?</span></blockquote><div><br></div><div>Not yet. Do I have any reason for that? </div><div><br></div><div><br></div><div>Best regards,</div><div>Boris Pavlovic </div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 5, 2015 at 8:43 PM, Sylvain Bauza <span dir="ltr"><<a href="mailto:sbauza@redhat.com" target="_blank">sbauza@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div><div class="h5">
<br>
<br>
<div>Le 05/06/2015 19:03, Boris Pavlovic a
écrit :<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi stackers,
<div><br>
</div>
<div>Seems likes after stackforge/rally -> openstack/rally
Rally project started being more attractive.</div>
<div>According recent stats we are on top 3 position (based on
Patch sets stats) <br>
</div>
<div><a href="http://stackalytics.com/?release=liberty&metric=patches&project_type=All" target="_blank">http://stackalytics.com/?release=liberty&metric=patches&project_type=All</a> </div>
<div>And if we compare half year ago we have 40 open reviews and
now we have about 140... </div>
<div>In other words we need to scale core reviewing process with
keeping quality. </div>
<div><br>
</div>
<div><history_note></div>
<div><br>
</div>
<div>I suggested in mailing thread: </div>
[openstack-dev][all][infra][tc][ptl] Scaling up code review
process (subdir cores)
<div>To create special rules & ACL groups to have fully
automated system. <br>
</div>
<div><br>
</div>
<div>Instead of support I got raped by community. </div>
<div>Community was very polite & technical oriented in that
thread and they said: </div>
<div>1) I am bad PTL, </div>
<div>2) I don't know how to do open source </div>
<div>3) Rally project sux </div>
<div>4) Rally project community sux</div>
<div>5) Rally project has troubles </div>
<div>6) A lot of more constructive critics </div>
<div><br>
</div>
<div>So Instead of having NICE fully automated system for
subcores we will use ugly, not automated but very popular in
community "trust" model based on excel.....</div>
<div><br>
</div>
<div></history_note><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Solution: </div>
<div>We will have single core team that can merge anything.</div>
<div>But there will be two types of core (based on trust ;()</div>
<div><br>
</div>
<div>I created page in docs, that explains who is who: </div>
<div><a href="https://review.openstack.org/#/c/188843/1" target="_blank">https://review.openstack.org/#/c/188843/1</a></div>
<div><br>
</div>
<div>Core reviewer</div>
<div>------------------ </div>
<div>That are core for whole project </div>
<div><br>
</div>
<div>Plugin Core reviewer</div>
<div>----------------------------</div>
<div>That will just review/merge their component plugins and
nothing else</div>
<div><br>
</div>
<div> <br>
</div>
<div>I hope by end of this cycle each component will have own
subteam which will resolve </div>
<div>most of reviewing process scale issues.. </div>
<div><br>
</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Boris Pavlovic</div>
</div>
</blockquote>
<br></div></div>
Are you sure your tone is appropriate once you read again your email
?<br>
<br>
How can we help you understand that opinions help us to think about
us and how we can be better ?<br>
<br>
Do you think you have to apologize for such this email ?<span class="HOEnZb"><font color="#888888"><br>
<br>
-Sylvain</font></span><span class=""><br>
<br>
<blockquote type="cite">
<br>
<fieldset></fieldset>
<br>
<pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</span></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>