useful-forks.github.io VS lovely-forks

Here "branches" is for Git branches - or, rather, forks - of the emulator project. It means checking GitHub (or https://useful-forks.github.io/) to see if any individual developers have recently forked the project and made new commits. If so, you can try to build the updated project, and see how it goes.

Find alternatives or use useful fork

gorilla/mux is at least more battle-tested. I'd rather fork it myself, or evaluate a useful fork of it such as this one (if it seems well-maintained, I haven't done the leg-work).

An acquaintance of mine built this: https://github.com/useful-forks/useful-forks.github.io

>One problem is discoverability. GitHub lists forks in an un-sort-able manner.

This obviously doesn't solve the problem generally, but I recently found an extension called lovely-forks[1], that automatically shows the most starred fork for every github repository.

1:https://github.com/musically-ut/lovely-forks

The post resonates with me as an OSS user and a contributor. Many a brave souls have taken to forking the project to fix the bugs but those forked projects almost always suffer from a discoverability problem. I have tried making fixes and tried forking projects only to discover that someone else has done it better elsewhere.

I've been burned by this problem often enough that I wrote a Chrome extension which would _tell_ me if there are any notable forks of the project I'm currently looking at on GitHub: https://github.com/musically-ut/lovely-forks .

Lovely forks is a chrome add-on built to bring your notice to notable forks (i.e., forks with the most stars) for GitHub projects. It helps to keep track of the community-appreciated fork by adding a subscription under the repository's name on the Github page of all projects with a link to that fork.