Closed Bug 1525560 Opened 5 years ago Closed 5 years ago

Please close #moc and #servicedesk IRC channels

Categories

(Infrastructure & Operations Graveyard :: Infrastructure: IRC, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gcox, Assigned: ashish)

Details

The IRC channels for #moc and #servicedesk were retired in favor of Slack. However, both channels still have 200+ people in them.

However, as public channels, they continue to receive questions, which then sit unanswered / need to be manually guided to Slack.

Please close these channels.

:fauweh, :soap - Any objections?

Flags: needinfo?(saik)
Flags: needinfo?(kferrando)

@Ashish

No objections. Thanks!

Flags: needinfo?(saik)

Where should non-NDA'ed volunteers (ie. contributors who don't have Slack access) ask questions when they need help or see something broken?

Passing NI over to mcristofi as she worked on a plan for this with leadership.

Flags: needinfo?(kferrando) → needinfo?(mcristofi)

Regarding the IRC MOC channel, the plan is to keep it opened until Wed Feb 13, 2019, in order to give a chance for as many people to see the comms as possible.

During the weekly project call, they announced the MOC and ServiceDesk IRC channels are closing as well in order to reach a wider audience.

Flags: needinfo?(mcristofi)
Due Date: 2019-02-13

A few people reached out to me asking me what happens now with no MOC IRC channel. Where can people get help and ask questions?
The recommendation right now is to open a Bugzilla ticket and it will get routed to the right area to get helped. This might not be ideal for all I did mention this to IT leadership and recommendation, for now, is Bugzilla.

(In reply to Maryann Cristofi [:mcristofi] from comment #6)

A few people reached out to me asking me what happens now with no MOC IRC channel. Where can people get help and ask questions?

It's unclear to me who this question is directed to, but, since I opened this bug, I'll take the first stab.

Did nobody ask that question of the decision-makers before, or was it asked and rejected?

The decision was already made-and-announced to retire these channels, with the gdoc as the answer of "here's where you go." Leaving channels open and deliberately unstaffed is disingenuous - reports can/will be ignored/missed because there's no expectation of staffing or engagement.

This bug is "commit to the announcement." Based on comment 5, I'm expecting the channels closed on 13Feb (or minimally de-voiced, if we don't want to kick everyone), or to remain open with a new topic/dates/plans.

(In reply to Greg Cox [:gcox] from comment #7)

(In reply to Maryann Cristofi [:mcristofi] from comment #6)

A few people reached out to me asking me what happens now with no MOC IRC channel. Where can people get help and ask questions?

It's unclear to me who this question is directed to, but, since I opened this bug, I'll take the first stab.

Did nobody ask that question of the decision-makers before, or was it asked and rejected?

The decision was already made-and-announced to retire these channels, with the gdoc as the answer of "here's where you go." Leaving channels open and deliberately unstaffed is disingenuous - reports can/will be ignored/missed because there's no expectation of staffing or engagement.

This bug is "commit to the announcement." Based on comment 5, I'm expecting the channels closed on 13Feb (or minimally de-voiced, if we don't want to kick everyone), or to remain open with a new topic/dates/plans.

Hi Greg,
I am replying to Florian Quèze [:florian] from comment 3, and a few people in the office and old MOC team mentioned it to me.
Correct. Its safe to close the MOC and Service Desk IRC channel that has been agreed upon by the teams and IT leadership.

Channels closed for new JOINs, muted for non-ops. Will be cleared out at EOD, suspecting a mass CLEAR might cause IRCCloud to hiccup in the middle of a business day.

Channels cleared of users.

Assignee: infra → ashish
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.