RE: webappsec tests moved to GitHub

[Keeping this thread on public-test-infra.]

Quoting Brad Hill:
> A couple questions here:
>
> 1) Where do I get an intro on how to use this in the w3c context?
> How do I create an account, etc.?

You can simply create a github account if you don't have one yet. New 
submissions are handled by forking the repository, pushing to your own 
fork, and submitting a pull request.

> 2) Who manages these repositories?  This doesn't do us any good if it
> takes the same or longer for commits to get approved.  Can a group
> set its own set of reviewers/approvers?  How?

They can be merged as soon as someone reviewed them. Most likely that 
will be members of your WG. Reviews can happen on github or using James' 
installation of Opera Critic [1], at the discretion of reviewers and 
submitters.

The bottleneck here remains people doing the actual review work. 
However, even if reviews come in no faster than they have before, you 
still benefit from lowering the barrier of entry to non-WG-members, and 
from the tools that are written for the common repository.

> 3) How are these repositories reflected back to the official test
> site at w3c-test.org?

Pull requests are mirrored on w3c-test.org under submissions [2] 
(automatically if the submitter is trusted; after a 'w3c-test:mirror' 
comment if not). Once the pull request is merged into master, the files 
will also be mirrored there [3].

HTH
Ms2ger

[1] http://critic.hoppipolla.co.uk/
[2] http://w3c-test.org/web-platform-tests/submissions/
[2] http://w3c-test.org/web-platform-tests/master/

Received on Friday, 7 June 2013 09:54:35 UTC