3 ms·
> One of the great things about open source is that if an open source project with a permissive license does become inactive, it can be forked seamlessly. Somet
by Aurornis 3y ago
> One of the great things about open source is that if an open source project with a permissive license does become inactive, it can be forked seamlessly. Sometimes the fork can become even better than the original project, which is great for everyone! But in my experience, it’s instead used as a threat. And it’s the maintainer’s fault for creating a reason for a fork to be made and fragment the development community.
I understand the pressure open source maintainers are under (having been there myself), but the general advice has always been to fork a project if the maintainers can't or won't integrate PRs and fixes that you need.
If we can't ask questions about the repo's status, the backlog of legitimate PRs is growing without response, and even forking the project is considered hostile, that leaves no real options.
If someone wants to publish something to GitHub with expectations like this, it's better IMO to advertise them at the top of the README.md. Or better yet, don't publish a project to GitHub if you don't want to have to read GitHub issues and you don't want anyone forking your work.
> The best-case scenario for asking if an open source project is dead is that you annoy the maintainers and delay development. The worst-case scenario is that you give the maintainers an opportunity to reconsider if continuing to work on the open source project is worth it.
This is remarkably cynical. I've seen many GitHub issues asking about the status of a project that turned into constructive discussions about adding more maintainers, collaborating on future work, or coordinating a newly-maintained fork with an updated link in the README.md.
To say that the outcome can only possibly be negative or that spending 60 seconds responding to a couple legitimate GitHub questions (I checked, the repo has had 3 new issues in 2023) will significantly "delay development" is really negative.
If such simple communications are causing the developer to publish long rants on their blog and consider withdrawal from open source completely, I think there's something deeper going on. This long rant in response to a single legitimate GitHub question is more than the typical open source maintainer frustration.