[QGIS-Developer] Last call for switching to github issue tracker

[Andreas Neumann]

Hi, 

I think the biggest question: who does all the work to migrate from
Redmine to Github while not loosing all our history? 

The migration attempts so far haven't been very convincing. 

And I don't think that Redmine is so bad usability wise. I agree, the UI
is not as sexy as Github, but it does its job well. It is much more
powerful for finding and filtering. The issues we had with the slow
performance was fixed when moving to a new Machine at Hetzner. The main
argument for github is in my opinion not ease of use - but the
integration with the code base - that is definitely a strength of github
issue reporting. 

To undermine that github is not easy to use for non-dev users: last
Wednesday at the Swiss QGIS user meeting I was in the meeting for QWC2.
Users had no idea at all how Github works and could be used for issue
reporting. One had to explain it to them and teach them how to use it.
To assume that using github is self-explanatory for non-tech users is a
wrong assumption. 

Andreas 

On 2018-01-12 14:52, Denis Rouzaud wrote:

> Hi all, 
> 
> I'ld like to raise a last call to switch to github issue tracker before the release. 
> I'd like to summarize briefly why. 
> 
> Pros (to me): 
> - integration with code and mainly with PR 
> - avoid multiplication of platforms 
> - so much more powerful (attachment, text formatting, referecing issue/PR, pinging people, fitlering/searching/tagging, possibility to plugin external issue management such as zenhub or others) 
> - so much more responsive, mobile friendy and easy to use 
> - lower infrstructure management on QGIS team (would be available for other stuff) 
> - opportunity to clean the list 
> 
> A proof that current situation is sub-optimal: 
> - people are pointing to code issues directly in comments of commits on github rather than creating an issue (high chance of getting lost) 
> - people send mail to the mailing saying they have created an issue (sic) 
> - people creates new gitub repo for creating issue lists (sic again): see qgis 3 API or UX changes 
> - mantra thing is a nightmare for new comers 
> 
> Why I don't agree on the raised issues to not to move to github: 
> - migration of existing issues: we have migrated a to a new redmine which should make migration easier [0]. 
> - Github has a close-source: there is an API and existing tools to migrate to other issue tracker [1]. I guess it leads down to pragmatic vs ethical matters. 
> 
> I would be in favor of using a semi-automatic migration: 
> - move all open tickets 
> - propose a tool to migrate others on demand: like a one-click process to move the features. 
> But this can be decided afterwards. 
> 
> I know PSC is (was?) against it, but I feel the majority of devs (and new issue posters) are for it. 
> Sorry to hassle on the topic. Let me know if I shall shut-up forever. Or raise your hand :) 
> 
> Or can we setup a loomio vote directly??? 
> 
> Best wishes, 
> Denis 
> 
> [0] https://github.com/gmontard/issue-sync-redmine-github 
> [1] Github importer for Gitlab: https://docs.gitlab.com/ee/user/project/import/github.html 
> 
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20180112/c739502b/attachment.html>