Documentation: Move services page to infrastructure section

The services page documents various services and tools which are
provided by the project. It's more related to the infrastructure and
less related to the community section.

Thus, move it to the infrastructure section.

Change-Id: I0ca2aba8ae817cf874367fa17e567065aec99a93
Signed-off-by: Felix Singer <felixsinger@posteo.net>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/62442
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Martin L Roth <martinroth@google.com>
Reviewed-by: Paul Menzel <paulepanter@mailbox.org>

2 files changed, 50 insertions, 0 deletions

diff --git a/Documentation/infrastructure/index.md b/Documentation/infrastructure/index.md
index 755709ece4..744809f2fd 100644
--- a/Documentation/infrastructure/index.md
+++ b/Documentation/infrastructure/index.md
@@ -2,6 +2,11 @@
 
 This section contains documentation about our infrastructure
 
+## Services
+
+* [Project services](services.md)
+
+
 ## Jenkins builders and builds
 * [Setting up Jenkins build machines](builders.md)
 * [Coverity Scan integration](coverity.md)
diff --git a/Documentation/infrastructure/services.md b/Documentation/infrastructure/services.md
new file mode 100644
index 0000000000..a7f13eefb5
--- /dev/null
+++ b/Documentation/infrastructure/services.md
@@ -0,0 +1,45 @@
+# Accounts on coreboot.org
+
+There are a number of places where you can benefit from creating an account
+in our community. Since there is no single sign-on system in place (at this
+time), they come with their own setup routines.
+
+## Gerrit code review
+We exchange and review patches to the code using our [Gerrit code review
+system](https://review.coreboot.org).
+
+It allows logging in with a Google or GitHub account using OAuth2 as well
+as with any OpenID provider that you may already use.
+
+On the [settings screen](https://review.coreboot.org/settings) you can register
+all your email addresses you intend to use in the context of coreboot
+development so that commits with your email address in them are associated with
+you properly.
+
+### https push access
+When using the https URLs to git repositories, you can push with the "HTTP
+Credentials" you can have Gerrit generate for you on that page. By default,
+git uses `$HOME/.netrc` for http authentication data, so add a line there
+stating:
+
+    machine review.coreboot.org login $your-user-name password $your-password
+
+### Gerrit user avatar
+To setup an avatar to show in Gerrit, clone the avatars repository at
+https://review.coreboot.org/gerrit-avatars.git and add a file named
+$your-user-ID.jpg (the user ID is a number shown on the [settings screen](https://review.coreboot.org/settings)).
+The image must be provided in JPEG format, must be square and have at most 50000
+bytes.
+
+After you push for review, the system will automatically verify your change
+and, if adhering to these constraints, approve it. You can then immediately
+submit it.
+
+## Issue tracker
+We have an [issue tracker](https://ticket.coreboot.org) that is used for
+coreboot and related code, such as libpayload, as well as for the project's
+infrastructure.
+
+It can be helpful to refer to issues we track there in commit messages:
+
+    Fixes: https://ticket.coreboot.org/issues/$id