Skip to main content


#GNOME replaces its mailing lists with Discourse:
mail.gnome.org/archives/deskto…

As someone who grew at a time where email was an unquestioned, decentralized foundation of #FreeSoftware workflows, moves like leave a bad taste in my mouth. I understand how Discourse facilitates onboarding, but the idea of delegating to a central server and using the browser as the sole user interface remains unappealing to me.

Getting old?

in reply to Ludovic Courtès

Mailman is a terrible UX. Spam is out of control (fortunately not visible to list members, but for list admins, it's a huge problem). The problems with mailing list dynamics are well documented, and I'm happy that Discourse has been written explicitly with an eye to mitigating them.
in reply to Ludovic Courtès

GNOME mailing lists have a central server as well, so I don't understand the point. It's not like you could send emails to any random server and have them appear in a list.

In any case, mailing lists are terrible for moderation, onboarding, and spam—just like anything that is based on email. Email is a centralised game, these days, unless you want everything to be marked as spam, and have nobody receive anything.

In any case: you can interact with Discourse via email as well.

in reply to Ludovic Courtès

@ebassi I’ve found Discourse’s onboarding features smart—messages essentially getting you to learn the etiquette, to better understand where the other person is talking from (whether they’re a newcomer or not), and so on. It probably helps lower the barrier to entry and make interactions smoother.

(I find it intriguing though that we need such “social prostheses” in the first place; is the on-line etiquette too different from real-life interactions?)

in reply to Ludovic Courtès

@khinsen @ebassi I like the idea too. Maybe Discourse’s email support goes in that direction? Delta Chat seems to be for small groups, from what I understand.
in reply to Ludovic Courtès

@khinsen @ebassi Do you know if Discourse supports email as a primary way of interaction? Is it possible to interact with a thread without registration on the discourse instance?
in reply to Andrew Tropin

@abcdw @khinsen No, you can't do that. You need to have an account on the Discourse instance.

Depending on the configuration of the instance, you may also need to actually browse it and interact with it a bit to raise your user level, before you can open topics just by sending an email.

in reply to Emmanuele Bassi

@ebassi @khinsen 😔 I really like the way it looks, but don't like the fact that for each interaction with any new project I have to create an account on gitlab/gitea instance to send a simple patch or to comment on the ongoing discussion, it seems that adding one more registration requiring tool will only increase this pain.
in reply to Andrew Tropin

@abcdw @khinsen That's not our experience. Though, of course, if you start contributing a lot to GNOME, you can ask to get an LDAP account, and then you get single-sign-on for all GNOME services.

If you're referring to being able to send patches via email, that's just false economy: you have a steep set up cost (git send-email is not a simple thing), and then you get stuck with patches over email, which is a fate worse than death.

in reply to Emmanuele Bassi

@ebassi @khinsen I mean the case, when you contribute to various FOSS projects on different platforms/forges. Maybe forgefed will make it less painful someday.

I agree the set up process is tough and there are not much good modern tools, but after initial configuration the experience is quite pleasant and in addition to that it's also offline-friendly. YMMV of course.

in reply to Emmanuele Bassi

@ebassi @khinsen @abcdw Which is “a fate worse than death” is a matter of perspective. I’m not saying patch over email doesn’t have its warts, but you’ll find many free software hackers disagree with this assessment.
in reply to Ludovic Courtès

@khinsen @abcdw Only the Linux kernel devs "enjoy" patches over email, because they have sunk a massive amount of time in their ad hoc tools. It's a textbook case of sunk cost fallacy. Everybody else either never used email to deal with contributions, or moved away from the patches-in-an-email-thread model over time