does anyone know if this is eventually going to end up in jenkins, or do we need to write a plugin?

Let's write a plug-in. I wonder what it would take to do that.

i think looking at the claim plugin (https://wiki.jenkins-ci.org/display/JENKINS/Claim+plugin) and then going from there would be an easy approach, but first we'd need to come up with a list of features we want

Claim would be a good way to see how to add a new link into the UI for a new report. I've never used Claim.

Understanding how to work with JUnit might be gotten from looking at DistTest. I've never used DistTest.
DistTest Plugin — This plugin allows distribute JUnit tests to all slaves in a specified label for a project.

Better still LabeledTestGroupsPublisher might be real handy to label tests as Quarantined. I've never used LabeledTestGroupsPublisher.
LabeledTestGroupsPublisher Plugin — This plugin provides the functionality to group tests by types, such as "unit test", "smoke test", "regression test", etc.

It might be worth mentioning:
Test In Progress Plugin — This plugin allows you to see how the junit tests progress during a build.

Tell me, Samuel, do you know anything about getting a plugin hosted? Because I know nothing about that aspect.

i don't know anything about getting a plugin hosted, but should be easy enough to find out. my biggest problem right now is to get approval to spend time on writing the plugin during work hours...

ki82, do you think it would be appropriate to absorb this functionality in the claim plugin?

Hm. That's a thought. I haven't used claim. I have the impression that you claim a BUILD. But if it were married with Quarantine, then you could claim JUnit tests, or packages full of them. Or all the new failures in a build, or just check mark half of them.

I suppose that if the build only had one new commit, then you could automatically attribute failures to the commit owner.