4 ms·

Github having an objective "This isn't being worked on anymore" flag with a few options as to why, and pointers for where to reach a community for support/discu

by 5h 6y ago

Github having an objective "This isn't being worked on anymore" flag with a few options as to why, and pointers for where to reach a community for support/discussion would be most useful, especially overlaid on the crazy huge dependency graph frontend projects tend to acquire.

simongray 6y ago
I think that is the point of the "archive" functionality: https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-archiving-repositories https://docs.github.com/en/github/creating-cloning-and-archi...
- 5h 6y ago
  That's part of it, but doesn't give any useful data beyond 'archived' to make use of when considering your dependencies.
andrewnicolalde 6y ago
What’s the value in that vs a small note in README.md or similar?
- kedean 6y ago
  Well, it would be more obvious. Right now, one of the first things the eyes are drawn to on a repository is the date of the last commit. I know I'm I have an internal bias against projects as soon as I see "Feb 23, 2016" as the last commit, it can make me stop scrolling without thinking about it. It would be nice to have a badge that is more obvious than the last commit date to supercede that.
  - barry27 6y ago
    Sure, or it could just not be used by people who subscribe to this silly notion that the last commit has to have been 5 minutes ago.