[announcement] Telegram bridging to be retired Wed. 20 Sept. | 5 to-dos
Hello KDE community, apologies for cross-posting! The time has finally come: both Telegram <-> Matrix bridges will be shut down in 4 weeks on *Wednesday 20 September*. Let's start the co-ordination process now so everything goes as smoothly as possible. For all KDE contributors: please read at least the "Five To-Dos" below to be informed about what will happen and what needs to be done. Below that there is some additional information about the bridging situation at KDE. Consult these notes if you want more background information about why the Telegram bridge is being retired. Cheers, Joseph _Five To-Dos_ 1. *General*: On Wednesday 20 September the Telegram bridging to KDE Matrix rooms will be shut down. To make the transition go smoothly, teams should start co-ordinating for the shutdown now. The Matrix room for co-ordination is "Telegram shutdown co-ordination" at https://go.kde.org/matrix/#/#telegram-shutdown:kde.org. 2. *Co-ordination*: This includes: (i) migrating all contributors to Matrix, and (ii) deleting the Telegram rooms before the bridge is shutdown or -- at most -- one day after the shutdown. Keeping Telegram rooms open when they are no longer being used will cause unnecessary confusion. Importantly, do not later add a non-KDE Telegram bridge to KDE's Matrix rooms as that will not solve the problems from doubled user accounts and lack of control over Telegram; see below for operational issues with Telegram bridging. 3. *Action needed by Telegram room admins*: Due to the unexpected shutdown of the public Libera.Chat bridge, we will have to move rooms over to the matterbridge (ircsomebot) bridge as we work through moving channels over to our own Libera.Chat IRC bridge. This will require someone with admin in the Telegram room to ensure @ircsomebot is in the Telegram room with admin. This needs to be done after we unbridge the Matrix bridge from the Matrix side, so the room can continue to be bridged until the Telegram shutdown on 20 September. 4. *Are there exceptions?": There /may/ be some rooms that focus on interacting with people external to the KDE Community who would benefit by having a Telegram bridge. We are thinking teams like those involved in the KDE Network program: https://community.kde.org/The_KDE_Network. Not all will need an exception, and it may turn out most don't. We would like to start putting together a list of these rooms so we can review for potential exceptions and estimate the scale of how much support is needed. However, this should be kept to a minimum; see below for operational issues with Telegram bridging. We understand that there are large internal KDE communities which rely heavily on Telegram, and we understand that shutting down the Telegram bridge is less than ideal for these rooms, but the issues we have with the Telegram bridge mean we need to keep exceptions to a minimum and only for those teeams whose work has a primarily external focus. 5. *Getting a Matrix account*: We can offer KDE Contributors (usually those in the developers group, but will consider other requests) a Matrix account on our KDE Matrix Homeserver. To request an account please file a sysadmin ticket https://go.kde.org/systickets. However, as Matrix is federated you do not need to have an account on our homeserver to access KDE's Matrix rooms -- you can use any homeserver! A list of some alternative Matrix servers is available on https://joinmatrix.org/servers/. To co-ordinate with other teams to make this transition go as smoothly as possible, please reach out to the "Telegram shutdown co-ordination" Matrix room: https://go.kde.org/matrix/#/#telegram-shutdown:kde.org. _Additional Information Re Bridges_ * Four years ago it was decided to add Matrix to IRC as KDE's official IM platforms (bridged together). IRC is not planned to be shut down. * Telegram is not Free Software and has never been an official platform for KDE communications. However, it has been used unofficially in a number of areas. * EMS hosts KDE's Matrix instance and the current Telegram bridge, and the majority of issues our community have with Matrix are related to bridges. Due to the huge extra load and poor performance Telegram bridging has in the Matrix rooms, it was agreed with EMS that the bridge would be only run for about a year until people had time to migrate to Matrix. * However, instead of people migrating away from Telegram, we have seen an increase in contributors using /both/ Matrix and Telegram, which has doubled the number of users we have to cope with. Having twice as many users as needed in the room slows everything down: longer joins, more state events for each user, higher chances of room state developing problems. * The public Libera.Chat bridge was unexpectedly shutdown, and we have to move rooms over to the matterbridge (ircsomebot) bridge as we work through moving channels over to our own
Re: Review of Codevis (ie - Making Codevis a KDE Project)
Update, it now builds on qt6 and qt5.
Struggling a bit with craft for windows.
On Fri, 18 Aug 2023 at 21:22 Ben Cooksley wrote:
> On Sat, Aug 19, 2023 at 3:37 AM Tomaz Canabrava
> wrote:
>
>> (some help / I need to set the default branch to master, from main,
>> because the tooling doesn't accept the later, I don't think I have the
>> permission to do that).
>>
>
> That has been done now.
>
> Cheers,
> Ben
>
>
>>
>> On Fri, Aug 18, 2023 at 5:10 PM Tomaz Canabrava
>> wrote:
>>
>>> Small update that the CI is now fully passing.
>>>
>>> On Fri, Aug 18, 2023 at 2:25 PM Tomaz Canabrava
>>> wrote:
>>>
Carl, Sysadmins:
The current error on the KDE ci is this:
Looking for clang tool headers at /usr/lib64/clang/16.0.6/include. You
can change this by defining CT_CLANG_HEADERS_DIR
CMake Error at CMakeLists.txt:87 (message):
Cannot find clang tool headers at /usr/lib64/clang/16.0.6/include
-- Configuring incomplete, errors occurred!
(to which I understand that carl said there's an error with Clang6.
This is not an error - it basically says that we are unable to find
`stddef.h` on the path `
${LLVM_LIBRARY_DIR}/clang/${LLVM_PACKAGE_VERSION}/include`
This is needed for the tool to run properly, but not compile, so I
removed the FATAL from the message.
On Thu, Aug 17, 2023 at 6:51 PM Tomaz Canabrava
wrote:
>
>
> On Thu, 17 Aug 2023 at 18:29 Carl Schwan
> wrote:
>
>> On Thursday, August 17, 2023 11:18:24 AM CEST Tomaz Canabrava wrote:
>> > Hello Fellow KDE Devs,
>> >
>> > I'm here, formally asking for a review of the Codevis project, to
>> move
>> > forward and make it a part of kdesdk.
>>
>> Very cool project, I was amazed by the presentation of it from
>> tarcisio at
>> Akademy.
>>
>> > Currently we are using parts of KWdigetsAddons as a submodule
>> > Most things that are related to buildsystems will be moved to craft
>> /
>> > kdesrc-build as soon as possible, right now we rely in conan for
>> windows
>> > and mac, plus a hand-written build script that downloads and builds
>> llvm
>> > for those platforms.
>> >
>> > Things that I know that are out of KDE Accordance:
>> > - Translation System (uses Qt's tr() system)
>>
>> This isn't an issue and we have other KDE projects using the tr()
>> system. But
>> if you want to port to ki18n, it's best to do it now since you don't
>> seems to
>> have any translations yet.
>>
>> > - Settings System (it uses my own configuration parser that
>> resembles QML)
>>
>> Yeah probably best to use kconfigxt or make your configuration parser
>> part of
>> kconfigxt next gen ;)
>>
>> > - Folder naming specification (follows the lakosian naming
>> specification)
>>
>> I don't think we have any folder (and file) naming specification in
>> kde, or at
>> least if we have one, it varies a lot between projects.
>>
>> > - CI used is based on Gitlab, but fails on KDE
>>
>> When trying to build it on my laptop it failed, due to the
>> requirement of
>> clang 16. This might also be an issue with the kde ci on tumbleweed.
>
>
> Carl,
>
> There’s no requirement for clang16 (I build with 15, tarcisio builds
> with 14, the previous ci had 13, I believe)
>
> Mind if you share the build logs?
>
> Best
>
>
>
>
>>
>> > The current repository of Codevis is:
>> > https://invent.kde.org/tcanabrava/codevis
>> >
>> > The KDE developers on this project are me, tarcisio fischer (that
>> presented
>> > Codevis on Akademy), and Richard Dale.
>> >
>> > Best regards,
>> > Tomaz
>>
>>
