Hi Dee, Okay, that's sort of what I was expecting the reason to be.
The in-development 1.6 release has access policy control, where you can: 1) Make groups invite-only, which will prevent people from joining 2) Make groups private, which will prevent non-group members from seeing any review requests in them (unless those review request are also targetted to some public groups) 3) Make repositories private, which limits access to selected users or invite-only groups. 4) Segment the Review Board server into several virtual "sites", each with their own configured users, groups, and repositories. These would be, say, http://reviews.example.com/s/site1/, /s/site2/, etc. 1.6 is still in development, but there are nightly builds if you want to try them. We run our own server off the nightlies, so we definitely try to keep it stable. Right now, 1.6 contains the access policies, some bug fixes, and a few new small features. If you wanted to instead work around this in your own install, it's very important to know a few things: 1) You have to modify the actual Review Board code, not just the templates. 2) You're not actually limiting anything. You're just hiding it from plain sight. Any user will still be able to access anything. As for reporting, there's nothing yet, but we have plans to do something in the future. No time table just yet. You can access the database directly, assuming you have it configured to be public. Review Board doesn't lock out any access. However, we can't officially support that. We do support the API. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Mon, Feb 7, 2011 at 3:48 PM, Dee <dlit...@yahoo.com> wrote: > Hi Christian, > > The reason that we want to disable some of the top bar buttons (like > All review requests) is primarily because of our internal rule of who > can access/ view what piece of code. For example, only certain group > of developers have access to the engine code because that portion of > code is more sensitive. Our subversion is configured to support this. > Our concern is that after all the code pieces are routed to the > reviewboard, then a developer can potentially bypass the rule to look > at any piece of diff, e.g. "All review requests" - > view diff. > > I am thinking if there is an easy way to modify the GUI templates, it > will give us what we need for now. If I can save those modified > templates elsewhere, all I have to do is to put them back after an > upgrade? > > Another thing we need is reporting capability, mainly because we need > to have some metrics to give feedbacks to the team and developers on > how we are doing in code review. Some basic metrics like, defect > count; defect count by category, defect duration (from open to close), > etc. I would think this is something that most orgs will need for > measurement and improvements. Is it something that is available now or > is being considered for enhancement? Otherwise, we can make our own > metrics in Excel, but what will be the best way to get the review info > out of the reviewboard? I know there is Web APIs, but is not very > easy. I don't know if reviewboard allows to access its mySql db? It > will be really nice if reviewboard provides some kind of export > feature to Excel or open up the db access. > > Thx, > Dee > > > > > > > > > On Feb 7, 12:29 pm, Christian Hammond <chip...@chipx86.com> wrote: > > Hi Dee, > > > > It's not possible without modifying code. You're completely welcome to > dive > > in and modify things to get what you want, but it will make for harder > > upgrades. > > > > it's always helpful to know what people need and why. You should always > feel > > free to file tickets on each thing you need and the reasons for it. It's > > important to know, though, that at the moment our TODO list is quite > long, > > so I wouldn't be able to give you an ETA on anything. > > > > It's also possible that your reasons for needing this are already covered > by > > something else we're working on. Can you tell me what you want to disable > > and why? > > > > Christian > > > > -- > > Christian Hammond - chip...@chipx86.com > > Review Board -http://www.reviewboard.org > > VMware, Inc. -http://www.vmware.com > > > > > > > > On Mon, Feb 7, 2011 at 8:54 AM, Dee <dlit...@yahoo.com> wrote: > > > I am new to reviewboard. We are looking into using reviewboard in our > > > org. One thing we didn't find from the documentation is how to > > > customize reviewboard GUI. In our case, particularly, we want to > > > disable the some buttons on the top bar (e.g. All review requests). Is > > > it possible to do in version 1.5? and How? > > > > > Thx > > > > > -- > > > Want to help the Review Board project? Donate today at > > >http://www.reviewboard.org/donate/ > > > Happy user? Let us know athttp://www.reviewboard.org/users/ > > > -~----------~----~----~----~------~----~------~--~--- > > > To unsubscribe from this group, send email to > > > reviewboard+unsubscr...@googlegroups.com > > > For more options, visit this group at > > >http://groups.google.com/group/reviewboard?hl=en- Hide quoted text - > > > > - Show quoted text - > > -- > Want to help the Review Board project? Donate today at > http://www.reviewboard.org/donate/ > Happy user? Let us know at http://www.reviewboard.org/users/ > -~----------~----~----~----~------~----~------~--~--- > To unsubscribe from this group, send email to > reviewboard+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/reviewboard?hl=en > -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~----------~----~----~----~------~----~------~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en