Re: [Ctags-devel] Future of ctags

[Jan L. <li...@ma...>]

Darren Hiebert <dhi...@us...>:
> If I understand you correctly, you are proposing that the source code no
> longer be hosted at SourceForge, which is what I would prefer. What are the
> reasons that you believe that SourceForge cannot provide the support
> necessary?

I also want to chime in with a preference for GitHub. GitHub is essentially
were most of the developers are nowadays, and with good reason. I have used
SourceForge for years before GitHub was around, but now that GitHub has shown
how convenient project hosting can be it is hard to go back to SourceForge,
and every time I have to do it I find the SF interface very cumbersome.
Especially contributing a quick patch is dead easy with GitHub, you just clone
the repository, commit your patch, and send a pull request. There are even
tools to do this with a few commands on the command line.

And this is even without all the benefits that Git itself brings for
developers. I myself would not want to miss them, I even use subversion
repositories (almost) exclusively through git-svn instead of the normal svn
client. But if someone does want to stick with the svn client for some reason
it is possible to access GitHub repositories as subversion repositories. I
don't think that is possible on SourceForge.

So the short version is that a project hosted on GitHub will not only be more
convenient for the core developers, but will almost certainly also attract a
lot more outside contributions.

-Jan

-- 
-[ OpenPGP key ID: 00A0FD5F ]-
But I don't have to know an answer. I don't feel frightened by not knowing
things, by being lost in the mysterious universe without having any purpose
— which is the way it really is, as far as I can tell. Possibly. It doesn't
frighten me.
                -- Richard Feynman