[theme-reviewers] Formal Request for Change of Methodology.

Sayontan Sinha sayontan at gmail.com
Wed Jun 26 17:47:35 UTC 2013


>
> I agree, however, I disagree that that is what you are doing. You are
> locking users into your themes when they have no migration path away that
> allows them to retain their data because they unknowingly typed it into
> your theme not into WordPress.


So let me ask you this - what if I were to offer this code as a plugin AND
bundled with my theme? This way I am giving a user a migration path, I am
offering value-added stuff in my theme for those who don't want to use
something else, and I am avoiding breaking sites by yanking the code. Would
you consider this acceptable? The WPTRT doesn't find this acceptable
either, and that is one of the points Frumph is trying to make.



On Wed, Jun 26, 2013 at 12:40 PM, Philip M. Hofer (Frumph) <
philip at frumph.net> wrote:

> Yes, yes I am.   .. and it's entirely my choice to give my users the
> features that the theme has.
>
> If another theme wants to use those features, I would gladly give them
> code and be more then willing to help them add it to theirs; it is afterall
> GPL.
>
>
>
>
>
>
> -----Original Message----- From: Dane Morgan
> Sent: Wednesday, June 26, 2013 10:35 AM
>
> To: theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
> Subject: Re: [theme-reviewers] Formal Request for Change of Methodology.
>
> On 2013-06-26 12:31, Philip M. Hofer (Frumph) wrote:
>
>> Removing CHOICE is never a good idea.
>>
> I agree, however, I disagree that that is what you are doing. You are
> locking users into your themes when they have no migration path away
> that allows them to retain their data because they unknowingly typed it
> into your theme not into WordPress.
>
> Separating generation and display of content does not remove choice. It
> enhances it. they can choose any theme they want when they know all of
> the content is safe in plugins and core. Otherwise they can only choose
> to stick with your theme (however wonderful it may be) or lose their data.
> ______________________________**_________________
> theme-reviewers mailing list
> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
> http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
> ______________________________**_________________
> theme-reviewers mailing list
> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
> http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
>



-- 
Sayontan Sinha
http://mynethome.net | http://mynethome.net/blog
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130626/ec8adaf9/attachment.html>


More information about the theme-reviewers mailing list