News for hackers. Stuff that matters.
Re:We now consider Moment.js to be a legacy project in maint... by 5h on Tuesday September 15, 2020 @04:31AM (#24479062)
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.
Re:We now consider Moment.js to be a legacy project in maint... by simongray on Tuesday September 15, 2020 @04:40AM (#24479112)
I think that is the point of the "archive" functionality: https://docs.github.com/en/github/creating-cloning-and-archi...
Re:We now consider Moment.js to be a legacy project in maint... by 5h on Tuesday September 15, 2020 @06:00AM (#24479539)
That's part of it, but doesn't give any useful data beyond 'archived' to make use of when considering your dependencies.
Re:We now consider Moment.js to be a legacy project in maint... by andrewnicolalde on Tuesday September 15, 2020 @03:59PM (#24486037)
What’s the value in that vs a small note in README.md or similar?
Re:We now consider Moment.js to be a legacy project in maint... by kedean on Tuesday September 15, 2020 @04:38PM (#24486431)
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.