46 lines
1.9 KiB
Markdown
46 lines
1.9 KiB
Markdown
|
# Accounts on coreboot.org
|
||
|
|
|
||
|
|
There are a number of places where you can benefit from creaating 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
|