> a) it doesn't integrate as well with our other systems (such as trybots and cq) and b) the UI has some issues.
Is there a tracking bug for all the integration and UI issues? How can folks working on Chromium but without an @google.com help?
Is there a tracking bug for all the integration and UI issues? How can folks working on Chromium but without an @google.com help?
There are three things going on:
1) Rietveld exists
2) A new Polymer-based UI for Rietveld exists
3) Gerrit exists
The bug linked above is about evaluating the ability to make the Polymer-based UI (which is pretty and functional) work on top of Gerrit instead of on top of Rietveld. This is one of the possible paths forward for getting people to use Gerrit, and the one for which external contributors could be the most help.
Other paths forward exist: making Rietveld and the polymer Rietveld UI so good that no one wants to switch to Gerrit anymore; working directly on the Gerrit UI; or convincing devs that the Gerrit UI is good enough. But I think the bug and description above is the path on which external contributors could do the most good.