<div dir="ltr">Update here: patch was marked as WIP for now due to comment from Anita Kuno:<div><p style="margin-top:0px;margin-bottom:0px;padding-top:0.5em;padding-bottom:0.5em;color:rgb(0,0,0);font-family:sans-serif;font-size:small;line-height:normal">> On Oct. 17 all active stackforge projects that have themselves listed on the stackforge retirement wikipage will be moved. This includes reviewing all acl files for that move.</p><p style="margin-top:0px;margin-bottom:0px;padding-top:0.5em;padding-bottom:0.5em;color:rgb(0,0,0);font-family:sans-serif;font-size:small;line-height:normal">> Can we mark this patch wip until after the Oct. 17 stackforge rename and then change the paths on these files to the openstack namespace?</p></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Oct 1, 2015 at 4:03 PM Dmitry Borodaenko <<a href="mailto:dborodaenko@mirantis.com">dborodaenko@mirantis.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This commit brings Fuel ACLs in sync with each other and in line with<br>
the agreement on this thread:<br>
<a href="https://review.openstack.org/230195" rel="noreferrer" target="_blank">https://review.openstack.org/230195</a><br>
<br>
Please review carefully. Note that I intentionally didn't touch any of<br>
the plugins ACLs, primarily to save time for us and the<br>
openstack-infra team until after the stackforge->openstack namespace<br>
migration.<br>
<br>
On Mon, Sep 21, 2015 at 4:17 PM, Mike Scherbakov<br>
<<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>> wrote:<br>
> Thanks guys.<br>
> So for fuel-octane then there are no actions needed.<br>
><br>
> For fuel-agent-core group [1], looks like we are already good (it doesn't<br>
> have fuel-core group nested). But it would need to include fuel-infra group<br>
> and remove Aleksandra Fedorova (she will be a part of fuel-infra group).<br>
><br>
> python-fuel-client-core [2] is good as well (no nested fuel-core). However,<br>
> there is another group python-fuelclient-release [3], which has to be<br>
> eliminated, and main python-fuelclient-core would just have fuel-infra group<br>
> included for maintenance purposes.<br>
><br>
> [1] <a href="https://review.openstack.org/#/admin/groups/995,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/995,members</a><br>
> [2] <a href="https://review.openstack.org/#/admin/groups/551,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/551,members</a><br>
> [3] <a href="https://review.openstack.org/#/admin/groups/552,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/552,members</a><br>
><br>
><br>
> On Mon, Sep 21, 2015 at 11:06 AM Oleg Gelbukh <<a href="mailto:ogelbukh@mirantis.com" target="_blank">ogelbukh@mirantis.com</a>> wrote:<br>
>><br>
>> FYI, we have a separate core group for stackforge/fuel-octane repository<br>
>> [1].<br>
>><br>
>> I'm supporting the move to modularization of Fuel with cleaner separation<br>
>> of authority and better defined interfaces. Thus, I'm +1 to such a change as<br>
>> a part of that move.<br>
>><br>
>> [1] <a href="https://review.openstack.org/#/admin/groups/1020,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/1020,members</a><br>
>><br>
>> --<br>
>> Best regards,<br>
>> Oleg Gelbukh<br>
>><br>
>> On Sun, Sep 20, 2015 at 11:56 PM, Mike Scherbakov<br>
>> <<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>> wrote:<br>
>>><br>
>>> Hi all,<br>
>>> as of my larger proposal on improvements to code review workflow [1], we<br>
>>> need to have cores for repositories, not for the whole Fuel. It is the path<br>
>>> we are taking for a while, and new core reviewers added to specific repos<br>
>>> only. Now we need to complete this work.<br>
>>><br>
>>> My proposal is:<br>
>>><br>
>>> Get rid of one common fuel-core [2] group, members of which can merge<br>
>>> code anywhere in Fuel. Some members of this group may cover a couple of<br>
>>> repositories, but can't really be cores in all repos.<br>
>>> Extend existing groups, such as fuel-library [3], with members from<br>
>>> fuel-core who are keeping up with large number of reviews / merges. This<br>
>>> data can be queried at Stackalytics.<br>
>>> Establish a new group "fuel-infra", and ensure that it's included into<br>
>>> any other core group. This is for maintenance purposes, it is expected to be<br>
>>> used only in exceptional cases. Fuel Infra team will have to decide whom to<br>
>>> include into this group.<br>
>>> Ensure that fuel-plugin-* repos will not be affected by removal of<br>
>>> fuel-core group.<br>
>>><br>
>>> #2 needs specific details. Stackalytics can show active cores easily, we<br>
>>> can look at people with *:<br>
>>> <a href="http://stackalytics.com/report/contribution/fuel-web/180" rel="noreferrer" target="_blank">http://stackalytics.com/report/contribution/fuel-web/180</a>. This is for<br>
>>> fuel-web, change the link for other repos accordingly. If people are added<br>
>>> specifically to the particular group, leaving as is (some of them are no<br>
>>> longer active. But let's clean them up separately from this group<br>
>>> restructure process).<br>
>>><br>
>>> fuel-library-core [3] group will have following members: Bogdan D.,<br>
>>> Sergii G., Alex Schultz, Vladimir Kuklin, Alex Didenko.<br>
>>> fuel-web-core [4]: Sebastian K., Igor Kalnitsky, Alexey Kasatkin, Vitaly<br>
>>> Kramskikh, Julia Aranovich, Evgeny Li, Dima Shulyak<br>
>>> fuel-astute-core [5]: Vladimir Sharshov, Evgeny Li<br>
>>> fuel-dev-tools-core [6]: Przemek Kaminski, Sebastian K.<br>
>>> fuel-devops-core [7]: Tatyana Leontovich, Andrey Sledzinsky, Nastya<br>
>>> Urlapova<br>
>>> fuel-docs-core [8]: Irina Povolotskaya, Denis Klepikov, Evgeny<br>
>>> Konstantinov, Olga Gusarenko<br>
>>> fuel-main-core [9]: Vladimir Kozhukalov, Roman Vyalov, Dmitry Pyzhov,<br>
>>> Sergii Golovatyuk, Vladimir Kuklin, Igor Kalnitsky<br>
>>> fuel-nailgun-agent-core [10]: Vladimir Sharshov, V.Kozhukalov<br>
>>> fuel-ostf-core [11]: Tatyana Leontovich, Nastya Urlapova, Andrey<br>
>>> Sledzinsky, Dmitry Shulyak<br>
>>> fuel-plugins-core [12]: Igor Kalnitsky, Evgeny Li, Alexey Kasatkin<br>
>>> fuel-qa-core [13]: Andrey Sledzinsky, Tatyana Leontovich, Nastya Urlapova<br>
>>> fuel-stats-core [14]: Alex Kislitsky, Alexey Kasatkin, Vitaly Kramskikh<br>
>>> fuel-tasklib-core [15]: Igor Kalnitsky, Dima Shulyak, Alexey Kasatkin<br>
>>> (this project seems to be dead, let's consider to rip it off)<br>
>>> fuel-specs-core: there is no such a group at the moment. I propose to<br>
>>> create one with following members, based on stackalytics data [16]: Vitaly<br>
>>> Kramskikh, Bogdan Dobrelia, Evgeny Li, Sergii Golovatyuk, Vladimir Kuklin,<br>
>>> Igor Kalnitsky, Alexey Kasatkin, Roman Vyalov, Dmitry Borodaenko, Mike<br>
>>> Scherbakov, Dmitry Pyzhov. We would need to reconsider who can merge after<br>
>>> Fuel PTL/Component Leads elections<br>
>>> fuel-octane-core: needs to be created. Members: Yury Taraday, Oleg<br>
>>> Gelbukh, Ilya Kharin<br>
>>> fuel-mirror-core: needs to be created. Sergey Kulanov, Vitaly Parakhin<br>
>>> fuel-upgrade-core: needs to be created. Sebastian Kalinowski, Alex<br>
>>> Schultz, Evgeny Li, Igor Kalnitsky<br>
>>> fuel-provision: repo seems to be outdated, needs to be removed.<br>
>>><br>
>>> I suggest to make changes in groups first, and then separately address<br>
>>> specific issues like removing someone from cores (not doing enough reviews<br>
>>> anymore or too many positive reviews, let's say > 95%).<br>
>>><br>
>>> I hope I don't miss anyone / anything. Please check carefully.<br>
>>> Comments / objections?<br>
>>><br>
>>> [1]<br>
>>> <a href="http://lists.openstack.org/pipermail/openstack-dev/2015-August/072406.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2015-August/072406.html</a><br>
>>> [2] <a href="https://review.openstack.org/#/admin/groups/209,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/209,members</a><br>
>>> [3] <a href="https://review.openstack.org/#/admin/groups/658,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/658,members</a><br>
>>> [4] <a href="https://review.openstack.org/#/admin/groups/664,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/664,members</a><br>
>>> [5] <a href="https://review.openstack.org/#/admin/groups/655,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/655,members</a><br>
>>> [6] <a href="https://review.openstack.org/#/admin/groups/646,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/646,members</a><br>
>>> [7] <a href="https://review.openstack.org/#/admin/groups/656,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/656,members</a><br>
>>> [8] <a href="https://review.openstack.org/#/admin/groups/657,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/657,members</a><br>
>>> [9] <a href="https://review.openstack.org/#/admin/groups/659,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/659,members</a><br>
>>> [10] <a href="https://review.openstack.org/#/admin/groups/1000,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/1000,members</a><br>
>>> [11] <a href="https://review.openstack.org/#/admin/groups/660,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/660,members</a><br>
>>> [12] <a href="https://review.openstack.org/#/admin/groups/661,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/661,members</a><br>
>>> [13] <a href="https://review.openstack.org/#/admin/groups/662,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/662,members</a><br>
>>> [14] <a href="https://review.openstack.org/#/admin/groups/663,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/663,members</a><br>
>>> [15] <a href="https://review.openstack.org/#/admin/groups/624,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/624,members</a><br>
>>> [16] <a href="http://stackalytics.com/report/contribution/fuel-specs/180" rel="noreferrer" target="_blank">http://stackalytics.com/report/contribution/fuel-specs/180</a><br>
>>><br>
>>><br>
>>> --<br>
>>> Mike Scherbakov<br>
>>> #mihgen<br>
>>><br>
>>><br>
>>> __________________________________________________________________________<br>
>>> OpenStack Development Mailing List (not for usage questions)<br>
>>> Unsubscribe:<br>
>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
> --<br>
> Mike Scherbakov<br>
> #mihgen<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
<br>
--<br>
Dmitry Borodaenko<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><div dir="ltr">-- <br></div><div dir="ltr">Mike Scherbakov<br>#mihgen</div>