<div dir="ltr">On 20 April 2015 at 17:52, David Kranz <span dir="ltr"><<a href="mailto:dkranz@redhat.com" target="_blank">dkranz@redhat.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class="">
<div>On 04/20/2015 08:07 PM, Ian Wells
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Whatever your preference might be, I think it's best we
lose the ambiguity. And perhaps advertise that page a
little more widely, actually - I hadn't come across it in
my travels. And perhaps improve its air of authority:
rules on this subject should probably live somewhere in a
repo so that it's clear there's consensus for changes.
Currently anyone can change it for any reason, and two
years after the last substantive change it's hard to say
who even knew it was being changed, let alone whether they
agreed.<br>
<div class="gmail_extra"><div class="gmail_quote">
</div>
</div>
</div>
</blockquote></span>
This page has some kind of authority as it is linked to from
<a href="https://wiki.openstack.org/wiki/Governance/Approved/APIStability" target="_blank">https://wiki.openstack.org/wiki/Governance/Approved/APIStability</a>. At
that time the guidelines were a work in progress but clearly at this
point it belongs in a more controlled repo. That said, this document
has been referenced many times on the dev list and I am not sure
that just moving it to a repo would increase awareness. It would
also need to be more advertised.<span class="HOEnZb"><font color="#888888"><br></font></span></div></blockquote><div><br></div><div>Yeah - the repo was more an issue of authority, so that when it changes it's clear that it's been changed and people checked the change.<br><br>The awareness thing is probably something that PTLs need to propagate - reviewers need to know of it and what it says and check it when approving API-affecting changes.<br>-- <br></div><div>Ian.<br></div></div></div></div>