Re:Fork Freshness: Project lifespans in the Ruby ecosystem
by exciteabletom on Sunday October 24, 2021 @10:23PM
(#28983905)
This problem could be solved if Github simply sorted the list of forks by stars instead of alphabetically.
[ Parent
| on HN ]
Re:Fork Freshness: Project lifespans in the Ruby ecosystem
by zxcvbn4038 on Sunday October 24, 2021 @10:28PM
(#28983931)
More active repos don't necessarily have more stars, maybe a better way to sort would be to have main repo followed by number of commits ahead, then number of commits behind. Most often what I find is a repo will have 3-5 dozen forks and the vast majority will either be far behind or have one or two localizations. It is very rare that I find something that someone has really forked and started doing active development on.
Re:Fork Freshness: Project lifespans in the Ruby ecosystem
by trinovantes on Sunday October 24, 2021 @11:04PM
(#28984108)
I think sorting forks by most recent commit would good enough. Not sure why GitHub doesn't do more to help with discoverability
Re:Fork Freshness: Project lifespans in the Ruby ecosystem
by tessierashpool on Sunday October 24, 2021 @11:49PM
(#28984339)
I wholeheartedly agree with this. I think it's just a blind spot they have, although back in the day a GitHubber told me it was also about maintaining an agnostic approach to governance.
btw, iirc GitLab does give you the option of sorting by most recent commit.
Re:Fork Freshness: Project lifespans in the Ruby ecosystem
by oezi on Monday October 25, 2021 @02:09AM
(#28984901)
That is a good idea but they actually also should do:
- hide any repo that hasn't seen any commits
- show commits ahead and behind as well as number of tags
- include issue tracker activity
- highlight those forks that were renamed which is often an indicator of a new package/gem being released from this fork
- Show a link from the main page of a repository to the most active fork to make it clear that there is an active fork at all.