+1 This is a good proposal, I also think we should have single fuel-core group for all repos. In real life core reviewers won't set +2 or merge to repos with which they are not familiar with. Regards, Andrey Maximov On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov < vkozhukalov at mirantis.com> wrote: > Dear colleagues, > > I'd like to suggest to use common fuel-core group for all Fuel projects > instead of having separate independent 'by-project' core groups like > 'fuel-astute-core' or 'fuel-agent-core'. > > Pros: > 1) It will be easier to access core members (timezone and holiday > tolerance) > 2) It will be easier to manage single core group (promote new members, > remove not active members) > > Cons: > 1) Less of flexibility. Permissions will be the same for all core > reviewers in all Fuel projects. > > What do you think? > > Vladimir Kozhukalov > > __________________________________________________________________________ > 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/20160905/b4d880fe/attachment.html>