[postgis-devel] PSC Vote: Move from svn to Git (and by git I mean Gitea)

[Regina Obe]

Raul and Sandro,

Thanks for the great feedback.  My heart sank when I heard everyone say "Git is pointless without Github"

Dan,

Our gitea is a bit out of date -- one of the new features they added since we updated is this:

Pull request review/approval and comment on code
https://github.com/go-gitea/gitea/pull/3748

I have on my task list to update our gitea instance https://trac.osgeo.org/osgeo/ticket/2371 
 (and have tested installing  it on the replica tracsvn container)
https://dev.git.osgeo.org/gitea/  (it's about a month old) -- give it a try to see if you have the same feelings.

 to the latest version so perhaps that will help some of your pain points.

Komzpa,

What you want to move to github so you skip putting in tickets and click Pull easily -- man you are the encarnation of my fear.
And you want to put our issues on github so you can HAVE MORE ISSUES.  ARE YOU NUTS?
But seriously don't think I'm thoughtless in dismissing your pain.  I'd just rather have more like a federated pull system that allows pull requests to be accepted from anywhere and merged.  That vision disappears when everyone is on GitHub as what's the point.  I don't think that feature is too far off and other projects like gitlab and bitbucket want that too.

I know this sounds crazy coming from a user on Windows -- but don't let a plate of food destroy your ability to see what is possible.
That is why I joined PostGIS and use PostgreSQL because I saw what they could be rather than what they were.

Thanks,
Regina

-----Original Message-----
From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of rmrodriguez at carto.com
Sent: Tuesday, October 22, 2019 5:35 AM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] PSC Vote: Move from svn to Git (and by git I mean Gitea)

I want to start with some context.

Whenever I have to backport a patch, which I see has happened 30+ times in the last year, in git I can cherry-pick the commit to an older branch, push it to my Github fork Github and wait for Travis to confirm it's ok.
Then, to push it to svn, I have to generate a patch (git diff), move into svn and apply it.
This might seem trivial, but patch is quite basic as it doesn't consider the project history, so more often than not I have to generate multiple patches (one per active branch, currently 5) so it's quite a bit of work.
Anything we do to minimize that procedure would be great.

I use git because it's easier for me, I started with it and I use it in all other projects except for pushing into Postgis, it's way faster than svn, and it takes way less disk space (my current git folder with 6 remotes is 343MB, my current svn folder just with upstream is 6.6GB).
And I test against Travis because it's easy, fast, and I only run a single PG version in my main machine, now PG12, which only works with Postgis 2.5+.

I agree with Komzpa and Paul in that I prefer Github over Gitea, I also like things being (partially) tested before they are merged and making it easier to contribute, but for me moving to git IS first about git, then about whatever cool features we can get out of Github / Gitlab / Gitea, so I disagree in that "Git-on-gitea" isn't different from "svn-on-trac".
Even getting a git server with no UI would be an improvement for me.

In any case, my +1 for whatever moves us out of svn.

--
Ra l Mar n Rodr guez
carto.com
_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-devel