I think PTLs would naturally like to have those updated, and for me a
TC +w would make sense.
But we need to have guidelines, so that's it's more tangible, and the
subtlety stays impartial.
__
OpenStack Development Mailing
Excerpts from Jean-Philippe Evrard's message of 2018-06-13 11:04:51 +0200:
> > - Drop tags, write a regular report instead that can account for the
> > subtlety of each situation (ttx). One issue here is that it's obviously a
> > lot more work than the current situation.
>
> That's what I'd
> - Drop tags, write a regular report instead that can account for the
> subtlety of each situation (ttx). One issue here is that it's obviously a
> lot more work than the current situation.
That's what I'd prefer personally.
We have a website with a nice project navigator now [1].
This is
On Tue, Jun 12, 2018 at 1:07 PM Thierry Carrez
wrote:
> Neil Jerram wrote:
> >> The issue is that the current method (which uses a formula to apply
> >>single-vendor and diverse-affiliation tags) is not working so well
> >>anymore, with lots of low-activity projects quickly flapping
On 12/06/18 11:44 +0200, Thierry Carrez wrote:
Hi!
We had a decently-sized thread on how to better track organizational
diversity, which I think would benefit from a summary.
The issue is that the current method (which uses a formula to apply
single-vendor and diverse-affiliation tags) is
Neil Jerram wrote:
The issue is that the current method (which uses a formula to apply
single-vendor and diverse-affiliation tags) is not working so well
anymore, with lots of low-activity projects quickly flapping between
states.
I think you need to explore and state much more
FWIW, as an outside observer of this conversation:
On Tue, Jun 12, 2018 at 10:46 AM Thierry Carrez
wrote:
>
> The issue is that the current method (which uses a formula to apply
> single-vendor and diverse-affiliation tags) is not working so well
> anymore, with lots of low-activity projects
Hi!
We had a decently-sized thread on how to better track organizational
diversity, which I think would benefit from a summary.
The issue is that the current method (which uses a formula to apply
single-vendor and diverse-affiliation tags) is not working so well
anymore, with lots of
