<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>Agreed. The premise to increase the productivity of the tools used
vs. the amount of time a volunteer is available is a very merit able route to
take; while also increasing the innovation and continuation of feature rich
themes.</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><FONT size=3 face=Calibri></FONT> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=edward.caissie@gmail.com
href="mailto:edward.caissie@gmail.com">Edward Caissie</A> </DIV>
<DIV><B>Sent:</B> Wednesday, June 26, 2013 5:38 AM</DIV>
<DIV><B>To:</B> <A title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">WP Theme Reviewers Mailing
List</A> </DIV>
<DIV><B>Subject:</B> Re: [theme-reviewers] Formal Request for Change of
Methodology.</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>
<DIV>Although Frumph's suggestion might be considered extreme by some, I am
having a tough time not agreeing with it as a whole (if it was to be implemented
it would likely need a tweak or three, but the ideals are sound) ... but the
greatest issue always seems to come back around to the core nature of the
reviewers: we are all volunteers.<BR><BR></DIV>
<DIV>I know I have considered it, and suggested it in the past; I know it has
been discussed from time to time within the community; and, I know there is
interest from the theme authors in it coming to fruition ... the "it" in this
case is a "paid" WordPress team of reviewers that are specifically tasked with
maintaining the theme repository, guidelines, processes, etc. We, as volunteers,
all have to pay the bills and as such our time is at a premium.<BR><BR>We may be
gaining great insights and invaluable knowledge of WordPress as well as the
satisfaction of being able to give back to the community in a meaningful manner
but in the real world we still have to pay those bills ... and prioritize
accordingly. The idea of adding additional "admins" to help with the workload is
great *and* being seriously looked at *and* implemented but will it be enough?
Time will tell, but we are falling victim to time as it is.<BR></DIV></DIV>
<DIV class=gmail_extra>
<DIV> </DIV>
<DIV>Edward Caissie<BR>aka Cais.</DIV><BR><BR>
<DIV class=gmail_quote>On Wed, Jun 26, 2013 at 8:01 AM, devcorn <SPAN
dir=ltr><<A href="mailto:wp@devcorn.com"
target=_blank>wp@devcorn.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>I just want to add to Greg, I read there was some controversy
that theme developer should not use Sponsored links on public page blah blah..
I believe then the community might have decided for strict human reviews.. but
we already have theme check plugin and if we don't go in detail for plugin
territory stuff then we can automate the whole theme review process.
<DIV> </DIV>
<DIV>why the discrimination with plugin and themes, a plugin developer can
overwrite whole theme engine and can control the content ( Coming Soon, Launch
pad, Mobile theme plugins are some to name)... and as Greg mentioned they
don't need any human intervention to get it approved.. but If a new
theme is submitted , it has to wait for close to a month and if it
misses something then again the next review will need atleast 2 weeks or
so and it goes on.. </DIV>
<DIV> </DIV>
<DIV>I am not sure what will be decided for plugin territory stuff but we
should remove the human intervention and this time consuming review
process.... Let's fully automate it.... or something that will show the theme
as soon as it pass the automated tests.. it will be encouraging for
developers and keep them interested.. <B>I know how great it feels when the
download stats increase and people ask question or request a feature.. that's
the beauty of opensource.</B></DIV>
<DIV> </DIV>
<DIV>WordPress theme directory is a starting place for a newbie and I have
seen developers losing interest due to this long approval process.</DIV>
<DIV> </DIV>
<DIV>Thanks<BR></DIV>
<DIV>Ash</DIV></DIV>
<DIV class=HOEnZb>
<DIV class=h5>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Wed, Jun 26, 2013 at 2:44 PM, Greg Priday <SPAN
dir=ltr><<A href="mailto:greg@siteorigin.com"
target=_blank>greg@siteorigin.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>Developing my WordPress plugin is an absolute dream. It was first
approved within a few days. I can push updates via SVN in seconds, get
feedback from users within minutes and have bug fixes done within hours.
This keeps development flowing which is great for me and my users.<BR></DIV>
<DIV> </DIV>
<DIV>In contrast, a new theme can take months to get approved. This gap
means there's always a code relearning overhead when I start
fixing/enhancing my themes based on user feedback.</DIV>
<DIV> </DIV>
<DIV>Even updates can take a week or more to go live. A lot of my support is
telling users that they have to hang tight for the next update to go
live.</DIV>
<DIV> </DIV>
<DIV>I'm not sure why themes and plugins are treated so differently. Are
plugin devs just more trustworthy ;)</DIV>
<DIV> </DIV>
<DIV>That said. Some advice for all theme devs. Use _s.</DIV>
<DIV class=gmail_extra>
<DIV>
<DIV><BR><BR>
<DIV class=gmail_quote>On Wed, Jun 26, 2013 at 7:43 AM, Emil Uzelac <SPAN
dir=ltr><<A href="mailto:emil@uzelac.me"
target=_blank>emil@uzelac.me</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>here* is the thing, not hear, sorry my phone is acting weird!
</DIV>
<DIV>
<DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Wed, Jun 26, 2013 at 12:41 AM, Emil Uzelac <SPAN
dir=ltr><<A href="mailto:emil@uzelac.me"
target=_blank>emil@uzelac.me</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>So hear is the thing. With the blessings of others, I am
thinking that
<DIV>Themes should not be "crucified" the way we're doing this now.
As</DIV>
<DIV>I was previously expressing, not all things are the "plugin
territory".</DIV>
<DIV> </DIV>
<DIV>My personal methodology is, if nothing breaks, or interferes with
the</DIV>
<DIV>core and it's useful to users, let it be, as simple as that.</DIV>
<DIV> </DIV>
<DIV>Restricting and eliminating rather harmful stuff, will project
very</DIV>
<DIV>negatively to Theme authors.</DIV>
<DIV> </DIV>
<DIV>I don't want to step on anyone's toe here and this is what I
believe</DIV>
<DIV>is right, or at least it should be :)</DIV><SPAN><FONT
color=#888888>
<DIV> </DIV>
<DIV>Emil </DIV></FONT></SPAN></DIV>
<DIV>
<DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Wed, Jun 26, 2013 at 12:35 AM, Philip M. Hofer
(Frumph) <SPAN dir=ltr><<A href="mailto:philip@frumph.net"
target=_blank>philip@frumph.net</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>i.e. don't even give it a second glance, that's a
feature of the theme<BR><BR><BR><BR>-----Original Message----- From:
Philip M. Hofer (Frumph)<BR>Sent: Tuesday, June 25, 2013 10:35 PM
<DIV>
<DIV><BR>To: <A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.<U></U>wordpress.org</A><BR>Subject:
Re: [theme-reviewers] Formal Request for Change of
Methodology.<BR><BR>There's no question about it, as long as it passes
the theme unit test with<BR>default settings it would pass
right?<BR><BR><BR><BR>-----Original Message----- From: Daniel<BR>Sent:
Tuesday, June 25, 2013 10:31 PM<BR>To: <A
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.<U></U>wordpress.org</A><BR>Subject:
Re: [theme-reviewers] Formal Request for Change of
Methodology.<BR><BR>What about themes like my one where you can remove
the header and<BR>footer because your using a bridge like wp-united?
Where do those sort<BR>of things come into play?<BR><BR><BR><BR><BR>On
Wed, Jun 26, 2013 at 3:29 PM, Philip M. Hofer (Frumph)<BR><<A
href="mailto:philip@frumph.net"
target=_blank>philip@frumph.net</A>> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>These are features of a theme, the shortcodes and
more are 'features' of the<BR>theme.<BR><BR>If they use the theme
and use those shortcodes, then that is the theme that<BR>is using
it, to require shortcodes to be cross compatible and in a plugin
is<BR>simply ridiculous.<BR><BR>The end user, while picking a theme
will choose a theme that has features<BR>that they want.
When they choose another theme that doesn't have those<BR>previous
themes features they miss out, it's not a question of requiring
a<BR>compatibility.<BR><BR>This also goes with themes that have
specialty programming in the way of<BR>custom post types and the
like. - again the data is not lost, it's still<BR>there, just
switching to a different theme will not grant access to
it.<BR><BR>The age of feature rich themes and innovation should be
promoted not<BR>stifled.<BR><BR><BR>-----Original Message----- From:
Harish<BR>Sent: Tuesday, June 25, 2013 10:24 PM<BR>To: <A
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.<U></U>wordpress.org</A><BR>Subject:
Re: [theme-reviewers] Formal Request for Change of
Methodology.<BR><BR><BR>Good suggestions by Philip (Frumph) however
I have to disagree with:<BR><BR>" the idea that a theme must adhere
and be cross compatible with other<BR>themes in features is a nuance
that is unnecessary to worry about."<BR><BR>Themes do not have to be
cross compatible with other themes, but they should<BR>not be the
cause of the end user losing data when changing their
themes.<BR><BR>2 of the most common issues are shortcodes and custom
meta boxes where the<BR>key has "_" in front to hide it from
the custom meta fields section.<BR><BR>If theme developers are
worried of making things easier for the end user,<BR>most of these
things should not have been in the theme in the first
place.<BR><BR><BR><BR>Regards,<BR>Harish<BR><BR><BR>-----Original
Message-----<BR>From: theme-reviewers [mailto:<A
href="mailto:theme-reviewers-bounces@lists.wordpress.org"
target=_blank>theme-reviewers-<U></U>bounces@lists.wordpress.org</A>]<BR>On
Behalf Of Philip M. Hofer (Frumph)<BR>Sent: Wed 26 June 13 10:41
AM<BR>To: <A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.<U></U>wordpress.org</A><BR>Subject:
[theme-reviewers] Formal Request for Change of
Methodology.<BR><BR>1) Remove all requirements and recommendations,
change it all to 'best<BR>practices', do not remove anything in the
codex just yet.<BR><BR>2) Theme review process.<BR>* Theme reviewers
tag a theme for review. / It already passed the
upload<BR>checker<BR>* Check theme with the other plugin(s)[1]
available for development, check<BR>it for notices, warnings, fatals
and deprecation messages, Pass/Fail<BR>* Check theme with theme unit
test. Pass/Fail<BR>* Review the tags, website links, theme
name. Pass/Fail<BR><BR>It's done, it's reviewed, it's over, if
it passed all of those, flag it as<BR>passing review and
live.<BR><BR>3) Anything else missing on the above list that is a
MUST should be added to<BR>the list but only if it's a MUST, and
can't go live no exception.<BR><BR>[1] Make the plugins work for the
theme review team; add common security<BR>problems,
etc.<BR><BR>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<U></U>~~~~~~~~~~~~~~~~~~~~~~~~~~~<BR><BR>This
is it, this is all that is needed.
Everything else is icing on the<BR>cake for best
practices.<BR><BR><BR>Themes are the 'meat and potatoes' of
WordPress, the idea that a theme must<BR>adhere and be cross
compatible with other themes in features is a nuance<BR>that is
unnecessary to worry about. Plugins are made to enhance
themes;<BR>if a plugin doesn't work with a theme the community WILL
contact the author;<BR><BR>they always do. As long as
the theme is up to date with core coding which<BR>all of the tools
at our disposal make you aware of - of which even the<BR>messages
from core will also state things it is unnecessary to do
anything<BR>otherwise.<BR><BR>// not sure about<BR>Not sure what
Nacin wrote in entirety on the Make site, but having the<BR>themes
that are live and pass the upload process and immediately go
live<BR>again would be a boon; that basically makes it like the
theme developer has<BR>svn access, without having svn
access.<BR><BR><BR><BR><BR><BR>______________________________<U></U>_________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.<U></U>wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/<U></U>mailman/listinfo/theme-<U></U>reviewers</A><BR><BR>______________________________<U></U>_________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.<U></U>wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/<U></U>mailman/listinfo/theme-<U></U>reviewers</A><BR>______________________________<U></U>_________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.<U></U>wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/<U></U>mailman/listinfo/theme-<U></U>reviewers</A><BR></BLOCKQUOTE>______________________________<U></U>_________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.<U></U>wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/<U></U>mailman/listinfo/theme-<U></U>reviewers</A><BR><BR>______________________________<U></U>_________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.<U></U>wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/<U></U>mailman/listinfo/theme-<U></U>reviewers</A>
<BR>______________________________<U></U>_________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.<U></U>wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/<U></U>mailman/listinfo/theme-<U></U>reviewers</A><BR></DIV></DIV></BLOCKQUOTE></DIV>
<DIV> </DIV></DIV></DIV></DIV></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><BR><BR
clear=all>
<DIV> </DIV></DIV></DIV><SPAN><FONT color=#888888>-- <BR>I make free
WordPress themes<BR><A href="http://siteorigin.com"
target=_blank>http://siteorigin.com</A>
</FONT></SPAN></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>