Nixpkgs: Issue stats badges on readme.md don't load anymore

Created on 19 Jul 2016 · 10Comments · Source: NixOS/nixpkgs

The "build: passing" badge works fine, but that comes from travis. The other two (that displayed stats about our PR merge rate and issue close rate) fail to load on all my devices.

Source

copumpkin

👍1

Most helpful comment

I don't know how useful these kind of badges are.. We have a lot of issues and pull requests that are left open for long periods of time. Some issues are addressed quickly but take a long time to resolve.

What would be really cool is if someone could make some badges that incorporate information from Hydra regarding the last evaluation.

matthewbauer on 20 Jul 2016

👍2

All 10 comments

Looks like http://www.issuestats.com/ is just down and has been for a couple of days? cc @jagajaga who I think originally added the stats badges.

copumpkin on 19 Jul 2016

Based on the issues on the repo of issuestats.com, they made it as part of a GitHub Data Challenge and don't really maintain it outside of accepting PRs. We could switch to isitmaintained.com but they don't have very nice things to say about us :) http://isitmaintained.com/project/nixos/nixpkgs

grahamc on 19 Jul 2016

👍1

Looking now, IssueStats says our issues are closed in 5 days (the second badge just loaded)

grahamc on 19 Jul 2016

What would be really cool is if someone could make some badges that incorporate information from Hydra regarding the last evaluation.

matthewbauer on 20 Jul 2016

👍2

These seem to be working again now, so I'm closing this. Agree with @matthewbauer's suggestion, but it's probably worth submitting a ticket against Hydra for that instead of putting it in a comment here.

copumpkin on 22 Jul 2016

We can probably remove this badge.

jagajaga on 24 Jul 2016

This weekend I made a readme-badge thing which shows: https://jsfiddle.net/45g501mw/ -- is that interesting enough to show on our readme? :) (I made it to examine the data, turns out we do pretty
good.) https://gist.github.com/grahamc/878017f8ce04d2f1a8404088c0214618

(specifically looking for a +1 / -1 @domenkozar or @edolstra )

grahamc on 25 Jul 2016

@grahamc how would we use that badge? Can we host the logic somewhere?

domenkozar on 25 Jul 2016

Here's where we are:

I've built the data collector
I have it running on a regular basis to update
I have the SVG output I want to make (linked above)
Next is to wire up the data to the SVG output over HTTP

I was planning on (and am currently) hosting it on my own, but I don't mind it running elsewhere. It requires a mysql database.

A couple notes:

our actual number is 56% merged in the first day.
I can come up with different data to output, if there are specific ideas.
@copumpkin mentioned showing a distribution of all the times, I can do this (see the linked gist above) but it'd be much bigger than the widget currently is :)

grahamc on 25 Jul 2016

The one existing badge at the moment seems to work just fine.