From kde-community  Wed Feb 24 08:40:56 2021
From: Paul Brown <paul.brown () kde ! org>
Date: Wed, 24 Feb 2021 08:40:56 +0000
To: kde-community
Subject: Re: Formal request to set up a KDE Discourse instance
Message-Id: <44839319.NidGqpURPd () rachel>
X-MARC-Message: https://marc.info/?l=kde-community&m=161415608023888

On mi=E9rcoles, 24 de febrero de 2021 2:49:28 (CET) Nate Graham wrote:
> On 2/23/21 5:34 PM, Eike Hein wrote:
> > Hey,
> >=20
> > This all sounds much too confrontational :-). Come on everyone, we can
> > do this much better.
> >=20
> > Ben, I don't think Nate's request implies prioritization. For folks
> > outside a particular team it can be difficult to follow what the team
> > has on their plate at the moment; you probably also wouldn't know the
> > same about Nate's VDG/QA space.
> >=20
> > Everyone knows that sysadmin is working hard all the time, but it has to
> > still be possible to do roadmap planning. In fact it's one of the best
> > ways to avoid getting overcommitted in the future. Declaring a goal
> > and/or agreeing to work on it in the abstract doesn't mean it has to be
> > done straight away or rushed, but it e.g. allows attracting contributors
> > to the goal to get the work done, as also seen in the thread already.
>=20
> Yes, Ben has made me aware that I don't actually have a good sense of
> what the sysadmin team is working on at any point in time. I'd love to
> be able to see at a glance which tasks are queued up in front of the
> things I'm eager to see done. Even something simple like a wiki page
> would be nice. It could even list ways for interested and technically
> competent people to help. That would be cool.

=46rom Promo's point of view, a Discourse instance would be helpful: As on =
of=20
our goals is to increase the number of community members, directing them to=
 a=20
Discourse instance makes the onboarding easier than sending them to a harde=
r=20
to navigate forum or a mailing list, a technology many younger users may fi=
nd=20
unfamiliar.

Which brings me to the next point: Over the last few weeks I have had to as=
k=20
for some things from sysadmin and become very aware of how stretched you ar=
e.=20
But, maybe in the long run, running a Discourse instance may alleviate the=
=20
workload somewhat, as Discourse can substitute both the forum and mailing=20
lists.

According to this:

https://meta.discourse.org/t/discourse-vs-email-mailing-lists/54298

Discourse can take on a lot of the functionality of mailing lists, apart fr=
om=20
its own particular features.

And according to this:

https://meta.discourse.org/t/what-is-mailing-list-mode/46008

Users who still prefer mailing lists, can interact with Discourse over emai=
l.

So, although the initial migration will be hard (as migrations tend to be),=
=20
maybe sysadmin could end up maintaining one service (Discourse) instead of =
two=20
(forum and mailing list).

Cheers

Paul
=2D-=20
Promotion & Communication

www: http://kde.org
Mastodon: https://mastodon.technology/@kde
=46acebook: https://www.facebook.com/kde/
Twitter: https://twitter.com/kdecommunity
LinkedIn: https://www.linkedin.com/company/kde