3 ms·
And then those GitHub issues get closed by stalebot a month later and the repo looks like it doesn't have many issues.
by Lord_Zero 2y ago
And then those GitHub issues get closed by stalebot a month later and the repo looks like it doesn't have many issues.
- kmarc 2y agoWhenever a new tool / library / plugin / whatever is evaluated by myself or my team, I spend some time on gathering some github issue / PR stats. I think this is now part of my "software engineering toolset" / best practices. If there are too many open PRs, or unresolved tickets, OR there are too many _new_ ones, I would rather start searching for something else
- klabb3 2y agoSame. I do a lot of research and try to get a sense of the person/team behind it and their values, vision, dedication, if they accept outside contributions, etc. A few years ago it became popular to document the project processes, but it all turned into generic code of conduct garbage and abstract governance pillars, as if they were writing a constitution. So looking at GitHub issues and commit history is still the best way. And very well invested time.
- dewey 2y agoDokku is actually the opposite of that. Super responsive, helpful and nice maintainer (Already mentioned by a few other people in this thread). I was so positively surprised that I got help so quickly after asking that I started to sponsor it via GitHub immediately.