Re: [cclib-devel] Moving to github (Was: github fork)

[Karol M. L. <kar...@gm...>]

Hi,

On Dec 29 2013, Noel O'Boyle wrote:
> Let's move to git on github. Adam are you okay with this?
> 
> Moving to github for Open Babel has meant a lot more commits from 3rd
> parties. I think cclib might benefit here also as it's so easy for
> someone just to patch their fork and send a pull request. I'm on the
> record as not liking using git too much, but if I can survive doing it
> for Open Babel I can do it for cclib too.
> 
> I will set up a cclib organisation there with all of us on it, and see
> whether I can import everything with full history. If this works out,
> Karol, you should probably delete your current cclib repo and fork
> this instead.

I was going to do that next, but if you're taking the initiative then I don't mind :)
The repo I set up already has the full history, albeit only for trunk. I could do
the branches the same way (git-svn), but I hear svn2git does that and all tags
automatically... let me know if you have any problems. I'm not bent on retaining
all the old releases, but we do need the dev branches.
 
> Regarding one of your points, it's github not just git that is key
> here, so I don't think SF's git is really an option.

My point of view, too.

> Regarding the
> other points on SF versus github, let's think about those later as
> this move is largely independent (apart from the bug tracker).

OK. I haven't looked at it much, but noticed this for the tracker: https://github.com/ttencate/sf2github

Cheers,
Karol

-- 
written by Karol M. Langner
Sun Dec 29 19:53:12 EST 2013