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

[Regina Obe]

What purpose would a headless git serve vs. gitea?  Gitea is a single executable and does everything we are using it’s PostgreSQL backend (though it supports other databases like SQLite, MySQL, and even SQL Server – even has integration with Microsoft Teams if we cared).

 

How would we do LDAP with a headless git.  It would be more trouble than it’s worth?

How would it make your life on Github any easier when you still wouldn’t have a a flashy green button to push?

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Daniel Baston
Sent: Thursday, October 24, 2019 7:41 AM
To: Sandro Santilli <strk at kbt.io>
Cc: 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)

 

Please don't confuse source control and GUIs.
You cannot compare Gitea with SVN.
You cannot compare GitHub with SVN.
You cannot compare GitHub with GIT.
You cannot compare Trac with GIT.
You cannot compare Trac with SVN.

This proposal is about migrating code source repository
from SVN to GIT, as we did in the past migrate from CVS to SVN.

 

Sorry for being confused. Is this proposal not about switching from SVN to a git server managed by Gitea? Or are you proposing a headless git server?

 

Dan 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20191024/283e9c08/attachment-0001.html>