2 ms·
In my experience, bureaucracy is mostly uncorrelated with the willingness of a project to accept a PR from a new contributor. Homebrew has very strict contribu
by nerdponx 6y ago
In my experience, bureaucracy is mostly uncorrelated with the willingness of a project to accept a PR from a new contributor.
Homebrew has very strict contribution requirements but has a huge number of contributors and is generally easy to contribute to. Meanwhile there are lots of little projects that go dead for lack of interest by the sole maintainer in reviewing and merging patches.
Also this:
Since then there has sprung up a fetish for bureaucratic process, and tooling has arisen to foster that, such that the barrier to entry is significantly higher now than it was in the 90s. All you needed was a text editor and an email account. Now you need accounts on whatever code forge is involved, and you didn't write enough unit tests, and you failed to properly format your pull request, and what do you mean you're not an expert in whatever version control we've adopted? This pull request sat in an open state because you didn't tag it appropriately. The CI system was updated and your code wasn't covered in the automated integration test, please resubmit after making minor punctuation changes in a metadata file.
Doesn't really make sense to me. How many projects have you actually had this problem with?
I don't think the author is right about things having been harder in the old days led to a higher proportion of the internet being qualified to contribute. I think it's much harder now to patch software upstream than it ever has been.
For some people, using Git and Github is a barrier to entry. For others, submitting a patch to a mailing list is a barrier to entry.
- musicale 6y ago> dead for lack of interest by the sole maintainer in reviewing and merging patches I think you mean "lack of action" rather than "lack of interest." It's easy to be enthusiastic about developers doing lots of work for you (usually for free) and to cast them as "uninterested" if they don't comply quickly (or at all) with your requests. I suspect many maintainers are "interested" in reviewing and merging patches but are simply unable to perform large amounts of work without pay, due to time and financial constraints.