Currently workstation chat is split between #fedora-desktop on irc.gnome.org and #fedora-workstation on irc.freenode.org. I don't think many people know about either.
If we want to grow a contributor community (see #218), then consolidating our chat in one place, and making that place well-known, seems like an obvious thing to do.
Apparently Matrix is the answer here?!
Matrix is the answer here.
We're waiting for @mattdm and @riecatnor to get us the new Matrix server up. Once it exists, we can make it our preferred entry point and link them all in.
See https://pagure.io/fedora-workstation/issue/218#comment-731111
So... possibly we could bridge a matrix channel to irc.gnome.org, if that helps?
What's the logic behind keeping close to GNOME in this case? The obvious argument I can see is to facilitate communication with other upstream developers...?
A matrix room can have multiple addresses on multiple servers.
So, for example: #workstation:fedoraproject.org could also have #fedora-workstation:gnome.org as an alias address pointing to the same room.
#workstation:fedoraproject.org
#fedora-workstation:gnome.org
Well we have lots of people on GIMPNet and a lot of problems discussed and fixed in #fedora-desktop. I don't use freenode, and won't because polari does not handle it well, so #fedora-workstation is not so useful to me. I'm sure other developers have their own preferences.
Assuming the Matrix bridging is working properly -- which is a very big assumption, because both GNOME's and freenode's bridges seem to be pretty severely busted -- we should have a better future.
See https://pagure.io/fedora-workstation/issue/218#comment-731111 What's the logic behind keeping close to GNOME in this case? The obvious argument I can see is to facilitate communication with other upstream developers...?
In what case, sorry? I wasn't replying to anything in particular, I was pointing out one of the reasons why the IRC channels were the way they were. I don't particularly like Matrix, or the clients it has for GNOME.
Certainly having #fedora-desktop on GIMPnet was intentional, and somewhat controversial at the time 15 years ago or whenever it was. Parameters have since changed in various ways:
So I don't think the long ago history is that relevant. I also think that we have to accept that we might personally find change in this area inconvenient - I haven't made any move from Polari towards Matrix, in advance of being forced to :-)
See https://pagure.io/fedora-workstation/issue/218#comment-731111 What's the logic behind keeping close to GNOME in this case? The obvious argument I can see is to facilitate communication with other upstream developers...? In what case, sorry?
In what case, sorry?
Sorry, could have expressed that better. I was interested in the historical motivations for having #fedora-desktop on irc.gnome.org, as opposed to somewhere else. You said that it was to be closer to upstream, and I was wondering if there were specific practical aspects to that closeness.
The new docs site advertises the workstation channel through both IRC and Matrix.
Do we maybe want to encourage people to join it, if they haven't already?
We discussed this topic at yesterday's working group meeting. One goal we set out was to migrate to the workstation channel on libera and Fedora's Matrix. I have the actions to:
Metadata Update from @aday: - Issue assigned to aday - Issue tagged with: pending-action
See if we can get the #fedora-desktop topic updated, to direct people to our channels of choice
This has been done.
It looks like #fedora-desktop on Gimpnet is bridged to #fedora-desktop:matrix.org. I think we said that we'd try and get the latter switched so that it bridges to #fedora-workstation on libera instead?
A request was put in on 5 May to tombstone #fedora-desktop:matrix.org, and have it point to #workstation:fedoraproject.org. I checked back yesterday and this still hasn't happened, and am currently chasing to see what the story is.
This has now happened - I think we can call this issue done.
Metadata Update from @aday: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.