Hi
Just as a follow up to this thread, I have started a Loomio vote for QGIS
Voters to decide if we should move to GitHub issues.
https://www.loomio.org/d/cDwCmhsG/proposal-to-shift-bug-issue-tracking-work-to-github-issues-for-qgis-3x-
Regards
Tim
On Thu, Jan 25, 2018 at 4:29 PM, Jorge Gustavo
Thanks, Gio.
GitLab and CI in GitLab is also included as another topic. Good!
We already 30 people registered. Very good!
See you in Madeira,
On 25-01-2018 15:20, Giovanni Manghi wrote:
>> (about GH) IMHO tech decision and user experience are nothing that can
>> be fixed for more than 3y => I s
> (about GH) IMHO tech decision and user experience are nothing that can
> be fixed for more than 3y => I shouldn't decide focusing on user
> experience (now oauth login is widely supported), but basing on:
>
> 1) FOSS tool
> 2) opt-out ability
Hi all,
I added a topic about this matter in the nex
(about GH) IMHO tech decision and user experience are nothing that can
be fixed for more than 3y => I shouldn't decide focusing on user
experience (now oauth login is widely supported), but basing on:
1) FOSS tool
2) opt-out ability
I should be for a -1, but I prefer for an honest 0, because I ca
Hi all,
I've asked the Italian community, and surprisingly most bug reporters
find Redmine easier that GitHub.
No idea whether this is a generalized opinion, but IMHO we should hear
bug reporters at first place.
I agree with Borys that the opinion of bug managers counts a lot as well.
All the best.
> Who actually are the target of this desire of move: developers (who are
> missing ability to do some magics in the backend) or issue reporters (who
> would find Redmine difficult and Github better/easier)?
I'd count the bug reporters *and* the bug queue maintainers - so in fact
Giovanni, who do
On Thu, Jan 18, 2018 at 6:55 PM, Vincent Picavet (ml) <
vincent...@oslandia.com> wrote:
> Hello,
>
> A bit late to the party, and I think for such an important matter it is
> good to wait a bit to hear more voices.
>
Me too.
> I have mixed feelings about switching to a new issue manager withou
Hi,
my 2cts (and I have a partial view of what is discussed here)
Who actually are the target of this desire of move: developers (who are
missing ability to do some magics in the backend) or issue reporters (who
would find Redmine difficult and Github better/easier)?
As an issue reporter I agree
W dniu 18.01.2018 o 18:29, Tom Chadwin pisze:
Jorge Gustavo Rocha wrote
It would be amazing if we could share things among OSGeo projects. We
could dream with common resources, like glossaries, for example.
What a brilliant idea. Do we work with gvSIG to share translation resource?
There must
Hello,
A bit late to the party, and I think for such an important matter it is
good to wait a bit to hear more voices.
I have mixed feelings about switching to a new issue manager without the
history for QGIS3, and will not argue here for a specific roadmap.
But I think the GitHub vs GitLab deb
Le mer. 17 janv. 2018 à 18:06, Tim Sutton a écrit :
> Hi
>
>
> On Wed, Jan 17, 2018 at 8:34 AM, Denis Rouzaud
> 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 again
Jorge Gustavo Rocha wrote
> It would be amazing if we could share things among OSGeo projects. We
> could dream with common resources, like glossaries, for example.
What a brilliant idea. Do we work with gvSIG to share translation resource?
There must be considerable overlap.
Tom
-
Buy Pie
Hi Sandro,
I would prefer to use translate.osgeo.org. The first advantage would be
the authentication support and the unified OSGeo user profile.
Translators working on QGIS and other OSGeo projects would love to stay
on the same platform.
Our translation requirements are similar to other OSGeo p
On Thu, Jan 18, 2018 at 11:00:45AM +, Jorge Gustavo Rocha wrote:
> After this discussion about the development workflow, I would prefer to
> start another "disruptive" change and move from Transifex to Weblate.
As OSGeo system administrators we were considering adding a Weblate
instance on tr
Hi all,
Tim's proposal seems a interesting compromise.
We keeping the redmine active to support 2.x version and we start a new
development workflow for 3.x. based on git[hub|lab].
As Paolo, Nyall and other pointed out, we will have some noise regarding
duplication of issues, out of sync issues (c
On Thu, Jan 18, 2018 at 07:52:37AM +1000, Nyall Dawson wrote:
> since the redmine upgrade I've no strong issues with it. (Reactivation
> of the mantra would totally change this opinion though!!)
Note that the mantra is currentcly active.
Incidentally, many recent people asking for a mantra are co
Hi all,
Il 18/01/2018 00:07, Nyall Dawson ha scritto:
> On 18 January 2018 at 08:06, Tim Sutton wrote:
>
>> So I would suggest raising a vote on the motion:
>>
>> “We should adopt GitHub issues for reporting issues in 3.0 and restrict
>> Redmine for the management of issues in QGIS 2.x”.
>>
>>
Hi Denis,
On Wed, 17. Jan 2018 at 13:34:02 +, Denis Rouzaud wrote:
> 5 neutral (or did not pronounce): Jürgen, Andreas, Richard, Paolo, Nyall
I just didn't have anything new to add. Everything has been broadly discussed
already and led to the decision to stay with redmine.
> * Another upcom
On 18 January 2018 at 08:06, Tim Sutton wrote:
> So I would suggest raising a vote on the motion:
>
> “We should adopt GitHub issues for reporting issues in 3.0 and restrict
> Redmine for the management of issues in QGIS 2.x”.
>
> After there are no more active 2.x releases, we make the Redmine
Hi
> On 17 Jan 2018, at 19:35, chris marx wrote:
>
> 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 coul
On Wed, Jan 17, 2018 at 12:35:05PM -0500, chris marx wrote:
> Another vote to move to git*
What does git* mean ?
Does it include gitea, gitorious, gitlab ?
--strk;
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.o
On 17 January 2018 at 23:34, Denis Rouzaud 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, N
Hey,
You can include me on the +1.
On Wed, Jan 17, 2018 at 11:34 PM, Denis Rouzaud
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 pro
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
w
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 Redm
On Wed, Jan 17, 2018 at 03:16:02AM +, Tisham Dhar wrote:
> Having to remember multiple logins is another issue for me.
There's a Redmine plugin which would let users login with their
GitHub account: https://github.com/gpstogis/redmine_oauth2_login
Given that the current https://hub.qgis.org s
Having to remember multiple logins is another issue for me. I prefer Github for
centralized management as well.
Tisham Dhar
Research Engineer
Aerometrex PTY LTD
59 King William St.
Kent Town SA 5067
Australia
___
QGIS-Developer mailing list
QGIS-Develo
> On 16 Jan 2018, at 14:03, Sandro Santilli wrote:
>
> On Tue, Jan 16, 2018 at 01:42:06PM +0200, Tim Sutton wrote:
>
>> Since you are solving all problems here, the other nice thing to have
>> would be the ability to drag and drop screenshots into the issue like
>> you can on GH.
>
> I'm not
On Tue, Jan 16, 2018 at 01:42:06PM +0200, Tim Sutton wrote:
> Since you are solving all problems here, the other nice thing to have
> would be the ability to drag and drop screenshots into the issue like
> you can on GH.
I'm not so powerful to solve all problems, but it's surely something
that ca
Hi
> On 16 Jan 2018, at 12:43, Sandro Santilli wrote:
>
> On Sun, Jan 14, 2018 at 01:17:58AM +0200, Tim Sutton wrote:
>
>> @sandro: the wiki markup of GitHub is Markdown (an open format) which is
>> widely used in many places so it is definitely a re-useable skill beyond
>> GitHub. The conve
On Sun, Jan 14, 2018 at 01:17:58AM +0200, Tim Sutton wrote:
> @sandro: the wiki markup of GitHub is Markdown (an open format) which is
> widely used in many places so it is definitely a re-useable skill beyond
> GitHub. The converse is true for Redmine’s markup language which seems pretty
> arc
> On 14 January 2018 at 23:19, Paolo Cavallini wrote:
> > 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
On 14 January 2018 at 08:33, Sandro Santilli wrote:
> On Fri, Jan 12, 2018 at 07:44:57PM +0100, Régis Haubourg wrote:
>
>> That would imply a big task switching travis to gitlab-ci.
>
> How about *adding* gitlab-ci, rather than *switching* ?
I'm sure if someone volunteers to set this up and maint
On 14 January 2018 at 23:19, Paolo Cavallini wrote:
> 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
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
ts we can't solve.
Regards,
Jorge Gustavo
On 14-01-2018 11:11, Richard Duivenvoorde wrote:
> On 14-01-18 00:17, Tim Sutton wrote:
>> Hi All
>>
>>> [QGIS-Developer] Last call for switching to github issue tracker
>>
>> Given our history on the topic, I dou
On 14-01-18 00:17, Tim Sutton wrote:
> Hi All
>
>> [QGIS-Developer] Last call for switching to github issue tracker
>
> Given our history on the topic, I doubt very much this is true :-P
>
>> I know PSC is (was?) against it, but I feel the majority of devs (and
>
Hi All
> [QGIS-Developer] Last call for switching to github issue tracker
Given our history on the topic, I doubt very much this is true :-P
> I know PSC is (was?) against it, but I feel the majority of devs (and new
> issue posters) are for it.
Actually this is not true (correct m
On Fri, Jan 12, 2018 at 07:44:57PM +0100, Régis Haubourg wrote:
> That would imply a big task switching travis to gitlab-ci.
How about *adding* gitlab-ci, rather than *switching* ?
With PostGIS and GEOS we have both Travis adn Gitlab-CI
and Drone and Jenkins watching after the code...
--strk;
__
On Fri, Jan 12, 2018 at 03:49:54PM +0100, Matthias Kuhn wrote:
> I wouldn't claim that for either of the two platforms. There's a
> learning curve for both. Myself, I happen to meanwhile embrace markdown
> but struggle with the redmine syntax. Not because it's worse, just
> because I am too lazy t
For me as a simple user, the main obstacle of posting issues in redmine
is, that I fear to produce a duplicate, cause I didn't even learn over the
years how to efficiently track an issue down if it already exists.
No idea if github or any other solution is better, but redmine just sucks.
My 2
Hi Loïc,
using both gitlab and github, I'd definitly would be in favor of gitlab,
which would allow us to host our own servers. That would imply a big task
switching travis to gitlab-ci.
Cheers
Régis
2018-01-12 18:21 GMT+01:00 L.Bartoletti :
> On 12.01.2018 14:52, Denis Rouzaud wrote:
>
>> Hi al
On 12.01.2018 14:52, Denis Rouzaud wrote:
Hi all,
Hi,
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 (a
Hi all,
+1 too.
My main concern is that I now fail to search efficiently for redmine
issues, because there are so many now. And this leads to duplicates, or
even worst, no declaring the issue because the process is too long.
Github issues are very well indexed by google, which doesn't seem to be th
Hi,
Good point, Denis!
Mathias already have done a lot to support the migration.
I volunteer to help on this task.
Regards,
Jorge Gustavo
On 12-01-2018 14:49, Matthias Kuhn wrote:
> On 01/12/2018 03:31 PM, Andreas Neumann wrote:
>>
>> Hi,
>>
>> I think the biggest question: who does all the wo
On 01/12/2018 03:31 PM, Andreas Neumann wrote:
>
> Hi,
>
> I think the biggest question: who does all the work to migrate from
> Redmine to Github while not loosing all our history?
>
I started working on it some time ago and thought it looked quite
promising. I stopped the work because of lack of
A huge +1 from me. I was too intimidated to add issues to Redmine for some
time through not understanding what some fields meant.
Tom
-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
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 do
On 01/12/2018 03:19 PM, Borys Jurgiel wrote:
> Well, I have reconciled myself with the fact we're stuck in the darks of
> Redmine forever, but if there is still any chance for the migration, I'd not
> hesitate for a moment of course.
I couldn't have said it better.
+1
Matthias
_
Well, I have reconciled myself with the fact we're stuck in the darks of
Redmine forever, but if there is still any chance for the migration, I'd not
hesitate for a moment of course.
Borys
On piątek, 12 stycznia 2018 13:52:39 CET Denis Rouzaud wrote:
> Hi all,
>
> I'ld like to raise a last ca
Hi Denis,
On Fri, 12. Jan 2018 at 13:52:39 +, Denis Rouzaud wrote:
> - mantra thing is a nightmare for new comers
Again: osgeo ids are not a requirement to use our redmine.
Jürgen
--
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rh
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,
p
52 matches
Mail list logo
