As an interim measure, added keystone-core to oslo-policy-core[1] Thanks, Dims
[1] https://review.openstack.org/#/admin/groups/556,members On Wed, Dec 16, 2015 at 10:40 PM, Dolph Mathews <dolph.math...@gmail.com> wrote: > > On Wed, Dec 16, 2015 at 1:33 PM, Davanum Srinivas <dava...@gmail.com> wrote: >> >> Brant, >> >> I am ok either way, guess the alternative was to add keystone-core >> directly to the oslo.policy core group (can't check right now). > > > That's certainly reasonable, and kind of what we did with pycadf. > >> >> >> The name is very possibly going to create confusion > > > I assume you're not referring to unnecessarily changing the name of the > project itself (oslo.policy) just because there might be a shift in the > group of maintainers! Either way, let's definitely not do that. > >> >> -- Dims >> >> On Wed, Dec 16, 2015 at 7:22 PM, Jordan Pittier >> <jordan.pitt...@scality.com> wrote: >> > Hi, >> > I am sure oslo.policy would be good under Keystone's governance. But I >> > am >> > not sure I understood what's wrong in having oslo.policy under the oslo >> > program ? >> > >> > Jordan >> > >> > On Wed, Dec 16, 2015 at 6:13 PM, Brant Knudson <b...@acm.org> wrote: >> >> >> >> >> >> I'd like to propose moving oslo.policy from the oslo program to the >> >> keystone program. Keystone developers know what's going on with >> >> oslo.policy >> >> and I think are more interested in what's going on with it so that >> >> reviews >> >> will get proper vetting, and it's not like oslo doesn't have enough >> >> going on >> >> with all the other repos. Keystone core has equivalent stringent >> >> development >> >> policy that we already enforce with keystoneclient and keystoneauth, so >> >> oslo.policy isn't going to be losing any stability. >> >> >> >> If there aren't any objections, let's go ahead with this. I heard this >> >> requires a change to a governance repo, and gerrit permission changes >> >> to >> >> make keystone-core core, and updates in oslo.policy to change some docs >> >> or >> >> links. Any oslo.policy specs that are currently proposed >> >> >> >> - Brant >> >> >> >> >> >> >> >> __________________________________________________________________________ >> >> 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 >> > >> >> >> >> -- >> Davanum Srinivas :: https://twitter.com/dims >> >> __________________________________________________________________________ >> 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 > -- Davanum Srinivas :: https://twitter.com/dims __________________________________________________________________________ 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