As part of vmware, Zimbra has clearly adopted reviewboard as part of the development process. This is probably very helpful.
However, in an increasing number of bug reports, designs, code, or other (unspecified) documents are being referred to from within the reviewboard system.
External developers and contributors have no access to this system.
Even more frustratingly, links to reviewboard documentation is often given with no explanation of the content. The development process is thus at risk of becoming opaque and hidden, in addition to the potential burden of developers being frequently asked to explain what is in the referred-to reviewboard documents.
In the spirit of open collaboration and efficiency, could you please review the usage of reviewboard, and how this fits in with external collaborators, developers, and contributors and bugzilla users, and devise a policy to deal with this.