Re: Issue 1885 in reviewboard: Permissions to restrict viewing of all commits and closing review requests

2011-03-31 Thread reviewboard

Updates:
Status: Fixed

Comment #3 on issue 1885 by trowb...@gmail.com: Permissions to restrict  
viewing of all commits and closing review requests

http://code.google.com/p/reviewboard/issues/detail?id=1885

These are all possible now with 1.6

- Invite-only groups can handle the cases where you want to limit who's in  
a group, and who sees a review request

- Repositories have group and user-level access lists
- You can keep developers from closing reviews for their own code by using  
--submit-as to post their code under a different username.


--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.



Re: Issue 1885 in reviewboard: Permissions to restrict viewing of all commits and closing review requests

2011-01-27 Thread reviewboard


Comment #2 on issue 1885 by chip...@gmail.com: Permissions to restrict  
viewing of all commits and closing review requests

http://code.google.com/p/reviewboard/issues/detail?id=1885

The in-development 1.6 has invite-only groups, allowing you to limit who  
can be in the group. It also has the ability to restrict access to a  
repository, to one or more invite-only groups or to specific users.


There is nothing for limiting who can close out a review request. I'm not  
sure that's something we'll be doing for 1.6, but we'll consider it. Most  
likely, that will wait, though, as everyone's going to have different rules  
for how that should work (we've already seen many very different,  
incompatible requests).


Both the original request and the reply list many feature requests. Please  
file one bug report per request so that we can close them out when the  
particular feature is implemented.


--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.



Re: Issue 1885 in reviewboard: Permissions to restrict viewing of all commits and closing review requests

2011-01-26 Thread reviewboard


Comment #1 on issue 1885 by ruben.st...@mevis.fraunhofer.de: Permissions to  
restrict viewing of all commits and closing review requests

http://code.google.com/p/reviewboard/issues/detail?id=1885

I would appreciate that feature too. At our institute there are projects  
whose code is restricted to a small group of people working on that  
project. Pushing all code as post-commit review to review-board would  
enable everyone to see that code.
I would add to the request above a request to restrict permissions  
regarding specific repositories. Otherwise one would be able to see code  
you have no svn-access to by simply expanding the diff in the diff-view.


From that, more paranoid, point of view I would also appreciate to let  
every user provide his own repository credentials instead of having one  
fixed account communicating with the repository.


--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.