[Qgis-psc] Moving the issue queue to github

[Tim Sutton]

Hi

> On 11 Apr 2016, at 12:21, DelazJ <delazj at gmail.com> wrote:
> 
> You may be right, Giovanni, but now, it won't only concern wrongly or not done reports: _ALL the reports_ will have to be tagged by you…

Actually in GitHub you can make teams, including people who may not have commit rights but who can set tags and be referenced from tickets. So we can easily make a IssueManagers team that can manage tags etc.


> 
> I must confess that I don't always know which category to set when reporting an issue and I prefer to not fill it rather than setting a wrong one. I think an explicite title helps developers to decide if the report may concern them or not.
> imho, priority is not a really clear item, given that it looks like a mix of level of urgency (to be solved) and impacts of the bug. There have been discussions about rewording this list, if I'm not wrong (I recall a mail of Paolo asking to follow Debian's classification). This is even hard to understand, with the "target release" field, choosing among lower, higher and nice to have priorities.
> There are things to improve in Redmine. Sure!
> 
> That said, my above point was more about setting the QGIS version, which is currently a mandatory information. And note that I'm not against change (github, as said before, may add coherence/consistency to a newcomer. I was really puzzled the first time I wanted to contribute to issues and code), just wanted to raise these points I haven't read yet.


One other thing that may have been overlooked is that GitHub supports issue templates. Its a simple markdown file which if found in your repo, will profile the issue with some content. You can see a simple example that we use in InaSAFE here: https://github.com/inasafe/inasafe/tree/develop/.github It doesn’t provide structured fields like Redline but it at least goes some of the way.

Regards

Tim


> 
> 2016-04-11 11:45 GMT+02:00 Giovanni Manghi <giovanni.manghi at gmail.com <mailto:giovanni.manghi at gmail.com>>:
> > Actually, I'm not sure that how filter reported issues using tags is what we
> > should care about first. To use tags, they should be filled with the issue
> > report. How will this be done and by who? eg, Who will add the Qgis release
> > concerned by the bug reported? who will set the category? ... Will all
> > reporters think to add these information in their description? Does it ease
> > their reports steps? And if not done, ...?
> > "Bref", considering this point, will moving to Github ease life for
> > developers and bug list cleaners?
> 
> 
> regardless the fact that on redmine the reporters have now the
> possibility to set category, priority, etc. they mostly don't do, and
> often they do it wrong. So this work is actually already done mostly
> manually.
> 
> -- G --
> 
> _______________________________________________
> Qgis-psc mailing list
> Qgis-psc at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-psc




---

Tim Sutton
QGIS Project Steering Committee Chair
tim at qgis.org




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20160411/cffe1234/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qgis_icon.jpg
Type: image/jpeg
Size: 4642 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20160411/cffe1234/attachment.jpg>