You might consider a GitHub organization for coderay, coderay-scanner-tests and the coderay web site. It would make it easier to manage commit access to the repos.

@korny I put a repo over here https://github.com/coderay/coderay-scanner-tests, but feel free to "Transfer" it into your @rubychan organization if you prefer.

So we need a LICENSE file for each folder in the example code? That's probably going to be difficult to track down now. :-(

We could probably use Git Submodules to have the tests in a separate repo, while making it easy to (optionally) fetch them.

Problem is branches/versions.

Yeah, actually I didn't have a problem with new scanners, since the tests are just ignored if no scanner is found. But if you fix anything, and change the expected output, you can't get master and the fix-branch to pass on the same repo revision :(

Decision was to keep it simple, just use one master branch instead of Submodules.

Again, from the chat:

Okay, so let's try this :) We use a normal git clone/git co instead of svn up. New scanner tests can always be added, but need to be skipped if the scanner is not found. Fixes should also be added, and we accept that this can cause master to fail.