Robert Collins wrote: > On 9 July 2013 20:12, Thierry Carrez <thie...@openstack.org > <mailto:thie...@openstack.org>> wrote: > > So - here is the draft: > > > > Official Title: OpenStack Deployment > > PTL: Robert Collins <robe...@robertcollins.net > <mailto:robe...@robertcollins.net> > > <mailto:robe...@robertcollins.net <mailto:robe...@robertcollins.net>>> > > Mission Statement: > > Develop and maintain the tooling and infrastructure needed to > > deploy OpenStack in production, using OpenStack itself wherever > > possible. > > Looks good. Personally I'd probably not say "needed to deploy OpenStack > in production", which sounds a bit exclusive: I'm not sure we want to > bless one deployment method and exclude others... Maybe something like > "...tooling and infrastructure able to deploy OpenStack in production at > scale, reusing OpenStack itself..." > > > > So tripleo scales down too, the same potential issue you raise with > excluding other deployment methodologies applies if we say 'at scale', > in reverse ;). > > How about >> Develop and maintain tooling and infrastructure able to >> deploy OpenStack in production, using OpenStack itself wherever >> possible. > > That is s/the// - removing the implication of a singleton, and > s/needed/able/
Yes, that works. -- Thierry Carrez (ttx) _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
