[openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

Doug Hellmann doug at doughellmann.com
Mon Sep 12 18:17:19 UTC 2016


Excerpts from Thierry Carrez's message of 2016-09-12 08:53:58 +0200:
> Doug Hellmann wrote:
> > Excerpts from Jay Pipes's message of 2016-09-09 14:30:29 -0400:
> >>  > To me, this statement
> >>> about One OpenStack is about emphasizing those commonalities and
> >>> working together to increase them, with the combined goals of
> >>> improving the user and operator experience of using OpenStack and
> >>> improving our own experience of making it.
> >>
> >> +1000 to the above, and I don't believe anything about my stance that 
> >> OpenStack should be a cloud toolkit goes against that.
> >>
> >> The wording/philosophy that I disagree with is the "one product" thing :)
> > 
> > Tomato, tomato.
> > 
> > We're all, I think, looking at this "One OpenStack" principle from
> > different perspectives.  You say "a toolkit". I say "a project".
> > Thierry said "a product". The important word in all of those phrases
> > is "a" -- as in singular.
> 
> FWIW I agree with Jay that the wording "a product" is definitely
> outdated and does not represent the current reality. "Product"
> presupposes a level of integration that we never achieved, and which is,
> in my opinion, not desirable at this stage. I think that saying "a
> framework" would be more accurate today. Something like "OpenStack is
> one community with one common mission, producing one framework of
> collaborating components" would capture my thinking.
> 

>From the perspective of what we are delivering, I can go along with
either "toolkit" or "framework." Do those terms capture the spirit
of the original meaning, though, when considered from a governance
perspective? Aren't we trying to say that we're a single community,
too?

Doug



More information about the OpenStack-dev mailing list