On Thu, Jan 5, 2017 at 4:34 PM, Jeremy Stanley <fu...@yuggoth.org> wrote:
> On 2017-01-05 15:58:45 +0000 (+0000), Sam Yaple wrote: > > Involving kolla-ansible and kolla-kubernetes in a decision about > kolla-salt > > (or kolla-puppet, or kolla-chef) is silly since the projects are > unrelated. > > That would be like involving glance when cinder has a new service because > > they both use keystone. The kolla-core team is reasonable since those are > > the images being consumed. > > In contrast, the Infra team also has a vast number of fairly > unrelated deliverables with their own dedicated core review teams. > In our case, we refer to them as our "Infra Council" and ask them to > weigh in with Roll-Call votes on proposals to the infra-specs repo. > In short, just because people work primarily on one particular > service doesn't mean they're incapable of providing useful feedback > on and help prioritize proposals to add other (possibly unrelated) > services. > I do feel this is slightly different than whats described. Since it is not unrelated services, but rather, for lack of a better word, competing services. To my knowledge infra doesn't have several service doing the same job with different core teams (though I could be wrong). Thanks, SamYaple > -- > Jeremy Stanley > > __________________________________________________________________________ > 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
