tree 67ca40bef927188a7f9b871cb36ebc4b427ed90b
parent 99a192ee4155b926cb6f94f8b53caae136bfb520
author Luca Milanesio <luca.milanesio@gmail.com> 1405529550 +0100
committer Luca Milanesio <luca.milanesio@gmail.com> 1406034938 +0000

GitHub organisations plugged as GroupBackend

Initial support for using GitHub organisations
plugged into Gerrit as GroupBackend and thus visibles from:
- User’s group membership (/#/settings/group-memberships)
- Project’s access control (/#/admin/projects/All-Projects,access)

By typing github/OrgName in the Project’s access screen you will see
listed all the organisations that your user belongs to and you can then
assign Gerrit project permissions to it.
The members of that organisation will automatically be granted 
permissions to the Gerrit project. 

Membership is resolved at runtime by making a GitHub API call using
the current user scope, with a cache TTL of 15’. This means
that only 4 GitHub calls/h per user can be actually consumed 
by group resolution. Changes on GitHub organisation membership
will be then detected by Gerrit after at least 15’.

Gerrit cache for GitHub organisations membership is called:
github-plugin-organisations.

Change-Id: I051cd44c978b7f25a5508a33c298fd18b904177e