[postgis-devel] is PostGIS ready for git ?

[Paragon Corporation]

> 
> > To recap, Paul would like to move to github, while Regina would like 
> > to not loose trac, but both are ok with moving the code to GIT, 
> > correct ? (refs below)
> > 
I think Paul was okay with it only if we move everything to github.

I can live with any git if it makes core developers lives easier.  I personally don't care for git myself.
I would like to keep trac history if at all possible and it be tied to the revisions, but the idea of keeping trac in a frozen state just for historical purposes is not appealing at all.


> > Mark, Bborie, your pick ?
> >
>>  Absolutely fine with moving the code with git, although I'm not sure 
>>  exactly what the benefits would be of moving to github. Regardless of 
>>  this, it's definitely worth keeping trac around so that bugfix history 
>>  as referenced in commit messages is still available for those who need it.

Mark, Bborie, Nicklas, Olivier.  I would like to hear what you think too as if you are indifferent there is no point in the move.

If you feel strongly about the benefits of git and you are not completely serviced by the current github mirror, then I'm willing to move to any git that makes people most happy.

> I've never proposed moving to GitHub, the thread was about GIT.
Yah I think it was Paul saying no git that is not github adds value to our current operation and to not have to report to 2 bug tracking gods, it's easier to just move the whole shebang to git.
I feel 70% that way.

> Thanks for your comments, my current focus as a new SAC member is on improving the OSGeo trac experience (git integration being part of that).

I think it has value to other groups like Mapserver, GDAL, QGIS maybe.    Mapserver and QGIS are much bigger  projects than we are with more factions, so perhaps it makes more sense.
We are relatively small in comparison.

Strk you are stuck with old-fogey programmers I'm afraid.  You're just too bleeding edge for us, but I do appreciate you kicking the tires so don't take my disagreement as a lack of appreciation :)

How about starting with GEOS?  There will be no dissention there because you and Mat are the main committers and you both see the benefit of git.  GEOS is also a smaller scope so easier to backout if something goes wrong.

Thanks,
Regina