Re: Abstimmung: Umzug der QGIS Fehlerverfolgung von Redmine zu GitHub?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Abstimmung: Umzug der QGIS Fehlerverfolgung von Redmine zu GitHub?

Jürgen E. Fischer
Hi,

On Tue, 30. Jan 2018 at 14:16:27 +0100, Thomas Schüttenberg QGIS-DE e.V. wrote:
> Liebe QGIS-DE Mitglieder,
>
> ABSTIMMUNG:
> I agree to migrate to GitHub issues and deprecate the current Redmine tracker

I don't - but I don't have a vote.  And I even missed that there was going to
be a vote and there is another discussion going on in a closed forum.

I'd like to see migrated issues first to get a feel how much better it is -
because now I can only imagine that we only get the same ability to classify
bugs using a huge tag cloud - which I'd imagine would render the thing
unusable.

How is bug reporting in gitlab?


Jürgen

--
Jürgen E. Fischer         norBIT GmbH               Tel. +49-4931-918175-31
Dipl.-Inf. (FH)           Rheinstraße 13            Fax. +49-4931-918175-50
Software Engineer         D-26506 Norden               http://www.norbit.de

_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc

signature.asc (844 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Abstimmung: Umzug der QGIS Fehlerverfolgung von Redmine zu GitHub?

Régis Haubourg -2

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

Concerning gitlab tags, it is pretty much the same label / tag system as in github. So yes we need a good
labeling system. But I think in redmine, we probably have too much categories. If search engine is more
accurate than Redmine's , I won't miss them. 

Cheers
Régis Le mardi 30 janvier 2018 à 15:32 +0100, Jürgen E. Fischer a écrit :

> Hi,
>
> On Tue, 30. Jan 2018 at 14:16:27 +0100, Thomas Schüttenberg QGIS-DE e.V. wrote:
> >
> > Liebe QGIS-DE Mitglieder,
> >
> > ABSTIMMUNG:
> > I agree to migrate to GitHub issues and deprecate the current Redmine tracker
> I don't - but I don't have a vote.  And I even missed that there was going to
> be a vote and there is another discussion going on in a closed forum.
>
> I'd like to see migrated issues first to get a feel how much better it is -
> because now I can only imagine that we only get the same ability to classify
> bugs using a huge tag cloud - which I'd imagine would render the thing
> unusable.
>
> How is bug reporting in gitlab?
>
>
> Jürgen
>
> _______________________________________________
> Qgis-psc mailing list
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/qgis-psc
_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc

signature.asc (308 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Abstimmung: Umzug der QGIS Fehlerverfolgung von Redmine zu GitHub?

pcav
In reply to this post by Jürgen E. Fischer
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
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc
Reply | Threaded
Open this post in threaded view
|

Re: Abstimmung: Umzug der QGIS Fehlerverfolgung von Redmine zu GitHub?

Tim Sutton-6
​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 <[hidden email]> 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
[hidden email]
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

_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc