Re: [announcement] Telegram bridging to be retired Wed. 20 Sept. | 5 to-dos

2023-08-24 Thread Ben Cooksley
On Fri, Aug 25, 2023 at 3:12 AM Carl Schwan wrote: > On Tuesday, 22 August 2023 08:57:31 CEST Joseph P. De Veaugh-Geiss wrote: > > Hello KDE community, > > > > apologies for cross-posting! > > Please let's stop doing that, it's generating a lot of duplicated emails > for > everyone. Most people i

Re: [announcement] Telegram bridging to be retired Wed. 20 Sept. | 5 to-dos

2023-08-24 Thread Carl Schwan
On Tuesday, 22 August 2023 08:57:31 CEST Joseph P. De Veaugh-Geiss wrote: > Hello KDE community, > > apologies for cross-posting! Please let's stop doing that, it's generating a lot of duplicated emails for everyone. Most people interested in this discussion are in the kde-community channel and

Phabricator task | formalizing a process for adding/removing services to KDE's infrastructure

2023-08-24 Thread Joseph P. De Veaugh-Geiss
Hi again, as promised, here's the link to the Phabricator task about formalizing a process for adding/removing services to KDE's infrastructure: https://phabricator.kde.org/T16410 I think having a formal process for this will help situations like we are having now with Telegram, and preven

Re: [announcement] Telegram bridging to be retired Wed. 20 Sept. | 5 to-dos

2023-08-24 Thread Joseph P. De Veaugh-Geiss
Hi all, we are a diverse community with a diverse set of needs, that is evident in the responses. There may be a more general discussion to be had about formalizing a process for adding/removing services to KDE's infrastructure. In fact, there is currently a Phabricator task about this, which I