16:00:03 <lbragstad> #startmeeting policy
16:00:05 <lbragstad> o/
16:00:05 <openstack> Meeting started Wed Oct  4 16:00:03 2017 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:06 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:08 <openstack> The meeting name has been set to 'policy'
16:00:09 <kmalloc> o/
16:00:24 <lbragstad> #link https://etherpad.openstack.org/p/keystone-policy-meeting
16:00:32 <lbragstad> agenda ^
16:01:22 <lbragstad> #topic oslo specs
16:01:25 <lbragstad> quick update on these
16:01:27 <lbragstad> #link https://review.openstack.org/#/c/500141/
16:01:31 <lbragstad> #link https://review.openstack.org/#/c/500207/
16:01:39 <lbragstad> i've updated both per reviews
16:01:49 <lbragstad> i'll be starting on an implementation for policy deprecation this afternoon
16:02:34 <lbragstad> reviews appreciated!
16:02:42 <lbragstad> #topic community goal status
16:02:50 <lbragstad> we're getting there
16:02:50 <cmurphy> o/
16:02:51 <lbragstad> #link https://www.lbragstad.com/policy-burndown/
16:03:02 <lbragstad> nearly half the projects have started moving policy into code
16:03:14 <lbragstad> which means we have **tons** to review
16:03:21 <hrybacki> woo
16:03:26 <lbragstad> #link https://review.openstack.org/#/q/topic:policy-and-docs-in-code%20is:open
16:03:56 <hrybacki> wow, three pages atm
16:04:17 <lbragstad> yeah - it's a good bit
16:04:50 <lbragstad> i'm mostly checking to make sure things are done somewhat consistently - that's the biggest thing i'm seeing
16:04:59 <gagehugo> o/
16:06:00 <lbragstad> any questions or comments on the policy in code stuff?
16:07:12 <lbragstad> #topic open discussion
16:07:28 <lbragstad> in other news - i posted a thread to the mailing list from yesterday's meeting
16:07:28 * hrybacki has nothing to add
16:07:31 <lbragstad> #link http://lists.openstack.org/pipermail/openstack-dev/2017-October/123069.html
16:09:10 <lbragstad> figured it would be appropriate to mention it here since this is a policy meeting
16:10:48 <lbragstad> blancos: is there anything specific needed for patrole to consume the policy in code stuff?
16:11:16 <blancos> We already have tests making use of Nova and Keystone's policy in code and they work fine
16:11:42 <blancos> If that's the format everyone's following, we won't need to make any big changes
16:11:44 <lbragstad> nice - so it's a pretty established process to convert from in-file policy testing to in-code testing?
16:12:20 <blancos> In Patrole? Yes
16:12:28 <lbragstad> good deal
16:13:13 <lbragstad> is patrole just checking policy patches manually, or the community goal document to know when to switch a project over?
16:13:58 <blancos> In our framework we check for custom policy file and policy in code
16:14:11 <lbragstad> oh - cool
16:14:41 <lbragstad> i was wondering how you know when to start making changes, but that sounds pretty automatic
16:14:56 <blancos> Yes, it's baked into the framework
16:15:08 <lbragstad> or if pinging someone from patrole was necessary when a project gets it implemented
16:15:11 <lbragstad> aweseome
16:16:20 <lbragstad> that's all i had for open discussion
16:16:30 <lbragstad> if no one has anything else, we can get some time back
16:18:02 <lbragstad> thanks for coming!
16:18:06 <lbragstad> #endmeeting