[theme-reviewers] Why can't theme authors have a second version of a theme?

[Tammie Lister]

I've not responded to this thread but seen it over the days grow. I now
feel on seeing broad stroke comments like 'you guys' and other comments,
that I as an admin, theme reviewer and proud member of this community,
should add my voice. Like many I am keen we avoid things like this thread.
We all should be a united community not fractured.

What sometimes it's easy to forget on this list, is that any new theme
reviewer sees this mailing list pretty much as their gate to the team. It's
one of the steps to becoming a reviewer. We just got 27 new people signed
up this weekend at WordCamp Europe. This was their welcome. I don't know
about anyone else, but this gets me thinking how we should avoid things
like this and look at how we can unite, move forward and show how welcoming
we are as a community.

I have a simple suggestion. That is to talk. Lets talk, lets communicate as
a team and speak to each other rather than use this mailing list like some
verbal ping pong. Maybe we have a hangout, maybe a Skype, maybe we use IRC.
Whatever, if there is an issue lets deal with it and communicate with each
other. Lets have a virtual cup of tea and be a little more human towards
each other. Maybe this will work, maybe we can all find out we're not all
on such different pages after all, maybe we find out our differences can be
met in the middle or at least we can agree to disagree.

Just my thoughts. I'd be happy to make a chat happen if anyone is
interested.

Thanks
Tammie Lister

On Sat, Sep 27, 2014 at 11:28 PM, Trent Lapinski <trent at cyberchimps.com>
wrote:

> Cais,
>
> I came to this list for help, all I received was pointless bureaucracy.
>
> It is wrong to prevent theme authors from using their own brand names for
> multiple products. This rule only serves to limit the freedoms of theme
> authors, which was never its intention. The purpose of this rule was to
> protect theme authors from having their names and brands from being stolen,
> not to prevent authors from using their own names and brands.
>
> Did I get frustrated? Absolutely, TRT does not have the authority or the
> right to limit the freedoms of an open source community, and force theme
> authors to rebrand and rename their established product lines, and force
> thousands of developers to follow rules that no free open market would ever
> enact. You guys are over reaching your authority, and literally becoming
> the brand and naming police of the WordPress community. It is silly,
> offensive, and downright scary that you guys have all literally agreed to
> limit our rights.
>
> I am trying to find a resolution to this problem without having my rights,
> and the rights of my fellow theme authors taken away by people who have
> contributed just as much as I have to this community. I have every right to
> be here, and I don't need to be an admin to have a say, nor do I need to be
> an admin to defend myself and others from pointless bureaucracy and
> unneeded politics.
>
> -Trent
> CEO CyberChimps Inc.
> Sent from my iPad
>
> On Sep 27, 2014, at 11:06 AM, Edward Caissie <edward.caissie at gmail.com>
> wrote:
>
>
> On Sat, Sep 27, 2014 at 1:53 PM, Trent Lapinski <trent at cyberchimps.com>
> wrote:
>
>> Condescending yes, ...
>
>
> Thanks for making your position and opinion of the WordPress Theme
> Reviewers and Administrators that much more obvious.
>
> Feel free to carry on the conversation. I have already expressed my
> opinion and your admission really doesn't give me much reason to reconsider
> what I have already written about theme names.
>
>
>
> Edward Caissie
> aka Cais.
>
> _______________________________________________
> 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/20140930/c1ecf887/attachment-0001.html>