Project talk:Pywikibot/Migrating to bugzilla

Jump to navigation Jump to search


I'm Amir (User:Ladsgroup) and I suggested to PWB people in pywikipedia-l to migrate from sourceforge (which currently is PWB bug tracker now) to Bugzilla. They're agreed So I request here to migrate because of these reasons:

  1. In the sourceforge, people can report bugs via OpenID. So you don't need to register and every week we receive spam/non-sense reports [1] that won't happen If we use bugzilla (or rarely happens)
  2. This become a centralized bug tracker. Some of PWB devs are also mediawiki devs so they have to work on bugzilla and sourceforge separately to track bugs but in this way, all of related bugs for them, will show in a page
  • People don't know sourceforge (So it's hard for them to report If they see any bugs) but they know bugzilla

Best, Ladsgroup (talk) 10:32, 27 May 2013 (UTC)


I disagree with (1): it's an advantage that people can easily submit bugs, not a disadvantage. The spam bugs are actually not submitted using OpenID, but rather just by anonymous users. I also think (3) is nonsense - the typical user doesn't know bugzilla either, and will just click a link and write down some things there. (2) is somewhat an advantage, but 'show all relevant bugs' is nonsense, because that is neigh-impossible in bugzilla.

During the hackathon, I discussed this (among others) with André Klapper. The basic idea is to first move to gerrit. Afterwards, we can check what the best bug tracker option is. Valhallasw (talk) 11:23, 27 May 2013 (UTC)

I think we must distinguish between ordinary people and bot operators. bot operators are usually experienced wikipedians (I am emphasizing on this part) and reporting a bug in bugzilla is more easier than using OpenID and submitting a bug in sourceforge for these people (Please see people who recently submitted bugs, All of them has account in bugzilla and they report mediawiki bugs too). about (2) I meant if you vote or add your e-mail to cc you can see all of your bugs in "My bugs" or if you're dev of both mediawiki and PWB, you can see bugs assigned to you in "Assigned to me" (all of them in one place) in sidebar Ladsgroup (talk) 09:40, 28 May 2013 (UTC)
  • Personally I never liked sourceforge's tracker very much, so I would love to move to bugzilla. I think Valhallasw brings up a good point though, lets migrate to gerrit first and once that's all settled down we should then discuss bug tracking. Legoktm (talk) 18:37, 30 May 2013 (UTC)
  • I agree that we should move to Bugzilla after we've migrated to Gerrit.  Hazard-SJ  ±  23:44, 30 May 2013 (UTC)
  • Anyway, is the SF tracker being followed? I filed this bug over 2 weeks ago, but there's a chance that I'll login with gerrit and try to solve the issue by myself. --Ricordisamoa 10:53, 11 June 2013 (UTC)
    • It's (unfortunately) totally normal in free software in general that not every report gets a response. So yes, the SF tracker is being followed, but there is always room for improvement. --AKlapper (WMF) (talk) 15:57, 11 June 2013 (UTC)
  • In general the plan to first sort out SVN vs. Git sounds more urgent (as SVN is supposed to get shut down at some point). I don't see how VCS and Bugtracker are technically related, but if it is about resources and disturbance I can understand that you don't want to work on both at the same time. I'm happy to set up Bugzilla (also see here) for you. I don't know if there is a script to automatically import tickets from SourceForge into Bugzilla, plus if that is even something we'd like to use - I'd prefer a cleanup first. All together I'd love to see PWB developers set up a task list and a rough time schedule for the VCS migration part and the Bugtracker part. --AKlapper (WMF) (talk) 16:04, 11 June 2013 (UTC)
    about git vs. svn see Git/Conversion/pywikibot AFAIK it suppose to be done in 14 June (but I'm not sure) about the other part let me do some research Ladsgroup (talk) 16:30, 11 June 2013 (UTC)