<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 17, 2015 at 1:51 PM, Davanum Srinivas <span dir="ltr"><<a href="mailto:davanum@gmail.com" target="_blank">davanum@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thinking more about it. The only change we'll have is that if someone<br>
files a oslo-specs for oslo.policy we need to tell them to switch over<br>
to keystone-specs. We could add notes in README etc to make this<br>
apparent. So i am +1 to making this move.<br>
<br>
Brant, other keystone cores,<br>
Can you please file the governance review request and we can make sure<br>
oslo cores chime in there? and make it official?<br>
<br></blockquote><div><br></div><div>Here's the proposed governance change: <a href="https://review.openstack.org/#/c/259169/">https://review.openstack.org/#/c/259169/</a><br><br></div><div> - Brant<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Thanks,<br>
Dims<br>
<div class=""><div class="h5"><br>
<br>
On Thu, Dec 17, 2015 at 2:40 PM, Flavio Percoco <<a href="mailto:flavio@redhat.com">flavio@redhat.com</a>> wrote:<br>
> On 16/12/15 18:51 -0800, Morgan Fainberg wrote:<br>
>><br>
>> For what is is worth, we originally proposed oslo.policy to graduate to<br>
>> Keystone when we were converting to the library. I still think it belongs<br>
>> in<br>
>> keystone (as long as the oslo team doesn't mind that long-term keystone<br>
>> team<br>
>> owns something in the oslo.XXXX namespace).<br>
>><br>
>> The short term adding keystone-core should get some more eyes on the<br>
>> reviews,<br>
>> so +1 to that.<br>
><br>
><br>
><br>
> Just want to +1 all the above.<br>
><br>
> It'd be great if we can finally hand the library over to the keystone<br>
> team, where I think it belongs.<br>
><br>
> Cheers,<br>
> Flavio<br>
><br>
>><br>
>> --Morgan<br>
>><br>
>> On Wed, Dec 16, 2015 at 4:08 PM, Davanum Srinivas <<a href="mailto:davanum@gmail.com">davanum@gmail.com</a>><br>
>> wrote:<br>
>><br>
>> As an interim measure, added keystone-core to oslo-policy-core[1]<br>
>><br>
>> Thanks,<br>
>> Dims<br>
>><br>
>> [1] <a href="https://review.openstack.org/#/admin/groups/556,members" rel="noreferrer" target="_blank">https://review.openstack.org/#/admin/groups/556,members</a><br>
>><br>
>> On Wed, Dec 16, 2015 at 10:40 PM, Dolph Mathews<br>
>> <<a href="mailto:dolph.mathews@gmail.com">dolph.mathews@gmail.com</a>><br>
>> wrote:<br>
>> ><br>
>> > On Wed, Dec 16, 2015 at 1:33 PM, Davanum Srinivas <<a href="mailto:davanum@gmail.com">davanum@gmail.com</a>><br>
>> wrote:<br>
>> >><br>
>> >> Brant,<br>
>> >><br>
>> >> I am ok either way, guess the alternative was to add keystone-core<br>
>> >> directly to the oslo.policy core group (can't check right now).<br>
>> ><br>
>> ><br>
>> > That's certainly reasonable, and kind of what we did with pycadf.<br>
>> ><br>
>> >><br>
>> >><br>
>> >> The name is very possibly going to create confusion<br>
>> ><br>
>> ><br>
>> > I assume you're not referring to unnecessarily changing the name of<br>
>> the<br>
>> > project itself (oslo.policy) just because there might be a shift in<br>
>> the<br>
>> > group of maintainers! Either way, let's definitely not do that.<br>
>> ><br>
>> >><br>
>> >> -- Dims<br>
>> >><br>
>> >> On Wed, Dec 16, 2015 at 7:22 PM, Jordan Pittier<br>
>> >> <<a href="mailto:jordan.pittier@scality.com">jordan.pittier@scality.com</a>> wrote:<br>
>> >> > Hi,<br>
>> >> > I am sure oslo.policy would be good under Keystone's governance.<br>
>> But I<br>
>> >> > am<br>
>> >> > not sure I understood what's wrong in having oslo.policy under the<br>
>> oslo<br>
>> >> > program ?<br>
>> >> ><br>
>> >> > Jordan<br>
>> >> ><br>
>> >> > On Wed, Dec 16, 2015 at 6:13 PM, Brant Knudson <<a href="mailto:blk@acm.org">blk@acm.org</a>><br>
>> wrote:<br>
>> >> >><br>
>> >> >><br>
>> >> >> I'd like to propose moving oslo.policy from the oslo program to<br>
>> the<br>
>> >> >> keystone program. Keystone developers know what's going on with<br>
>> >> >> oslo.policy<br>
>> >> >> and I think are more interested in what's going on with it so<br>
>> that<br>
>> >> >> reviews<br>
>> >> >> will get proper vetting, and it's not like oslo doesn't have<br>
>> enough<br>
>> >> >> going on<br>
>> >> >> with all the other repos. Keystone core has equivalent stringent<br>
>> >> >> development<br>
>> >> >> policy that we already enforce with keystoneclient and<br>
>> keystoneauth,<br>
>> so<br>
>> >> >> oslo.policy isn't going to be losing any stability.<br>
>> >> >><br>
>> >> >> If there aren't any objections, let's go ahead with this. I heard<br>
>> this<br>
>> >> >> requires a change to a governance repo, and gerrit permission<br>
>> changes<br>
>> >> >> to<br>
>> >> >> make keystone-core core, and updates in oslo.policy to change<br>
>> some<br>
>> docs<br>
>> >> >> or<br>
>> >> >> links. Any oslo.policy specs that are currently proposed<br>
>> >> >><br>
>> >> >> - Brant<br>
>> >> >><br>
>> >> >><br>
>> >> >><br>
>> >> >><br>
>><br>
>> __________________________________________________________________________<br>
>> >> >> OpenStack Development Mailing List (not for usage questions)<br>
>> >> >> Unsubscribe:<br>
>> >> >> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> >> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>> >> >><br>
>> >> ><br>
>> >> ><br>
>> >> ><br>
>> >> ><br>
>><br>
>> __________________________________________________________________________<br>
>> >> > OpenStack Development Mailing List (not for usage questions)<br>
>> >> > Unsubscribe:<br>
>> >> > <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> >> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>> >> ><br>
>> >><br>
>> >><br>
>> >><br>
>> >> --<br>
>> >> Davanum Srinivas :: <a href="https://twitter.com/dims" rel="noreferrer" target="_blank">https://twitter.com/dims</a><br>
>> >><br>
>> >><br>
>><br>
>> __________________________________________________________________________<br>
>> >> OpenStack Development Mailing List (not for usage questions)<br>
>> >> Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?<br>
>> subject:unsubscribe<br>
>> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>><br>
>> __________________________________________________________________________<br>
>> > OpenStack Development Mailing List (not for usage questions)<br>
>> > Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?<br>
>> subject:unsubscribe<br>
>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> Davanum Srinivas :: <a href="https://twitter.com/dims" rel="noreferrer" target="_blank">https://twitter.com/dims</a><br>
>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
> --<br>
> @flaper87<br>
> Flavio Percoco<br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
--<br>
Davanum Srinivas :: <a href="https://twitter.com/dims" rel="noreferrer" target="_blank">https://twitter.com/dims</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>