[Qgis-psc] Abstimmung: Umzug der QGIS Fehlerverfolgung von Redmine zu GitHub?

[Tim Sutton]

​Hi all

> like Jurgen, the Loomio vote came suddenly, did we miss a decision
somewhere?

​That is probably a case of me handling it badly - on the one hand I have
community members pressing me to put it to a vote so the discussion can be
concluded, and on the other community members complaining that it is called
to vote. I don't know how to keep everyone happy,  but my feeling is that
this is what the community voting members are for. The whole issue of issue
trackers is not a ​new or sudden topic - it has been dragging on for years.
The PSC made a decision in Essen last year - it was probably not a popular
decision and the topic never 'went away'. Using a community vote is
supposed to be the mechanism to make decisions, even to supercede the PSC
if needed. If we have to make a decision as to whether we make a vote to
make a decision it seems to me we are entering an infinite loop. Email
threads are not good places for decisions. Loomio is a good place to make
decisions and it is open and public what transpires there.

So my apologies about not communicating better about the vote, I'll try to
do better next time, but please lets find a way to put this topic to an end
instead of starting meta discussions about it....


>this makes sense to me.
> in short, my points are:
> * losing the history is a major damage to the project

Nothing will be lost under the proposal - the old tracker will be preserved
but new tickets cannot be opened in it. Users clicking 'new issue' would
get redirected to Git*** and at some point Redmine will fade into the
sunset.


> * keeping a double system can easily lead to confusion, waste of time,and
paradoxical situation.

It wont be a double system, it will be an old replace a new - like having
3.x releases out and also 2.x releases....eventually 2.x releases will fade
away and we will only concentrate on 3. The same process of attrition would
apply to the ticket queue.

> Frankly, I do not see the urgency of this issue, but perhaps I'm missing some
point of view.

Some people want to have the new ticket queue set up to go along with
upcoming release of 3.0. Personally I don't care so much even if the vote
is 'stay on Redmine forever' I do think we should try to resolve this now
instead of keeping it lingering around. If everyone votes 'no' to this
motion, we raise one more 'Redmine or GitLab' motion and if the community
votes to stay on Redmine we can put the topic to sleep with a quick
reference to the community vote outcome everytime it gets raised again (as
it surely will).

And in the case where there is a vote to move to GitLab, honestly I think
its going to be even worse than your double system complaint above - we
will have code etc on GitHub and tickets on GitLab plus the archive in
Redmine.

The only good outcome I can see is if we move ****everything**** over to
GitLab, code, issues, all repos, (git)hooks lines and sinkers....but I
think there is substantial risk in that option that a lot of churn will be
introduced into the project for an outcome that leaves us no further
advanced as a project than we were when we started.

Anyway the point of having a community voting system is to have a mechanism
to make hard decisions like this one....so I still think putting it out to
a loomio vote is a good move even if I did a bad job of communicating with
the PSC about this (for which I apologize again).



Regards

Tim

On Wed, Jan 31, 2018 at 11:23 AM, Paolo Cavallini <cavallini at faunalia.it>
wrote:

> Il 30/01/2018 14:32, Jürgen E. Fischer ha scritto:
>
> > I'd like to see migrated issues first to get a feel how much better it
> is -
>
> this makes sense to me.
> in short, my points are:
> * losing the history is a major damage to the project
> * keeping a double system can easily lead to confusion, waste of time,
> and paradoxical situation.
> Frankly, I do not see the urgency of this issue, but perhaps I'm missing
> some point of view.
> I'm cleaning up the bug queue, I hope others will do the same.
> 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
> _______________________________________________
> Qgis-psc mailing list
> Qgis-psc at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>



-- 
------------------------------------------------------------------------------------------
​

Tim Sutton
Visit http://kartoza.com to find out about open source:
 * Desktop GIS programming services
 * Geospatial web development
* GIS Training
* Consulting Services
Skype: timlinux Irc: timlinux on #qgis at freenode.net
Tim is a member of the QGIS Project Steering Committee
-------------------------------------------------------------------------------------------
Kartoza is a merger between Linfiniti and Afrispatial
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20180131/389f0400/attachment.html>