I can remove the regular fetch script from tuleap.

- Experiment gerrit replication
- Define the rules for project namings
- See the impact on Tuleap
- How a gerrit admin manage the Tuleap/gerrit group
- How several Tuleap (or other ALMs) are connected to one central Gerrit server

See discussion https://tuleap.net/plugins/forumml/message.php?group_id=101&topic=17412&list=1

-> Gerrit replication is working fine, the only "shadow" part is the one about ssh key used by Gerrit in order to replicate on remote repositories of Tuleap, but generating an id_rsa pair key in the gerrit user's ssh folder result in a use of this key, so problem solved.

-> Projects can't contain Forge's name anymore, they have to be named like they are on Tuleap side.

-> A Tuleap user with the ssh key of the gerrit's user must be granted the rights to push on the Tuleap repository, otherwise replication fails, and like said above, the naming of projects during gerrit migration must strictly respect the ones on Tuleap side.

-> ? don't understand the point

-> The replication mechanism will try to push on each mirror set up, a failure on push (Gerrit has a repo 'toto' but not Tuleap) doesn't result in a failure on the whole replication event, the only failing repository is skipped. But, if there are two instances of Tuleap with the same repository (eg: same project name and repository name) there is a risk of repository being pushed twice. A good guard would be not to give the Gerrit user on Tuleap the rewind rights on the repository, thereby it will not be able to push if the history doesn't come from this repository; But, if you rewind on Gerrit's Side…