General purpose shields about shields HOT 4 CLOSED

Seems like an interesting idea, could you give me more details regarding the use case for this?

One potential issue I see is the fact that most (if not all) badges displayed on repositories involved automated third-party services. If someone has abandoned their repo, unless you can build a service able to detect that from activity metrics (which sites like The Ruby Toolbox do offer), then I worry these badges would quickly become disconnected with reality and untrustworthy.

Does that make sense?

from shields.

Yes, I was thinking about manual setup and no third party service involved. IMHO this is not the kind of information a static code analyzer could reliably detect, but your point makes sense.

from shields.

Most of these are covered by methods other than a badge, usually better and more accurately.

Dev/Prod/Release are all better covered by tag/branch systems (master/development branch setup is relatively commonplace)
Stable/Unstable is much better handled by testing and CI, and to a lesser extent the tag/branch systems in place.
Not that likely to see an abandoned/looking for contributors badge on a project if it's truly been abandoned. Stillmaintained could provide such functionality, though again if the project is truly and outright abandoned it's not as likely to see the abandoner return to place such a badge on the project. Probably the most viable of 'general purpose' shields, though I would rather see stillmaintained offer badges to accomplish such a thing to be more reliable.

from shields.

@nicoulaj closing this for the reasons outlined by @ackerdev and myself. No hard feelings. I like the ideas you surfaced for other types of services we could reach out to in the future. 😃

from shields.