<div dir="ltr"><div dir="ltr"><div dir="ltr">On Fri, Feb 8, 2019 at 8:20 AM Chris Dent <<a href="mailto:cdent%2Bos@anticdent.org">cdent+os@anticdent.org</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Yesterday at the TC meeting [1] we decided that the in-progress task<br>
to make sure the technical vision document [2] has been fully<br>
evaluated by project teams needs a bit more time, so this message is<br>
being produced as a reminder.<br>
<br>
Back in January Julia produced a message [3] suggesting that each<br>
project consider producing a document where they compare their<br>
current state with an idealized state if they were in complete<br>
alignment with the vision. There were two hoped for outcomes:<br>
<br>
* A useful in-project document that could help guide future<br>
   development.<br>
* Patches to the vision document to clarify or correct the vision<br>
   where it is discovered to be not quite right.<br>
<br>
A few projects have started that process (see, for example,<br>
melwitt's recent message for some links [4]) resulting in some good<br>
plans as well as some improvements to the vision document [5].<br></blockquote><div><br></div><div>As a note, we're compiling links to these in the vision document</div><div>itself. This is the first: <a href="https://review.openstack.org/#/c/644953/">https://review.openstack.org/#/c/644953/</a></div><div><br></div><div>Teams are welcome to add to that list as they write these sorts</div><div>of documents. :)</div><div><br></div><div>// jim </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
In the future the TC would like to use the vision document to help<br>
evaluate projects applying to be "official" as well as determining<br>
if projects are "healthy". As such it is important that the document<br>
be constantly evolving toward whatever "correct" means. The process<br>
described in Julia's message [3] is a useful to make it so. Please<br>
check it out.<br>
<br>
Thanks.<br>
<br>
[1] <a href="http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-02-07-14.00.html" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-02-07-14.00.html</a><br>
[2] <a href="https://governance.openstack.org/tc/reference/technical-vision.html" rel="noreferrer" target="_blank">https://governance.openstack.org/tc/reference/technical-vision.html</a><br>
[3] <a href="http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001417.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001417.html</a><br>
[4] <a href="http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002501.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002501.html</a><br>
[5] <a href="https://review.openstack.org/#/q/project:openstack/governance+file:reference/technical-vision.rst" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/project:openstack/governance+file:reference/technical-vision.rst</a><br>
<br>
-- <br>
Chris Dent                       ٩◔̯◔۶           <a href="https://anticdent.org/" rel="noreferrer" target="_blank">https://anticdent.org/</a><br>
freenode: cdent                                         tw: @anticdent</blockquote></div></div></div>