Gerrit

Note that there is already a zookeeper plugin that was created some years ago, but is empty because the initial implementation never got submitted.

[Empty comment from Monorail migration]

Do you have more context / details?

JGit has a DfsRefDatabase concept that I would expect to mean that Gerrit doesn't need to be aware of how references are stored.

https://gerrit-review.googlesource.com/c/gerrit/+/237177

https://gerrit.googlesource.com/plugins/multi-site/+/refs/heads/master/DESIGN.md#global-ref_db-plugin says this plugin does consensus at the Gerrit level.

I strongly recommend doing consensus at the JGit level instead.

A design document was requested for this feature.

[Monorail components: ESC]

Change moved to https://gerrit-review.googlesource.com/c/gerrit/+/237606

[Empty comment from Monorail migration]

Why was this set to "submitted"? The change mentioned above [1] is still open, and the zookeeper-refdb plugin repository [2] is still empty. The implementation has only been submitted on the GerritForge fork [3].

[1] https://gerrit-review.googlesource.com/c/gerrit/+/237606
[2] https://gerrit.googlesource.com/plugins/zookeeper-refdb/
[3] https://review.gerrithub.io/q/project:GerritForge/plugins_zookeeper+status:merged

You are right, I got confused with the change in multi-site.
This looks like referring to the change in Gerrit core and the associated design document. Will update the component to Gerrit backend.

[Monorail components: -plugins>multi-site Backend]

Can this be closed now?

[Empty comment from Monorail migration]

[Monorail components: SteeringCommittee]

[Monorail components: -ESC]

Edits were made to reflect the following in Monorail: auto-CCs.