commit | de2c7e10c7011a1a3c64c22715c0fc19677070f2 | [log] [tgz] |
---|---|---|
author | Edwin Kempin <ekempin@google.com> | Mon May 06 11:57:24 2019 +0200 |
committer | Edwin Kempin <ekempin@google.com> | Wed Jul 24 10:02:50 2019 +0200 |
tree | cd85037b5d90147b83cf78b27aff8810e7e76df1 | |
parent | 210f95aa44f75c2bac966544c83266f5757e416a [diff] |
Define clear criteria for maintainer election At the moment the election process for new maintainers is not clearly defined: * Is consensus reached if some of the maintainers do not vote? * How long must a nomination stay open before a new maintainer can be accepted? Make this clearer and require that: * nominations stay open for at least 14 calendar days * there are at least 5 positive votes * there are no negative votes (during the 14 days) Specifying this is important if we consider that we have some inactive maintainers that likely don't take part in votes and in this situation the maintainer election should not get stalled waiting on their votes. If there are negative votes that are considered unjustified, the engineering steering committee may get involved to decide whether the new maintainer can be accepted anyway. Being able to escalate negative votes to the ESC is important to avoid that a single maintainer can block the whole process. Bug: Issue 11069 Signed-off-by: Edwin Kempin <ekempin@google.com> Change-Id: I888897f8f2ee5f35436acee8885d6ed994f750e2
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.