ITK/Git/Account: Difference between revisions

From KitwarePublic
< ITK‎ | Git
Jump to navigationJump to search
No edit summary
No edit summary
Line 1: Line 1:
This page documents how to setup ITK developer accounts.
This page documents how to setup ITK developer accounts.
See our [[ITK/Git|table of contents]] for more information.
See our [[ITK/Git|table of contents]] for more information.
'''Note''': Google is currently dropping support for OpenID authentification through Google accounts.
While currently registered Gerrit users ''can still use their account'', '''new''' Gerrit account
registrations with Google currently face the error:
  ''400. That's an error. OpenID auth request contains an unregistered domain.''
[[File:OpenID400Error.png]]
We are currently upgrading the Gerrit infrastructure, and GitHub-based authentifications will soon
be possible. Until that time, it is suggested that ''new'' Gerrit accounts be made with a Yahoo account. 


=Gerrit=
=Gerrit=
Line 19: Line 7:
Follow these steps to set up access:
Follow these steps to set up access:


# Get an [http://openid.net/get-an-openid/ OpenID]
# We use [https://github.com/ Github] OAuth, so sign in to your Github account
# Register at http://review.source.kitware.com using your OpenID (link in upper right)
# Sign in to http://review.source.kitware.com using the link in the upper right and approve when Github prompts
# Sign in
# Set all fields in your profile at http://review.source.kitware.com/#/settings/
# Set all fields in your profile at http://review.source.kitware.com/#settings
# Add your ssh public key at http://review.source.kitware.com/#/settings/ssh-keys
# Add your ssh public key at http://review.source.kitware.com/#settings,ssh-keys


===Firewall blocks SSH traffic===
===Firewall blocks SSH traffic===

Revision as of 19:20, 26 March 2015

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

Gerrit

Anyone may request 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
  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

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