Unified internal communications channel

[slbtty]

Why not push this more radically by shutting down mailing lists?
This story keeps repeating itself.

* Long time project primarily used mailing list in the past
-> New people come, but they bring a new communication channel
-> Split, the community have to choose one
-> Choose the new communication because the new communication channel
causes the split

So, deprecating the mailing list and setting up a new discourse
section for developers would be the first step.

The next step is linking a short tutorial of Discourse's mailing list
mode for email lovers.

I find Python's discourse is superior.

Normal users can ask questions, while core developers can discuss proposals.

They have "Committers" and "core dev" sections, which are supposed to
be low volume.

Only officially recognized developers can use "Committers" section.

https://discuss.python.org

Other similar things

Julia internals https://discourse.julialang.org/c/dev/5
Rust internals https://internals.rust-lang.org

On Thu, Dec 7, 2023 at 10:16 AM Nate Graham <nate at kde.org> wrote:
>
> Hello everyone,
>
> There have been a couple instances of drama this week caused by
> decisions being made without some of the relevant stakeholders knowing
> about them. In all cases, the decisions were announced, but either not
> announced in the places where all the stakeholders saw it, or not all
> stakeholders were able to notice the announcement in a place where they
> do generally pay attention.
>
> It makes me think that maybe the KDE development community has grown so
> large that we can't reasonably expect everyone to be paying attention to
> everything, or for everyone with something to announce to know exactly
> where the people who need to know it expect to find those messages.
>
> So perhaps this could be addressed at the source by creating a single
> unified "internal announcements" place that everyone can pay attention
> to without fear of being spammed with too many messages. In theory the
> kde-devel mailing list is one such place, but it's got more than just
> announcements, and also mailing lists aren't very accessible for a lot
> of newer contributors who didn't grow up with them.
>
> What I'm proposing is some kind of place that *only* has internal
> announcements and is very log signal-to-noise such that we can
> fearlessly recommend that *everybody* subscribe to it. In addition,
> ideally those who want to subscribe via mailing list could do so, but
> its content would automatically appear in other places too, such as
> discuss.kde.org and an invent.kde.org project. That way people can
> subscribe by whatever means is most comfortable to them.
>
> Thoughts?
>
> Nate