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

[Adam T. <ate...@gm...>]

Hi Noel and others,

I think moving cclib development to Github is a great idea. Let me know if
there is anything I can do to help.

Adam



On Sun, Dec 29, 2013 at 1:42 PM, Noel O'Boyle <bao...@gm...> 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.
>
> 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. 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).
>
> - Noel
>
> On 29 December 2013 05:58, Karol M. Langner <kar...@gm...>
> wrote:
> > Hi Noel,
> >
> > It seems that Sourceforge actually now supports git repositories, if we
> wanted to convert and stay there.
> > The way to do it is to 'add' a git repository by adding the appropriate
> 'app' in the admin panel,
> > which creates an empty repository. The svn tree can then be converted to
> git and pushed to that.
> >
> > I don't think we could resaonably use both repositories for development,
> so one would need to be
> > read-only, and I think we should keep the svn repo online for users that
> have that set up.
> >
> > Meanwhile, to start off I pushed the trunk to a repostiory on github:
> https://github.com/langner/cclib
> > I will keep this up to date and would be in favor of moving mostly to
> github in the future.
> > If we went that route, I suppose the sf repo would be read-only.
> Additional things things to consider:
> > - what to do with current wiki / web page
> > - what to do with current branches
> > - what to do with previous releases/tags
> > - what to do with current and old issues in the tracker
> > - what to do with mailing lists
> >
> > What do you think? I believe you did something similar for OpenBabel at
> some point. How did that work?
> >
> > Cheers,
> > Karol
> >
> > On Nov 08 2013, Karol M. Langner wrote:
> >> Hi guys,
> >>
> >> Nice to see this. And Clyde -- nice project!
> >>
> >> Noel, how recently have you looked at the github interface for Windows?
> If I rememeber
> >> correctly, several weeks ago they made some significant improvements.
> >>
> >> I don't know about mercurial, but they do support svn now.
> >>
> >> Before moving to github, however, we could set up an "official" fork --
> I'd be happy to do it,
> >> and try to suck in Clyde's contribution via that. BTW, I'm +1 on moving
> to git. I always struggle
> >> with the sourceforge svn tools.
> >>
> >> - Karol
> >>
> >> On Nov 08 2013, Noel O'Boyle wrote:
> >> > (ccing to the list)
> >> >
> >> > Hi Clyde,
> >> >
> >> > Thanks for letting me know. You're free to do this of course - might
> >> > be good to make it clear that this is an "unofficial" fork though.
> >> > Just to save people contacting us asking about ASE.
> >> >
> >> > Naturally for us we would prefer if you contribute any fixes directly
> >> > to cclib. In this case, if any of our units are incorrect we would
> >> > like to fix our source.
> >> >
> >> > This might be the push we need to consider moving to Github. Git on
> >> > Windows though is a joke. The interface is not a lot better than the
> >> > old CVS one (you probably don't remember this) which also used to call
> >> > out to the command line. If only Github ran mercurial...:-/
> >> >
> >> > - Noel
> >> >
> >> >
> >> >
> >> > On 7 November 2013 15:05, Clyde Fare <cly...@gm...> wrote:
> >> > > Hi Noel
> >> > >
> >> > > I've got a git repository with cclib in it because I am faffing
> about trying
> >> > > to put together a bunch of python of tools associated with quantum
> chemistry
> >> > > to use with the ipython notebook. In my version I've changed the
> units that
> >> > > cclib uses in it's conversions because I want the various parsers I
> use to
> >> > > all use the same units.
> >> > >
> >> > > As I wanted an easy way of loading the package into Anaconda I've
> put the
> >> > > result on github here:
> >> > > https://github.com/Clyde-fare/cclib
> >> > >
> >> > > Github  have a very fork-me friendly mentality but it occurred to
> me that
> >> > > you might not be so happy that I'd done this so just wanted to
> check in with
> >> > > you - I could write a version that means the units used are chosen
> based on
> >> > > some flag (and your initial units are the default) which would mean
> I could
> >> > > keep my version synced with yours if that's something you would
> prefer.
> >> > >
> >> > > Cheers
> >> > >
> >> > > Clyde
> >> > >
> >> >
> >> >
> ------------------------------------------------------------------------------
> >> > November Webinars for C, C++, Fortran Developers
> >> > Accelerate application performance with scalable programming models.
> Explore
> >> > techniques for threading, error checking, porting, and tuning. Get
> the most
> >> > from the latest Intel processors and coprocessors. See abstracts and
> register
> >> >
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> >> > _______________________________________________
> >> > cclib-devel mailing list
> >> > ccl...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/cclib-devel
> >>
> >> --
> >> written by Karol M. Langner
> >> Fri Nov  8 15:32:34 EST 2013
> >
> > --
> > written by Karol M. Langner
> > Sun Dec 29 00:39:40 EST 2013
>