Open Stack

We can define the diagrams together at the summit during the two sessions. Writing it up in Etherpad was a technical challenge :-)

I plan to be at the 15h40 meeting (assuming previous meetings finish earlier) and I'll see who else from the user committee can be available.

Tim

> -----Original Message-----
> From: Barrett, Carol L [mailto:carol.l.barrett at intel.com]
> Sent: 11 May 2015 17:11
> To: maishsk+openstack at maishsk.com; user-committee at lists.openstack.org
> Subject: Re: [User-committee] User requirements feedback loop
> 
> I found it a bit tough to follow the flow in the diagram at the link, but think I got
> the gist of it from the text.
> 
> I like the approach of having the Product Work group, be the collector of the
> input from the User Committee and other community work groups. I think it
> would be valuable for us to have some type of common format to make it
> identify commonalties and exchange use cases or user stories amongst the work
> groups as well as with the PTLs and developers.
> 
> The Product Work Group has drafted a process flow for taking user stories and
> working with PTLs to create a roadmap and development priorities. There is a
> cross Work Group/Project working session planned for Monday 5/18 at 3:40 in
> Room 212 to discuss and improve this draft and have invited all interested
> community and work group members to join. This, plus the User Committee
> meeting, give us good opportunities to further discussion next week in
> Vancouver.
> 
> Carol
> 
> -----Original Message-----
> From: Maish Saidel-Keesing [mailto:maishsk at maishsk.com]
> Sent: Monday, May 11, 2015 6:00 AM
> To: user-committee at lists.openstack.org
> Subject: Re: [User-committee] User requirements feedback loop
> 
> 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.
> 
> 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.
> 
> 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.
> >
> > 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
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee