> -----Original Message----- > From: Doug Hellmann <d...@doughellmann.com> > Sent: Monday, June 4, 2018 5:52 PM > To: openstack-dev <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [tc] Organizational diversity tag > > Excerpts from Zane Bitter's message of 2018-06-04 17:41:10 -0400: > > On 02/06/18 13:23, Doug Hellmann wrote: > > > Excerpts from Zane Bitter's message of 2018-06-01 15:19:46 -0400: > > >> On 01/06/18 12:18, Doug Hellmann wrote: > > > > > > [snip] > > Apparently enough people see it the way you described that this is > > probably not something we want to actively spread to other projects at > > the moment. > > I am still curious to know which teams have the policy. If it is more > widespread than I realized, maybe it's reasonable to extend it and use it as > the basis for a health check after all. >
A while back, Trove had this policy. When Rackspace, HP, and Tesora had core reviewers, (at various times, eBay, IBM and Red Hat also had cores), the agreement was that multiple cores from any one company would not merge a change unless it was an emergency. It was not formally written down (to my knowledge). It worked well, and ensured that the operators didn't get surprised by some unexpected thing that took down their service. -amrith __________________________________________________________________________ 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
