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

Davanum Srinivas davanum at gmail.com
Mon Aug 1 14:28:34 UTC 2016


So we will programatically test the metrics (if we are not doing that
already) to apply/remove "team:single-vendor" tag:


And trigger exit when the tag is present for more than 3 cycles in a
row (say as of release date?)

-- Dims

On Mon, Aug 1, 2016 at 10:19 AM, Sean Dague <sean at dague.net> 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
> team).
> 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.
>         -Sean
> --
> Sean Dague
> http://dague.net
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Davanum Srinivas :: https://twitter.com/dims

More information about the OpenStack-dev mailing list