Get rid of the "first names" experiment

On larger hosts we could not really convince teams to use the first name
feature, because there will always be some first names that are
ambiguous.

Adding the initial letter of the second name for disambiguation was not
visually appealing enough. Shortening the full name seems the more
appropriate solution.

"First names" had two primary goals: A dense reviewers column on the
dashboard. And saving vertical space on the change page in the
reviewers section.

We will continue to use first names for the reviewer column only, but
not anywhere else. We may re-evaluate how to render the reviewers
column specifically, but this should not affect the entire application.

On the change page we have tweaked the max-width of account chips such
that two reviewer chips will fit next to each other, even when using
full names. The overall width of the metadata column has grown a few
pixels for that.

Also included in this change:
- Adding attention set related utility methods to account-util.
- Tweaking the length of the account label in other places.
- Making sure that the submit requirements component does not
  increase the width of the metadata column too much as currently
  very often seen on android-review.

Screenshots:

gerrit-review change page:
Before: https://imgur.com/a/wuSWEU7
After: https://imgur.com/a/hl6uWOV

gerrit-review dashboard:
Before: https://imgur.com/a/Wb5DJ9o
After: https://imgur.com/a/SudGTAU

android-review change page:
Before: https://imgur.com/a/h9Y5jqT
After: https://imgur.com/a/m1awjpX

Change-Id: I3189e76f6859bbf2bea370cdd976d5abb4b2d0be
17 files changed
tree: 66d1759c84d1a4a1c2abad1d1515133c8376d86e
  1. .settings/
  2. .ts-out/
  3. antlr3/
  4. contrib/
  5. Documentation/
  6. e2e-tests/
  7. java/
  8. javatests/
  9. lib/
  10. modules/
  11. plugins/
  12. polygerrit-ui/
  13. prolog/
  14. prologtests/
  15. proto/
  16. resources/
  17. tools/
  18. webapp/
  19. .bazelignore
  20. .bazelproject
  21. .bazelrc
  22. .bazelversion
  23. .editorconfig
  24. .git-blame-ignore-revs
  25. .gitignore
  26. .gitmodules
  27. .gitreview
  28. .mailmap
  29. .pydevproject
  30. .zuul.yaml
  31. BUILD
  32. COPYING
  33. INSTALL
  34. Jenkinsfile
  35. package.json
  36. README.md
  37. SUBMITTING_PATCHES
  38. version.bzl
  39. WORKSPACE
  40. yarn.lock
README.md

Gerrit Code Review

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

Build Status Maven Central

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 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 8 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8

To run a Ubuntu 20.04 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20

NOTE: release is optional. Last released package of the version is installed if the release number is omitted.