Open Stack

On 07/30/2014 09:43 PM, Gauvain Pocentek wrote:
> Hi all,
> 
> We have to define a workflow to define and approve specs. Anne proposed
> the following on the HOT spec:
> 
> - approve the blueprint in Launchpad
> - then ask only some for docs-specs
> - then docs-specs is just used to ensure the approach and scope are what
> we want
> 
> Anne please correct me if I'm twisting your words :)
> 
> My opinion is that we should create the Launchpad BP only after a patch
> to docs-specs has been accepted. This would make sure that there's been
> some thinking about how things can be done, and that we agree on the
> choices.

Do we have a reference what other projects are doing? I'd like to use
the same workflow as much as possible.

I have no strong reference either way.

> My experience with the HOT spec shows that there's a lot of questions
> that need to be answered, and LP doesn't provide a simple way to
> discuss, modify, or keep the history of the spec definition --- which I
> think is important. And we're used to git and gerrit anyway :)
> 
> The HOT spec review for reference: https://review.openstack.org/#/c/108133/
> 
> What so you think?

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126