<div dir="ltr">Wrote them an email suggesting that we could brainstorm on the guidelines and exchange different ideas and best practices while reviewing themes. I am really curious if they are going to respond positively but yet again it is a chance to bond and get a fresh workflow ideas. <div>
<br></div><div>Best,<br clear="all"><div dir="ltr"><br>Mario Peshev<br>Training and Consulting Services @ DevriX<div><a href="http://www.linkedin.com/in/mpeshev" target="_blank" class="vt-p">http://www.linkedin.com/in/mpeshev</a><br>
<a href="http://peshev.net/blog" target="_blank" class="vt-p">http://peshev.net/blog</a><br></div></div><br>
<br><br><div class="gmail_quote">On Sun, Oct 9, 2011 at 10:16 PM, Justin Tadlock <span dir="ltr"><<a href="mailto:justin@justintadlock.com">justin@justintadlock.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<u></u>
<div bgcolor="#ffffff" text="#000000">
Definitely tell folks to join the mailing list. I work for
DevPress, which has its own set of theme guidelines that go beyond
what we do here. I welcome feedback on guidelines from other theme
communities/shops/repositories because it'll help here as well as in
our guidelines.<div><div></div><div class="h5"><br>
<br>
On 10/8/2011 12:19 PM, Edward Caissie wrote:
<blockquote type="cite">It's a public mailing list, by all means let them know
it is available.<br>
<br>
<br clear="all">
Cais.<br>
<br>
<br>
<div class="gmail_quote">On Sat, Oct 8, 2011 at 12:38 PM, Mario
Peshev <span dir="ltr"><<a href="mailto:mario@peshev.net" target="_blank" class="vt-p">mario@peshev.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div dir="ltr">Hey Cais,
<div><br>
Thanks for the feedback.</div>
<div><br>
</div>
<div>Could I invite two of the reviewers to the mailing list
here informally on behalf of the WPORG or it's better just
to share them my personal thoughts as for how can we help
each other?</div>
<div><br>
Best,
<div><br clear="all">
<div dir="ltr"><br>
Mario Peshev<br>
Training and Consulting Services @ DevriX
<div><a href="http://www.linkedin.com/in/mpeshev" target="_blank" class="vt-p">http://www.linkedin.com/in/mpeshev</a><br>
<a href="http://peshev.net/blog" target="_blank" class="vt-p">http://peshev.net/blog</a><br>
</div>
</div>
<br>
<br>
<br>
</div>
<div>
<div>
<div class="gmail_quote">On Sat, Oct 8, 2011 at 7:05
PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank" class="vt-p">edward.caissie@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
We are always open to constructive discussions.<br>
That is really one of the core views of the WPTRT.<br>
We want to listen to the community and get their
feedback.<br>
<br>
Granted, there may be differing points of view
based on the venue the themes will be available
from, and we make every effort to keep to the what
we understand as the WordPress guiding ideals; but
that in no way hinders us from listening to and
discussing other ideals used by other
"repositories".<br>
<br>
<br clear="all">
Cais.<br>
<br>
<br>
<div class="gmail_quote">
<div>
<div>On Sat, Oct 8, 2011 at 11:51 AM, Mario
Peshev <span dir="ltr"><<a href="mailto:mario@peshev.net" target="_blank" class="vt-p">mario@peshev.net</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div>
<div>
<div dir="ltr">Hello Reviewers,
<div><br>
</div>
<div>Since we are discussing the
guidelines and some possible changes
out there, I would like to comment
something interesting (at least in my
opinion) about the toolkit of
reviewers here and in other markets.
My team has submitted a theme
framework for sale on Envato's theme
market last week after an unsuccessful
submission half a year ago. During the
first review in April there was no
specific technical review - it was
mostly stability and design uniqueness
and function richness, but after the
approval last week we actually
commented out with their reviewers
that they have started to actively use
the Theme-Check plugin. </div>
<div><br>
</div>
<div>Since their overall concept is
different, I was surprised that they
actually insist on different things
such as styling the .sticky class or
using some file operations. Due to the
market specifics some required options
are considered recommended only, but
still they consider using it closely
for their reviewing process.</div>
<div><br>
Also, since the recent huge attack of
timthumb, most of the authors in the
market actually got interested in the
'best practices' and what comes 'in
the box' of WordPress. I've been
researching the market since January
and themes are implementing
post-thumbnails instead of timthumb
nowadays (probably Justin's "Get the
Image" <a href="http://wordpress.org/extend/plugins/get-the-image/" target="_blank" class="vt-p">http://wordpress.org/extend/plugins/get-the-image/</a> and
user comments have helped). The point
is that there are other 'secret' teams
that also respect these guidelines and
tools and I believe that we could
probably contact them and discuss some
changes or best practices (even share
and exchange reviewing ideas). By
popularizing that relation some theme
sellers could join and contribute to
the WPORG repository (we plan
revamping the framework as a free
version as Pagelines did) or take part
as reviewers.</div>
<div><br>
So does it make any sense or we are
kinda 'closed' to other reviewing
groups?</div>
<div>
<div dir="ltr"><br>
<font color="#888888">Mario Peshev<br>
Training and Consulting Services @
DevriX
<div><a href="http://www.linkedin.com/in/mpeshev" target="_blank" class="vt-p">http://www.linkedin.com/in/mpeshev</a><br>
<a href="http://peshev.net/blog" target="_blank" class="vt-p">http://peshev.net/blog</a><br>
</div>
</font></div>
<br>
</div>
</div>
<br>
</div>
</div>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" class="vt-p">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank" class="vt-p">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br>
</blockquote>
</div>
<br>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" class="vt-p">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank" class="vt-p">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" class="vt-p">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank" class="vt-p">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br>
</blockquote>
</div>
<br>
<pre><fieldset></fieldset>
_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank" class="vt-p">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank" class="vt-p">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
</div></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" class="vt-p">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank" class="vt-p">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div></div>