<div dir="ltr">here* is the thing, not hear, sorry my phone is acting weird! </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 class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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><br></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><br></div><div>Restricting and eliminating rather harmful stuff, will project very</div>
<div>negatively to Theme authors.</div><div><br></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 class="HOEnZb"><font color="#888888"><div>
<br></div><div>Emil </div></font></span></div><div class="HOEnZb"><div class="h5"><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 class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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 class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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><br></div>
</div></div></blockquote></div><br></div>