Page MenuHomePhabricator

Don't fragment bugzilla conversation/IRC output
Closed, DeclinedPublic

Description

According to https://gerrit.wikimedia.org/r/#/c/54984 , the new wikibugs code (not yet deployed) will split the wikibugs output into a myriad of channels (this is independent from the name of the default channel).

This fragmentation is very annoying because it effectively subtracts important parts of the code/development/discussion from the normal public view on the main channel (whatever its name is) even though they are offtopic, hiding them in some secondary channel.
The secondary channels should receive additional copies of the relay, but not remove them from the main channel if they are on topic (for instance, the visual editor for MediaWiki obviously is on topic for MediaWiki-General and #wikimedia-dev).

As a fallback, if people really think those products are so unimportant/trashy ("noise") as to be ignored by people on the main channel, I'd like a single unified feed somewhere, e.g. #mediawiki-feed (it's not clear to me what wm-bot4 [~wm-bot@wikimedia/bot/wm-bot] is doing there exactly).


Version: unspecified
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=52529
https://bugzilla.wikimedia.org/show_bug.cgi?id=10760

Details

Reference
bz55807

Related Objects

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 2:40 AM
bzimport set Reference to bz55807.
bzimport added a subscriber: Unknown Object (MLST).

+1 to having it in #mediawiki-feed so people who want the full force of the firehose can have it.

The conversation is currently fragmented between MediaWiki-General (wikibugs) and #wikimedia-dev (grrit-wm).

grrit-wm can also post to other channels on demand, such as #-operations and #-visualeditor, which is a very useful feature (both of these are completely useless in MediaWiki-General and only tangenially related in #wikimedia-dev).

A separate channel that would *mirror* all other feeds would be okay, but a *separate* one.

(In reply to comment #2)

The conversation

Where is this conversation happening? I have opinions but I'd rather read first what has been discussed.

(In reply to comment #3)

(In reply to comment #2)

The conversation

Where is this conversation happening? I have opinions but I'd rather read
first
what has been discussed.

I mean the development conversation.

(In reply to comment #2)

The conversation is currently fragmented between MediaWiki-General (wikibugs) and
#wikimedia-dev (grrit-wm).

That's another bug.

grrit-wm can also post to other channels on demand, such as #-operations and
#-visualeditor, which is a very useful feature (both of these are completely
useless in MediaWiki-General and only tangenially related in #wikimedia-dev).

This is also another issue, and only in part overlapping this (gerrit changes are apparently considered more "noisy", otherwise they wouldn't have been moved first).

A separate channel that would *mirror* all other feeds would be okay, but a
*separate* one.

This bug is not about "all the feeds": pywikibot is already on another channel, because it's not sent to wikibugs-l.

(In reply to comment #4)

This bug is not about "all the feeds": pywikibot is already on another
channel,
because it's not sent to wikibugs-l.

Actually Pywikibot bugs show up in MediaWiki-General, and I wrote a python script which copies the output of wikibugs into #pywikipediabot if it's one of our bugs.

Yeah, wikibugs-l is a global watcher, and wikibugs bot just relays all mail that is sent there. So *everything* goes to MediaWiki-General, apart from security bugs.

+1 to all bugs continuing to go to MediaWiki-General. and all commit output (At least to mediawiki + ext) go to either MediaWiki-General or #wikimedia-dev

Having bug output in these channels helps bring new contributors in, and allows them to see what is being worked on. Moving it to #mediawiki-feed would destroy this.