[Ctags-devel] Github collaboration flow

[Vitor A. <vit...@gm...>]

Dear all,

Let me start by apologizing for creating a new thread, but I was not
subscribed to this mailing list before and, as such, can't reply directly
to the original one.

I've been collaborating in the development at Github and I am interested in
having our effort merged into main ctags. I am strongly against the
creation of a fork. Open source initiatives suffer too much from these
splits and I do not want to see this happen also in ctags.

So, let me propose the following flow:

1. Bleeding edge development will/can be done in Github. I feel that we can
take advantage of the fork/pull-request flow to bring in changes, fixes and
updates with much more ease than what is currently possible in Sourceforge.
2. Some (or all) main developers at Github will frequently submit the
changes to Sourceforge, be it through mailing list or by having direct
access to the subversion repository at Sourceforge.
3. Developers at Github synchronize what was submitted at Sourceforge using
git-svn and merge it to guarantee that the differences between the two
trees are always tracked.

IMHO, this will allow everyone to keep their preferred work flow, but still
adding a collaborative alternative development at Github.

If everyone agrees, I would be so bold as to suggest that we start by
sending in the patches for the new verification environment, which will not
break ctags code directly but will benefit the current verification at
Sourceforge. As such, it would be a perfect candidate to test if this flow
would work.

It is just a matter of defining how these patches will be delivered to
Sourceforge.

Thanks for reading,
Vitor