3 ms·
I wonder if it's a "raised barrier to entry" to prevent low-effort drive-by PRs. I have a couple of extremely-small OSS libs that are available in public packag
by ubertaco 5y ago
I wonder if it's a "raised barrier to entry" to prevent low-effort drive-by PRs. I have a couple of extremely-small OSS libs that are available in public package repos and are hosted on Github, and even those have gotten the drive-by "I slightly reworded your README" PRs that don't help. I can't imagine the volume of noise that larger projects get.
By requiring a .patch file to be sent via a mailing list, the sort of "burden of effort" shifts away from "log into Github and click the pencil icon in the preview for README.md" and towards a slightly-heavier-weight minimum threshold -- one that shouldn't be so bad as to discourage folks making earnest valuable changes, but might be enough to make low-effort spam more annoying for the spammer than the spam-ee.
- andrew_ 5y agoBarrier of entry is a good call. From my experience on some rather large OSS projects, the ratio of noise to signal on PRs tends to go along with the target audience of the project.
- londons_explore 5y agoMailing lists suffer from other kinds of spam... Actual email spam, poor moderation tools, etc.