[User-committee] User requirements feedback loop
Matt Van Winkle
mvanwink at rackspace.com
Mon May 11 15:12:10 UTC 2015
On 5/11/15 8:00 AM, "Maish Saidel-Keesing" <maishsk at maishsk.com> wrote:
>On 05/11/15 14:27, Tom Fifield wrote:
>> On 11/05/15 18:52, Maish Saidel-Keesing wrote:
>>> On 05/11/15 09:47, Tim Bell wrote:
>>>>
>>>>
>>>> Within the user committee, we¹ve been reviewing how the various teams
>>>> and working groups around operators, end users and ecosystem
>>>> developers could be structured. In particular, how we can turn the
>>>> ideas into actionable items and expand the activities given the growth
>>>> in the user community.
>>>>
>>>>
>>>>
>>>> In preparation for the summit, we would welcome feedback from those
>>>> interested in the user committee and product working groups on the
>>>> proposal below before wider circulation. The details are in
>>>> https://etherpad.openstack.org/p/uc-2015
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Tim, Jon, Subbu and Tom
>>>>
>>>>
>>>>
>>>>
>>>>
>>> Hi Tim, this looks like a great start.
>>>
>>> There is something that I am missing and perhaps there could be a way
>>>to
>>> pursue this further at the summit.
>>>
>>> Collecting requirements, from different segments - and then what?
>> Maish,
>>
>> Where is this lacking and what would you suggest to fix it?
>At the moment I am not aware (perhaps it is only me) of how this
>feedback is looped back into the teams.
To some degree, I think it exists, but I can say that's the big hurdle I
have left with large deployments - getting our wants, needs, issues, etc
into blueprints or code review comments. We are getting there - slowly -
but this is were we can really push the "feedback loop" as a group. It
will shake things up a bit as this opens the door for specs to come in
without developers assigned, but maybe we want that. :)
>
>How this can fixed?
>Regular meetings between the User committee and their respective groups
>to collect the info?
>Regular meetings with the User commitee and the TC/PTLs to get the
>feedback back into the projects and receive feedback on the work being
>done.
Not that I want to add more meetings to my plate, but I have been
wondering if there should be some regular sync between all the working
group leaders, the User Committee members and some potential other set of
folks. Mainly to make sure we are focusing on the big problems from all
the right perspectives are getting useful feedback on key features form
several groups. I'd also love to know what's working and what is not from
other groups.
>
>Someone of course needs to track this - and I think that a Project
>manager would be a perfect fit for this. Where that project manager
>comes from - is of course the question.
1,2,3 - not it! :) I agree, though, someone needs to keep us all inline.
We are a rowdy bunch. ;)
>>
>> Regards,
>>
>>
>> Tom
>>
>--
>Best Regards,
>Maish Saidel-Keesing
>
>_______________________________________________
>User-committee mailing list
>User-committee at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
More information about the User-committee
mailing list