The EGit and JGit teams heavily use Gerrit for their reviews (and have done long before this was an officially provided service) but the momentum will be gathering shortly with other projects. Some are debating whether to use Gerrit for all changes, or just for external contributions; the advantage of all changes is that it opens the review process up to everyone and is easier to involve changes from outside contributors than if there’s two paths to the repository.
However, the Git Contributions document is a little outdated, and requires the user to assert that:
Contributor asserts on the corresponding bug or in a comment on the Gerrit push record that they:
- authored 100% the content they are contributing
- have the rights to donate the content to EPL
- contribute the content under the EPL
Quite apart from missing the point about a Gerrit push (it’s not a push, it’s a commit) this also misses one of the most valuable parts of the Gerrit process, which is to allow a user agreement to define what the terms of contribution are. Gerrit supports the possibility of having these questions, answered at user creation time, for all subsequent pushes.
In any case, in the meantime, you can configure Git to automatically add
the random IP cruft when you commit the code from the command line. (EGit
1.2 does not appear to observe the
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
For those who are new to Gerrit, you might want to have a look at some of the demos that I have recored and posts that I have written on Gerrit before.