V8 and WebRTC teams are interested in having their own code coverage dashboards, which makes sense, as they want to see coverage by only project specific tests (not including various Chromium tests e.g. content_unittests). A separate dashboard would also let them to see coverage before doing the roll into Chromium.

I see two ways:

1) make the dashboard source code customizable (i.e. move project specific constants and other files to a particular location / config file) + provide some tutorial

2) add support for other projects on the main dashboard

I'm leaning towards 1), as the 2) sounds less stable to me, plus I'd expect more contributions to the dashboard code if people will deploy and use it themselves.