Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

Now that OpenStack Infra team has completed the stackforge namespace retirement and merged our ACL update [0], the rest of core reviewers cleanup is done: - creating tags and branches is now restricted to fuel-release group [1] - fuel-specs-core is populated as per proposal quoted below [2] [0]

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

While we're waiting for openstack-infra team to finish the stackforge migration and review our ACL changes, I implemented the rest of the changes agreed in this thread: - Fuel-core group removed everywhere. - Per-project core groups populated with individual reviewers as quoted below.

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

On Wed, Oct 07, 2015 at 02:04:52PM -0700, Dmitry Borodaenko wrote: > While we're waiting for openstack-infra team to finish the stackforge > migration and review our ACL changes, I implemented the rest of the > changes agreed in this thread: > > - Fuel-core group removed everywhere. > > -

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

Update here: patch was marked as WIP for now due to comment from Anita Kuno: > 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. > Can we mark this patch wip until after

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

This commit brings Fuel ACLs in sync with each other and in line with the agreement on this thread: https://review.openstack.org/230195 Please review carefully. Note that I intentionally didn't touch any of the plugins ACLs, primarily to save time for us and the openstack-infra team until after

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

+1 On Tue, Sep 22, 2015 at 2:17 AM, Mike Scherbakov wrote: > Thanks guys. > So for fuel-octane then there are no actions needed. > > For fuel-agent-core group [1], looks like we are already good (it doesn't > have fuel-core group nested). But it would need to include

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

+1 -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Sep 23, 2015 at 12:10 PM, Vladimir Kuklin wrote: > +1 > > > On Tue, Sep 22, 2015 at 2:17 AM, Mike Scherbakov > wrote: > >> Thanks guys. >> So for fuel-octane then there

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

Thanks guys. So for fuel-octane then there are no actions needed. For fuel-agent-core group [1], looks like we are already good (it doesn't have fuel-core group nested). But it would need to include fuel-infra group and remove Aleksandra Fedorova (she will be a part of fuel-infra group).

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

Hi, Just a remark: python-fuelclient is missing here. Aleksey Kasatkin On Sun, Sep 20, 2015 at 3:56 PM, Mike Scherbakov wrote: > Hi all, > as of my larger proposal on improvements to code review workflow [1], we > need to have cores for repositories, not for the

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

FYI, we have a separate core group for stackforge/fuel-octane repository [1]. I'm supporting the move to modularization of Fuel with cleaner separation of authority and better defined interfaces. Thus, I'm +1 to such a change as a part of that move. [1]

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

Hi, Mike, fuel-agent is missing here too. http://stackalytics.com/report/contribution/fuel-agent/180 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Fuel] Core Reviewers groups restructure

Hi all, as of my larger proposal on improvements to code review workflow [1], we need to have cores for repositories, not for the whole Fuel. It is the path we are taking for a while, and new core reviewers added to specific repos only. Now we need to complete this work. My proposal is: 1.