[theme-reviewers] Spammy theme?

[Chip Bennett]

I think there is no issue with moving a given Theme to a second repository.
The only issues are introduced when someone wants to "adopt" such a Theme.

At that point, every reasonable effort should be made to contact the
original developer, and to get consent for the Theme to be adopted.

I would go even farther, and say that if the developer doesn't consent, then
the Theme should be suspended outright, and the would-be adopting developer
can simply fork the Theme.

Chip

On Mon, Jul 25, 2011 at 7:34 PM, Edward Caissie <edward.caissie at gmail.com>wrote:

> The original author should be contacted if possible ... although the
> expectation and transfer of ownership details would need to be sorted
> through along the way to bringing this idea to life.
>
> We would likely take on the task of establishing relevant guidelines on the
> various details that would need to be addressed.
>
>
> Cais.
>
>
>
> On Mon, Jul 25, 2011 at 7:45 PM, Vicky Arulsingam <
> vicky.arulsingam at gmail.com> wrote:
>
>> I like this idea a lot, especially allowing other developers to adopt
>> a theme and bring it up to WP standards.
>>
>> Should the original theme author be contacted about their outdated
>> theme or is it considered forfeit especially since a theme hasn't been
>> updated in 2 years
>>
>> On 7/26/11, Edward Caissie <edward.caissie at gmail.com> wrote:
>> > The basic premise I have always tried to champion is moving the "older"
>> > themes into a secondary repository so they are not lost but are
>> obviously
>> > shown as "out-of-date"
>> >
>> > There are many older themes that can be easily brought up to current
>> > standards but the original author's are no longer interested in updating
>> > and/or involved with WordPress.
>> >
>> > I would like to see these themes simply moved, then after another
>> arbitrary
>> > time limit made available to be adopted by a new author. I have put
>> forward
>> > this idea at least once before and still see it as having a great deal
>> of
>> > potential (aside from all necessary changes to the repository to make it
>> > work).
>> >
>> >
>> > Cais.
>> >
>> >
>> > On Mon, Jul 25, 2011 at 4:15 PM, Claude Needham <gxxaxx at gmail.com>
>> wrote:
>> >
>> >> On Mon, Jul 25, 2011 at 1:11 PM, Angelo Bertolli
>> >> <angelo.bertolli at gmail.com> wrote:
>> >> > Why not just have a "works with version X" selection for users like
>> on
>> >> > the plugin side?  Then the users could decide what was working, and
>> >> > things could be pruned accordingly.
>> >> >
>> >> If a theme seriously does not work with the current version of
>> >> wordpress, it should be retired.
>> >> I am assuming that we are trying to encourage people to work with the
>> >> latest release that they can.
>> >>
>> >> I have been in situations where a plugin that I relied upon had not
>> >> been updated yet. (A shopping cart).
>> >> But if I need an old obsolete theme -- I probably already have it
>> >> installed on my site.
>> >>
>> >> If I am theme hunting, it would be very disappointing to dl a theme
>> >> from wporg that is obsolete under the most current core.
>> >>
>> >> Just my thoughts,
>> >> Claude Needham
>> >> _______________________________________________
>> >> theme-reviewers mailing list
>> >> theme-reviewers at lists.wordpress.org
>> >> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>> >>
>> >
>>
>>
>> --
>> -----
>> Vicky Arulsingam
>> _______________________________________________
>> 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/20110725/741800d7/attachment.htm>