I would be fine with creating a "formal" Theme Review Team "group" and would suggest Simon and I as the ones to "act as management" for the group to start, as long as we are able to add additional "managers" to help out if or when the need arises. I see it as a natural progression to our current access privileges in this case.<br>
<br>If this allows us to better manage and make improvements to the process while still keeping things reasonably open for the general community to continue their involvement then I am all for it!<br><br>I know I would definitely want any reviewer to still be able to review any theme/ticket they choose if we continue with this idea ...<br>
<br>... but, quick question in this regard, if we see "problematic" reviewers would we be able to address them if they are persistent? Restrict their access/privileges/etc. it's not something I would want to do, but something that could be time-sensitive; and, it also must be reversible!<br>
<br><br>Cais.<br><br><br><div class="gmail_quote">On Fri, Oct 1, 2010 at 11:25 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div id=":7v">Now, as nacin said, if you want to formalize a working reviewer group,<br>
we can do that. We'd need somebody (or group of somebody's) to act as<br>
management (cause it ain't gonna be me!) and we'd give them the power<br>
to modify the users in the group. We'd make a "reviewer" group and<br>
give them the power to change the ticket resolutions and assign/accept<br>
tickets and such. I suspect that we don't want some management team<br>
explicitly assigning tickets to reviewers, so any reviewer would be<br>
able to accept any ticket. We'd just leave that step of the normal<br>
process out...</div></blockquote></div><br>