Live data from Hacker News

Fork Freshness: Project lifespans in the Ruby ecosystem

gilesbowkett.com

1–10 of 38 posts

Re: Fork Freshness: Project lifespans in the Ruby ecosystem

#7
Fork Freshness is poking at an important problem. If the author of an open source project stops responding, then there is usually no obvious way for the project's community to reorganize or recognize a new leader or a replacement for the project.

I 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

#8
post #2

Is there a reason this requires a Twitter account? Seems like something I'd like to use but I don't have Twitter.

The author says it's too slow and works better as an asynchronous request. They also write something about rails' "User" object being unwieldy, whatever that is.

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

#9

I 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

Nice. I wonder whether the posted tool offers any more data since this tool is instantaneous and the posted one is slow.

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...

[2] https://github.com/dragongling/Better-Github-Forks

Post reply on HN