Fork Freshness: Project lifespans in the Ruby ecosystem
gilesbowkett.com
Fork Freshness: Project lifespans in the Ruby ecosystem
1–10 of 38 posts
Re: Fork Freshness: Project lifespans in the Ruby ecosystem
#2Re: Fork Freshness: Project lifespans in the Ruby ecosystem
#3Re: Fork Freshness: Project lifespans in the Ruby ecosystem
#4Re: Fork Freshness: Project lifespans in the Ruby ecosystem
#5Any chance this could be made not to rely on Twitter?
Re: Fork Freshness: Project lifespans in the Ruby ecosystem
#6Is there a reason this requires a Twitter account? Seems like something I'd like to use but I don't have Twitter.
Re: Fork Freshness: Project lifespans in the Ruby ecosystem
#7I agree with other commenters; I really don't want to talk about my dependencies on twitter to this bot.
Re: Fork Freshness: Project lifespans in the Ruby ecosystem
#8Is there a reason this requires a Twitter account? Seems like something I'd like to use but I don't have Twitter.
That still doesn't explain the Twitter dependency. It could just be an attempt to get popular and share the tool at the same time.
Re: Fork Freshness: Project lifespans in the Ruby ecosystem
#9I ran across this site a few years ago and I've used it since then to find active forks: https://techgaun.github.io/active-forks/index.html
It would be great to know, for example, "commits ahead of". EDIT: found a few! [1] is easiest to use. For [2] you need to give it a github access token.
[1] https://stackoverflow.com/questions/54868988/how-to-determin...