[pycsw-devel] #61 Migrate scm from Subversion to Git

[Angelos Tzotsos]

Hi Tom,

What I am saying is that the real issue is the svn to git move. I agree
that after this move we should keep the code in GitHub.
Remember that every Git clone is a full repository, so having a copy over
OSGeo, or another site in parallel is not forbidden and is not going to
create issues to our developments.
Of course after this move to git, we can use GitHub pull requests for
collaboration with new devs, etc. We can also use the Tracker in GitHub for
ease of use and integration.

About OSGeo: Git is going to be supported soon (as I was told recently) but
I am not sure if and when it will be integrated with OSGeo Trac. I assume
that this will happen at some point (but perhaps that is late for us).

I agree that GitHub will help us grow faster... I am just keeping in mind
that we want to be an OSGeo Project in the future and we should keep in
touch with what is offered as infrastructure there too. Perhaps when Git is
supported there, Mapserver, Openlayers, Geoserver and others will clone
their code there too.

Cheers,
Angelos

On Tue, May 8, 2012 at 12:05 AM, Tom Kralidis <tomkralidis at hotmail.com>wrote:

>
>
> Hi Angelos: thanks for the info.
>
> My main concern is by going with git and not github, how does this impact
> github interactions?  We had quite the time integrating Adam's github
> branch into our own (mind you, that was into svn).  Would github be an
> easier collaborative environment (pull requests, etc.)?
>
> If we move our issue tracker to OSGeo, does/will OSGeo support git?
>
> Comments/thoughts valued.  My overall feeling is that if putting pycsw on
> github will increase code development/involvement, that would be a good
> thing.  As well, I think keeping the scm and issue tracker bound to one
> platform would be valuable for integration.
>
> ..Tom
>
>
> Date: Sat, 5 May 2012 02:00:10 +0300
> Subject: [pycsw-devel] #61 Migrate scm from Subversion to Git
> From: gcpp.kalxas at gmail.com
> To: pycsw-devel at lists.osgeo.org
>
> Hi all,
>
> I am bringing this issue for discussion here, it is more convenient than
> trac (https://sourceforge.net/apps/trac/pycsw/ticket/61).
>
> I think the first step would be moving to git. After that, github is just
> a hosting issue and can be done using a simple git push...
>
>
> Now the tracker issue is more tricky. We have the alternative to use osgeo
> trac.
> I know the trend is to use github throughout a project these days (see
> mapserver, openlayers etc)
>
> My only concern is that Github is not Free (as in freedom and as in beer).
> On the other hand sourceforge code was never available too :)
>
>
> So basically I am not against moving to github, I am just proposing to
> move slowly:
> - Move to Git scm after 1.4.0 release (around July). Clone the new
> repository to Github and create a project account for it.
> - Use as many osgeo resources available (we already use it for web site,
> downloads)
>
> - Move our tracker system to Github or OSGeo as a last step to moving away
> from sf.net.
>
> What do you think?
>
> Cheers,
> Angelos
> --
>
> Angelos TzotsosRemote Sensing LaboratoryNational Technical University of
> Athenshttp://users.ntua.gr/tzotsos
>
>
>
> _______________________________________________
> pycsw-devel mailing list
> pycsw-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pycsw-devel
>




-- 
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
http://users.ntua.gr/tzotsos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/pycsw-devel/attachments/20120508/e0601881/attachment.html