<div dir="ltr"><div class="gmail_extra"><span style="font-family:arial,sans-serif;font-size:13px">To summarise we have a few ways then for a contribution day to go:</span><div style="font-family:arial,sans-serif;font-size:13px">
- One theme that is reviewed by group together: This has issue of a large group. At Manchester we had over 11 people - that's too big a group for one contributor to lead through a review without people loosing interest. This also relies on someone being able to assign to themselves.</div>
<div style="font-family:arial,sans-serif;font-size:13px">- A small selection of themes (maybe earlier defined) : This poses issue of how many, prior knowledge.</div><div style="font-family:arial,sans-serif;font-size:13px">
- Everyone gets one and does review: This has a higher fail rate and could impact negatively on the submitter.</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">
Whatever we do more work for admins has to stop. I'm very against adding to your already filled plates.</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">
What about the idea of a theme_doing_it_wrong that could be used to train people on? Think of it as a test everyone has to pass. I know this would take effort to create, but could that be worth it? Could this be a way to get people involved? Or is this a crazy idea that should be dropped?</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Tammie Lister</div><div class="" style="font-family:arial,sans-serif;font-size:13px"></div><br><div class="gmail_quote">
On Mon, Jul 14, 2014 at 5:57 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div style="font-family:arial,helvetica,sans-serif">That's a tough one, not really sure how we would scale :) </div><div style="font-family:arial,helvetica,sans-serif">
<br></div><div style="font-family:arial,helvetica,sans-serif">Main reason, person would need to have an admin privileges, know what he/she is doing and to be trusted as well.</div></div><div class=""><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Jul 14, 2014 at 11:32 AM, Tammie Lister <span dir="ltr"><<a href="mailto:karmatosed@gmail.com" target="_blank">karmatosed@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">That rocks Emil, and I absolutely appreciate all the effort put in by admins to help assign. This happened for us at WordCamp Manchester also, I think we woke Chip up a long list of emails :) Your workloads as admins are huge though, I'd love to find a way to make this easier on you and the new reviewers.</span><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">However, that doesn't solve the times when people are busy. Dealing camp by camp isn't a great way for scalability. People rightly have lives outside of theme reviews and I feel relying on anyone being around isn't great or a good solid long term plan. It's unfair on anyone. I'd love to see every contribution day (a girl can dream) have a group for Theme Review. At that scale, it would be hard to have someone be there all the time.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Thanks,</div><div style="font-family:arial,sans-serif;font-size:13px">Tammie Lister</div><div><div>
<div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Jul 14, 2014 at 5:26 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div style="font-family:arial,helvetica,sans-serif">I will be in San Francisco for 5 days, including the Contribution Days. Tickets can be assigned on the spot if needed.</div></div><div><div>
<div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Jul 14, 2014 at 11:19 AM, Srikanth Koneru <span dir="ltr"><<a href="mailto:tskk79@gmail.com" target="_blank">tskk79@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">A theme that does everything wrong as a training tool, for new reviewers to cut their teeth, they can practice on it and when ready can start reviewing themes. I think that will greatly reduce admin effort in auditing approved themes.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Mon, Jul 14, 2014 at 9:40 PM, Tammie Lister <span dir="ltr"><<a href="mailto:karmatosed@gmail.com" target="_blank">karmatosed@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><div dir="ltr"><div>I wanted to take a little moment to start up a discussion on whether there is anything we can do to make contribution days run a little smoother for theme reviews. </div>
<div><br></div><div>Currently, we have a request post that people post to in order to get a review. Once assigned, they can do the review. This works well if time isn’t poor, often at contribution days we just want to strike while the iron is hot and get people contributing. Our current method also puts extra weight on admins, who already are doing a great amount of work. </div>
<div><br></div><div>Having people post also poses issues when people may not have posted on the blog. They then have to wait to be approved as flagged as potential spam before they can even post. This is a double hurdle.</div>
<div><br></div><div>I absolutely understand why we need to have a process and why we can’t just let anyone review anything without easing them in. However, I do wonder what could be done to improve this process and encourage more people to contribute. We need reviewers and contribution days are a great place to recruit :)</div>
<div><br></div><div>If one of us that can assign our own reviews, is at a contribution day we can assign to ourselves. But, that limits it again. Ideally nobody would need to be there that has any level.</div><div><br></div>
<div>I don’t claim to have the answers, but I have a few possibilities:</div><div>1. Better documentation on how to do your first review. I think Chip, you were going to refresh your great post about that - time willing of course.</div>
<div>2. A ‘how to run a theme review section at contribution day’ section.</div><div>3. Maybe a pool of past themes we can give new reviewers to ‘cut their teeth’? This could also even be a test theme. Maybe to level the playing field one that covers the basics you should know. Possibly a cool sub project? A doing_it_wrong theme.</div>
<div><br></div><div>I’m sure I am missing some great ideas, hence interested what people think. I’d love to find ways we can make this process better and get more contributors as a result.</div><div><br></div><div>What do people think?</div>
<span><font color="#888888">
<div><br></div><div>Tammie Lister</div></font></span></div>
<br></div></div>_______________________________________________<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>
<br></blockquote></div><br></div>
<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>
<br></blockquote></div><br></div>
</div></div><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>
<br></blockquote></div><br></div></div></div></div>
<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>
<br></blockquote></div><br></div>
</div></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></div></div>