Google Git
Sign in
gerrit / gerrit / 6671edcd1ad4e3638edea37c6e8503e67920d790
commit6671edcd1ad4e3638edea37c6e8503e67920d790[log] [tgz]
authorEdwin Kempin <ekempin@google.com>Wed Apr 24 11:22:53 2019 +0200
committerEdwin Kempin <ekempin@google.com>Thu May 02 08:15:54 2019 +0200
tree8dd697fb374794d1c9e22567bc66af1292110723
parentac69e582ed68b740ff51a3051f0a1c7c863cdeae [diff]
Document Gerrit community roles

There are many ways to engage with the Gerrit project. Over the years we
gained a common understanding of powers, responsibilities and tasks that
come with certain roles, but we never wrote them formally down. This
change attempts to document the current situation. Going forward we plan
to establish clearer project governance. To make it transparent what
exactly is changing it's important to document the current situation
first. Then follow-up changes can document the new processes and by
looking at the diffs one can easily see what's changing.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I7e80181022cb8efc6a6ba39400a3cc60a3c3a32c
3 files changed
tree: 8dd697fb374794d1c9e22567bc66af1292110723
  1. .settings/
  2. antlr3/
  3. contrib/
  4. Documentation/
  5. java/
  6. javatests/
  7. lib/
  8. plugins/
  9. polygerrit-ui/
  10. prolog/
  11. prologtests/
  12. proto/
  13. resources/
  14. tools/
  15. webapp/
  16. .bazelproject
  17. .bazelrc
  18. .editorconfig
  19. .git-blame-ignore-revs
  20. .gitignore
  21. .gitmodules
  22. .mailmap
  23. .pydevproject
  24. BUILD
  25. COPYING
  26. INSTALL
  27. README.md
  28. SUBMITTING_PATCHES
  29. version.bzl
  30. WORKSPACE
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status

Objective

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.

Documentation

For information about how to install and use Gerrit, refer to the documentation.

Source

Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.

Reporting bugs

Please report bugs on the issue tracker.

Contribute

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.

Getting in contact

The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.

The Developer Mailing list is repo-discuss on Google Groups.

License

Gerrit is provided under the Apache License 2.0.

Build

Install Bazel and run the following:

    git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
    cd gerrit && bazel build release

Install binary packages (Deb/Rpm)

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>]

Use pre-built Gerrit images on Docker

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.