Open Stack

On Fri, Apr 24, 2015 at 2:14 AM, Chris Dent <chdent at redhat.com> wrote:

>
> This might be a bit presumptuous, but why not give it a try...
>
> This cycle's TC elections didn't come with a set of prepackaged
> questions and though the self-nomination messages have included some
> very interesting stuff I think it would be useful to get answers
> from the candidates on at least one topical but open-ended
> question. Maybe other people have additional questions they think
> are important but this one is the one that matters to me and also
> captures the role that I wish the TC filled more strongly. Here's
> the preamble:
>
> There are lots of different ways to categorize the various
> stakeholders in the OpenStack community, no list is complete. For
> the sake of this question the people I'm concerned with are the
> developers, end-users and operators of OpenStack: the individuals
> who are actively involved with it on a daily basis. I'm intentionally
> leaving out things like "the downstream".
>
> There are many different ways to define "quality". For the sake of
> this question feel free to use whatever definition you like but take
> it as given that "quality" needs to be improved.
>
> Here's the question:
>
> What can and should the TC at large, and you specifically, do to ensure
> quality improves for the developers, end-users and operators of
> OpenStack as a full system, both as a project being developed and a
> product being used?


I think this can be broader still - "How can the TC herd cats" :-O

Jokes aside, OpenStack is an opensource project and it's not easy for
TC members or PTL's to "make developers do their bidding".

I'd like to think we at least need a better feedback loop from the user
survey
(or consumers of OpenStack in general) to what development actually
happens.
At the moment we have user feedback, but that doesn't always result in
developers doing exactly that. I think we need a number of tools for
PTLs and the TC be able to set priorities for particular "themes" OpenStack
wide.

1. I think the TC and PTLs need a place to say what the priorities are
    (that is visible to everyone).
2. Then follow up with assigning blueprints and bug priorities accordingly
3. Be open to saying no to work that is not within these "themes" if it is
creating
    a distraction.
4. recognition of work in these themes, perhaps on stackalytics (or else
where).

With some version of the above, we can hopefully get better at turning
user requests into solutions. (or "better quality").

Regards
Angus


>
>
> --
> Chris Dent tw:@anticdent freenode:cdent
> https://tank.peermore.com/tanks/cdent
>
> __________________________________________________________________________
> 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/20150424/63b4a3cf/attachment.html>