Team diversity tags (single-vendor and diverse-affiliation) no
longer provide useful context for our users:
- As projects mature and feature development activity is more
limited, a lot of projects were flapping between states
depending on a couple commits or reviews, cross-project work
or community goals activity.
- In teams where a single individual ends up picking up the bulk
of core reviewing duties, the diversity tags incentivized them
to limit their activity.
- Data was based on Stackalytics, which is not a highly reliable
data source. Basing tags on raw data is not a great idea. Raw
diversity data should be used to raise flags for further
analysis (with context) rather than jumping to conclusions.
- Binary tags can't reflect the complexity of that data.
Single-vendor does not mean the same for PowerVMStackers and
for Keystone. Trends are actually more important than value
at a single point in time.
- Organizational diversity is just one factor of fragility for
project teams. Individual fragility (where the bulk of the
work is done by one person) is actually more prevalent those
days.
Change-Id: I1f1e55a7605ddff572b7b674c58ab419a7fc913f
4d56baded8