[geos-devel] GEOS RFC 10 - Move Project to GitHub

Paul Ramsey pramsey at cleverelephant.ca
Tue Nov 2 17:44:36 PDT 2021

> On Nov 2, 2021, at 5:33 PM, Sandro Santilli <strk at kbt.io> wrote:
> On Tue, Nov 02, 2021 at 10:45:30AM -0700, Paul Ramsey wrote:
>>>> 	• Easier path for new contributors to discover and assist with the project
>>> Easier how ? What would be possible for new contributors which is not
>>> possible today ?
>> Easier in that they don't need to grok the "over here for this part,
>> over there for that part" hybrid setup we currently have.
> Which are the parts you are thinking about ?
> Software components or pull-requests vs. issues ?
> At the moment for GEOS itself (the library component) there's
> a two-parts situation due to the fact that we didn't want to
> ditch Trac in order to retain the commit<->issue links, like
> this one from 13 years ago:
>  https://git.osgeo.org/gitea/geos/geos/commit/9f42184aef30c34f9dd254d0fbb9705df418b048
> See how you go easily from commit hash to ticket and back.
> How do you plan to deal with those references ?

I don't. Perhaps the folks from proj or gdal could provide their experience with moving along and not necessarily retaining every scrap of history?
> For the software components we currently have 4 public
> repositories and 2 private ones listed on the Gitea organization
> page, would you also want to move all of them to GitHub ?

I can't see the private ones, but of the ones I see, 'geos', 'geos-docker' and 'php-geos' (not sure if that's defunct?). 


> --strk;
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel

More information about the geos-devel mailing list