W3C home > Mailing lists > Public > public-css-testsuite@w3.org > April 2017

Re: Guidelines for editing the CSS testsuite with github

From: Chris Lilley <chris@w3.org>
Date: Wed, 12 Apr 2017 19:56:09 -0400
To: public-css-testsuite@w3.org
Message-ID: <ef78d59e-eb62-c381-40e4-7dd8a1ef075c@w3.org>
Gérard,

Saying to Geoffrey "When will the documentation on GitHub be updated and reliable? " is about as reasonable as my asking you "When will all the CSS tests be updated and reliable?". It is a community effort, and we all need to work together to improve things.

Technically, it is better to point out specific problems with documentation. Then there can be discussion, and once there is consensus on how to correct it, the documentation can be updated (by whomever gets around to it first).

Socially, please see https://www.w3.org/Consortium/cepc/

Both of you have contributed greatly to CSS testing. Look forward to continuing to work with both of you in the future.


On 2017-04-12 12:36, Geoffrey Sneddon wrote:
> On Tue, Apr 11, 2017 at 3:09 AM, Gérard Talbot
> <css21testsuite@gtalbot.org> wrote:
>> When will the documentation on GitHub be updated and reliable? 
> What specific documentation is out of date or unreliable?
>
> And yes, I know some of documentation is wrong, but all of it was
> wrong before the merge and merging it hasn't made it any more wrong,
> and I don't think it's reasonable to expect me to fix all the problems
> with documentation around the testsuite. The wiki, especially, mostly
> contains documentation that has been out of date for many years. If
> people believe the documentation is wrong and is causing problems,
> they should step up to fix it.

-- 
Chris Lilley
@svgeesus
Technical Director @ W3C
W3C Strategy Team, Core Web Design
W3C Architecture & Technology Team, Core Web & Media
Received on Wednesday, 12 April 2017 23:56:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 12 April 2017 23:56:24 UTC