[wkz]

It's easy to forget the maintainers' side of this.

Yes, most contributors will prefer opening a PR on GitHub as apposed to mailinglists. But imagine instead that you are David Miller, and it's your job to consume the absolute fire hose of patches and messages related to Linux's networking subsystem. Would you rather wade through the hundreds of messages and patches coming in every day using either GitHub PRs and issues or email?

I would choose email for one simple reason: It's easier to script.

Even as a small-time contributor and observer to that space, I couldn't even imagine trying to keep up with everything going on if I couldn't bulk download, filter, tag etc. As a maintainer it would be excruciating.

[jeffybefffy519]

Github has an api for this…

[wkz]

And once you've used that API to download and tag everything, what tools do you use to interactively view the results, run search queries, apply patches to local trees etc?

If your on-disk format is an Mbox or a Maildir, you can use tools like notmuch and its emacs integration to do it.

Now don't get me wrong; I love GitHub. I host all my projects there, and I prefer PRs+issues to mailinglists in almost all cases. But for massive projects like Linux, a mailinglist (and associated tooling) scales better, in my opinion.

[diggan]

Which eventually will change, and you have to update everything. Or the company disappears and you have to move somewhere else.

Email is just email. You write SMTP/IMAP clients today and they'll continue to work for a long time, probably longer than most platforms with APIs online today.

[myaccountonhn]

It’s easier for contributors too, you don’t need an account.