Thanks Martin. This makes sense. Note that Apache has been home to many neutral implementations of standards. For example see JCP; cf. most Java standards that came out of it started as Apache projects. Apache is ‘vendor neutral’ since Apache isn’t a ‘vendor’.
Regardless, putting the GeoAPI spec code on Github makes sense since I think it’s superior to SF.net. 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 11:35 PM To: "GeoAPI 3.0 SWG" <[email protected]> Cc: "[email protected]" <[email protected]>, Apache SIS <[email protected]> Subject: Re: [GeoAPI-3.0.swg] Moving source code repository to GitHub OpenGeospatial repository? >Thanks for the feedbacks. Actually the main intend of the proposed move >is not to go on GitHub, but to go under the "Projects of the Open >Geospatial Consortium" umbrella, which happen to be on GitHub. If the >GeoAPI source code were hosted on the Apache Software Foundation >servers, I think that its relationship with OGC and its aim to be >implementation neutral would be less visible... > > Martin > > > >Le 03/12/14 16:22, Mattmann, Chris A (3980) a écrit : >> +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 >>> > >_______________________________________________ >GeoAPI-3.0.swg mailing list >[email protected] >https://lists.opengeospatial.org/mailman/listinfo/geoapi-3.0.swg
