@Otto ...<br><br>Here's a bit of a wish list you can look into for us:<br><br>(Summary: New column - 3 dropdown options (new, fix, update) auto set by previous results - start work on SVN access for theme authors?)<br>
<br>We would like added to Trac (see screenshot here: <a href="http://frumph.net/stuff/trac.jpg">http://frumph.net/stuff/trac.jpg</a>) a new column for additional status.<br><br>This column is to be auto-set when a theme is uploaded into the system.<br>
<ul><li>New - obvious, new theme</li><li>Fix - set by reviewer prior to the actual review, or possibly by the theme author as a note to reviewer<br></li><li>Update - based on the theme being previously passed and live in the repository<br>
</li></ul>This will help with the manual process until SVN access for theme authors to update their "live" themes is implemented. This is important and we realize is time consuming.<br><br>This is just a start ...<br>
<br>Thanks,<br><br><br>Cais.<br><br><br><div class="gmail_quote">On Wed, Aug 25, 2010 at 7:04 PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.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;">The more we can keep the authors in the loop the better we can communicate with them.<br><br>
As it sits now, the author gets an email from Extend/Themes when the button "mark as old" or "approved" is clicked.<br>
<br>That is all the communication that is done (by defaults) at the moment that I am aware of, adding emails from Trac would be a great help.<br><br>While you are looking at it, can you add an auto-subscribed "update by email" function ... or at least on by default, if possible.<br>
<br><br>Cais.<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Wed, Aug 25, 2010 at 6:57 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;">
Looking at the uploader, I see how it works. Basically, it connects to<br>
trac as "themetracbot" to submit the ticket. The problem is that it<br>
doesn't have access to the user's password at this point, so it can't<br>
create the ticket as the uploader user itself.<br>
<br>
I'll need to examine the trac code to see how it takes the passwords<br>
and such, but I don't see this as unfixable. If the ticket was created<br>
by the uploader user, then that might work better and allow for better<br>
emails and bidirectional communication and such.<br>
<font color="#888888"><br>
-Otto<br>
</font><div><div></div><div><br>
<br>
On Wed, Aug 25, 2010 at 4:17 PM, Otto <<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>> wrote:<br>
> On Wed, Aug 25, 2010 at 4:04 PM, Simon Prosser <<a href="mailto:pross@pross.org.uk" target="_blank">pross@pross.org.uk</a>> wrote:<br>
>> AFAIK when a ticket is created it only has a name, that all the uploader<br>
>> passes it, no owner no email address nothing, we 'claim' the ticket when we<br>
>> assign it to ourselves.<br>
><br>
> Hmph. The data is there when they're uploading, but yes I see now that<br>
> all the tickets are created by some kind of bot system.<br>
><br>
> If the tickets were created by the theme author, then it would be tied<br>
> into the org usernames and emails to them would likely work.<br>
><br>
> I'll see if I can figure out how that uploader process works.<br>
><br>
> -Otto<br>
><br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>