Guys, I have one serious question: WHO will be global core? Example: I'm core reviewer in 2 repos, but I'm absolutely could not be core reviewer in puppet!
On Tue, Sep 6, 2016 at 11:31 AM, Igor Kalnitsky <i...@kalnitsky.org> wrote: > -1 for the proposal. I see no problems to add guys who're familiar > with various sub-projects to multiple core groups. > > On Tue, Sep 6, 2016 at 10:38 AM, Evgeniy L <e...@mirantis.com> wrote: > > +1 to Lukasz. > > -1 to the proposal, we had it this way for a quite some time, and it was > not > > good for the project (as Lukasz pointed out), why should a person who > merges > > the code to the library have an access to merge the code to > Nailgun/Astute > > without proper expertise. Those are different areas which require > different > > skills. > > > > Thanks, > > > > On Tue, Sep 6, 2016 at 9:40 AM, Lukasz Oles <lo...@mirantis.com> wrote: > >> > >> On Mon, Sep 5, 2016 at 5:39 PM, Andrew Maksimov <amaksi...@mirantis.com > > > >> wrote: > >> > +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. > >> Actually one of the reasons why core groups were split was that it > >> happened a few times :) > >> > >> > > >> > Regards, > >> > Andrey Maximov > >> > > >> > On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov > >> > <vkozhuka...@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-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 > >> > > >> > >> > >> > >> -- > >> Łukasz Oleś > >> > >> ____________________________________________________________ > ______________ > >> 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 > > > > __________________________________________________________________________ > 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 > -- Alexey Stepanov
__________________________________________________________________________ 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