- From: James Graham <james@hoppipolla.co.uk>
- Date: Wed, 31 Jul 2013 18:30:55 +0100
- To: <public-test-infra@w3.org>
On 2013-07-31 14:12, Arthur Barstow wrote: > On 7/31/13 8:54 AM, ext Tobie Langel wrote: >> Hi folks, >> >> Turns out I need info like GitHub handle of the test coordinator for >> a spec, mailing list to send pull requests to for each spec, etc. >> >> I can either put all of this information along with the scripts I'm >> writing, or we can put it directly in the repository in each >> sub-directory. >> >> So for example, you'd have a manifest.json file in FileAPI/ which >> would contain the following info: >> >> { >> "test-coordinator": "KrisKrueger", >> "mailing-list": [ >> "public-webapps-testsuite@w3.org" >> ] >> } >> >> Thoughts? > > I tend to prefer what you describe above i.e. to distribute this info > in each toplevel directory (e.g. FileAPI/). That seems fine, but I wonder what you plan to use this for. I can't imagine all the subscribers to public-webapps-testsuite will want to get review spam for every webapps review, with no real way to silence it for reviews they aren't following.
Received on Wednesday, 31 July 2013 17:31:22 UTC