Yesterday at the TC meeting [1] we decided that the in-progress task
to make sure the technical vision document [2] has been fully
evaluated by project teams needs a bit more time, so this message is
being produced as a reminder.

Back in January Julia produced a message [3] suggesting that each
project consider producing a document where they compare their
current state with an idealized state if they were in complete
alignment with the vision. There were two hoped for outcomes:

* A useful in-project document that could help guide future
   development.
* Patches to the vision document to clarify or correct the vision
   where it is discovered to be not quite right.

A few projects have started that process (see, for example,
melwitt's recent message for some links [4]) resulting in some good
plans as well as some improvements to the vision document [5].

In the future the TC would like to use the vision document to help
evaluate projects applying to be "official" as well as determining
if projects are "healthy". As such it is important that the document
be constantly evolving toward whatever "correct" means. The process
described in Julia's message [3] is a useful to make it so. Please
check it out.

Thanks.

[1] http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-02-07-14.00.html
[2] https://governance.openstack.org/tc/reference/technical-vision.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001417.html
[4] http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002501.html
[5] https://review.openstack.org/#/q/project:openstack/governance+file:reference/technical-vision.rst

--
Chris Dent                       ٩◔̯◔۶           https://anticdent.org/
freenode: cdent                                         tw: @anticdent