[postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

[Regina Obe]

Darafei,

 

I think the issues you faced wouldn't matter if we were on github, gogs, or svn and we'll still have at the very least a Github mirror for the very reasons you mentioned.

 

The reason half your PR for parallelization did not go thru is because I intentionally deleted them.  I did not want them in 2.3 and wanted to think about them for 2.4.

So that has nothing to do with github/svn

 

The travis issue with not being able to test was because our travis was broken.  I think regardless which we choose, our laziness about fixing bots is not going to change.

 

The other patch about the points index optimizations that was then again me deliberating.  There is  some stuff there I have not committed and some I might revert because I wanted to do more tests on real data and some tests I did I did not see much of an improvement and in some cases slower.

 

So as far as your commits it shouldn't matter whether github, git whatever.  I’d still want to study and cut things out I don't think should be in there.

 

Thanks,

Regina

 

 

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Darafei "Kom?pa" Praliaskouski
Sent: Wednesday, August 09, 2017 9:25 AM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN

 

I'm not that frequent PostGIS contributor or a maintainer.


Most time I'm interacting with its code is when something is not covered in docs (like O() of the functions to get idea of how long the query will be running, or details of estimator, etc.).
I just read it on Github repo, as search and code highlighting are good enough there.
Sometimes I see a logical error and fix it right away in the github web editor, making a PR and looking at tests passing or not.

I think process of moving from git to svn let half of our parallel aggregates patch fall through the cracks, and I'm not even sure if it's completely there, as it's not a "merged PR", but a diff applied by maintainer. I also had issues creating OSGeo account, so a couple of tickets were created on trac by my IRC reports by other good people.

Github as a main home for postgis would be much easier for me, as postgis is not the only piece of software I'm looking into.

 

ср, 9 авг. 2017 г. в 16:10, Regina Obe <lr at pcorp.us <mailto:lr at pcorp.us> >:


> On 8 August 2017 at 23:07, Paul Ramsey <pramsey at cleverelephant.ca <mailto:pramsey at cleverelephant.ca> > wrote:
>> The practical aspects of "going where the people are" leads me to
>>  advocate for going all over to github. Code, tickets, etc.

> I second Paul's vote,

Paul has not voted.  He has advocated.  Advocation is NOT a vote.
It's a way of saying I'm encouraging other people to move in the direction I feel is right. :)

He has to say +1, -1, 0 for it to be considered a vote.

I suspect Sandro is conveniently not voting either.

> Although, I'm just an ad-hoc contributor, so I don't aim to interfere with PSC decision.

> Best regards,
--
> Mateusz Loskot

Mat,

If you had a choice between doing noting (e.g. keep svn, trac)

Or moving to

Gogs (git.osgeo.org <http://git.osgeo.org> , gogs ticket system)

Which would you choose?

I would choose the second, because even if git.osgeo.org <http://git.osgeo.org>  isn't stable it's more trivial to go to github.
Nothing lost - we get to experiment, developers get to use git instead of svn while we do so.
We've already started the experiment.


Thanks,
Regina


_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/postgis-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20170809/b9411dd6/attachment.html>