Posted by eliza411 on April 27, 2011 at 4:09pm
We have several talented, experienced themers planning to attend the PDX user group's Code review/Project application meet up in a couple of weeks. I wanted to pull up a list of the project applications that were requesting review of a theme (rather than a module) as I'm getting the message that people are more comfortable reviewing in their domain, but I don't see an easy way to do that. Searching for the word theme includes lots of modules.
I'm wondering, is there enough value in the distinction for others to change the component field so that applicants can indicate whether their project is a theme, project, install profile, or other. The intent isn't to box anyone in, just to find more focused ways of getting reviewers involved.
Comments
+1
I think that would be a great idea. I recently went through all of the projects that are seeking reviews to provide a list of just the themes that are there.
The result was cross posted to a couple of theme related groups and can be seen here http://groups.drupal.org/node/145794
Having a filter by category would make this task much easier!
Dreamleaf Media
"PAReview: Theme" tag
Using tags or components to pick out more specific types of projects awaiting review (e.g. themes) was recently suggested here:
http://groups.drupal.org/node/145289#comment-486249
I think components would be better than tags for focusing on themes, but since tagging is something we can all do right now, I'm going to go ahead and start tagging themes awaiting review with "PAReview: Theme" and suggest others do the same.
i've been filtering via
i've been filtering via "PAReview: Theme" tag, but it took me a while to figure that out. I think a component would be much more intuitive, so I'd favor that over the existing tag.
Re:
I totally agree; it's quite a time-saver being able to focus on themes, as I'm not really comfortable reviewing modules yet.