IMHO nginx has never been a particularly "open" or friendly open source project. I don't mean to sound rude. I don't think open source contributors "owe" anyone

IMHO nginx has never been a particularly "open" or friendly open source project. I don't mean to sound rude. I don't think open source contributors "owe" anyone anything in this regard. If you want to throw code over a wall and run away, that's your prerogative. However I do think Cloudflare's assessment is accurate and a real liability for them. Some of the OSS papercuts with nginx: - nginx has always used a "submit a patch to a mailing list" style of contributions. Many contributions, my own attempt a decade ago, just get ghosted: https://mailman.nginx.org/pipermail/nginx-devel/2010-December/000605.html https://mailman.nginx.org/pipermail/nginx-devel/2010-Decembe... - Neither the contributing page (http://nginx.org/en/docs/contributing_changes.html http://nginx.org/en/docs/contributing_changes.html) nor the Mercurial repo (http://hg.nginx.org/ http://hg.nginx.org/) redirect to HTTPS! - Tests were a later addition and in a distinct repo with a bespoke harness. I'm sure it has advantages, but it also takes extra work for contributors to figure out. - They use Trac?! I loved Trac circa 2008 but had no idea it was still a thing. I can't even login to it without it timing out. I don't want to nitpick an excellent project like nginx, but I think it's clear that easing third party contributions has never been a high priority.