Can we stick to one tag [kolla] for all ML discussion? A whole slew of people already have filters setup. Kolla is one project with one mission with multiple deliverables. No other project that has multiple deliverables tags emails per deliverable. I don’t think this is an occasion to be a special snowflake.
TIA :) -steve On 11/16/16, 11:23 AM, "Michał Jastrzębski" <inc...@gmail.com> wrote: >Hello, > >In light of recent events (kolla-kubernetes becoming thriving project, >kolla-ansible being split) I feel we need to change of core reviewer >election process. > >Currently Kolla was single core team. That is no longer the case, as >right now we have 3 distinct core teams (kolla, kolla-ansible and >kolla-kubernetes), although for now with big overlap in terms of >people in them. > >For future-proofing, as we already have difference between teams, I >propose following change to core election process: > > >Core reviewer voting rights are reserved by core team in question. >Which means if someone propose core reviewer to kolla-kubernetes, only >kolla-kubernetes cores has a voting right (not kolla or kolla-ansible >cores). > > >Voting will be open until 30 Nov '16 end of day. Reviewers from all >core teams in kolla has voting rights on this policy change. > >Regards >Michal > >__________________________________________________________________________ >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