Last modified: 2013-08-10 03:17:32 UTC
merge #wikivoyage and #wikimedia-wikivoyage IRC channels during the project migration. -have a plan how to redirect users -move/adjust desired IRC bots, add channels to configs, allow topic changes for all (mode -t) and have it enforced by chanserv -renew chanserv registration/give permissions/password to people if necessary -offer wikivoyage cloaks (separate bug)
This is GCs stuff, so I am unsure why this is listed here on bugzilla. Anyway, I have added the GC as it is them who handle these matters. As it works right now, the #wikimedia-wikivoyage channel is for dev-talk regarding the transition. End-user/editor stuff should go in #wikivoyage, as it is now within the Wikimedia Freenode Group Thingy Thing domain, and cloaks are offered for it now. I would suggest that the merge, which is easily implemented (tho only Eloquence has access to #Wikimedia-wikivoyage so most likely when it will be needed the GC will have to act) by redirecting #wikimedia-wikivoyage to #wikivoyage. I would suggest that no localized channels be created until wikivoyage has a more solid irc community, as fragmentation of a community that's at the moment quite small seems hardly a good idea. I don't see a need for any bots in the channel as it stands right now, tho if the local community, once it is established needs it, we can easily provide a watcher bot to monitor key community pages in the various languages (would do so thru the stewardbot group as it allows for multiple people to handle restarts and such). -t is a good idea, have it enforced by chanserv is a really silly idea, for it creates issues should there be the need to lock it down due to troll attacks and such. There are no "chanserv passwords" to give out, just to handle contacts and access list that's all. So in short, 1) easily done/done 2) which bots? which configs? topic chances very easily set up 3) not sure what you mean but that depends on how the channel evolves 4) already handled and done
Copied over the to dos to https://meta.wikimedia.org/wiki/User:Snowolf/Wikivoyage_IRC#To_do_list
(In reply to comment #1) > This is GCs stuff GC = https://meta.wikimedia.org/wiki/General_Counsel ? > so I am unsure why this is listed here on bugzilla. Because we somewhere need to track technical tasks to sort them out, especially if we don't know yet how exactly to proceed. :) Hence thanks for pointing out who else needs to take part in this process! For future reference: Which other potential technical/infrastructure changes related to integrate Wikivoyage are also GCs stuff so we should CC? > I don't see a need for any bots in the channel as it stands right now Guess we need to find out if Wikivoyage folks would like to receive IRC notifications on e.g. changes in bug reports about bugs that affect Wikivoyage. Maybe that's stuff that should only go to a *technical* Wikivoyage IRC channel though - depends on channel audience and triggered amount of messages.
(In reply to comment #3) > (In reply to comment #1) > > This is GCs stuff > > GC = https://meta.wikimedia.org/wiki/General_Counsel ? No, https://meta.wikimedia.org/wiki/IRC/Group_Contacts
> No, https://meta.wikimedia.org/wiki/IRC/Group_Contacts Sigh, I should have known better. Thanks. (In reply to comment #1) > This is GCs stuff, so I am unsure why this is listed here on bugzilla. Snowolf: There is an IRC component in this Bugzilla so I'd expect IRC "maintainers" to take a look sporadically. Where else would you have expected contact instead? Or does that even imply that IRC bug reports should not be filed here? Clarification welcome.
(In reply to comment #5) > Snowolf: There is an IRC component in this Bugzilla so I'd expect IRC > "maintainers" to take a look sporadically. > Where else would you have expected contact instead? Or does that even imply > that IRC bug reports should not be filed here? Clarification welcome. AFAIK the IRC component here deals with irc.wikimedia.org not the freenode stuff, and the GCs are not on the autocc list for this stuff :) In general, I'd say that this stuff would end up raised in #wikimedia-ops or on Meta. Not saying it's a better system, all I'm saying is that most likely the GCs had no idea this bug was around until they were added to the CC list ;-)
From https://bugzilla.wikimedia.org/describecomponents.cgi?product=Wikimedia : >Issues with Recent Changes feeds on irc.wikimedia.org, and bot tools on irc.freenode.net not covered elsewhere. So no, it's not really relevant to the IRC component.
In future, any additional freenode-related IRC tasks should be directed to irc-contacts-owner@wikimedia.org - there is no point in tracking them here, as some actions will be recorded and some won't. Plus as Snowolf said, the first we (the Group Contacts) heard about this was via the CC, and in reality, the GCs are the only people who will be able to sort freenode issues. Thanks.
[Snowolf: Thanks for explaining! I've updated the BZ component descriptions.]
please also close this as WONTFIX or something, per the comments above that GC people don't want their bugs in Bugzilla.
