uncurled VS lovely-forks

Start from the top:

https://un.curl.dev/

Some more discussion in the last year:

https://news.ycombinator.com/item?id=34981518

I think the better submission link is

https://un.curl.dev/

Linking to the git repo for the book source, it's not immediately apparent how to begin reading.

Look like it's easier to read from there: https://un.curl.dev/

Daniel Stenberg, the lead maintainer of cURL, has some interesting tweets about this topic. In fact several of the toxic comments he posts are from people who seem to lack a basic understanding of what the project even provides.

https://twitter.com/bagder/status/1561459354431275009

https://twitter.com/bagder/status/1535188747427405824

Just to provide some counterbalance there's also this: https://twitter.com/bagder/status/1552414274101940225

He has an interesting guide on his thoughts on maintaining open-source as well. Here's the People section: https://github.com/bagder/uncurled/blob/main/people/

The GitBook / eBook by Daniel Stenberg (creator of cURL) can be found at https://un.curl.dev and on GitHub at https://github.com/bagder/uncurled includes tips on people, community building, project management, monetization, and much much more.

Uncurled is a great resource for OSS maintainers by Daniel Stenberg and includes tips on community building and monetization. Source is on GitHub: https://github.com/bagder/uncurled

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