<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/09/2014 12:18 PM, Morgan Fainberg
wrote:<br>
</div>
<blockquote cite="mid:etPan.54872ef8.74b0dc51.201e@nullptr.local"
type="cite">
<style>body{font-family:Helvetica,Arial;font-size:13px}</style>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I would like
to propose that we keep the policy library under the oslo
program. As with other graduated projects we will maintain a
core team (that while including the oslo-core team) will be
comprised of the expected individuals from the Identity and
other security related teams.</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br>
</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;">The change in
direction is due to the policy library being more generic and
not exactly a clean fit with the OpenStack Identity program.
This is the policy rules engine, which is currently used by all
(or almost all) OpenStack projects. Based on the continued
conversation, it doesn’t make sense to take it out of the
“common” namespace.</div>
</blockquote>
Agreed. I think the original design was quite clean, and could
easily be used by projects not even in Open Stack. While we don't
want to be challenge any of the python based replacements for
Prolog, the name should reflect its general purpose.<br>
<br>
Is the congress program still planning on using the same rules
engine?<br>
<br>
<br>
<blockquote cite="mid:etPan.54872ef8.74b0dc51.201e@nullptr.local"
type="cite">
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br>
</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;">If there are
no concerns with this change of direction we will update the
spec[1] to reflect this proposal and continue with the plans to
graduate as soon as possible.</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br>
</div>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;">[1] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/140161/">https://review.openstack.org/#/c/140161/</a></div>
<br>
<div id="bloop_sign_1418145096905398016" class="bloop_sign">
<div style="font-family:helvetica,arial;font-size:13px">-- <br>
Morgan Fainberg<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>