[User-committee] User requirements feedback loop
Maish Saidel-Keesing
maishsk at maishsk.com
Mon May 11 10:52:31 UTC 2015
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?
There should be a defined way that this is fed back into the TC or the
project groups and how these requirements and items are made actionable
and placed on the relevant project's roadmap with a defined target date
(release).
Currently there are a number of groups that are collecting all sorts of
information - which is a great thing - but I am still missing the other
part of the equation.
So to go back to your North/South idea - perhaps also an east/west
segment - with a feedback loop also to the teams/TC/Foundation?
--
Best Regards,
Maish Saidel-Keesing
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20150511/4eed245a/attachment-0001.html>
More information about the User-committee
mailing list