PS: The whole idea behind this is I see no reason to suspend a theme simply because it is old ... if there are security issues due to old code sure, but simply being out-dated really is not a great reason. Just consider the "senior" citizens of our world, they're old, should they be trundled off to some place out of site, out of mind left to obscurity? I say NO! Some, possibly many, are still very capable of providing valuable knowledge and experience to the younger crowd.<br>
<br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Mon, Jul 25, 2011 at 8:19 PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
@Vicky -<br><br>Let's start by setting aside the code that would have to be written and just discuss the ideals of moving versus suspending themes ...<br><br>In simple terms, at least the way I understand it, the current repository is a heavily modded bbPress installation that has one forum and the process of approving a theme into the repository either creates a new topic or overwrites the existing one for every theme. Now, consider a second "forum" for out-dated themes; and, rather than suspend a theme that uses old or outdated functions or methods simply move it into the new Out of Date (OoD) forum and use the same processes currently in use for current themes.<br>
<br>I would continue with *not* having the OoD themes be searchable from the Administration Panels but only viewable from the dot-org listing as in add another menu item under extend: Themes, OoD Themes, Plugins, Mobile.<br>
Minimizing the search methods would help reduce the code impact, while still making them readily available and findable.<br><br>Continuing even further down the road, on sort sort of schedule relevant to the stable version releases the OoD themes are marked as available for "adoption"; or in other words you can pick up that old theme, give it new life, and re-submit it to the repository meeting current guidelines and carry on updating it as your own. This currently is actually possible but manually intensive. I would imagine there would be plenty of time to create a more automated approach if the first parts are brought online.<br>
<br>Just some thoughts ...<br><br><br clear="all">Cais.<div><div></div><div class="h5"><br>
<br><br><div class="gmail_quote">On Mon, Jul 25, 2011 at 7:39 PM, Vicky Arulsingam <span dir="ltr"><<a href="mailto:vicky.arulsingam@gmail.com" target="_blank">vicky.arulsingam@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm intrigued by this second repository idea - how would it work?<br>
<br>
As for cut-off, I agree for removing WP 2.8 themes from Extend but one question:<br>
<br>
Is there any way to inform users that they're using an obsolete theme?<br>
<div><br>
On 7/26/11, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
> Just as an FYI, a WP 2.9 cutoff would put the cutoff on about Page<br>
</div>> 37<<a href="http://wordpress.org/extend/themes/browse/updated/page/37/" target="_blank">http://wordpress.org/extend/themes/browse/updated/page/37/</a>>,<br>
<div>> resulting in the suspension of 58 of 95 pages of Themes; and a WP 2.8 cutoff<br>
> would put the cutoff on about Page<br>
</div>> 57<<a href="http://wordpress.org/extend/themes/browse/updated/page/57/" target="_blank">http://wordpress.org/extend/themes/browse/updated/page/57/</a>>,<br>
<div><div></div><div>> resulting in the suspension of 38 of 95 pages of Themes.<br>
><br>
> Cais: any further thoughts on your "secondary repository" idea, that we<br>
> might be able to implement here?<br>
><br>
> Chp<br>
><br>
> On Mon, Jul 25, 2011 at 2:09 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
><br>
>> I support this as well, but we need buy-in from higher up.<br>
>><br>
>> I would propose WordPress 2.9 (December 18, 2009) is the *ideal* cutoff -<br>
>> or, barring that, WordPress 2.8 (June 11 2009), as the "generous" cutoff.<br>
>><br>
>> I will raise the flag, if there is general consensus?<br>
>><br>
>> Chip<br>
>><br>
>> On Mon, Jul 25, 2011 at 2:02 PM, Amy Hendrix <<a href="mailto:sabreuse@gmail.com" target="_blank">sabreuse@gmail.com</a>> wrote:<br>
>><br>
>>> I noticed that this theme was last updated in 2008 -- it seems like,<br>
>>> as we're just now gearing up for the next release cycle, it might be a<br>
>>> good time to revisit enforcement of the "must be kept up-to-date"<br>
>>> guideline? I'd welcome autosuspension of themes that haven't been<br>
>>> updated in n core versions with a "please update" message to the dev<br>
>>> (where n is a somewhat generous number).<br>
>>><br>
>>> On Mon, Jul 25, 2011 at 2:50 PM, Emil Uzelac <<a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a>> wrote:<br>
>>> > Yes and thank you. Theme has been suspended from the directory. They<br>
>>> > had<br>
>>> at<br>
>>> > least one more site which was suspended in the past.<br>
>>> ><br>
>>> > ----<br>
>>> > Emil Uzelac | ThemeID | T: <a href="tel:224-444-0006" value="+12244440006" target="_blank">224-444-0006</a> | Twitter: @EmilUzelac | E:<br>
>>> > <a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a> | <a href="http://themeid.com" target="_blank">http://themeid.com</a><br>
>>> > Make everything as simple as possible, but not simpler. - Albert<br>
>>> Einstein<br>
>>> ><br>
>>> ><br>
>>> > On Mon, Jul 25, 2011 at 1:38 PM, esmi at quirm dot net <<a href="mailto:esmi@quirm.net" target="_blank">esmi@quirm.net</a>><br>
>>> > wrote:<br>
>>> >><br>
>>> >> <<a href="http://wordpress.org/extend/themes/3d-realty" target="_blank">http://wordpress.org/extend/themes/3d-realty</a>><br>
>>> >><br>
>>> >> The link on the theme's Repo page and in the footer of the theme leads<br>
>>> to<br>
>>> >> an SEO site. No mention of the theme anywhere on the SEO site.<br>
>>> >><br>
>>> >> Mel P.<br>
>>> >> _______________________________________________<br>
>>> >> theme-reviewers mailing list<br>
>>> >> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
>>> > _______________________________________________<br>
>>> > theme-reviewers mailing list<br>
>>> > <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
>>> _______________________________________________<br>
>>> theme-reviewers mailing list<br>
>>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
>><br>
><br>
<br>
<br>
</div></div>--<br>
-----<br>
<font color="#888888">Vicky Arulsingam<br>
</font><div><div></div><div>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
</div></div></blockquote></div><br>