Open Stack

The purpose of coordination across SIGs is threefold:

1.       Having a single priority list for projects

2.       Having coordinated priority (and people) of a requirement across projects

a.       Having work done in one project but not others that is required for functionality does not deliver anything to a user

3.       Having a coordinated longer term roadmap

As Leong stated, PWG shrinkage does not allowed us to deliver on it.

Thanks,
Arkady

From: Yih Leong, Sun. [mailto:yihleong at gmail.com]
Sent: Tuesday, September 26, 2017 1:03 PM
To: openstack-sigs at lists.openstack.org
Subject: Re: [Openstack-sigs] [openstack-sigs][meta] requirements process questions



On Tue, Sep 26, 2017 at 10:47 AM, Chris Dent <cdent+os at anticdent.org<mailto:cdent+os at anticdent.org>> wrote:
On Tue, 26 Sep 2017, Doug Hellmann wrote:
Excerpts from Thierry Carrez's message of 2017-09-26 17:10:43 +0100:
That sounds like a good idea. That said, one of the goals behind SIGs is
that they are open to developer types as much as operator types, and
therefore can be used as a vehicle to combine developer resources from
like-minded organizations around a given topic. The SIG can come up with
a common priority list and have all those "internal" development
resources working together in implementing those priorities. If that's
successful, there might not be as much need for external coordination
and priority exposure.

This is the similar concept in Product WG when it was first established, however, this model doesn't seems to pick up over the past two years especially with the lack of resource/developer commitment from organizations. I am hoping that shifting to SIG model can change the course to drive prioritize implementation.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20170927/987fc1b2/attachment-0001.html>