+1, moving to Github makes sense to me. It would be great to consider at some point in the future if Apache itself would be a good home for the GeoAPI, in particular, either as a new project, or part of SIS.
Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Martin Desruisseaux <[email protected]> Organization: Geomatys Date: Tuesday, December 2, 2014 at 6:57 PM To: "GeoAPI 3.0 SWG" <[email protected]> Cc: Apache SIS <[email protected]>, "[email protected]" <[email protected]> Subject: [GeoAPI-3.0.swg] Moving source code repository to GitHub OpenGeospatial repository? >The GeoAPI [1] source code is hosted on a SubVersion repository on >SourceForge [2] since 2002. But the OGC is now managing an >OpenGeospatial repository on GitHub. Should GeoAPI source code move to >that repository? If we do so, the URL would be: > >https://github.com/opengeospatial/geoapi > >The code on the SourceForge directory would be replaced by a link to >GitHub. What peoples think? (Reminder: OGC license is BSD-like [3]). > > Martin > > >[1] http://www.geoapi.org/index.html >[2] https://svn.code.sf.net/p/geoapi/code/trunk/ >[3] http://www.opengeospatial.org/ogc/software > >_______________________________________________ >GeoAPI-3.0.swg mailing list >[email protected] >https://lists.opengeospatial.org/mailman/listinfo/geoapi-3.0.swg
