On Fri, Apr 25 2014, Chmouel Boudjnah wrote:
> I am not sure tho that forking oslo.common.policy is any better than
> copy/pasting it with its dependences.
+1, forking is not an option.
> I would suggest we move `swift-keystoneauth` to its own project part of the
> swift umbrella projects to han
I haven't done a full review but I like what you did and this should be the
proper way to handle ACL for keystoneauth.
I am not sure tho that forking oslo.common.policy is any better than
copy/pasting it with its dependences.
I would suggest we move `swift-keystoneauth` to its own project part of
