I use a rule of thumb that says: there must be a significant difference in design and / or functionality between the submitted theme and the "parent" it was derived from.<br><br>As Justin suggests, if it can be accomplished with CSS alone (and minimal code) then it is not likely to be "approved" for the repository but of course this is very subjective. Essentially it boils down to if you have to ask if it is a child-theme then most likely it is.<br>
<br><br>Cais.<br><br><div class="gmail_quote">On Tue, Dec 28, 2010 at 6:03 PM, <span dir="ltr"><<a href="mailto:justin@justintadlock.com">justin@justintadlock.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;">
I have a few rules when deciding whether something should be a child<br>
theme of another theme.<br>
<br>
* Could the theme be achieved with CSS alone? It should be a child<br>
theme.<br>
* Are there 5 custom templates or more that step outside of what the<br>
parent theme does? It should be a parent theme.<br>
* Does the functions.php file have more than 10kb (very generous) of<br>
custom functions? It should be a parent theme.<br>
<br>
These are just some general rules I go by to give myself some sort of<br>
standard.<br>
<br>
Obviously, there has to be a little more leeway when it comes to<br>
TwentyTen. That's the theme that devs will learn to build from. I just<br>
hate having to see that same code over and over and over.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
-------- Original Message --------<br>
Subject: [theme-reviewers] how close is too close?<br>
From: Amy Hendrix <<a href="mailto:sabreuse@gmail.com">sabreuse@gmail.com</a>><br>
Date: Tue, December 28, 2010 2:52 pm<br>
To: <a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<br>
Hi all,<br>
<br>
I'd love to see some discussion on themes that are obviously derived<br>
from another theme, but have more new work in them than something<br>
that's just a straight-up child theme. What's "too close"? Is it a<br>
matter of adding or removing functionality? Rewriting significant<br>
parts of template files (as opposed to, say, copy-pasting the new<br>
theme name wherever the old one appears)?<br>
<br>
At this point, I feel like there's a continuum that goes something like:<br>
<br>
Author copied Twenty Ten but changed the site title to pink. Child<br>
theme, also poor taste.<br>
Author copied Twenty Ten, changed the site title to pink, and removed<br>
the headers that say "Twenty Ten".<br>
...<br>
...<br>
...<br>
...<br>
Author wrote every line from scratch. Author is an utter masochist who<br>
never heard of code re-use.<br>
<br>
And I'm clear on recognizing the ends of the spectrum but the middle<br>
is fuzzy - so I'd love some thoughts from the rest of you about how<br>
you recognize the line?<br>
<br>
Thanks,<br>
Amy<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>
_______________________________________________<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>
</div></div></blockquote></div><br>