Open Stack

On 18/06/15 21:39, Steve Gordon wrote:
> ----- Original Message -----
>> From: "Carol L Barrett" <carol.l.barrett at intel.com>
>> To: user-committee at lists.openstack.org, product-wg at lists.openstack.org
>>
>> Hi All – As the Product Work Group and the User Committee were
>> getting ready for the Vancouver Summit we drafted the picture below
>> as a framework for work groups in the community. In the Product Work
>> Group (P-WG) sessions in Vancouver we used this framework and
>> received positive feedback.
>>
>> Now the question I have is: What is our next step to operationalize
>> this model?
>>
>> The P-WG is moving forward with a Pilot process for gathering use
>> cases, reviewing and prioritizing them to provide input to the
>> M-Design Summit. Based upon what we learn during this Pilot, we’ll
>> evolve and expand our areas of engagement. Ideally our Pilot would
>> include interacting with the User Committee or some of the other WGs
>> under their umbrella. Which is why I raise this question.
>>
>> Pls let me know what you think.
>> Thanks
>> Carol
> 
> From a Telco working group perspective we have been endeavoring to formalize our workflow here:
> 
>     https://review.openstack.org/#/c/178347/
> 
> Currently it's attuned to feeding into the relevant project(s) directly, at least where that is feasible (e.g. backlog specs for projects that support them where there is nobody in the WG with the technical chops to action, or real specs/bugs/etc. where there is). That's not to say that can't change, just highlighting what we have at the moment.
> 

Might be worthwhile to contact each of the working groups and teams to
find out where they're at and how to plug in.

Most of them have coordinates for contact on their wiki pages, however,
there are also a number of areas that sporadically gather but don't have
a ongoing presence which will be harder to engage with. There's a list
of both of these types at:

https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Working_Groups




Regards,


Tom