Open Stack

Sylvain,

Are you sure your tone is appropriate once you read again your email ?


I don't see anything wrong in tone & email at all.
I just summarize for Rally team results of that thread. So they won't need
to read it.
And explain why we won't have sub cores and need trust model.
That's all.



> How can we help you understand that opinions help us to think about us and
> how we can be better ?


Some members from community can avoid doing things from list that I wrote.


>
> Do you think you have to apologize for such this email ?


Not yet. Do I have any reason for that?


Best regards,
Boris Pavlovic

On Fri, Jun 5, 2015 at 8:43 PM, Sylvain Bauza <sbauza at redhat.com> wrote:

>
>
> Le 05/06/2015 19:03, Boris Pavlovic a écrit :
>
> Hi stackers,
>
>  Seems likes after stackforge/rally -> openstack/rally Rally project
> started being more attractive.
> According recent stats we are on top 3 position (based on Patch sets
> stats)
>  http://stackalytics.com/?release=liberty&metric=patches&project_type=All
> And if we compare half year ago we have 40 open reviews and now we have
> about 140...
> In other words we need to scale core reviewing process with keeping
> quality.
>
>  <history_note>
>
>  I suggested in mailing thread:
> [openstack-dev][all][infra][tc][ptl] Scaling up code review process
> (subdir cores)
> To create special rules & ACL groups to have fully automated system.
>
>  Instead of support I got raped by community.
> Community was very polite & technical oriented in that thread and they
> said:
> 1) I am bad PTL,
> 2) I don't know how to do open source
> 3) Rally project sux
> 4) Rally project community sux
> 5) Rally project has troubles
> 6) A lot of more constructive critics
>
>  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.....
>
>  </history_note>
>
>
>  Solution:
> We will have single core team that can merge anything.
> But there will be two types of core (based on trust ;()
>
>  I created page in docs, that explains who is who:
> https://review.openstack.org/#/c/188843/1
>
>  Core reviewer
> ------------------
> That are core for whole project
>
>  Plugin Core reviewer
> ----------------------------
> That will just review/merge their component plugins and nothing else
>
>
>  I hope by end of this cycle each component will have own subteam which
> will resolve
> most of reviewing process scale issues..
>
>
>  Best regards,
> Boris Pavlovic
>
>
> Are you sure your tone is appropriate once you read again your email ?
>
> How can we help you understand that opinions help us to think about us and
> how we can be better ?
>
> Do you think you have to apologize for such this email ?
>
> -Sylvain
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150605/3377d869/attachment.html>