5 ms·
Updating docs or dependencies is part of maintaining a project. If no new features are needed the author doesn't need to do more. As a user it still shows me th
by mtmail 7y ago
Updating docs or dependencies is part of maintaining a project. If no new features are needed the author doesn't need to do more. As a user it still shows me the maintainer is alive, uses a computer and does open source work. I have 5+ such projects. For some I wouldn't even update the dependencies but I get automated messages about security issues with dependencies so of course I'm interested it fixing that.
> many great projects have their last commit a year ago for example but everyone knows it's maintained
How does everyone know?
- generalpass 7y ago> How does everyone know? I think one year is not out of the actively maintained zone for a mature project, but that >18-month zone is problematic. Also the number and type of issues. I was just yesterday looking at such a Schrodinger's project and wishing I had a way to determine if it was still maintained.
- craftoman 7y agoExactly. I have never experienced problems caused by outdated stuff with code less than a year since the last update. Edit: People ALWAYS fix things when something outdated breaks the whole project.
- craftoman 7y agoNo it's not part of maintaining a project if you clearly trying to manipulate things. I'm talking about the smart kids who take advantage of this and they update a bunch of words in some document that no one ever cared about.
- craftoman 7y ago> How does everyone know? I personally added some badges to all of my projects that inform the user if I abandoned the project and besides that, if a new feature from let's say Java is lunched and start breaking a project then why don't people raise an issue? It's not a PR and can be done in a few seconds. I'm sure someone will notice especially if a project is maintained by a handful of people.
- generalpass 7y agoYou should get some sort of special bonus Internet points for this.