<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jul 25, 2014, at 2:09 PM, Dolph Mathews <<a href="mailto:dolph.mathews@gmail.com">dolph.mathews@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div>Hello everyone,</div><div><br></div><div>This is me waving my arms around trying to gather feedback on a change in scope that seems agreeable to a smaller audience. Most recently, we've discussed this in both the Keystone [1] and Oslo [2] weekly meetings.</div>
<div><br></div><div>tl;dr it seems to make sense to move the PyCADF library from the oslo program to the Identity program, and increase the scope of the Identity program's mission statement accordingly.</div><div><br>
</div><div>I've included ceilometer on this thread since I believe it was originally proposed that PyCADF be included in that program, but was subsequently rejected.</div><div><br></div><div>Expand scope of the Identity program to include auditing: <a href="https://review.openstack.org/#/c/109664/">https://review.openstack.org/#/c/109664/</a><br></div></div></blockquote><div><br></div><div>I think this move makes sense. It provides a good home with interested contributors for PyCADF, and if it makes it easier for the Identity team to manage cross-repository changes then that’s a bonus.</div><div><br></div><div>Before we move ahead, I would like to hear from the other current pycadf and oslo team members, especially Gordon since he is the primary maintainer.</div><div><br></div><div>Doug</div><div><br></div><blockquote type="cite"><div dir="ltr"><div><br></div><div>As a closely related but subsequent (and dependent) change, I've proposed renaming the Identity program to better reflect the new scope: <a href="https://review.openstack.org/#/c/108739/">https://review.openstack.org/#/c/108739/</a></div></div></blockquote><blockquote type="cite"><div dir="ltr"><div><br></div><div>The commit messages on these two changes hopefully explain the reasoning behind each change, if it's not already self-explanatory. Although only the TC has voting power in this repo, your review comments and replies on this thread are equally welcome.</div>
<div><br></div><div>As an important consequence, Doug suggested maintaining pycadf-core [3] as a discrete core group focused on the library during today's oslo meeting. If any other program/project has gone through a similar process, I'd be interested in hearing about the experience if there's anything we can learn from. Otherwise, Doug's suggestion sounds like a reasonable approach to me.</div>
<div><div><br class="">[1] <a href="http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-07-22-18.02.html">http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-07-22-18.02.html</a></div><div>
<br></div><div>[2] <a href="http://eavesdrop.openstack.org/meetings/oslo/2014/oslo.2014-07-25-16.00.html">http://eavesdrop.openstack.org/meetings/oslo/2014/oslo.2014-07-25-16.00.html</a></div></div><div><br></div><div>[3] <a href="https://review.openstack.org/#/admin/groups/192,members">https://review.openstack.org/#/admin/groups/192,members</a></div>
<div><br></div><div>Thanks!</div><div><br></div><div>-Dolph</div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></body></html>