Migrate chat channels from freenode to libera.chat

[Tim Jacomb]

Hi all,

I would like to propose moving the following channels that currently live on freenode to libera.chat:

• #jenkins
• #jenkins-hosting
• #jenkins-infra
• #jenkins-release

There's been some very user / FOSS hostile behaviour from the owner of freenode, latest example can be seen in https://news.ycombinator.com/item?id=27286628.

Implementation is:

• Update jenkins.io
• Let people currently in the channel know
• Update ircbot to connect to new server and create new credentials

There's been other conversations about moving the community to places like discourse and replacing the ircbot with Jira webhooks, but I don't believe that this is the right thread for those.

ircbot does more than just hosting, it manages github permissions and Jira components as well.

Any changes to ircbot require or Jira webhook integration requires interested contributors to build solutions.

Thanks

Tim

[Oleg Nenashev]

Hi all,

I definitely support such a move. For the record we've had a discussion about the migration among the Jenkins governance board and infra/security members. I believe we have a consensus that we want to move, effective as soon as possible. I also support moving all the listed channels. We have other channels, but all of them are rather dead or redundant.

Notes about channels:

• I would like to keep #jenkins equivalent, but not as a declared default channel. We could create #jenkins-users and #jenkins-dev similar to the mailing lists. Discourse would be indeed preferable for many subjects, and the IRC channels might become redundant (see the parallel thread)
  
• Private CERT chat is not a problem, we can just discontinue it in favor of mailing lists
• #jenkins-release and #jenkins-infra can be moved to Libera chat or any other chat like Gitter or CDF Slack. I have a preference to keep them on the same platform with conversation history by default
• #jenkins-hosting can be moved anywhere or just replaced by some form of GitHub/Jira integration bot
• #jenkins-meeting and #jenkins-hackhouse can be deleted. For meetings, if needed, we can create #jenkins-governance later

Best regards,

Oleg Nenashev

--
You received this message because you are subscribed to the Google Groups "Jenkins Infrastructure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-infr...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/CAH-3BidgAHKm6t8iwB91cQ%3DO89XXEbo%2B6SX33AR_ZofsE-Pq%3DQ%40mail.gmail.com.