I have never been a big fan of “bridging” between chat services – while it might be convenient for those who are into the project already and don’t want to miss some communication, it is heck of confusing for those who
joins for the first time.
I’d rather pick one and go with it and I would base the choice off how many similar / other projects are using one platform vs the other for their public facing communication.
i.e. Yocto / Zephyr / AGL I think they are all historically on IRC, so if one potential developer moves adjacently into “Oniro” from those adjacent projects, having such developer change platform for something new he/she
might be interested in exploring would be a sufficient obstacle thrown into the daily routine that would prevent him/her from joining.
In summary, I would pick one and stick to it (public facing channel), avoid bridging, and choose which platform (IRC, matrix) based on a survey of adjacent projects in order to maximize cross-room roaming (as opposed
to cross-platform switching).
Cheers
D
From: Agustin Benito Bethencourt <agustin.benito@xxxxxxxxxxxxxxxxxxxxxx>
Sent: domenica 29 gennaio 2023 18:52
To: Andrei Gherzan <andrei@xxxxxxxxxxx>
Cc: onirocore developer discussions <oniro-dev@xxxxxxxxxxx>; Davide Ricci <davide.ricci@xxxxxxxxxx>
Subject: Re: [oniro-dev] Towards an Oniro chat service: channels structure proposal
Hello,
Hello,
On Friday, 27 January 2023 14:34:37 CET Davide Ricci wrote:
> Thanks, while I suspect the public facing open channel will remain #oniro @
> Libera.
Right?
With the current implementation, no, since anyone can join our matrix channels
with any account open in any public server.
We can keep it for some time though, just in case.
Consider having a bridge configured for a public synapse channel <-> iRC channel.
True. I will add the request.
From my mobile. Excuse my brevity.
Agustín Benito Bethencourt
Program Manager at Eclipse Foundation
