2 ms·
Do you remember how you looked for projects or even specific ones? I submitted pull request removing dead project and it was soon merged: https://github.com/up
by matkoniecz 5y ago
Do you remember how you looked for projects or even specific ones?
I submitted pull request removing dead project and it was soon merged: https://github.com/up-for-grabs/up-for-grabs.net/pull/2781 https://github.com/up-for-grabs/up-for-grabs.net/pull/2781
Also, they replied in https://github.com/up-for-grabs/up-for-grabs.net/issues/2536#issuecomment-869090795 https://github.com/up-for-grabs/up-for-grabs.net/issues/2536...
> We don't want to direct new contributors to the projects where they would feel lost or ignored. That gives a bad user experience due to which people tend to stop contributing to Open Source. I had same experiences so many times.
> Do you have a solution or suggestion for this? How should we tackle this.
> One way we can do this is to track the latest commit on the repo, but there could be a reason like the Repo is hard to work with and the Maintainers are reviewing PRs and Issues but there is nothing useful to be committed for a long time. This happens.
- fundamental 5y agoI just clicked around for a while seeing mostly dead repos IIRC. If you want assistance for reviewing the age of a load of repositories I was looking into a commit metric similar to what's mentioned in the github thread. Example output of my script (fetches repos, gets stats, dumps output): https://fundamental-code.com/mruby-timeline/ https://fundamental-code.com/mruby-timeline/ . From there it should be easy to prune short lived/old repos and then the rest of the process becomes somewhat more manual from there. EDIT: actually forget that, it looks like there's already a last-updated stat which seems to be in place, up-for-grabs seems to be fine with projects which don't have any activity for a few years based on their existing metric.