I like that idea, we would need to coordinate with OSGeo slack with respect
to migrating mailing lists.

--
Jody Garnett

On 6 March 2018 at 13:32, Torben Barsballe <tbarsba...@boundlessgeo.com>
wrote:

>
>
>
>
>
>
>
> *SourceForge had outages / reduced service during the week of the GeoTools
> 19-beta / GeoServer 2.13-beta release.This caused: - Delays on mailing list
> discussions and announcements (including the release announcement), - Loss
> of all download statistics for the release, so we don't know how many
> people are downloading / testing it.Once again, this brings up the topic of
> whether we should consider something a bit more reliable than sourceforge
> for hosting mailing lists and release artifacts. There is a preexisting
> migration proposal here:
> https://github.com/geotools/geotools/wiki/SourceForge-exit-strategy
> <https://github.com/geotools/geotools/wiki/SourceForge-exit-strategy> One
> suggestion was to start by migrating the GeoTools project (As it is a
> lower-risk migration, given that most people get there artifacts via
> maven), and use that to determine feasibility of migrating the GeoServer
> project.Any thoughts?Torben*
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to