[theme-reviewers] theme-reviewers Digest, Vol 2, Issue 29

Chip Bennett chip at chipbennett.net
Wed Jul 7 11:47:58 UTC 2010

Hmm, I wasn't envisioning child themes being developed for "old" parent themes 
- but that's a good point. What's to stop someone from making a proper Kubrick 
child theme? *grin*

But, perhaps we can state that, if a child theme is submitted, then both the 
child and parent must have a "recent" pass through the approval process (where 
"recent" is defined as "since the last release of a major WordPress version"), 
or the child theme must use an official theme (e.g. TwentyTen) as its parent.

As for a parent theme being removed from the repository: I suppose it would 
depend on the reason the theme is removed. What are the possible reasons? 
Developer requests removal? Theme is removed for inappropriate content? Theme 
removed due to obsolescence?

I can only see one of those being a concern with respect to a parent theme: 
developer requests removal. (Since all themes must pass the review process in 
order to be updated, inappropriate content for future versions of a given 
theme would never make it into the repository, thus protecting existing child 
themes; likewise, with the criteria above, an obsolete theme would never be 
eligible to be a parent theme.)

So, I suppose that we could just not allow a parent theme to be removed upon 
request, unless all children are also removed?

Chip Bennett
chip at chipbennett.net

On Tuesday 06 July 2010 11:37:58 pm you wrote:
> As a follow up to the parent theme being in the repository ...
> Should not the parent theme meet or exceed all current requirements before
> child themes can be uploaded for it? Granted this may be very difficult to
> do for the existing bulk of the themes in the repository, but from a
> specific go-forward date it may not be as difficult. For example, child
> themes of Twenty Ten can be allowed as Twenty Ten passes all criteria for
> being hosted in the repository, whereas a theme that has not been updated
> in "years" would likely not pass current standards making the review of
> the child theme near impossible to bear on its own merits.
> Cais.
> On Wed, Jul 7, 2010 at 12:24 AM, Joseph Scott <joseph at josephscott.org>wrote:
> > There are some situations that come up with this.  For instance, you
> > mentioned that the parent should be in the theme directory.  What
> > happens if a parent theme gets removed from the directory?
> > 
> > I don't think the various issues that come need to be show stoppers,
> > but it is worth walking through them to figure out what the answers
> > should be (then likely document it on the Codex).
> > 
> > On Tue, Jul 6, 2010 at 12:26 PM, Chip Bennett <chip at chipbennett.net>
> > 
> > wrote:
> > > I think the only requirement should be that child themes should be
> > 
> > limited to
> > 
> > > parent themes available in the repository (to ensure that neither
> > 
> > reviewers
> > 
> > > nor end users have to go to any third-party sources for the parent
> > 
> > theme).
> > 
> > > As for the reviewers: as long as the parent theme is available in the
> > > repository, I don't think reviewing a child theme will pose any
> > 
> > particular
> > 
> > > inconvenience.
> > > 
> > > In other words: I'm all for it!
> > 
> > --
> > Joseph Scott
> > joseph at josephscott.org
> > http://josephscott.org/
> > _______________________________________________
> > theme-reviewers mailing list
> > theme-reviewers at lists.wordpress.org
> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20100707/4759ee7e/attachment.pgp>

More information about the theme-reviewers mailing list