Page MenuHomePhabricator

Add AWB to list of products
Closed, InvalidPublic

Description

Not exactly a bug, but it would be nice to have AWB (AutoWikiBroswer) in https://bugzilla.wikimedia.org/enter_bug.cgi so that the bugs are reported here and we can keep better track of them.

Many editors asked for it and some guys proposed that to me in Wikimania.


Version: unspecified
Severity: enhancement

Details

Reference
bz39072

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 12:59 AM
bzimport set Reference to bz39072.
bzimport added a subscriber: Unknown Object (MLST).

Hi Marios,
that means that both
https://en.wikipedia.org/wiki/Wikipedia_talk:AutoWikiBrowser/Bugs and
https://en.wikipedia.org/wiki/Wikipedia_talk:AutoWikiBrowser/Feature_requests
would be obsoleted by using bugzilla.wikimedia.org instead?

Out of curiosity, do you plan to manually copy existing tickets to Bugzilla?

For the theoretical case of a future reorganization of products in this Bugzilla, where would you add AWB in the section "Proposed products" on
https://www.mediawiki.org/wiki/Requests_for_comment/Bugzilla_taxonomy ?

Yes. I think the best strategy is to obsolete the existing lists and change the code so that the bugs are uploaded in Bugzilla after the person who reports creates an account.

I could copy the old bugs manually.

It should be a component not a product.

(In reply to comment #3)

It should be a component not a product.

matanya: Component of which product?

I'd suggest tools. Though it might be better to see what happens on bug#38990

I can't see why you couldn't keep the existing pages open too. Bugzilla is totally non-user-friendly, at least at first, and at least to the non-technically inclined. Such a category includes most AWB users.

I don't know what you refer to when saying "keep existing pages open".
Bugs and Feature_requests? How would keeping two reporting places in sync work, without having two places to look and search for?

(In reply to comment #7)

I don't know what you refer to when saying "keep existing pages open".
Bugs and Feature_requests?

Yes.

How would keeping two reporting places in sync work,
without having two places to look and search for?

There's no need to keep them in sync, just avoid duplication. The product/component can even be set up so as to assign the bug automatically and thus to alert all major AWB developers of new Bugzilla bugs via email. I can't see that that would add much to the workloaad of AWB devs (inc. me).

In general: Is there concensus among AWB developers to use Bugzilla? Some link to discussions would be highly welcome.

Marios Magioladitis: Who would be default assignee for reports against AWB?
(Does not necessarily have to be a person, I could also set up an account like "awb-bugs@example.xyz" and people could add that account to their "User Watching" list under https://bugzilla.wikimedia.org/userprefs.cgi?tab=email

Would you need subcomponents?

(In reply to comment #8 by Jarry1250)

There's no need to keep them in sync, just avoid duplication.

Yeah, but I wonder how to avoid duplication, so I wouldn't say "just". :)

Still no comments by other AWB devs. I still believe we should have a page which bugs that are AWB-Mediawiki connected should be reported to at least get more opinions. For instance:

https://en.wikipedia.org/wiki/Wikipedia_talk:AutoWikiBrowser/Bugs#Unable_to_save_some_pages_causes_infinite_loop

M.

@Andre Klapper

A bugzilla account for awb developers would be good. We could forward the notifications to the current awb devs.

No subcomponents should be needed for starts.

We have 50 exceptions reported and 2-3 more bugs that are MW related.

All other reports can be solved in the old wikipedia page.

M.

I'd rally prefer to see some agreement and commitment among AWB developers (also on the bug report workflow) before setting up something that in the worst case only one or two persons might take a look at from time to time.

(In reply to comment #13)

A bugzilla account for awb developers would be good. We could forward the
notifications to the current awb devs.

Not sure if I understand completely.
Does this depend on creating an AWB product in Bugzilla first?
With "notifications" you refer to bugmail, but who would receive this? An email address to an existing AWB mailing list? Asking as one Bugzilla account is always linked to one email address.

I'm closing this due to missing feedback and public agreement of AWB developers. Please reopen if there is agreement that this is wanted.