←back to thread

When Sigterm Does Nothing: A Postgres Mystery

(clickhouse.com)
115 points saisrirampur | 2 comments | 15 Jul 25 04:43 UTC | HN request time: 1.395s | source
Show context
bhaak ◴[15 Jul 25 12:25 UTC] No.44570425[source]▶
> While the Postgres community has an older and sometimes daunting contribution process of submitting patches to a mailing list, [...]

The Linux kernel works the same way.

What are other big open source projects using if they are not using mailing lists?

I could imagine some using GitHub but IME it's way less efficient than mailing list. (If I were a regular contributor to a big project using GitHub, me being me, I would probably look for or write myself a GitHub to e-mail gateway).

replies(2): >>44572655 #>>44573425 #
1. Bigpet ◴[15 Jul 25 16:10 UTC] No.44572655[source]▶
You can already subscribe to projects or single issues/PRs on github and reply via email to post comments.

I can understand not wanting to use GitHub/GitLab/etc. for various reasons. But I don't understand how usability vs mailing lists is one.

How is a set of 9+ mailing lists any better? It has significantly worse discovery and search tools unless you download all the archives. So you're creating a hurdle for people there already.

Then you have people use all kinds of custom formatting in their email clients, so consistent readability is out the window.

People will keep top-posting (TOFU), transforming the inconsistent styles in the process. Creating an unnecessarily complicated problem for your email client to "detect quotes", or you have to keep reminding people.

Enforcing structure of any kind in email lists seems so tedious. I'm not advocating for bugzilla style "file out these 20 nonsensical fields before you can report anything" but some minimal structure enforced by some tooling as opposed to manual moderation seems very helpful to me.

replies(1): >>44580514 #
2. bhaak ◴[16 Jul 25 10:03 UTC] No.44580514[source]▶
It's not about usability for newcomers (a mailing list is really not ideal for them) but usability for regular contributors and especially for lengthy discussions.

Call me old fashioned but there is no better way of discussing stuff online in an asynchronous way (OTOH video calls are better, but face to face doesn't scale) than a threaded medium. We don't have a better tool to manage threaded discussions than what mail clients (or Usenet clients but they are almost identical in handling).

Linear discussion forums (which GitHub issues are) are just inferior.