How do you tell if a project is maintained? Is it commit activity release activity the rate at which maintainers respond to issues and PRs or a combination of that?
We're a place where coders share, stay up-to-date and grow their careers.
How do you tell if a project is maintained? Is it commit activity release activity the rate at which maintainers respond to issues and PRs or a combination of that?
Antonin Januska -
Sm0ke -
Shubham Battoo -
Michelle Mannering -
Discussion (9)
The way I see it, it depends on what a "maintained" project looks like for you. For me it means there is a team is actively accepting new Pull Requests from other developers. There's also activity in the bug tracker and constructive comments on PRs. I consider specially important that the maintainers are currently accepting contributions. These mean that there's a community around it that still cares about the development of the software.
Some people are OK with one or two developers working on it on and off for the last few years. I would not base a commercial project on this, but it can be OK for small experiments or personal projects.
I usually look at commit activity, build status, release and PR activity.
Does build status really apply though? I see many really maintained and popular projects with failing build statuses. Also by PR activity, are you talking about stale/no response on PRs?
I guess build status doesn't really imply maintained, but if it's passing builds I know it's actively maintained.
Stale PRs is for sure a big indicator, but I think more important is PR's that are merged, as well as commits.
if maintainers respond to issues, and if it is archived
I just look at the year of the last commit
When a project is stable it doesn't mean it is no longer maintained. When there are bugs which aren't being addressed for a longer period, then a project is no longer maintained.
I've seen plenty really stable projects which did not get a commit in years, for which then a bug is found and fixed within a couple of days.
Old does not mean broken. For example zlib, last release was 4 years ago.
Just the year? What about month? I find projects that haven't had a commit in the last month or so are usually unmaintained.
I think it depends on the size of the project. I don't really know but when I see that it's got a commit in the last couple of months it's probably maintained. But if it's a big project, then obviously a couple of months might mean it's dead.