Thanks for the suggestion. I think it merits further work to write our policies down in git. I wanted to get this out a little more quickly since these are our foundational policies and there is some confusion among the cores about them - even though we have been using them for the better part of 2+ years :)
I'll see what I can do to get our policies put into our documentation. Regards, -steve On 6/17/16, 7:36 PM, "Gerard Braad" <m...@gbraad.nl> wrote: >On Sat, Jun 18, 2016 at 9:49 AM, Assaf Muller <as...@redhat.com> wrote: >> I would recommend in-tree policies .rsts instead of Wiki entries. >> There is a higher cost to make changes, but they have to go through >> the review process, and the content will survive as long as the .git >> repo does. > >Good point. The higher cost is probably even desirable. +1 > >__________________________________________________________________________ >OpenStack Development Mailing List (not for usage questions) >Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
