<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18928">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>Apparently Matt wants to push forward with child
themes on the repository since he put one up, the Mazeld theme.</FONT><FONT
size=2 face=Arial><BR>These are only my idea's of the child theme's being on the
repository; and thoughts of what it should be made to be like.</FONT></DIV>
<DIV><FONT size=2 face=Arial>--------------</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Discussion on Child-Themes for the
repository</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>------------</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Repo Info:</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Repository needs to catch the "template:" in the
style.css to determine that its a child theme and what child theme it is
connected to. </FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>The repository must acknowledge to the end user
that this is a child theme and lead to the end user that views the page for the
child theme to the parent theme.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>The tags should be generated as child-theme if a
template: is found in the style.css and the secondary tag as the parent theme's
name. In addition to any other tags that are found in the
style.css</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>-------------------</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Child Theme Review:</FONT></DIV>
<DIV><FONT size=2 face=Arial>Must adhere to the programming specifications that
would be required of a child-theme based on the current review process for the
parent theme. If PHP code is in the child theme it must be checked for all
of the same things that the parent theme would be. Especially with the
Theme Unit Test.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>If the child theme uses post-types <FONT size=3
face="Times New Roman">corethemefile-*.php will be allowed if it's important for
the functioning of the child theme and registered
post-types.</FONT></FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Parent theme's of the child theme must be on the
repository and up to spec with the current version of wordpress and theme review
process.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Tags in the style.css of the child-theme must not
contain 'child-theme' or the name of the parent theme, these should be generated
by the repository by finding the style.css template: code</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>- Phil</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV></BODY></HTML>