Re: [dev][tc][ptl] Continuing Evaluating projects in relation to OpenStack cloud vision
Colleen Murphy
colleen at gazlene.net
Tue Mar 19 21:45:00 UTC 2019
On Fri, Feb 8, 2019, at 3:40 PM, Lance Bragstad wrote:
>
>
> On 2/8/19 7:15 AM, Chris Dent wrote:
> >
> > 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].
>
> Is it worth knowing which projects have this underway? If so, do we want
> to track that somewhere?
>
> Colleen started generating notes for keystone [0] and there is a plan to
> get it proposed for review to our contributor guide sometime before the
> the Summit [1].
>
> [0] https://etherpad.openstack.org/p/keystone-technical-vision-notes
> [1]
> http://eavesdrop.openstack.org/meetings/keystone/2019/keystone.2019-02-05-16.01.log.html#l-13
We've started the process of adding this reflection to the keystone contributor guide[1], we'd welcome feedback from the TC.
[1] https://review.openstack.org/641374
Colleen
>
> >
> > 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
> >
>
>
>
> Attachments:
> * signature.asc
More information about the openstack-discuss
mailing list