Move this repo to organization

[ffes]

This issue is opened to track all the things needed to move this repo to the organization https://github.com/exuberant-ctags

FYI

The docs: https://help.github.com/articles/transferring-a-repository/ I suggest everybody to read at least the last section about git remote

Interesting read on permissions: https://help.github.com/articles/permission-levels-for-an-organization-repository/

Setup the organization properly

This needs to be done before the move, to make sure things like assignments are not lost

I have invited @fishman and @masatake as Owners of the organization and I created a team Developers. The only way for me to see who should be added to that team is by scanning issues and pull requests and see who has the "collaborator" sign in his posts. @fishman, could you invite whoever I missed.

Devs I invited:

• @dtikhonov
• @vhda
• @b4n
• @blueyed

Move the repository

This has to be done by @fishman

Tarvis-CI

I don't know how much impact this move has on our Travis-CI link. We probably only need to enable it again.

Code cleanup

We need to rename/remove the text "fishman" from various source files and many documentation files, ctags.h and configure.ac being the first to address. I think the file FISHMAN can be deleted.

After the repo is transferred README.md needs to be altered and merge README.exuberant into it.

Additional Repo's

Do we need additional repo's? I can think of a moving the regex based parsers or xcmd out of the core.

[vhda]

I'll start preparing the renaming from fishman-ctags to exuberant-ctags and remove all references to word "fork" from the tree. I'll do that within PR #182.

[masatake]

@ffes, thank you very much.

If I re-design optlib based on the comment from #92 and #89, all optlib(what you wrote the regex based parsers) should be part of ctags. xcmd driver should be part of core but commands invoked from the drivers will be out of tree. In the futuer I will need an repository for the tool building source code based, which will be used in new regression test(to solve #140). About #182, I want you to do as you want.

@ffes , @vhda or @dtikhonov , I have one request which I cannot do well; could you consider contacting and inviting David Fishburn?

[ffes]

@masatake I can contact David Fishburn. No problem.

Dmitri Tikhonov (@dtikhonov) is the original maintainer of the Perl parser and he is already member of our team.

I think I have found all the other original maintainers of parsers on github, but some are more active on github then others.

author	github	parser
David Fishburn	dfishburn	Ant, DosBatch, Flex, JavaScript, MATLAB, SQL, TeX, Vim
Elliott Hughes	enh	C#, Java, Ruby
Elias Pschernig	elias-pschernig	Basic, Python
Joseph Koshy	jkoshy	AWK, SML
Andrew Ruder	aeruder	Objective-C
Vincent Berthoux	Twinside	OCaml
John Lindal	jafl	PHP

The main question is: Are they still interested in ctags?

Note that I deliberately did not put the @ in front of their github account (yet?)
Also note that not much is left of John's original php parser, @b4n rewrote it completely

[vhda]

I've started the rename process in PR #182, but allow me some more time to complete the (first) documentation review.
@ffes could you please add ctags.1 review and update to the todo list?

[ffes]

Should I close this one?
The most important things are dealt with, I think.

New issues/PRs can be opened to address specific problems, like a release plan and a website (content as well as design).