John McHugh created an issue: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/475
The process of maintainers getting op status on irc is a bit inefficient. Many maintainers have at some point lost control of their irc channel. Fixing it usually involves contacting a sysadmin. Newer contributors who have been added to doap don't automatically get any op status on irc if I understand correctly. This has made trying to set up moderation on the matrix bridge a bit of a pain as the power levels are linked to op status on irc bridge so an oped user would need to invite moderation bot into the channel, It should be as simple as contacting a maintainer and letting them decide how to proceed but if the maintainer doesnt have any control over the irc channel then it brings that to a halt. The advantage of adding this bot would be having the ability to ban or kick irc users but also matrix users and matrix instances. For cases where GNOME is dealing with high levels of spam from a specefic instance, that instance can be banned from GNOME. The acl's with banned instances can be shared across Mozilla, KDE, GNOME etc reducing the burden on individual projects when it comes to enforcing COC's. So, to get back on topic, op status and irc. I think that giving all maintainers of e.g gtk op status in #gtk or tracker op status in #tracker is reasonable. If they are trustworthy enough to be a maintainer then they should be trustworthy enough to manage an irc channel. -- Reply to this email directly or view it on GitLab: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/475 You're receiving this email because of your account on gitlab.gnome.org.
_______________________________________________ gnome-infrastructure mailing list [email protected] https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
