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

[Paolo Cavallini]

Hi all,

Il 14/01/2018 12:11, Richard Duivenvoorde ha scritto:
> On 14-01-18 00:17, Tim Sutton wrote:

>> Actually this is not true (correct me if I am wrong PSC): the PSC was
>> against two things:
>>
>> 1) losing all history in issue manager. I think this is reasonable since
>> there is a lot of very useful history in the issue tracker and it was
>> felt that a 'clean slate start ‘ would be a disservice to all those who
>> have raised issues in the past.
>> 2) calling for a migration without a fully tested, fully fleshed out
>> plan to manage the migration from start to finish. This means someone
>> taking responsibility for the *whole* process which so far hasn’t been
>> forthcoming.
> 
> That is exactly what it was in my memory too.

I can confirm. I Still believe loosing all our history of open and
closed issues would be a serious damage to the project.

> Some conclusions (at that time):
> - our Redmine version was (at that time) too old to be used for newer
> migrate scripts
> - Github was not very friendly for migrating our huge issue list
> - Some dev's wanted to hold full history, while others were ok with
> starting from 3/scratch
> - Nobody took the time to further investigate, and people told us that
> speed was the main issue on the old Redmine, so we upgraded Redmine AND
> put it on a dedicated fast server now.
> 
> But I'm pretty sure that IF somebody takes lead and:
> - migrates all our current issues with history and comments and users
> - convinces all/most devs (it is not a PSC descision in my view)
> 
> That we can move to Github or Gitlab or Gitea

I see the first a a serious problem, the second will be far easier or
even non existent IMHO.

All the best.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis