[theme-reviewers] Theme Names
Emil Uzelac
emil at uzelac.me
Mon May 12 03:08:23 UTC 2014
(FCFS) should apply for Theme names and it does, however at the same time
too similar makes directory look ugly.
On Sun, May 11, 2014 at 8:46 PM, Edward Caissie <edward.caissie at gmail.com>wrote:
> Common sense should be the best approach ... even though I had "Opus
> Primus" in the theme repository for some time prior, the "Opus" theme was
> still approved. Personally, I have no issues with that, and did not get
> involved in that conversation when it was happening.
>
> I had actually considered using Opus myself but chose a different naming
> convention due to the "branding" ideas I have for Opus ... er, Opus Primus.
> I guess I better get used to referring to my own theme by its proper name
> ... Opus Primus (*grin*)
>
> As it is, I do not think it would be wise for us to eliminate theme name
> possibilities based on another more or less generic name already in use, or
> submitted, but we should definitely take into consideration as theme
> authors that using a more unique name would be more beneficial in the long
> run than trying to capitalize on a common term. If you build something
> noteworthy the name itself will not matter so much.
>
>
> Edward Caissie
> aka Cais.
>
>
> On Sun, May 11, 2014 at 9:01 PM, Justin Tadlock <justin at justintadlock.com>wrote:
>
>> The theme name Solar would be too generic. It'd be unfair for us to
>> police something like Solar Flare because you shouldn't get the rights to
>> all uses of the single word "solar". On the other hand, if you had
>> submitted Solar Flare and someone else came along and submitted Solar Flare
>> Plus, that's when we have a problem.
>>
>> What we really want is for theme authors to come up with unique names.
>> Some of that just takes a little common sense when we review themes or
>> just awareness that this is something we need to look at.
>>
>>
>> On Sun, May 11, 2014 at 2:10 AM, Jose Castaneda <jomcastaneda at gmail.com>wrote:
>>
>>> Yes and no. It would be like me submitting a theme called Solar and then
>>> somebody else submitting a theme called Solar Flare. The biggest thing
>>> really is communicating that with the author. If they really have an issue
>>> with it we can, as a team, come up with a reasonable solution, right?
>>> Granted some are more active than others but more feedback is better than
>>> none. :)
>>>
>>> Let's just not turn this into a witch hunt.
>>>
>>>
>>> On Sat, May 10, 2014 at 3:56 PM, Srikanth Koneru <tskk79 at gmail.com>wrote:
>>>
>>>> But Business is toooooo generic and fair game according to Chip.
>>>>
>>>>
>>>> On Sun, May 11, 2014 at 4:25 AM, Emil Uzelac <emil at uzelac.me> wrote:
>>>>
>>>>> Dear Reviewers,
>>>>>
>>>>> (*while we hate to Police the names*)
>>>>>
>>>>> Before we do an actual Theme review, can you please check the names
>>>>> first and if the name is not appropriate, don't approve, or even continue
>>>>> with the ticket at all.
>>>>>
>>>>> We have been approving names similar to:
>>>>>
>>>>> - My Business
>>>>> - Your Business
>>>>> - Our Business
>>>>> - Flat Bootstrap
>>>>> - Real Bootstrap
>>>>> - Better Bootstrap
>>>>> - Good News
>>>>> - All News
>>>>> - Real-Estate News
>>>>>
>>>>> That's not good and also makes admins job difficult when we need to
>>>>> reopen the ticket and close as not-approved because of the Theme name.
>>>>>
>>>>> So if we already have a Theme called *Example*, *WP Example* won't be
>>>>> appropriate, therefore should not be approved either.
>>>>>
>>>>> Names must not be related to another Theme and no SEO injected
>>>>> keywords either.
>>>>>
>>>>> This is a full-stop and instant not-approval, no questions asked.
>>>>>
>>>>> Why? Two reasons.
>>>>>
>>>>> 1) Our guideline says:
>>>>>
>>>>> - Themes are required to use appropriate Theme Names.
>>>>> - Themes are not to use related Theme names (e.g. WP Twenty
>>>>> Fourteen, Twenty Fourteen WP, The Twenty Fourteen, etc.) in their name.
>>>>>
>>>>> 2) When Theme name changes it goes into different priority and won't
>>>>> be associated with first submission in anyway. It becomes a totally
>>>>> different beast.
>>>>>
>>>>> This is to avoid confusion, not only for users, but also for authors
>>>>> as well.
>>>>>
>>>>> Once we mark the ticket live there's nothing more we can do about, so
>>>>> if you can, let's try to avoid that please!
>>>>>
>>>>> Thanks,
>>>>> Emil
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
> _______________________________________________
> 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/20140511/6173d10a/attachment.html>
More information about the theme-reviewers
mailing list