Tim, I don't have a strong opinion on this, it seems like it may be somewhat disruptive to move to a new system and it is not clear to me that there is a huge gain from this. What is your motivation for proposing this? Is it because DCVS is technically superior or will eliminate some bottleneck in our current system? In all the replies so far, I haven't seen you respond with your motivation.
Cheers Paul On 2010-04-16, at 7:22 PM, Tim Schaub wrote: > Hey- > > In advance of our infrastructure meeting (time TBD), I thought I'd take > a poll for the heck of it. > > Would people be in favor of or opposed to moving the OpenLayers > repository to GitHub? > > If the developers are interested in a change like this (even if it is > not until 3.0) we could create a PSC managed account called openlayers > and put whatever projects (e.g. website, openlayers) under that. > Anybody could fork. "Core" committers would become collaborators on the > openlayers account. > > If we go with GitHub, we may or may not want to use their issue tracker. > This is a separate topic for discussion (the github-trac plugin can > allow some integration of Trac and GitHub). > > If we go with GitHub, we could also discuss using their wiki and GitHub > pages for a static website (still hosted from http://openlayers.org). > These are also separate topics for discussion. > > I'm interested mainly to hear if people are generally in favor or > opposed to the idea of a repository move - and a move specifically to > GitHub for hosting. > > Tim > > > -- > Tim Schaub > OpenGeo - http://opengeo.org > Expert service straight from the developers. > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev __________________________________________ Paul Spencer Chief Technology Officer DM Solutions Group Inc http://research.dmsolutions.ca/ _______________________________________________ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
