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

[Darafei "Komяpa" Praliaskouski]

IMHO there's no point in going off SVN if we're not going to Github.

If we go github, we get one-button merge pre-checking that CI is green, and
need to create a ticket goes away as PR with fix is self contained ticket.
It lowers a burden of maintenance significantly.

If we go to gitea, that's same story with "do this and that CLI stuff and
the github PR is merged" and no bot check that change is valid, same as
with dirty svn commits we have now.

If we're not really changing anything in development process what's the
point of changing the underlying svn->git?

Positive example of Github switch is QGIS: they migrated source code and
all the issues, and now creating an issue report is no pain. The Markdown
that everyone speaks now, and inserting screenshots right away are awesome.
That also means you don't have to run the bureaucracy of creating a ticket
for each pull request since each pull request is essentially a ticket
itself.

I believe Paul have already debugged the migrate-all-issues-to-github
thing, and it worked really well.

Otherwise there's no point in moving off the 1998-style trac and svn, I
don't see what do we fix with the move. This "use git" movement is not
really about git itself, it's about the well known github and infra around
it. Git-on-gitea is not noticeably different from svn-on-trac from that PoW.


On Mon, Oct 21, 2019 at 2:37 PM Regina Obe <lr at pcorp.us> wrote:

> Even,
>
> I'm not going to argue with you on that metric.  You are right that Github
> has more pull requests. I don't forsee that changing at all and I am not
> blind to the fact that a large portion of our casual contributors (and even
> long standing ones) came thru Github.
>
> I just don't perceive the effort of accepting pull requests from Github if
> gitea is our master repo any harder than it is now and in fact it will be
> easier since it will be Git / Git.
>
> In fact I'm more concerned about if our master is GitHub how easy it would
> be to accept pull requests and accidentally let in a rogue commits.
> The fact that GitHub is such a juicy target for exploits because it does
> have mass appeal and the pressure everyone is imposing to just "Move to
> GitHub" because everyone is doing it,  is of great concern to me.  I've
> seen
> the same episode played time and time again.  The mass crowd in the long
> run
> is almost never the right solution.
>
> Thanks,
> Regina
>
> -----Original Message-----
> From: Even Rouault [mailto:even.rouault at spatialys.com]
> Sent: Monday, October 21, 2019 7:13 PM
> To: postgis-devel at lists.osgeo.org
> Cc: Regina Obe <lr at pcorp.us>
> Subject: Re: [postgis-devel] PSC Vote: Move from svn to Git (and by git I
> mean Gitea)
>
> > So let's try it again without mouthing (GitHub this time).  Github is
> > too dirty of a pond to be our official repo and the thought of the
> > world completely running on GitHub is mighty depressing.
>
> You're just ignoring reality and where your contributors are/want to be
>
> Since its first pull request on June 15th 2016,
> https://git.osgeo.org/gitea/postgis/postgis/pulls has received a grand
> total
> of 37 pull requests.
>
> In the meantime, https://github.com/postgis/postgis/pulls has had 397 pull
> requests (on June 15th 2016, the pull request number was at 105, and we are
> currently at 501)
>
> Even
>
> --
> Spatialys - Geospatial professional services http://www.spatialys.com
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel



-- 
Darafei Praliaskouski
Support me: http://patreon.com/komzpa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20191021/f978020d/attachment-0001.html>