[theme-reviewers] Artiseer

[Chip Bennett]

Yep; discovered that VERY quickly.

1) Header Foreground photo images are not GPL-compatibly licensed.
2) Artisteer uses a TON of custom functions, instead core WP functionality
(menus, post thumbnails, etc.)
3) Artisteer uses the "Kubrick" namespace

(And you can imagine that it goes downhill from there...)

Chip

On Mon, Sep 27, 2010 at 1:33 PM, Edward Caissie <edward.caissie at gmail.com>wrote:

> Besides a lot of ugliness in the code and extra unnecessary files being
> generated/included ... it defintitely falls under the "cookie-cutter"
> approach. Other than that, its more of an inherited item from pre-Theme
> Review Team as far as I know.
>
>
> Cais.
>
> On Mon, Sep 27, 2010 at 2:13 PM, Chip Bennett <chip at chipbennett.net>wrote:
>
>> Can someone explain to me the issues/problems with Artiseer, and what to
>> do with Artiseer-generated Themes in the review queue? I don't really know
>> anything about it, and had never heard of it until Otto mentioned it in his
>> summary of the uploader script checks.
>>
>> Chip
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20100927/aea54202/attachment-0001.htm>