At first look I would agree a "Reviewer" group may be the better method to use, at least until something else can be sorted out, hopefully via automation.<br><br>The only concern, as Otto is bringing to light, is we would need an Admin to manage the group.<br>
<br>I'm hoping to see more people get involved in the process, so it may become cumbersome for a non-reviewer to manage this group; which leads to the question: is it possible for one or two of the group's members be given group-admin privileges?<br>
<br><br>Cais.<br><br><div class="gmail_quote">On Thu, Sep 2, 2010 at 5:23 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</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 class="gmail_quote"><div class="im">On Thu, Sep 2, 2010 at 3:47 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">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>On Thu, Sep 2, 2010 at 3:04 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
</div><div>> 1) Trac users cannot assign themselves their own tickets (this should be<br>
> enforceable through Trac, hopefully once Otto fixes associating tickets with<br>
> actual Trac usernames, rather than "themetracbot")<br>
<br>
</div>This turns out to be trickier than it seemed at first. So, it might<br>
take me a while, don't expect quick turnaround.<br>
<br>
Expect me to make a test ticket or two when trying this out. Just ignore them.<br>
<div><br>
> 2) keywords can only be modified by admins (we don't need to be modifying<br>
> these ourselves anyway, do we?)<br>
<br>
</div>Trac considers priority, assignment, keywords, etc to all be part of<br>
the same set of permissions. Exceptions: description field and cc<br>
field have their own permissions.<br>
<br>
Only way I can think of preventing this problem is to define who is a<br>
reviewer. This can be done, but it requires management by an admin to<br>
add/remove permissions from users (actually, you can use a reviewer<br>
group mechanism, but you still have to be an admin to do it).<br>
<br>
If you want to create a reviewers group and remove the ability of<br>
normal users to resolve tickets (reserving that to the reviewers<br>
group), well then that's something ya'll have to decide.<br>
<br>
You can see the full list of trac permissions and how they work here:<br>
<a href="http://trac.edgewall.org/wiki/TracPermissions" target="_blank">http://trac.edgewall.org/wiki/TracPermissions</a></blockquote><div><br></div></div><div>Hmm, perhaps a "Reviewers" group with custom permissions is the best/easiest way to go?</div>
<div><br></div><div>Then, everyone else can only add comments to tickets, and not change their status/keywords/owner/etc.</div><div><br></div><div>What does everyone else think?</div><div><br></div><font color="#888888"><div>
Chip </div></font></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br>