Last modified: 2014-03-08 20:18:32 UTC
They're a bunch of wiki grabbing scripts. I don't know what would be the right place for them would be since they're basically just a pile of non-core maintenance scripts, but it'd be nice to be able to track bugs in a saner way than by sticking comments in the cabal channel topic. Because that just plain doesn't work very well. (The aim is to turn them into an extension, but they're not there yet. Dunno if that would affect anything either.)
I think this could probably go under the Tools product for now, and get moved later on once the extension development gets started
https://git.wikimedia.org/summary/?r=mediawiki/tools/grabbers.git I'm not entirely convinced that "Tools" is a great name either (see bug 53986) but this sounds like the way to go for the time being, indeed.
Created: https://bugzilla.wikimedia.org/describecomponents.cgi?product=Tools If anybody wants to be on default CC, let me know.
Isarra: So I plan to revert this and remove this component. See bug 53986 comment 15: I'd like to kill the "Tools" product in Bugzilla in the next weeks, because it's reptty confusing now that we have Tool Labs. There is one ticket under "Grabbers" so far, and the component does not have any default CC. As long as "grabbers" is not a "proper" extension, the advantage of being able to find tickets about it in a dedicated component feels weaker than having this component "cluttering" (word is too strong but cannot find a weaker one) the list of components and having to query for bug summaries including "[grabbers]" under "Wikimedia > General/Unknown". Would that be acceptable?
(In reply to Andre Klapper from comment #4) > including "[grabbers]" under "Wikimedia > General/Unknown". Oops, should be instead: including "[grabbers]" under "MediaWiki > General/Unknown".
But how will people know to include that? And is there any way to set a default CC for those? (I mean, I should probably have been a default for the tools/grabbers, but I have no idea how to do these things, or how it works. Er.)
(In reply to Isarra from comment #6) > But how will people know to include that? There's triagers how can do this. "How will people know" can basically start at "How will people find the right product and component in Bugzilla". :) > And is there any way to set a default CC for those? Per Bugzilla component that's possible automatically, yeah. For single bug reports it would require manual CCing. Seeing that there has been one bug report so far, I don't expect too many more suddenly to come. :) > (I mean, I should probably have been a default for the > tools/grabbers, but I have no idea how to do these things, or how it works. Basically https://www.mediawiki.org/wiki/Bug_management/Project_Maintainers#To_add_a_project_or_component - a Bugzilla admin can set default CCs or default assignees for products and components in Bugzilla.
These are a thing that is generally only used once in the lifetime of a project (unless you're illogicopedia, which has been moved... what, five times now?), so bugs won't come steadily, but rather entirely at random. Basically they're something you never want to use. Ever. But sometimes you have to. That said, if tools don't get components anymore, then fine - you're right that there probably won't be very many bugs in general, so whatever reports come can get dumped into the main heap - but if it's practical, could you please make sure I, Jack Phoenix, and/or legoktm wind up CCed if so? (And ah, apparently I never found that page. Probably would have helped. Sorry about that.)
