3 ms·

Shouldn't the badge have a green checkmark to show everything's ok? Or is no maintenance intended supposed to imply your code is broken?

bArray 7y ago
Yeah I think it should at least not be red, indicating there is some problem.
- hcs 7y ago
  There probably will be a problem, though, and if it's unmaintained no one will be around to change the status, so it's more honest to leave it red for all time.
  - bArray 7y ago
    But that indicates that it's actively failing, even if one day old. To me it needs to say "this project is not actively tested", not that it's broken. Depending on how simple/self dependent it is, it might not ever really break.
tomxor 7y ago
Yes, there should be green AND red! maintenance comes in two flavors, it's absence can be a sign of good or bad, depending on the project: Very small projects given enough time can be cut almost perfectly up front, a few patches maybe then it's done. In this case lack of maintenance is a sign of stability and completeness. At the opposite end of the scale, in very large and _dynamic_ projects, maintenance is a continual necessity. Not only because of it's own scope being so large it's difficult to settle on a coherent, complete and bug free solution, but because of how it also interacts with many other changing external projects, in short these projects are an ecosystem - In this case lack of maintenance signifies death, instability, insecurity and abandonment. I find it particularly annoying when the latter is applied to projects fitting into the former category. Some package managers even auto-quantify package quality based on maintenance (release frequency) - looking at you NPM. Some other phrase should be used to clarify this, maybe: "No maintenance needed", although that sounds a bit unrealistic, the point is the lack of release churn doesn't mean it's broken.
- DougBTX 7y ago
  > Very small projects given enough time can be cut almost perfectly up front, a few patches maybe then it's done. Perhaps there needs to be a bigger distinction between "unchanging" and "unmaintained". In your example, a project could be unchanging simply because there is nothing to do, it is "done". But if a bug was found, would someone fix it? That's when maintained vs unmaintained would matter, perhaps it is only possible to know how well something is being maintained until problems are reported...
  - tomxor 7y ago
    Yes this is a better distinction, I suppose the problem is that inactivity tends to be equated with lack of maintenance - regardless of whether there are still people around that care but have nothing to do.
eMGm4D0zgUAVXc7 7y ago
The code for it is on GitHub, can someone please file an issue there to provide an additional green version? (Or fix it right away?) https://github.com/potch/unmaintained.tech/issues https://github.com/potch/unmaintained.tech/issues Thank you!
susam 7y ago
> Shouldn't the badge have a green checkmark to show everything's ok? Or is no maintenance intended supposed to imply your code is broken? Perhaps they can offer some way to customize the badge like Shields.IO does. For example, - https://img.shields.io/badge/Status-No%20Maintenance%20Intended-yellow https://img.shields.io/badge/Status-No%20Maintenance%20Inten... - https://img.shields.io/badge/Status-Actively%20Maintained-brightgreen https://img.shields.io/badge/Status-Actively%20Maintained-br... - https://img.shields.io/badge/Status-Obsolete%20Project-red https://img.shields.io/badge/Status-Obsolete%20Project-red - https://img.shields.io/badge/-No%20Maintenance%20Intended-yellow https://img.shields.io/badge/-No%20Maintenance%20Intended-ye... - https://img.shields.io/badge/-No%20Maintenance%20Intended-brightgreen https://img.shields.io/badge/-No%20Maintenance%20Intended-br...

bArray 7y ago

Yeah I think it should at least not be red, indicating there is some problem.

hcs 7y ago
There probably will be a problem, though, and if it's unmaintained no one will be around to change the status, so it's more honest to leave it red for all time.
- bArray 7y ago
  But that indicates that it's actively failing, even if one day old. To me it needs to say "this project is not actively tested", not that it's broken. Depending on how simple/self dependent it is, it might not ever really break.

tomxor 7y ago

Yes, there should be green AND red! maintenance comes in two flavors, it's absence can be a sign of good or bad, depending on the project: Very small projects given enough time can be cut almost perfectly up front, a few patches maybe then it's done. In this case lack of maintenance is a sign of stability and completeness. At the opposite end of the scale, in very large and _dynamic_ projects, maintenance is a continual necessity. Not only because of it's own scope being so large it's difficult to settle on a coherent, complete and bug free solution, but because of how it also interacts with many other changing external projects, in short these projects are an ecosystem - In this case lack of maintenance signifies death, instability, insecurity and abandonment. I find it particularly annoying when the latter is applied to projects fitting into the former category. Some package managers even auto-quantify package quality based on maintenance (release frequency) - looking at you NPM. Some other phrase should be used to clarify this, maybe: "No maintenance needed", although that sounds a bit unrealistic, the point is the lack of release churn doesn't mean it's broken.

DougBTX 7y ago
> Very small projects given enough time can be cut almost perfectly up front, a few patches maybe then it's done. Perhaps there needs to be a bigger distinction between "unchanging" and "unmaintained". In your example, a project could be unchanging simply because there is nothing to do, it is "done". But if a bug was found, would someone fix it? That's when maintained vs unmaintained would matter, perhaps it is only possible to know how well something is being maintained until problems are reported...
- tomxor 7y ago
  Yes this is a better distinction, I suppose the problem is that inactivity tends to be equated with lack of maintenance - regardless of whether there are still people around that care but have nothing to do.

eMGm4D0zgUAVXc7 7y ago

The code for it is on GitHub, can someone please file an issue there to provide an additional green version? (Or fix it right away?) https://github.com/potch/unmaintained.tech/issues https://github.com/potch/unmaintained.tech/issues Thank you!

susam 7y ago

> Shouldn't the badge have a green checkmark to show everything's ok? Or is no maintenance intended supposed to imply your code is broken? Perhaps they can offer some way to customize the badge like Shields.IO does. For example, - https://img.shields.io/badge/Status-No%20Maintenance%20Intended-yellow https://img.shields.io/badge/Status-No%20Maintenance%20Inten... - https://img.shields.io/badge/Status-Actively%20Maintained-brightgreen https://img.shields.io/badge/Status-Actively%20Maintained-br... - https://img.shields.io/badge/Status-Obsolete%20Project-red https://img.shields.io/badge/Status-Obsolete%20Project-red - https://img.shields.io/badge/-No%20Maintenance%20Intended-yellow https://img.shields.io/badge/-No%20Maintenance%20Intended-ye... - https://img.shields.io/badge/-No%20Maintenance%20Intended-brightgreen https://img.shields.io/badge/-No%20Maintenance%20Intended-br...