<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>plugin-support-comiceasel .. I like that idea ;)</DIV>
<DIV> </DIV>
<DIV>but yeah can’t the uploader find “markers” to determine the support and
auto generate the tags for it?</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=chip@chipbennett.net
href="mailto:chip@chipbennett.net">Chip Bennett</A> </DIV>
<DIV><B>Sent:</B> Friday, August 23, 2013 10:49 AM</DIV>
<DIV><B>To:</B> <A title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">Discussion list for WordPress
theme reviewers.</A> </DIV>
<DIV><B>Subject:</B> Re: [theme-reviewers] Tags and
description.</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV dir=ltr>Can I ask why declaring support for WooCommerce (or any other
commercial Plugin, such as any other commercial e-commerce Plugin, or Gravity
Forms, or whatever) would not be acceptable? I think if the following are true,
that should be sufficient:
<DIV> </DIV>
<DIV>1) The Plugin for which support is declared is GPL/compatible</DIV>
<DIV>2) Plugin support is declared in an approved/standardized manner, such as
<B>add_theme_support( 'plugin-name' )</B></DIV>
<DIV>3) The Plugin keyword conforms to an approved convention, such as
"<B>plugin-support-{plugin}</B>" (note: "bbpress" and "buddypress" could be
converted to "plugin-support-bbpress" and "plugin-support-buddypress")</DIV>
<DIV> </DIV>
<DIV>I see this as a win-win for developers and for end users. Simply using a
"e-commerce" tag probably isn't all that helpful, because more than likely,
users will already have an e-commerce Plugin solution in mind, and will be
looking for Themes that integrate support for their chosen Plugin,
explicitly.</DIV>
<DIV> </DIV>
<DIV>The biggest issue here is scope/implementation on WPORG's end. But perhaps
some of this could be automated, rather than all hard-coded in the WPORG
franken-code.</DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Fri, Aug 23, 2013 at 1:38 PM, Emil Uzelac <SPAN
dir=ltr><<A href="mailto:emil@uzelac.me"
target=_blank>emil@uzelac.me</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>@Ulrich e-commerce is fine, WooCommerce is not. None of us here
have
<DIV>final saying in any of this and all can speak there minds. All I said was
from</DIV>
<DIV>WPORG point of view, not mine :) <BR>
<DIV> </DIV></DIV></DIV>
<DIV class=HOEnZb>
<DIV class=h5>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Fri, Aug 23, 2013 at 2:16 AM, Ulrich Pogson <SPAN
dir=ltr><<A href="mailto:grapplerulrich@gmail.com"
target=_blank>grapplerulrich@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>
<DIV>@Emil Who makes the final decision? So is this discussion has no point
because we cannot influence anything?</DIV></DIV>
<DIV>
<DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On 23 August 2013 09:00, Emil Uzelac <SPAN
dir=ltr><<A href="mailto:emil@uzelac.me"
target=_blank>emil@uzelac.me</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<P dir=ltr>:-)</P>
<DIV>
<DIV>
<DIV class=gmail_quote>On Aug 23, 2013 1:45 AM, "Srikanth Koneru" <<A
href="mailto:tskk79@gmail.com" target=_blank>tskk79@gmail.com</A>>
wrote:<BR type="attribution">
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>+1 to Emil, just don't put "fluid grid system" in the
definition of responsive.<BR></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Fri, Aug 23, 2013 at 12:13 PM, Emil Uzelac
<SPAN dir=ltr><<A href="mailto:emil@uzelac.me"
target=_blank>emil@uzelac.me</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<P dir=ltr>Absolute no to WooCommerce or any other commercial site.
This is the policy that was laid before us. I for one will keep that.
Responsive and Accessibility are in, let us pass that. No surveys, we
will not carry this more than we already did. I dislike long
discussion over nothing. Community was involved, provided with the
chance to talk, that will wrap this up. And note that it is not up to
us, we don't hold the final word B-)</P>
<DIV>
<DIV>
<DIV class=gmail_quote>On Aug 23, 2013 1:23 AM, "myazalea" <<A
href="mailto:myazalea@hotmail.com"
target=_blank>myazalea@hotmail.com</A>> wrote:<BR
type="attribution">
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV>
<DIV>Big no to a woocommerce tag since its commercial and would be
favoring it over other plugins.</DIV>
<DIV> </DIV>
<DIV>yes to some sort of ecommerce or shop tag</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>
<DIV style="COLOR: #575757; FONT-SIZE: 75%">Skickat från min Samsung
Mobil</DIV></DIV><BR><BR><BR>-------- Originalmeddelande
--------<BR>Från: Ulrich Pogson <<A
href="mailto:grapplerulrich@gmail.com"
target=_blank>grapplerulrich@gmail.com</A>> <BR>Datum: 23-08-2013
8:17 (GMT+01:00) <BR>Till: "Discussion list for WordPress theme
reviewers." <<A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A>>
<BR>Rubrik: Re: [theme-reviewers] Tags and description. <BR><BR><BR>
<DIV dir=ltr>I am more for just "Responsive" because if I had to get
examples this is what comes to mind first.
<DIV> </DIV>
<DIV>
<DIV
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px">Responsive:
TwentyTwelve</DIV>
<DIV
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px">Mobile-Optimized:
Jetpack Mobile Theme</DIV>
<DIV style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px">Mobile:
<A href="http://wordpress.org/plugins/wptouch/"
target=_blank>WPTouch</A></DIV></DIV>
<DIV
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px"> </DIV>
<DIV style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px">The
solutions for "Mobile-Optimized" and "Mobile" are plugins.</DIV>
<DIV
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px"> </DIV>
<DIV style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px">As we
have "buddypress" tag there should be a place "bbpress" and even
"woocommerce" also.<BR></DIV>
<DIV
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px"> </DIV>
<DIV style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px">I think
a survey would not be bad so that we can track the responses
properly.</DIV>
<DIV
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px"> </DIV>
<DIV style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px">I have
created something. Would love some feedback. <A
style="FONT-FAMILY: arial; FONT-SIZE: small"
href="http://grapplerulrich.polldaddy.com/s/theme-tag-servey"
target=_blank>http://grapplerulrich.polldaddy.com/s/theme-tag-servey</A></DIV>
<DIV
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px"> </DIV>
<DIV
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px"> </DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On 23 August 2013 06:37, Emil Uzelac <SPAN
dir=ltr><<A href="mailto:emil@uzelac.me"
target=_blank>emil@uzelac.me</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<P dir=ltr>Understood, I wasn't aware. And yes for above mobile.
Accessibility is on the list too. I think.</P>
<DIV>
<DIV>
<DIV class=gmail_quote>On Aug 22, 2013 11:35 PM, "Josh Pollock"
<<A href="mailto:jpollock412@gmail.com"
target=_blank>jpollock412@gmail.com</A>> wrote:<BR
type="attribution">
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>@justin agreed.
<DIV> </DIV>
<DIV>We ned to think about more than just mobile/responsive/etc
tags.</DIV>
<DIV> </DIV>
<DIV>What about tags based one end purpose, how do we feel about
reviewing those? For instance theme forest has these top level
categories for their WordPress themes: Blog/ magazine, creative,
corporate, retail, technology, nonprofit, entertainment,
miscellaneous, mobile, buddypress, and ecommerce. Could we do
tags like that? What about a CMS tag?</DIV>
<DIV> </DIV>
<DIV>@emil - There is no guarantee that there will be new tags.
This process is very preliminary. But if a useful set of tags
can be generated by the THX38 project, then a new search
filtering system based on those tags will have a good shot at
being implemented.</DIV>
<DIV>I'm trying to take some initiative to bring the theme
review team's thoughts on tags back to the THX38 team because
I'm the only theme reviewer that was present for the first THX38
meeting and a lot of ideas for new tags were thrown around,
which made me worry about how we were going to review them.
Basically, I'd rather say, "this is what the theme review team
discussion resulted in", then say, "as one of the theme
reviewers this is what I think."</DIV>
<DIV> </DIV>
<DIV> </DIV></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Fri, Aug 23, 2013 at 12:16 AM, Justin
Tadlock <SPAN dir=ltr><<A
href="mailto:justin@justintadlock.com"
target=_blank>justin@justintadlock.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV bgcolor="#FFFFFF" text="#000000">I agree with Chip that
one tag would be better for end users. However, I also
think we need to propose multiple tags to whoever is in charge
of this. So, having a list of potential tags with their
definitions is what we should put together.<BR><BR>On that
note, I've never had a user ask for an "adaptive" theme.
It's mostly "responsive." But, "mobile-ready" and
"mobile-first" are terms that are also thrown around a
bit.<BR><BR>Also, I dislike the phrase "fluid grid system"
when referring to responsive design. Maybe something
along the lines of "a fluid layout that responds to screen
size." Anyway, I'm just nit-picking words here.
<DIV>
<DIV><BR><BR>
<DIV>On 8/22/2013 10:52 PM, Josh Pollock
wrote:<BR></DIV></DIV></DIV>
<BLOCKQUOTE type="cite">
<DIV>
<DIV>@chip- I think there is a good chance of a lot of new
tags being added. Everyone agrees we need to be able to
filter search results based on tags and the current set of
tags doesn't do it.
<DIV> </DIV>
<DIV>What does it hurt to create a list of tag and
definitions that the theme review team thinks would be
useful and we could review fairly?
<DIV> </DIV>
<DIV>I think it would be better if we brainstormed a list
without any premptive doomsaying, so I can take it back to
the THX38 meeting as the theme review teams ideas on new
tags, instead of just <SPAN></SPAN>bringing own
ideas.<BR><BR>On Thursday, August 22, 2013, Chip Bennett
wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>My main problem with that is that it's still
adding three tags where currently none exist. I just don't
see that flying with the powers-that-be. I think our best
bet of getting *any* tags added is to keep to a single
tag.
<DIV> </DIV>
<DIV>IMHO, the tag list could probably stand for a bit of
an overhaul - but that would be a bigger discussion than
this one.</DIV></DIV>
<DIV><BR><BR>
<DIV>On Thu, Aug 22, 2013 at 8:27 PM, Josh Pollock <SPAN
dir=ltr><<A>jpollock412@gmail.com</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex">
<DIV dir=ltr>How about this:
<DIV> </DIV>
<DIV>Responsive: "<SPAN
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px">A
theme with a layout that employs a fluid grid system
that changes in response to screen size."</SPAN></DIV>
<DIV><SPAN
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px">Mobile-Optimized:
"A theme that adjusts its layout, reduces the sizes of
its media elements and otherwise improves the page load
time and user experience for mobile."</SPAN></DIV>
<DIV><SPAN
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px">Mobile:
"A Theme that is designed to be used only on mobile
devices."</SPAN></DIV>
<DIV><SPAN
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px"><BR></SPAN></DIV>
<DIV><SPAN
style="FONT-FAMILY: arial,sans-serif; FONT-SIZE: 13px">Notice
I left adaptive off of the list, and I'm open to leaving
mobile off too if its not needed.</SPAN></DIV></DIV>
<DIV>
<DIV>
<DIV><BR><BR>
<DIV>On Thu, Aug 22, 2013 at 7:27 PM, Emil Uzelac <SPAN
dir=ltr><<A>emil@uzelac.me</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex">
<P dir=ltr>mobile-responsive and that includes
both?</P>
<DIV>
<DIV>
<DIV>On Aug 22, 2013 5:46 PM, "Emil Uzelac"
<<A>emil@uzelac.me</A>> wrote:<BR
type="attribution">
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex">
<P dir=ltr>Whatever is better. :-)</P>
<DIV>On Aug 22, 2013 5:44 PM, "Chip Bennett"
<<A>chip@chipbennett.net</A>> wrote:<BR
type="attribution">
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex">
<DIV dir=ltr>Remember: those tags are, primarily,
for *users* rather than for developers. To the end
user: what's the tangible difference between
"responsive" and "adaptive"? In this case, "end
user" could be both the site owner (the one who
chooses and installs the Theme) or the site
visitor (who would view the website via devices
with various screen sizes).
<DIV> </DIV>
<DIV>Do a developer, I agree 100% that the two
terms have tangible, meaningful differences.</DIV>
<DIV> </DIV>
<DIV>I'm just struggling to see how a user would
see any difference whatsoever. In both cases, the
Theme is designed to work on devices with
variously small screen sizes.</DIV></DIV>
<DIV><BR><BR>
<DIV>On Thu, Aug 22, 2013 at 3:34 PM, Josh Pollock
<SPAN
dir=ltr><<A>jpollock412@gmail.com</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex">
<DIV dir=ltr>I agree and disagree with Chip. I
agree we need to find the definition that is
most useful to end users and two tags with the
same definition is probably confusing. The
problem is some end users are more sophisticated
than others. Some know what responsive means,
some don't. That said, we shouldn't equate the
two, because they are different. GIve me a
little time and I will propose some new
definitions.
<DIV> </DIV>
<DIV>@Ulrich We can't just add tags to the
guidelines. They need to be supported by core.
As part of the THX38 project this will most
likely happening. I'm hoping to go to the next
THX38 meeting with a list of tags that we, as
theme reviewers, want added and feel like we can
review properly.</DIV></DIV>
<DIV>
<DIV>
<DIV><BR><BR>
<DIV>On Thu, Aug 22, 2013 at 3:17 PM, Chip
Bennett <SPAN
dir=ltr><<A>chip@chipbennett.net</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex">
<DIV dir=ltr>I'm one of those people who doesn't
know the difference between "responsive" and
"adaptive". Well, <A
href="http://www.techrepublic.com/blog/web-designer/what-is-the-difference-between-responsive-vs-adaptive-web-design/"
target=_blank>until just now, because I googled
it</A>.
<DIV> </DIV>
<DIV>The TL;DR of that article:</DIV>
<DIV> </DIV></DIV></BLOCKQUOTE></DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV></DIV></DIV></BLOCKQUOTE></DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV></DIV></BLOCKQUOTE></DIV></DIV><BR>
<FIELDSET></FIELDSET> <BR></DIV></DIV>
<DIV><PRE>_______________________________________________
theme-reviewers mailing list
<A href="mailto:theme-reviewers@lists.wordpress.org" target=_blank>theme-reviewers@lists.wordpress.org</A>
<A href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A>
</PRE></DIV></BLOCKQUOTE><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>
<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></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>
<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></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>
<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></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>
<DIV> </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>
<DIV> </DIV></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>
<DIV> </DIV></DIV>
<P>
<HR>
_______________________________________________<BR>theme-reviewers mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></DIV></DIV></DIV></BODY></HTML>