Add LICENSE and NOTICE
Add 'tips' script to suggest local configuration
Add 'setup-user' script to configure authorship information

Prompt the user to configure user.name and user.email interactively.
Add 'setup-hooks' script to install local hooks

Fetch the hooks right out of the local clone if possible.  Otherwise
fall back to a project-configured remote repository.
Add 'setup-gerrit' script to configure Gerrit access

Interactively prompt the user with Gerrit setup instructions.
Add 'setup-stage' script to configure topic stage remote
Add 'setup-ssh' script to configure ssh push access

Interactively prompt the user for ~/.ssh/config setup.
Add README instructions and sample configuration
Exclude from source archives files specific to Git work tree

Add the "export-ignore" attribute to all such files.  Remove the
suggestion from the README since this should not be a responsibility
of the including project.
setup-stage: Optionally reconfigure topic stage

When the topic stage has already been configured present the current
configuration and prompt for optional reconfiguration.  While at it,
make the topic stage remote name configurable by the project.
setup-gerrit: Allow ssh-only repo URLs

Honor the $username placeholder in the 'gerrit.url' configuration value.
Configure a separate pushurl only if it is different from the main url.
setup-stage: Allow 'url' without 'pushurl'

Configure a separate pushurl only if it is different from the main url.
Tell Git how to check GitSetup config files

Add a .gitattributes line to match both "config.sample" and any config
file added by the containing project.
Add 'git-gerrit-push' script

Add a script implementing our standard "git gerrit-push" alias.  When
invoked, first check that the current branch is a named topic.  Then
fetch 'master' from the 'gerrit' remote repository so the local
repository can compute a minimal pack to push.  Finally, push the topic
to the 'gerrit' remote as "refs/for/master/$topic".
Allow Catalyst to be initialized with a separate MPI communicator.

For some simulation codes, only a subset of the MPI processes
may use Catalyst but there wasn't any easy way to do that. This
allows Catalyst to be initialized with a different MPI communicator.

Change-Id: Ib09f446653faf60b25c2524241c348d5ad3b1920
Merge branch 'setup' into developer-setup

Add Utilities/GitSetup/ directory using subtree merge from
the general GitSetup repository "setup" branch.
Use vtkProcessModule::GlobalController to figure out the number of procs.

Change-Id: I53b886e232adc0ff3c8b149d1833903033b47349
Use generalized developer GitSetup scripts

Add Utilities/GitSetup/config to configure the generalized scripts for
ParaView.  Remove replaced Utilities/Scripts/*.sh scripts.  Teach
Utilities/SetupForDevelopment.sh to run the generalized scripts.

Change-Id: I39c6cf48eada7d7c1eb4e71c97e52bcbc108ae65
Adding a test for using an MPI sub controller.

Change-Id: If5289af43141fa0159d11d13b1ef6fd6ae3b74a6
Fixed formatting in doxygen, typos, and grammar

Change-Id: I386b8187cdac7aac36b76692ceba844fa7791523