I chatted with one or two regulars on IRC about the idea and there seemed to be some general support if someone else was willing to take the lead. Is there general interest in taking the initial steps for a migration to JIRA, setting up a project, etc.? Existing bugs could simply be linked from JIRA as new entries are made at the new location. Re-write is already (at least partly) there and we have a placeholder webpage on toolserver. We could also create some strategy/long term planning discussions there as well if we wanted to. If there's an interest, I can put some time into it. -Doug
I cannot put time into this project, but it sounds really good. :)
Il giorno venerdì 30 dicembre 2011, Doug wikipediadoug@googlemail.com ha scritto:
I chatted with one or two regulars on IRC about the idea and there seemed to be some general support if someone else was willing to take the lead. Is there general interest in taking the initial steps for a migration to JIRA, setting up a project, etc.? Existing bugs could simply be linked from JIRA as new entries are made at the new location. Re-write is already (at least partly) there and we have a placeholder webpage on toolserver. We could also create some strategy/long term planning discussions there as well if we wanted to. If there's an interest, I can put some time into it. -Doug
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Why not DrTrigonBot is already there too - good thing since bugs and feature request could be cross linked... ;))
Greetings
On 30.12.2011 16:27, Doug wrote:
I chatted with one or two regulars on IRC about the idea and there seemed to be some general support if someone else was willing to take the lead. Is there general interest in taking the initial steps for a migration to JIRA, setting up a project, etc.? Existing bugs could simply be linked from JIRA as new entries are made at the new location. Re-write is already (at least partly) there and we have a placeholder webpage on toolserver. We could also create some strategy/long term planning discussions there as well if we wanted to. If there's an interest, I can put some time into it. -Doug
_______________________________________________ Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
On 30/12/2011 15:27, Doug wrote:
I chatted with one or two regulars on IRC about the idea and there seemed to be some general support if someone else was willing to take the lead. Is there general interest in taking the initial steps for a migration to JIRA, setting up a project, etc.? Existing bugs could simply be linked from JIRA as new entries are made at the new location. Re-write is already (at least partly) there and we have a placeholder webpage on toolserver. We could also create some strategy/long term planning discussions there as well if we wanted to. If there's an interest, I can put some time into it. -Doug
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
I'm personally not a fan of JIRA, I prefer Bugzilla :/
Thats all I have to say on the subject, since I'm not a fan of Sourceforge's bugtracker...
-- Lewis Cawte
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 30.12.2011 19:40, Lewis Cawte wrote:
On 30/12/2011 15:27, Doug wrote:
I chatted with one or two regulars on IRC about the idea and there seemed to be some general support if someone else was willing to take the lead. Is there general interest in taking the initial steps for a migration to JIRA, setting up a project, etc.? Existing bugs could simply be linked from JIRA as new entries are made at the new location. Re-write is already (at least partly) there and we have a placeholder webpage on toolserver. We could also create some strategy/long term planning discussions there as well if we wanted to. If there's an interest, I can put some time into it. -Doug
_______________________________________________ Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
I'm personally not a fan of JIRA, I prefer Bugzilla :/
Thats all I have to say on the subject, since I'm not a fan of Sourceforge's bugtracker...
While you are mentioning this (btw. thanks for this) - I had contact to other people e.g. on dewiki which do also complain about JIRA no beeing user friendly and so on - this should may be considered... But I am not aware of how many low-level-users (regarding programming skills) are actually reporting e.g. interwiki bot errors...
On 30.12.11 23:53 , Dr. Trigon wrote:
While you are mentioning this (btw. thanks for this) - I had contact to other people e.g. on dewiki which do also complain about JIRA no beeing user friendly and so on - this should may be considered... But I am not aware of how many low-level-users (regarding programming skills) are actually reporting e.g. interwiki bot errors...
Hmm, did they say in what way it was not user friendly?
I have limited experience with it but only good. I have found it easier to use and more robust than bugzilla, though not necessarily an easy switch. I can see how a wikimedia editor who just wants to report a bug might find it overwhelming and full use of sub-tasks and components and the work flow and work history tools requires reading the documentation for all but the most intuitive, but I didn't find filing a bug difficult (and I'm almost certainly in your "low-level-users" at least as regards any programming skill - though I am experienced with work flow and project management concepts).
It seems well documented and easily linkable, not to mention it can be tied directly to TS FishEye so I think we could easily post patches and new proposed scripts to FishEye with complete back and forth linking to the issues they go with on JIRA. This would then allow users, even those who don't have commit access, to post their version controlled code where others could tweak it, before it's committed to the wikimedia svn.
Unlike either our current system or bugzilla, projects can be divided into different "components" and issues can overlap. As far as I can tell there is no need for junk like tracker bugs or keywords, though it does have "labels" which are like keywords.
Valhallasw said he has a script to move the bugs with but maybe we could try it out first without moving everything over.
TS-wiki (also integrated with JIRA/FishEye) is also available should we need it for a more static tracking of plans. Though of course, moving to JIRA does not mean we have to make use of TS-wiki or even FishEye.
Doug
Hi Doug,
Op 30-12-2011 16:27, Doug schreef:
I chatted with one or two regulars on IRC about the idea and there seemed to be some general support if someone else was willing to take the lead. Is there general interest in taking the initial steps for a migration to JIRA, setting up a project, etc.?
Sourceforge sucks. I think we can all agree on that. So where to move as a bug tracker? I would say bugzilla.wikimedia org. Why? * We already use the Wikimedia mailman lists * We already use the wikimedia svn * We already use the wikimedia code review at mediawiki.org * We already moved our documentation to mediawiki.org
We might as well integrate our bug tracking too. It's not that I dislike JIRA and especially like bugzilla, it's just that I really don't feel like setting up our own bug tracker.
Maarten
JIRA is used on ts, there is no need to "set it up" and it's used for the re-write (or can be - the project is set up in it) as well as many other ts projects.
It can also be integrated with git when wikimedia svn is converted. (that probably requires the ts admins to make some setting changes)
bugzilla is no more tied to mediawiki.org than the TS-JIRA
bugzilla's only real positive is that's it's free.
Doug
On 31.12.11 12:48 , Maarten Dammers wrote:
Hi Doug,
Op 30-12-2011 16:27, Doug schreef:
I chatted with one or two regulars on IRC about the idea and there seemed to be some general support if someone else was willing to take the lead. Is there general interest in taking the initial steps for a migration to JIRA, setting up a project, etc.?
Sourceforge sucks. I think we can all agree on that. So where to move as a bug tracker? I would say bugzilla.wikimedia org. Why?
- We already use the Wikimedia mailman lists
- We already use the wikimedia svn
- We already use the wikimedia code review at mediawiki.org
- We already moved our documentation to mediawiki.org
We might as well integrate our bug tracking too. It's not that I dislike JIRA and especially like bugzilla, it's just that I really don't feel like setting up our own bug tracker.
Maarten
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l