Re: Proposal to introduce test suite curators

> On Mar 4, 2017, at 00:33, Alan Stearns <stearns@adobe.com> wrote:
> 
> 
>> On Mar 2, 2017, at 11:51 PM, Florian Rivoal <florian@rivoal.net <mailto:florian@rivoal.net>> wrote:
>> 
>> I think it would be good if the curators were not just the editors (to avoid guessing what is in the spec instead of reading it), and it would be good to have implementers involved there, for the reason you say.
>> 
>> However, since we're generally facing a shortage of reviewers, I would say it should just be a preference when the chairs try and recruit curators rather than an absolute rule.
> 
> There is already a spot for a test coordinator on each test suite page:
> 
> https://test.csswg.org/suites/css-fonts-3_dev/nightly-unstable/ <https://test.csswg.org/suites/css-fonts-3_dev/nightly-unstable/>
> 
> This comes a proposal back in 2013 to have test suite owners. We did not get many volunteers, and assigning people to the role did not appear to spur more test suite development (as I recall).

This is not very discoverable: I did not know where to look, nor where I need to sign up to be listed there for the specs where I am actually reviewing tests.

Also, I do not think chairs (this generation or the previous) made a point of periodically calling out the missing positions and reaching out to member companies when specs that they are pushing lack test coordinators.

Maybe this would not make a difference, but it seems to me that identifying where we do (or do not) have people taking care of tests is just step one, and unless we use that list to work on filling the gaps, we haven't fully tried.

—Florian