[openstack-dev] [tc] persistently single-vendor projects

Flavio Percoco flavio at redhat.com
Tue Aug 2 14:36:28 UTC 2016

On 01/08/16 10:19 -0400, Sean Dague wrote:
>On 08/01/2016 09:58 AM, Davanum Srinivas wrote:
>> Thierry, Ben, Doug,
>> How can we distinguish between. "Project is doing the right thing, but
>> others are not joining" vs "Project is actively trying to keep people
>> out"?
>I think at some level, it's not really that different. If we treat them
>as different, everyone will always believe they did all the right
>things, but got no results. 3 cycles should be plenty of time to drop
>single entity contributions below 90%. That means prioritizing bugs /
>patches from outside groups (to drop below 90% on code commits),
>mentoring every outside member that provides feedback (to drop below 90%
>on reviews), shifting development resources towards mentoring / docs /
>on ramp exercises for others in the community (to drop below 90% on core
>Digging out of a single vendor status is hard, and requires making that
>your top priority. If teams aren't interested in putting that ahead of
>development work, that's fine, but that doesn't make it a sustainable
>OpenStack project.

++ to the above! I don't think they are that different either and we might not
need to differentiate them after all.


Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 847 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160802/525c5c83/attachment.pgp>

More information about the OpenStack-dev mailing list