Open Stack

Since there is some discussion going again, I thought I'd jump in since
I've talked to Sean 1:1 on this topic.

One way I could see this group adding value is to facilitate conversations
/ interviews / polls of top OpenStack users (the foundation is tracking
many of these already) and gather input on the key gaps they see in
different parts of OpenStack.  Then this could be presented in a session at
the Summit.  Stefano already does some of this in the state of openstack
polls (and maybe the operators group does to?) but I'm thinking of
something that could be guidance to the PTLs of what users actually want,
what should be prioritized.  It would be up to the PTLs / TC how to act on
this feedback.




On Thu, Dec 4, 2014 at 2:35 PM, Stefano Maffulli <stefano at openstack.org>
wrote:

> On 11/11/2014 03:44 PM, Roland Chan wrote:
> > In just saying that, some more big questions are raised:
> >
> >    - What are the goals of this group?
>
> I'll try pushing the ball forward. Thanks Roland for the assist.
>
> In my opinion, the goal of this group is to share resources and
> coordinate development efforts. A scenario I have in mind is:
>
>   - company A needs to have feature X merged in kilo
>   - company B needs to have bug Y fixed asap
>   - X and Y either collide or complement each other
>   - product owners of A and B can use this group to coordinate efforts,
> avoid conflict, share precious resources, prioritize reviewer's time, etc.
>
> There are other scenarios. We need to avoid getting towards the end of
> the release cycle and have product owners reallocate resources in a way
> that raises conflicts inside the community, creates inefficiencies. The
> Product team should be one place (among others) where synergies can emerge.
>
> >    - What strategy are we going to employ to achieve those goals?
>
> I'd start by looking at the list of priorities published by Nova and
> Neutron and make sure that your plans are not colliding:
>
> -
>
> http://specs.openstack.org/openstack/nova-specs/priorities/kilo-priorities.html
>
> -
>
> http://specs.openstack.org/openstack/neutron-specs/priorities/kilo-priorities.html
>
> If they collide ... let's talk about how to address them. At this stage
> I think communication is key. We floated around the idea to meet in
> person, although I'd suggest we start meeting regularly online before
> that. Anyone wants to volunteer to select a time slot and rally
> participants?
>
> >    - How do we gain acceptance from the wider community for this effort?
>
> What do you mean by 'wider community'?
>
> >       - How do we find an effective mechanism for product management to
> >       occur?
> >
> > and no doubt there are more.
>
> Let's get this straight: Product Management is already occurring in
> OpenStack. We've been shipping a functioning product for years, so
> product management per se is not the problem. I think we need now, given
> the size of OpenStack, a better way to coordinate the various
> conflicting commercial interests happening inside the ecosystem.
>
> I've put some initial thoughts on the team's wiki page but I don't like
> it myself. What do you think the mission of the group should be?
>
> From:  https://wiki.openstack.org/wiki/ProductTeam
>
>     Mission
>
>     The Product working group is made of managers, people, functions,
>     groups that own "products" based on OpenStack with the objective to
>     complete the circle of end users, operators, product owners,
>     developers.
>
> /stef
>
> _______________________________________________
> Product-wg mailing list
> Product-wg at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
>