[theme-reviewers] Theme Review Feedback at WPTavern Forum
edward.caissie at gmail.com
Wed Aug 25 22:29:42 UTC 2010
First ... often the Theme Review team members will write: they will "defer"
to myself. I would like to address these deferals by saying, Thank You for
your support. I look at it as standing point for the team and just the one
to take the figurative first bullet with our collective name written on it.
Be that as it may, this is what I am suggesting, and not specifically to
Otto, but to the Theme Authors and other individuals with a vested, or at
least a passing, interest in this project.
Do three (yes count 'em 3 theme reviews) ... and for the 1337
!!!!1111!!!!1!111! Just follow the general outlines and guides as currently
noted starting with the Theme
Review<http://codex.wordpress.org/Theme_Review>page in codex.
Now, if even 10 percent of the authors with themes currently, or recently,
submitted would take up this task the queue would be gone and more
importantly the single most glaring issue that has been previously brought
repeatedly to the attention of the Theme Review team will be addressed ...
why is this taking so long? (Place emphasis anywhere you want on that
question, its still the same issue.)
Now on to the rants, raves, rambling and ... well, they're all quite simply
a massive quantity of complaints brought forward in this thread, I am
putting this to you specifically Otto:
Do those same three reviews, but I ask you to add the following (other are
more than welcome to accept these same tasks):
For each and every one of your complaints, points, or issues that you have
addressed in this thread: make every effort to use the Trac ticket system
(as is) to adhere to the best of your ability and write your comments to
follow what you would expect to be done, what you would expect to see as a
theme author receiving this review, and most importantly (flawed as you
believe it to be) follow the Theme Review process as it is currently set. I
ask this of you for a simple reason: in two months you are essentially the
second person to show any real interest beyond one or two replies ... if you
want to build a community you have to be involved in the community.
Afterward, I personally will go over your reviews, not to question them but
to learn from them. If all of these points are valid, and I am not arguing
for or against anything in particular ... the proof will be in the works. I
will also strongly suggest every Theme Review team member read your reviews
as well. This is an opportunity to offer examples of improved review
As much as it may seem we have been terse and possibly harsh with our
reviews and commincation to the theme authors, our goals were: play catch-up
on the back log; and, provide insights into the theme's viability to be
included in the WordPress.org repository as we understood the guidelines and
standards. We did not, and I would say, do not view ourselves as theme
testers; we strive to be more quality assurance than anything else ... if we
have been over-zealous then after you have completed these reviews yourself
feel free help temper our zeal.
Come on, Otto ... and every other reader of this ... join this community
project and help us improve.
Just remember, if you think its flawed going in, you will absolutely without
a doubt find many, many flaws ... try to start with an open mind and a fresh
We will welcome all contructive criticism offered in a helpful manner. I'm
just asking you experience the process first.
On Wed, Aug 25, 2010 at 5:24 PM, Chip Bennett <chip at chipbennett.net> wrote:
> On Wed, Aug 25, 2010 at 4:11 PM, Otto <otto at ottodestruct.com> wrote:
>> On Wed, Aug 25, 2010 at 3:28 PM, Chip Bennett <chip at chipbennett.net>
>> > But keep this in mind: the Theme Review team has absolutely no control
>> > the Theme upload process. We can't do anything about it. Maybe you can,
>> > which would be invaluably helpful.
>> BTW, I wanted to make something clear because a lot of people
>> misunderstand my role here.
> I appreciate that - though I think that I personally do understand your
> role, and your stance.
>> Yes, I probably can make changes to whatever piece is needed. I'm a
>> developer, I now am in a position to make those changes, and I have
>> more or less total access. But I'm not the benevolent dictator here. I
>> don't get to make changes unilaterally.
>> This is a community and in order for me to keep it that way, I have to
>> have directives issued to me in a way that allows me to justify a
>> change. Either somebody high up asks me to do it, or there's a clear
>> community need, or a group of people in the community request a
>> specific change... Something.
> There are very few active people in the Theme Review team right now.
> Edward Caissie (Cais) is basically the acting Team leader. Phil (Frumph) is
> incredibly active. Fingli does quite a few reviews. Simon Prosser adds
> input, some Trac help, and reviews.
> That's pretty much it.
> So, I don't know: maybe we can organize a #wp-themes chat, and create a
> plan for going forward with some changes to the process and tools, that we
> could have you implement?
> I don't have any personal preferences for the workflow. I just want a
> system that works for everyone involved. (Although, if that workflow could
> somehow include SVN commit access for Theme developers, I think that would
> be simply awesome.) I also don't want to presume to speak for the rest of
> the team (though I'd defer to Cais, if he wants to speak on behalf of the
>> I can't just go change anything I want in the way I want it to be. And
>> this not because I wouldn't get away with it, because I probably
>> would. I don't want to do that because I really believe in making a
>> better community and I want things to be done to benefit that
>> community, by that community. Who actually implements a change is
> Likewise. So: let's figure out how to move forward with respect to
> improving the process and workflow. Let me know how I can help. In the
> meantime, I'll be reviewing Themes, and working on improving the Codex.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the theme-reviewers