SourceForge exit strategy

• Contact: [jodygarnett](https://github.com/jodygarnett
• TLDR: SourceForge is having trouble - this is exit strategy if we need it

Description

SourceForge is having infrastructure trouble, not playing well in public, and is in the process of being sold.

This exit strategy is a contingency if we need to migrate mailing lists and downloads to a new location.

Mailing Lists

Ideas:

• Google Groups (mailing list and web forum, slightly difficult for users without a google id, has proven impossible for projects to migrate away)
• OSGeo Mailman

Recommendation:

Migrate to OSGeo as path of least resistance.

Downloads

Ideas:

• Attach to GitHub tag? this will be easier for users to discover, however we do not have complete project history in GitHub (the earliest is GeoTools 2.6.6)
• Make available from OSGeo? We currently use the OSGeo download server as our maven repository (http://download.osgeo.org/webdav/geotools/org/geotools/) however we could ask for a second folder.

Recommendation:

• Attach downloads for 2.6.6 and newer, archive previous releases at OSGeo.

Status

Choose one of:

• Under Discussion
• In Progress
• Completed
• Rejected,
• Deferred

Voting:

• Andrea Aime
• Ben Caradoc-Davies
• Christian Mueller
• Ian Turton
• Justin Deoliveira
• Jody Garnett
• Simone Giannecchini

Tasks

1. Migrate mailing list to OSGeo

   • Ask Sys Admin Committee to migrating mailing list
   • Update website, user guide and developers guide

2. Migrate downloads to GitHub

   • Download previous releases
   • Attach to github tag for each release