New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the ability for crate authors to add isitmaintained.com badges to their crate #705

Closed
carols10cents opened this Issue May 2, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@carols10cents
Member

carols10cents commented May 2, 2017

Part of RFC 1824, rust-lang/rust#41616.

isitmaintained.com provides badges indicating the time to resolution of GitHub issues and percentage of GitHub issues that are open.

We will enable maintainers to add these badges to their crate, in a similar way that the TravisCI/Appveyor/Gitlab badges are implemented today.

Also need to update the documentation that currently lives in cargo's repo.

Please let me know if you have any questions, potential implementers!

@nisargthakkar

This comment has been minimized.

Contributor

nisargthakkar commented May 13, 2017

Hey @carols10cents, I'd like to pick up this task

@carols10cents

This comment has been minimized.

Member

carols10cents commented May 13, 2017

Awesome!! I'm imagining that this would fit in to the existing system of CI badges-- take a look in these spots:

Please let me know if you have any questions at all!!!

@nisargthakkar

This comment has been minimized.

Contributor

nisargthakkar commented May 13, 2017

@carols10cents I was able to set up the badges correctly for isitmaintained (issue resolution and open issues), codecov and coveralls.
I'm not sure what to set the content when the mouse is hovered on it.

This is what I have set currently:
Is It Maintained average time to resolve an issue
Is It Maintained percentage of issues still open
CodeCov coverage status for the branch
Coveralls coverage status for the branch

The ones for isitmaintained do not feel right, though. It would be great if you could suggest some improvements

@carols10cents

This comment has been minimized.

Member

carols10cents commented May 13, 2017

They sound fine to me, what doesn't feel right about them?

@nisargthakkar

This comment has been minimized.

Contributor

nisargthakkar commented May 13, 2017

I think it would be better if there were some punctuations like
Is It Maintained: Average time to resolve an issue

Also in the previous comment, i messed up in markdown, the text for CodeCov and Coveralls was set to:
CodeCov coverage status for the <branch> branch
Coveralls coverage status for the <branch> branch

@carols10cents

This comment has been minimized.

Member

carols10cents commented Jun 1, 2017

Fixed by #726!! Thank you @nisargthakkar!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment