[bagasme]

As an occasional docs janitor and now helping tracking kernel regressions, I also feel "high tension blood" when I see trivial patches from random Chinese contributors, then I reviewed them but these contributors don't reply to my and others's reviews at all. Last year there were people from @cdjrlc.com domain, then this year from @208suo.com. Even some maintainers agree to block such domains [1].

The takeaway is once you submit your patches, it's your responsibility to address reviews that may come to them.

[1]: https://lore.kernel.org/all/5fcffcebca2ef9b8c276e5f4b4464d88... [2]: https://lore.kernel.org/all/[e-mail]...

[jacquesm]

That's interesting, it looks like a reasonably effective way to DDOS the FOSS infrastructure that could be used to mask that something else is being slipped in under the radar. I'd be very suspicious of this, especially if there isn't any response, that means that just getting the mailing lists saturated may well be the primary goal.

[bagasme]

I think that's not the point that I want to highlight. The problem, however, is some drive-by contributors have unwillingness to accept feedback (including critical reviews). When that behavior become a pattern within contributor's organization/domain, maintainers may take on the err side. For example, Linux kernel maintainers advise to not run checkpatch script on existing sources ([1], [2]). On a occasion, another maintainer had to roll out comment wording fixes after original submitter ignored the maintainer's review ([3]). And the well-known example is when an university was banned from Linux kernel development [4].

[1]: https://lore.kernel.org/all/20230720134501.01f9f1de@gandalf.... [2]: https://lore.kernel.org/all/2023092730-shampoo-anytime-f437@... [3]: https://lore.kernel.org/all/162b5545-7d24-3cf2-9158-3100ef64... [4]: https://lore.kernel.org/linux-nfs/YH%2FfM%2FTsbmcZzwnX@kroah...