Re: [openstack-dev] [rally][scaling up development] Rally core team re-organization
Excerpts from Boris Pavlovic's message of 2015-06-05 20:03:44 +0300: 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=libertymetric=patchesproject_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. I understand that you feel that the negative response to your proposal was strong, but this is *COMPLETELY* inappropriate wording for this mailing list. Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rally][scaling up development] Rally core team re-organization
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 sba...@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=libertymetric=patchesproject_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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rally][scaling up development] Rally core team re-organization
Doug, I understand that you feel that the negative response to your proposal was strong, but this is *COMPLETELY* inappropriate wording for this mailing list. Okay, next time I will copy paste parts of emails from others (with the even more offensive tone in my side) Instead of making such list. Best regards, Boris Pavlovic On Fri, Jun 5, 2015 at 8:31 PM, Doug Hellmann d...@doughellmann.com wrote: Excerpts from Boris Pavlovic's message of 2015-06-05 20:03:44 +0300: 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=libertymetric=patchesproject_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. I understand that you feel that the negative response to your proposal was strong, but this is *COMPLETELY* inappropriate wording for this mailing list. Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rally][scaling up development] Rally core team re-organization
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=libertymetric=patchesproject_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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [rally][scaling up development] Rally core team re-organization
Excerpts from Boris Pavlovic's message of 2015-06-05 21:16:04 +0300: All, Sorry for picking very bad words. I am not native speaker. =( In Russia this word has as well another meaning like being to aggressive against somebody. I used it in that meaning. I didn't thought about sexually violated at all. Sorry sorry and one more time sorry! About using improper words.. Thank you, Boris. It's important for all of us to remember that with cultural and language differences we need to take care with phrasing to ensure we are communicating in a clear and friendly way. I appreciate your explanation and apology. Doug Best regards, Boris Pavlovic On Fri, Jun 5, 2015 at 9:05 PM, Nikola Đipanov ndipa...@redhat.com wrote: On 06/05/2015 06:31 PM, Doug Hellmann wrote: Excerpts from Boris Pavlovic's message of 2015-06-05 20:03:44 +0300: 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=libertymetric=patchesproject_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. I understand that you feel that the negative response to your proposal was strong, but this is *COMPLETELY* inappropriate wording for this mailing list. +1000 - words have meaning and getting ones ideas criticized on a mailing list by peers is not even in the same universe as being sexually violated!!! IMHO this kind of behaviour needs to be sanctioned now, this kind of language must not take root on this list ever! I have no idea what the process for this is but I am sure people who know will respond soon. Not cool Boris! Not even a little bit. N. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
