at GerritForge we have decided to give a lot more visibility to the Gerrit Community and get early feedback on our roadmap for the next 12 months.
We have always had the mission to donate the 100% of what we do to the OpenSource Community participating to both the Jenkins and Gerrit Code Review projects.
From now on, we want to make our plans also 100% transparent and open to the community, so that anyone can participate early on to the formation and design of the solution.
1. Gerrit multi-site
As anticipated already at the Gerrit User Summit in my talk (recording and transcript at ), we are committed to contributing an OpenSource solution to the problem of having multiple Gerrit Masters active at the same time across multiple sites. The project has been created at  and will continue with the following proposed topics:
1.a) Synchronous replication to an elected "disaster-recovery" site (see ), proposed by Saša
1.b) Support for NATS (see ) as message broker
1.c) Multi-site deployment on K8s, including autoscaling
1.d) Support for sharding across sites
2. Code Review analytics
We have started the initiative of extracting code analytics back in 2016 (see ) and we launched the Gerrit Analytics Wizard (see ) to enable anyone to get started in just a few clicks.
However, from a simple wizard to a real production deployment, there is still a gap we are committed to addressing, with the following improvements:
2.a) Introduction of authenticated access to the Gerrit Analytics dashboards
2.b) Isolation of the Analytics Dashboards by Teams
2.c) Allow selecting multiple repositories per Team to be part of the Analytics extraction
2.d) Allow importing of projects from multiple Gerrit Servers into the Analytics dashboards
2.e) Implement a "pull replication" plugin, to allow Gerrit to automatically synchronize incoming repositories from other Git repositories.
--- * ---
Again, the above list is our "roadmap" for GerritForge, wide open for discussion, contributions, amendments, and voting.
What should you care about what we do? Simply because the union makes Teams stronger: if we join forces in building a solution that is a common interest for the community, we will all benefit from a better, stronger and solid solution for everyone.
We will keep our promise, to continue with our endeavor in developing with full openness, transparency, and collaboration with the entire community.
Your feedback is precious, feel free to have your say (as Saša did already) and give your feedback on the above topics.