Working with gerrit

To configure Gerrit, do the following steps:

Enter Gerrit site and register (using OpenID, e.g. Google Account)
```
http://siekiera.mimuw.edu.pl:8082/
```
In settings, open SSH Public Keys tab. Add the public key from the machine you're using for development (cat .ssh/id_rsa.pub) If you don't have one it can be generate using
```
ssh-keygen -t rsa
```
after invoking that command there will be two files in your .ssh directory : id_rsa and id_rsa.pub. Move id_rsa.pub to contain your real email address.

Clone write access version of the repository

git clone --recursive ssh://<login>@siekiera.mimuw.edu.pl:29418/paal

Download commit message hook. It will add a line 'Change-Id: ...' to every commit message. This is required by Gerrit and allows keeping many versions of the same commit.
```
scp -p -P 29418 <login>@siekiera.mimuw.edu.pl:hooks/commit-msg <projectDir>/.git/hooks/
```
To send something for review, use a command:
```
git push origin HEAD:refs/for/master
```
If you want to update your commit (e.g. reviewers requested some changes) do:
```
git commit -a --amend
git push origin HEAD:refs/for/master
```
When commit is accepted, and you have the privileges to push to master, do:
```
git push origin HEAD:master
```

You can find more info about using Gerrit here:

http://gerrit-documentation.googlecode.com/svn/Documentation/2.6/intro-quick.html

General rules

The code review is divided into four parts. Each part is reviewed separately. Parts:
- Interface and Problem Description - this phase includes the public interface and main functions from private interface, the algorithm should be designed. The documentation consists of problem description (this helps understanding the interface). All declarations must compile, templates should be instantiated in test or example.
- Tests - both unit tests (short test) and efficiency test (long tests). Test should fail (use BOOST_AUTO_TEST_CASE_EXPECTED_FAILURES).
- Implementation
- Documentation in the standard form.
In order to update your working copy type
```
git fetch
git rebase origin/master
```
and follow the instructions. Particularly never use git pull
If you have no experience in using git or in case of any problems please contact wygos.nosp@m.@mim.nosp@m.uw.ed.nosp@m.u.pl