This draft looks really good. I left a few comments on the etherpad. Excerpts from Jimmy McArthur's message of 2017-10-05 10:33:48 -0500: > Sorry for the Google Docs link btw. That's where Petr and I were > initially collaborating. I've moved this back to the etherpad referenced > in ttps://etherpad.openstack.org/p/docs-i18n-ptg-queens > <https://etherpad.openstack.org/p/docs-i18n-ptg-queens> > > https://etherpad.openstack.org/p/docs-i18n-ptg-queens-mission-statement > > > Jimmy McArthur <mailto:ji...@openstack.org> > > October 4, 2017 at 1:18 PM > > > > > >> Emilien Macchi <mailto:emil...@redhat.com> > >> October 4, 2017 at 12:35 PM > >> > >> The draft is really good! It reflects very well what we said we would > >> do at the PTG, way to go. > >> > >> I think the next steps would be: > >> - Definition of Done, or how you consider something achieved (code > >> merged, doc published, etc). > >> - Metrics: what metrics do you use to measure what you're delivering. > > For the DoD and Metrics our understanding of the task was that they > > should be built into the Evidence of Success, though I think we could > > still use some more specific metrics in certain spots. Emilien, would > > you suggest we define these as separate line items as well? > > > > Thanks! > > Jimmy > >> - What do you expect by end of Queens (put some number in metrics is > >> probably a good start) - it's already mentioned in your draft vision > >> but it might be revisited once you define the 2 previous items. > >> > >> Good work! > >> Jimmy McArthur <mailto:ji...@openstack.org> > >> October 4, 2017 at 10:46 AM > >> I've made a bit of progress on the collaborative vision for the Docs > >> team: > >> https://docs.google.com/document/d/1Xy78CnmnKlQ7SbR1XewqgrUdGe7DqnKAGYw_9aj5Ndg/edit# > >> > >> > >> > >> This still needs plenty of work, but I wanted to put out what we have > >> so we can start to get some feedback from other members of the Docs > >> team. The Use Cases section in particular was really vast and hard to > >> cut down into prose without getting too detailed. > >> > >> Welcome your feedback and input! > >> > >> Thanks, > >> Jimmy > >> > >> > >> > >> __________________________________________________________________________ > >> > >> 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 > > Emilien Macchi <mailto:emil...@redhat.com> > > October 4, 2017 at 12:35 PM > > > > The draft is really good! It reflects very well what we said we would > > do at the PTG, way to go. > > > > I think the next steps would be: > > - Definition of Done, or how you consider something achieved (code > > merged, doc published, etc). > > - Metrics: what metrics do you use to measure what you're delivering. > > - What do you expect by end of Queens (put some number in metrics is > > probably a good start) - it's already mentioned in your draft vision > > but it might be revisited once you define the 2 previous items. > > > > Good work! > > Jimmy McArthur <mailto:ji...@openstack.org> > > October 4, 2017 at 10:46 AM > > I've made a bit of progress on the collaborative vision for the Docs > > team: > > https://docs.google.com/document/d/1Xy78CnmnKlQ7SbR1XewqgrUdGe7DqnKAGYw_9aj5Ndg/edit# > > > > > > > > This still needs plenty of work, but I wanted to put out what we have > > so we can start to get some feedback from other members of the Docs > > team. The Use Cases section in particular was really vast and hard to > > cut down into prose without getting too detailed. > > > > Welcome your feedback and input! > > > > Thanks, > > Jimmy > > > > > > > > __________________________________________________________________________ > > > > 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
