Open Stack

So Thierry I agree. Developers are required to make it happen. I would say
however that acknowledging the importance of developer contributions and
selecting leadership from the development community is really half the
battle as it's pretty rare to see project teams led and governed by only
developers. I think addressing the inclusion of architects/operators/admins
within this committee is a hugely positive development.

I also liked your suggestions earlier about potential ways to implement.
On May 4, 2015 9:31 AM, "Thierry Carrez" <thierry at openstack.org> wrote:

> Maish Saidel-Keesing wrote:
> > A three point triangle. I like the idea! Anita I assume that you are
> > talking about the TC[3], the board [1] and the user committee [2].
> >
> > I honestly do not see this at the moment as an equally weighted triangle.
> > Should they be? Perhaps not, maybe yes.
> >
> > It could be that my view of things is skew, but here it is.
> >
> > The way to get something into OpenStack is through code.
> > Who submits the code? Developers.
> > Who approves code? Reviewers and core
> > On top of that you have the PTL
> > Above the PTL - you have the TC. They decide what is added into
> > OpenStack and (are supposed) drive overall direction.
> >
> > These are the people that have actionable influence into what goes into
> > the products.
> >
> > AFAIK neither the Foundation - nor the User committee have any
> > actionable influence into what goes into the products, what items are
> > prioritized and what is dropped.
>
> That's simply acknowledging the mechanics of an open source / open
> innovation project like OpenStack. Having the Board or the User
> committee decide "what goes into the products, what items are
> prioritized and what is dropped" won't make it magically happen. At the
> end of the day, you need a contributor willing to write, review,
> prioritize that code.
>
> The contributors to an open source project ultimately make things go in
> the open source project. They can be (and should be) influenced by
> outside input, especially users of the project. Companies can influence
> what is being worked on by funding developers to work on specific
> things. But in the end, it all boils down to contributors that get the
> work done and therefore make it going in one direction or another.
>
> --
> Thierry Carrez (ttx)
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150504/12b7f241/attachment.html>