CSS test GitHub repo strategy for TestTWF Shenzhen

Hey Peter,

I wanted to give you a heads up that we're going to modify our GitHub CSS test submission process for the upcoming event in Shenzhen.

The plan + workflow for Shenzhen is this:

 *   Fork the w3c/csswg-test repo into the testthewebforward account [1]
 *   Have attendees fork this repo and do PRs there
 *   Merge approved PRs directly into the testthewebforward/csswg-test forked repo during the event
 *   Send one PR from this repo back to w3c/csswg-test at the end of the event.

This solves a number of problems that caused pain during & after the Tokyo and Shanghai events:

 *   Doing hg-git merges take a fair amount longer than a straight merge into the GH repo -- very long when multiplied by many PRs. If you recall, you and I had a difficult time keeping up with them in Tokyo and I worked on them for several days afterward. The Shanghai PRs have also been time-consuming.
 *   Because of the time lag in the hg-git merge process, it took many minutes (up to 30) for people's merged files to show up in the GH repo. This was because they had to do a round trip out to Mercurial and back and often waited in a queue in the middle when the PRs stacked up.  This was confusing to people - even the experts.
 *   The experts at the event can be Collaborators on the forked repo so they can merge as they approve (asking them to do the required 3-4 hour setup for hg-git to learn the steps is unreasonable). I selfishly want to delegate here so I don't have to be a merge monkey during the event. My time will be better spent helping people write tests & reviewing them.
 *   We can use the Issue Tracker in the testthewebforward fork during the event. We've tried several ways to list what tests people can write including google docs, txt files in Dropbox, readme's in the repo, whiteboards, etc.  All were flawed for obvious reasons, but mostly because it wasn't easy to tell who was doing what and what was already done. We've gotten lots of feedback on this and people were rightfully frustrated. The GH issue tracker, labels, and assignments solve all of this for us. My colleague Mihai Balan has started a similar dialog with you about this in a broader context, and in that thread I proposed we do this mini GitHub experiment during the Shenzhen event to test it out [2].

I'm also wondering if there is anything you're working on that we might be able to leverage or if any of this impacts what you have planned?

Thanks,
-Rebecca

[1] https://github.com/testthewebforward
[2] http://lists.w3.org/Archives/Public/public-css-testsuite/2013Sep/0014.html