This page documents how to setup ITK developer accounts. See our table of contents for more information.

Gerrit

Anyone may obtain access to the ITK Gerrit Code Review site to propose and review changes. Follow these steps to set up access:

  1. We use Github OAuth, so sign in to your Github account. Note: OAuth currently requests R/W access to GitHub repositories. However, none of the repositories will be modified.
  2. Sign in to http://review.source.kitware.com using the link in the upper right and approve when Github prompts
  3. Set all fields in your profile at http://review.source.kitware.com/#/settings/
  4. Add your ssh public key at http://review.source.kitware.com/#/settings/ssh-keys

Firewall blocks SSH traffic

This is currently out of order, please send patches as messages to the mailing list

If you are stuck behind a firewall that blocks SSH traffic (port 22), the following alternative URL may be used to push patches over HTTP (port 80):

  1. For Gerrit user bob: $ git config --global url.http://bob@review.source.kitware.com/p/ITK.insteadOf bob@review.source.kitware.com:ITK
  2. Generate a password at http://review.source.kitware.com/#/settings/http-password
  3. A password prompt will be presented when pushing patches to Gerrit.

This requires Git 1.6.6 or newer.

Git

Authorized community members may merge patches to the itk.org repositories, but most community members do not need merge permissions. All patches from all community members go through Gerrit Code Review, and patches will be merged by one of the maintainers after it has been reviewed.

Follow these steps to set up access:

  1. Submit your ssh public key to the Kitware Password form
  2. Perform an authentication test:
    $ ssh git@itk.org info