Open Stack

Arkady,

I've made changes based on your comments. And I also have some responses.

Regarding "What do we mean coordinate overlap?"
I was thinking of cases where two or more working groups (etc.) or two or more Development Proposals might be addressing some of the same things.  My thought was that the PWG could recognize that and help to bring the parties together in order to strengthen the objectives of both. I've changed "overlaps" to "synergies" in hopes that will better reflect the idea.

Regarding "Periodic coordination/collaboration across WGs/Product Managers"
The idea there was that we could (hopefully) begin doing that. 

Regarding "Work to inject User Priorities into the OpenStack Roadmap"
The reason I put that in under Multi-release Roadmap was because of discussion that we had in the March mid-cycle. We were exploring how, instead of only pulling information from projects regarding what they're planning in a release, we might also push some information back,  leveraging data from the User Survey and/or other sources, to provide user feedback to project teams in order to influence roadmap.  For that reason I'm inclined to want to keep it. Let's see what others think.

-Andy

Andrew Ukasick
Principal Systems Engineer
AT&T Integrated Cloud (AIC),  Openstack Community Coordination

From: Arkady.Kanevsky at dell.com [mailto:Arkady.Kanevsky at dell.com] 
Sent: Wednesday, June 21, 2017 11:45 AM
To: UKASICK, ANDREW <au3678 at att.com>; user-committee at lists.openstack.org
Subject: [Product] review of PWG slide deck

https://docs.google.com/presentation/d/1FWuIModYuIxNOYFne7y-yfF70UDKOMQ2JEUeEwTtt20/edit?usp=sharing

Andy,
First, great slides. Thanks for creating them.

A few comments.
Slide 1 - agree with all statements but one
* Lack of process or governance to prioritize Development Proposals and/or identify Community priorities/goals for each release
In PWG we do have a process. We actually put all proposals to vote on which ones we will drive per release. The real problem is lack of resources to drive them.
We can barely drive 3 proposal thru community. And users demand much more than that.
We do not have any real data how successful we are on driving proposals thru development projects.

The only real thing we were successful is roadmap creation and maintenance. 

Slide 8 - 
* Gather data/requirements from other working groups; coordinate overlaps
Other -> all user/operator WG
What do we mean coordinate overlap? The more people involved in development proposal the stronger it will be. And more people voting it to prioritize it for driving thru TC and PTLs.
* Periodic coordination/collaboration across WGs/Product Managers.
We do not do that too well after initial engagement on getting proposal gaps into various projects.

* Work to inject User Priorities into the OpenStack Roadmap
Not sure if we need this as a separate goal. That comes out of previous major goal: Development Proposal Planning, Prioritization, and Development


Thanks,
Arkady Kanevsky, Ph.D.
Director of SW Development
Dell EMC CPSD
Dell Inc. One Dell Way, MS PS2-91
Round Rock, TX 78682, USA
Phone: 512 723 5264