<!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>After a lengthy discussion with Cais in the
#wp-themes we've come to a conclusion that a 2 revision suspension would not be
entirely justified and would harshly impact the themes available that still will
work with the 3.0 series albiet even if using deprecated and non standard
code.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>We've thought about it and discussed the
functionality of the wordpress themes and what they do and what revision base at
this time would be best to spend anything of it and less then.
</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Anything from december 2008 and before should be
suspended for 'old and needs upgraded' themes, that is the release time when 2.7
came out, 2.7 was the the release that really gave themes something more then
previous revisions that match more closely with with what 'works' in a
theme. It was in essence really 2.8, but 2.7 was the start of
it. So anything previous to the 2.7 release really can be considered old
and needing updated.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Then on the 3.1 release, do the 2.8 as the base and
so on.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>The concern is the 'warning' to developers that
when it will be happening and enough word out to them that it will be
happening. Giving ample time for developers who might want to 'rescue' old
themes from the repository to revive them.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Which brings up two thoughts, information needed to
change ownership of said themes and ample time for developers to revive
them. And information theme developers that it's going to be
happening.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Me? I don't care, suspend em, if they want them
back up, they resubmit them.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Cais wants mass emails done, however collectively
finding the authors emails would be a chore, let alone the fact that WordPress
practically *never* mass emails and I doubt that it will ever happen,
ever. So alternatives need to be addressed as the following:</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>So what's the minimal that should be
done?</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>A stickied post on the theme developement forum and
a codex entry, in the most relevant places.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>What would be optimal?</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>A post by Matt or the developers blog that gets
seen in the RSS feed list of all wordpress sites, with the minimal post in the
forum and codex entry information.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>The idea' is to not be 'harsh' about the suspension
of said themes, hence to backtrack to the pre 2.7 release, which keeps WordPress
in a good light, while still giving a couple weeks ample warning.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>------ Side Note:</FONT></DIV>
<DIV><FONT size=2 face=Arial>Information about how to 'take over' an old theme,
i.e. reviving it should be noted as well and that all old themes should have
their original authors contacted then original author of said theme needs to
email the repository theme admin requesting the ownership change, pretty much
how it's already being done.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Side effect of the removal/suspension would also be
that when they resubmit they will be automatically added to the theme trac when
resubmit, which is a goal that would benefit everyone.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Additonal note: While the GPL Compatibility issue
arose with the suspensions previously and there were some very vocal people
about suspending the themes at that time, it was still done regardless of those
complaints. It was justified and responsible of the theme repository
admin to do it. It is the same with this; The theme repository has
an underlying responsibility to the end user to keep the repository up to date
and in a manageable state to the end user.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV></BODY></HTML>