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

[chris marx]

Another vote to move to git*, people may want to defend redmine, but it's
just not friendly for new users to come in and get engaged. And I realize
that QGIS may not want this, but I think it's a big user satisfaction win
if we could upvote issues-

On Wed, Jan 17, 2018 at 8:34 AM, Denis Rouzaud <denis.rouzaud at gmail.com>
wrote:

> Hi all,
>
> I'd like to move on a bit the discussion.
>
> I'll try to summarize (and to be fair and honest):
>
> * The desire to switch to Github is strong
> 1 against: Sandro
> 5 neutral (or did not pronounce): Jürgen, Andreas, Richard, Paolo, Nyall
> 9 for: Borys, Matthias, Tom, Jorge, Régis, Bernard (says Redmine sucks),
> Loic, Tisharm and myself
>
> * But among those who spoke. I was hoping for a broader response.
>
> * I think we shouldn't mix switching to github (for technical reason) with
> switching to gitlab or so (for ethical reason). My original call was mainly
> for technical reasons and I believe, the end-users should decide on this.
>
> * As stated, ethical reason should rely on the PSC. Feel free to call for
> it.
>
> * I believe that we should first decide on what to do and next find the
> technical (and financial) solutions. And not the other way around.
>
> * Jorge volunteered to work on the topic.
>
> Additional **personal** notes:
>
> * I would be against moving all issues to github. That doesn't mean losing
> our history: let's just keep redmine online but locked. This has to be
> discussed and decided after deciding to move to github.
>
> * Another upcoming issue we HAVE to take care of: soon the PR number in GH
> will catch up with the issue number in Redmine....so bugfix commits will
> link to an unrelated PR... Keeping things untouched by fear of losing
> history is a suicide!
>
>
> Can we make a decision, and in this order:
> 1. decide to move (but to be applied if following questions are made
> possible)
> 2. what/when to move (empty list or everything or open issues, before the
> release, etc.)
> 3. how to move (volunteer, grant proposal, etc)
>
> And if we realize the decision is not feasible: we start again the
> procedure by stating we cannot do it.
> It would be useless to spend hours on trying to migrate the issues if we
> decide to start with an empty list -- just to illustrate.
>
> What is next?
> A loomio vote for this?
>
> Cheers,
>
> Denis
>
> Le ven. 12 janv. 2018 à 09:52, Denis Rouzaud <denis.rouzaud at gmail.com> a
> écrit :
>
>> 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/20180117/464cbf89/attachment.html>