Proposal to shift bug/issue tracking work to GitHub Issues for QGIS 3x+
Tim Sutton
Public
Seen by 368
Dear QGIS Voting members
The bug tracker issue tracker for QGIS has been under much discussion over the last year (or more). This topic has again been under renewed discussion these last weeks and we need your help to move forward. If you want some back history, it would be good if you read this thread from the QGIS Developer mailing list:
In this context we would like to use this thread to make a decision and move forward in time for the QGIS 3.0 release.I will raise a motion for you to vote on attached to this thread. If we are not able to find a clear resolution we will present alternative options as a follow up vote, prompted by your discussion below.
Nathan Woodrow Mon 29 Jan 2018 11:27PM
OK so I'm going to vote yes mainly because I would like the experience of reporting issues to be better. I would also like our project management/planning tools to be better and there is a lot of tooling around GitHub for that.
I might support a move to gitlad in the future however it's a large endeavour and I don't think it's wise to do it yet.
Andrew Jeffrey (QGIS AU) Tue 30 Jan 2018 2:30AM
QGIS Australia User group has passed the question onto members and will provide a vote reflecting the majority by Friday 2/2/2018
Paolo Cavallini Tue 30 Jan 2018 6:37AM
QGIS Italy user group has voted for Redmine.
I would be against keeping a double system (it reminds me of the old times when so many things were doubled in QGIS ). I think this would be terribly confusing for users, and cumbersome to deal with for devs.
Matteo Ghetta Tue 30 Jan 2018 8:00AM
As pointed out by Paolo, the Italian user group is in favor of Readmine. The discussion is mainly on not loosing the ticket history. I think having 2 different systems (Readmine + GH) at the same time could enlarge the entropy and lead to a lot of confusion. So whatever agreement we find I'm just against a double system.
If we block new issues in Readmine from now on, what about the LTR release? 2.18 is maybe the most "delicate" LTR because of the QGIS 3 release: potentially lot of users can report other issues for 2.18 in the future and with a double system there could be a lot of double work for devs.
Vincent Picavet Tue 30 Jan 2018 9:43AM
I feel strongly uncomfortable with this vote : first there is no consensus neither convergence on the subject in the community. Then, we have a yes/no vote on a single alternative, whereas there are multiple alternative possible that should be studied, and this one ( GH migration) is clearly not the one gaining most favors.
Also, there is no action plan and resources linked to this decision, which is also a problem IMHO.
And I have a strong problem with migration to a proprietary solution.
DelazJ Tue 30 Jan 2018 9:51AM
Honestly, I'm surprised to find that there should be a vote while the last comment in the mailing-list discussion was Giovanni announcing this topic to the discussion held in Madeira. Worrying that it'd be an endless discussion?
Anyway, question has been passed to French QGIS User Group...
Deleted User Thu 1 Feb 2018 12:17PM
Hi, when I said "talk about it in Funchal" I think that this vote had not been published yet, if is not so I apologize.
Tim Sutton Tue 30 Jan 2018 9:59AM
@delazj I was asked by @denisrouzaud to raise it to a vote. I don't think it is an unreasonable request - if the consensus is 'just move to github' then it can cut a lot of wasted time in discussion of something that the majority of voters do not wish to happen. If the consensus is 'no we want to move to gitlab or stay on redmine' then at least the discussion in Madeira can go ahead knowing there is a mandate to make the proposed changes.
Kurt Menke Wed 31 Jan 2018 12:34AM
I've passed the question onto the USA user group for consensus. I too will provide a vote by Friday 2/2.
Tim Sutton · Mon 29 Jan 2018 8:53PM
Ok thanks for your inputs @nyalldawson I have updated the proposal accordingly. Those who wish to hold out for GitLab or some other platform feel free to vote no, but please join the process of actually making your preferred platform happen.