Closed
Bug 1512981
Opened 6 years ago
Closed 6 years ago
IRC loosing track of who are owners and operators of channels
Categories
(Infrastructure & Operations Graveyard :: Infrastructure: IRC, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: ashish)
Details
In the last few months I have noticed that IRC has lost track of the ownership and operators of the channels #frontend-infra and #cia.
Could you please investigate this and provide a solution?
At this point the original owner of #frontend-infra is not working for Mozilla anymore, thus, there's now no owner or ops for the channel.
Could you please register me as the original owner?
Reporter | ||
Comment 1•6 years ago
|
||
@cshields: Could someone please look at this?
#frontend-infra is a quite active channel and we don't have owners or ops.
Flags: needinfo?(cshields)
Assignee | ||
Comment 2•6 years ago
|
||
I've made you (armenzg) the founder of #frontend-infra. I see you are already the founder of #cia. You can manage operators for both these channels. anope provides multiple ways of managing operators. It depends on what the owners choose.
I suggest the simple:
> /msg chanserv help AOP
command to manage operators. Feel free to reach out to me on IRC if you need assistance.
Assignee: infra → ashish
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(cshields)
Resolution: --- → FIXED
Reporter | ||
Comment 3•6 years ago
|
||
Thank you Ashish!
This should alleviate one of the problems.
On the initial comment I mention that all ownership and operator changes I make dissapear after few days.
I have not determined when, however, I've noticed it happened at least twice.
The only setting that is kept is the founder.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 4•6 years ago
|
||
It depends on what mechanism was used to promote users to operators. Access granted via AO and ACCESS should stick, a simple /mode #channel +o nick will stick until the nick parts/quits.
Reporter | ||
Comment 5•6 years ago
|
||
Is there a guide were the right way of doing it?
It's frustrating using /msg chanserv op #channel nick and not know that it's the wrong way if I expect it to work
Assignee | ||
Comment 6•6 years ago
|
||
Anope's docs aren't very end-user friendly. The built-in help (/msg chanserv help aop) is not bad, but I've added some basic information to https://wiki.mozilla.org/IRC#Managing_channel_operators
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 7•6 years ago
|
||
Thanks ashish for the wiki page update!
However, I don't think this should be closed yet.
If there are some commands that do not persist op/owners operations we should remove them or give meaningful replies so people go and use the right ones.
Is this possible?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 8•6 years ago
|
||
I have updated the wiki to replace all /mode with their ChanServ equivalent. This would then serve as the "right" way to do things. It's non-trivial to change the configuration for the commands. I don't want to break current workflows that use these commands as-is.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 6 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 9•6 years ago
|
||
Thank you @ashish!
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•