OpenStack Kilo Product Management Midcycle, Doorway to a Greater Understanding

Look to the previous post for background on OpenStack Product Management

OpenStack is a very active community. Bursts of change happen quite often and it can be difficult to keep up if you are not immersed. We need manage the flow of critical information and decision making just like any other engineering organization. The people that represent the Product Management of OpenStack are a critical group within the community. The next OpenStack Product Management meeting is scheduled to happen 26-27 January 2015 at VMware, Creekside A, 900 Arastradero Road, Palo Alto, CA, 94304. Directions to VMware Palo Alto are here.
Anyone interested in participating can RSVP here.

There are many things to discuss. We have pulled a few important topics from the summit forward into this list. Some new issues to discuss, have bubbled to the top. The best topics are going to be about something we can do something about. e.g. Focusing more developers on a key blueprint for Kilo release, Major changes to the way the TC deals with projects. We have hour and half time slots for five major topics and one two hour breakout session. Let’s fine tune this list down to the five must important.

(Randy Bias) establish a process by which longer term vision and product direction can emerge from within the community, http://lists.openstack.org/pipermail/product-wg/2014-December/000051.html.
(Sean Roberts) Neutron services split https://github.com/openstack/neutron-specs/blob/master/specs/kilo/services-split.rst
(Sean Roberts) Tagging approach to project maturity, http://ttx.re/the-way-forward.html, TC spec https://review.openstack.org/#/c/138504/5/resolutions/20141202-project-structure-reform-spec.rst
(Sean Roberts) defcore and refstack. havana capabilities and designated sections are set. What does this mean? What’s in store for icehouse and beyond?
(Stefano Maffulli) discuss https://review.openstack.org/#/c/96149/
(Steve Gordon) it seems that there is still a lot of concern/confusion around the Neutron services split out and also the broader changes to governance currently being proposed/implemented.
(Rocky Gruber) Crossproject specs and efforts this cycle
Logging rationalization efforts/direction including https://review.openstack.org/#/c/132552/
OS profiler including https://review.openstack.org/#/c/134839/
(Arkady Kanevsky) Tempest and Grenade as deployment/upgrade validation tool
(Sean Roberts) 2-3 year architecture / use case strategy. Win the Enterprise is doing parts of this. https://wiki.openstack.org/wiki/Win_the_Enterprise. Each project has its own vision for the future. This group should debate the current state of binding use cases to development plans on a ongoing basis.