<br>- When this is green-lighted, I believe there should be an announcement about the suspensions or required theme updates published two weeks to a month before the fact and at an avenue where it would be seen by all e.g. <a href="http://wordpress.org/news/" target="_blank">wordpress.org/news/</a> or at Weblog Tools Collection, etc, This can serve as a friendly reminder to theme authors to upgrade themes or to "offer the theme up for adoption", etc. <br>
<br>- Noticed 4 themes from Automattic are in cut-off <a href="http://wordpress.org/extend/themes/profile/automattic" target="_blank">http://wordpress.org/extend/themes/profile/automattic</a><br><br>BuddyPress child/themes. <br>
- There are at least 3 themes in WP repo which need to be culled at this time because of deprecated template tags and js. While these themes were good for WP 3.0/BP 1.2.4, these themes have major hiccups in WP 3.2.1 and BP 1.2.9. These themes have to <br>
- There are 2 other themes which are good to go at present but are "broken" in BP 1.3 trunk when I checked them out. Only two out of the aforementioned have trac tickets where one can post a reminder to the theme authors to upgrade theme for BP 1.3 when it rolls out. Btw, can theme reviewers post such upgrade reminders in closed tickets just to get the message to the authors?<br>
<br>Thanks. <br><br><br>Mercime<br><br><br><div class="gmail_quote">On Mon, Jul 25, 2011 at 5:50 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But I think we need a short-term solution. The current situation is horribly, terribly, bad for end users, when they install a Theme that, since it is tied directly into their WP-Admin interface, comes with an implied endorsement of its fitness for use.<div>
<br></div><div>What do you suggest? Should we just go ahead and start suspending sufficiently old/obsolete Themes?</div><div><br></div><div>At least with Cais' idea, even if WPORG doesn't display a section in Extend for the "second" repository, the Themes will still exist in some not-suspended state.</div>
<div><br></div><div>I'm open to any ideas you might have here...</div><div><br></div><div><font color="#888888">Chip</font><div><div></div><div><br><br><div class="gmail_quote">On Mon, Jul 25, 2011 at 7:43 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">At some nebulous undefined point in the future, themes and plugins<br>
will likely both get an overhaul. It's something that's been bugging<br>
me and Nacin for a long time, but we've never had the time to sit down<br>
and figure it out.<br>
<br>
When that happens (and it will be a relatively long time), then this<br>
discussion will be useful, as what themes get migrated over to the new<br>
system will be up-for-debate. Until then, it's fun to think about, but<br>
I don't expect any action arising from it. It needs core backing to<br>
redefine and reimagine the system. Just creating a new one<br>
because-we-can ain't enough to get it done.<br>
<br>
The best thing to think of is this: What should a new themes directory<br>
be? What should it do? What new features should it have? Creating<br>
something new is easier to sell when you have actual new functionality<br>
and new core support needed for it.<br>
<font color="#888888"><br>
-Otto<br>
</font><div><div></div><div><br>
<br>
<br>
On Mon, Jul 25, 2011 at 7:35 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
> And I'm in exactly the opposite camp (though I agree with Cais' suggested<br>
> implementation): obsolete Themes cause all manner of problems for end users.<br>
> (If you don't believe me, try spending an hour a day in the WPORG "Themes<br>
> and Templates" and "Troubleshooting" forums.)<br>
> Older Themes have much to offer, especially the well thought-out and<br>
> well-designed ones. But that doesn't mean that end users should be made to<br>
> suffer because those Themes have obsolete functionality and code.<br>
> If we can make the "OoD Themes" repository idea work, then I'm all for it!<br>
> Chip<br>
><br>
> On Mon, Jul 25, 2011 at 7:24 PM, Edward Caissie <<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>><br>
> wrote:<br>
>><br>
>> PS: The whole idea behind this is I see no reason to suspend a theme<br>
>> simply because it is old ... if there are security issues due to old code<br>
>> sure, but simply being out-dated really is not a great reason. Just consider<br>
>> the "senior" citizens of our world, they're old, should they be trundled off<br>
>> to some place out of site, out of mind left to obscurity? I say NO! Some,<br>
>> possibly many, are still very capable of providing valuable knowledge and<br>
>> experience to the younger crowd.<br>
>><br>
>><br>
>> Cais.<br>
>><br>
>><br>
>> On Mon, Jul 25, 2011 at 8:19 PM, Edward Caissie <<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> @Vicky -<br>
>>><br>
>>> Let's start by setting aside the code that would have to be written and<br>
>>> just discuss the ideals of moving versus suspending themes ...<br>
>>><br>
>>> In simple terms, at least the way I understand it, the current repository<br>
>>> is a heavily modded bbPress installation that has one forum and the process<br>
>>> of approving a theme into the repository either creates a new topic or<br>
>>> overwrites the existing one for every theme. Now, consider a second "forum"<br>
>>> for out-dated themes; and, rather than suspend a theme that uses old or<br>
>>> outdated functions or methods simply move it into the new Out of Date (OoD)<br>
>>> 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<br>
>>> Administration Panels but only viewable from the dot-org listing as in add<br>
>>> another menu item under extend: Themes, OoD Themes, Plugins, Mobile.<br>
>>> Minimizing the search methods would help reduce the code impact, while<br>
>>> still making them readily available and findable.<br>
>>><br>
>>> Continuing even further down the road, on sort sort of schedule relevant<br>
>>> to the stable version releases the OoD themes are marked as available for<br>
>>> "adoption"; or in other words you can pick up that old theme, give it new<br>
>>> life, and re-submit it to the repository meeting current guidelines and<br>
>>> carry on updating it as your own. This currently is actually possible but<br>
>>> manually intensive. I would imagine there would be plenty of time to create<br>
>>> a more automated approach if the first parts are brought online.<br>
>>><br>
>>> Just some thoughts ...<br>
>>><br>
>>><br>
>>> Cais.<br>
>>><br>
>>><br>
>>> On Mon, Jul 25, 2011 at 7:39 PM, Vicky Arulsingam<br>
>>> <<a href="mailto:vicky.arulsingam@gmail.com" target="_blank">vicky.arulsingam@gmail.com</a>> wrote:<br>
>>>><br>
>>>> 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<br>
>>>> question:<br>
>>>><br>
>>>> Is there any way to inform users that they're using an obsolete theme?<br>
>>>><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>
>>>> > 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>
>>>> > resulting in the suspension of 58 of 95 pages of Themes; and a WP 2.8<br>
>>>> > cutoff<br>
>>>> > would put the cutoff on about Page<br>
>>>> > 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>
>>>> > resulting in the suspension of 38 of 95 pages of Themes.<br>
>>>> ><br>
>>>> > Cais: any further thoughts on your "secondary repository" idea, that<br>
>>>> > 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>><br>
>>>> > 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*<br>
>>>> >> cutoff -<br>
>>>> >> or, barring that, WordPress 2.8 (June 11 2009), as the "generous"<br>
>>>> >> 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>><br>
>>>> >> 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<br>
>>>> >>> 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>><br>
>>>> >>> wrote:<br>
>>>> >>> > Yes and thank you. Theme has been suspended from the directory.<br>
>>>> >>> > 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 |<br>
>>>> >>> > 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<br>
>>>> >>> > <<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<br>
>>>> >>> >> 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>
>>>> --<br>
>>>> -----<br>
>>>> Vicky Arulsingam<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>
>> 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>
> 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>
</div></div></blockquote></div><br></div></div></div>
<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></blockquote></div><br>