Re: [Ctags-devel] Future of ctags

[Martin d'A. <mar...@gm...>]

Hello Daren,

Please, let me weight in wrt to Git. I am a ctags user and usually a 
silent observer on this list. I used to have similar apprehensions, Git 
is a very complicated SCM. Recently I got involved in a couple of 
projects hosted on GitHub, and discovered the GitHub workflow with 
forked repositories and pull requests. This workflow puts "checks" 
around Git that prevent people from propagating unwanted changes beyond 
their own repository: the pull requests must be reviewed and approved by 
a real person before they are approved for merge into the "central" 
repository. Maybe pull requests can be configured to be automatically 
accepted but I would not turn that on unless there was an extensive 
automated test suite. The projects I participate in on GitHub have both 
human code reviews and automated testing. Project maintainers will not 
review nor accept the pull requests unless the tests have passed. For 
example: 
https://github.com/jenkinsci/validating-string-parameter-plugin/pull/3

So I encourage you to try the GitHub workflow of forked repositories and 
pull requests. To me this is the game changer that finally makes Git 
usable. This workflow does not prevent anyone from deeply messing up 
their local repository and their fork, but it certainly prevents them 
from propagating their mistakes to others, and I can deal with that.

Cheers,
Martin

On 15-02-03 12:31 AM, Darren Hiebert wrote:
> Hello Frank,
>
> I haven't forgotten you. My main apprehensions have been migrating to Git, and hosting off of SourceForge.
>
> We began using git on a project at work and it has been a ride. While I knew how to use Subversion thoroughly, I do not have such a comfort level with git and don't know how to undo problems that occur. We have had changes wiped out at work that had to be restored when folks would push from their local repository that didn't get fully merged with changes from others. This necessitated the only two guys who know how to get us out of the mess in order to restore the files that got overwritten with older files. Considering how often this has happened, I have some trepidation.
>
> Secondly, I prefer that ctags be hosted on SourceForge. I am uncertain how we can use git to do that, but still host on SourceForge. Can you please explain further to me how that can be done?
>
> Darren
>