<div dir="ltr">Stuart: your differentiation is exactly how I would interpret the Theme Name guideline as it currently exists. To extend the Guidelines example Theme name: "AwesomeSauce Mobile" would be fine; "MobileWP" would not be. At least, that's how I would interpret them.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 31, 2013 at 11:14 AM, Stuart Wider <span dir="ltr"><<a href="mailto:stuartwider@gmail.com" target="_blank">stuartwider@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks guys for your thoughts on naming rules.<div>Its helping me to formulate my own new theme name,</div><div>which of course will be using precisely none of the terms discussed so far ;)</div>
<div><br></div><div>Emil, </div>
<div>When discussing names I'm not focussing on the name Responsive Theme per se. The word responsive just happens to be a visible example of the naming conundrum, and of course (if we forget the namespace issue for a moment) its a very good name because its short, sweet and instantly lets people know exactly what's in the box, and in that respect, from both a user and the developers perspective, ideal :) </div>
<div><br></div><div>Chip,</div><div>I can see how naming issues can be very tricky and subjective.</div><div>As I was mulling over possible names for my own new theme I also started thinking about how the Theme name guidelines in this respect could possibly be less-subjective/more objective without necessarily being complex.</div>
<div><br></div><div>I'd suggest there are two types of related terms in the theme naming space...</div><div><br></div><div>1. Generic Terms ... <i style="line-height:22px;font-size:13px;font-family:sans-serif">Blog</i><span style="line-height:22px;font-size:13px;font-family:sans-serif">, </span><i style="line-height:22px;font-size:13px;font-family:sans-serif">Web Log</i><span style="line-height:22px;font-size:13px;font-family:sans-serif">, </span><i style="line-height:22px;font-size:13px;font-family:sans-serif">Template</i><span style="line-height:22px;font-size:13px;font-family:sans-serif">, </span><i style="line-height:22px;font-size:13px;font-family:sans-serif">Skin, Theme </i></div>
<div>Of course you already have these covered in the guidelines and this is sensible as they are essentially 'nothing' words in terms of a theme repository</div><div><br></div><div>2. Descriptive Web related Terms</div>
<div>These terms are common but useful for names as they help a user know what's actually in the box when used in a theme name. They are helpful and add meaning (ie not generic terms as above).</div><div>eg.</div><div>
Store, Mobile, Cart, Directory, Gallery... etc etc </div><div><br></div><div>So for example,</div><div><br></div><div>'Retroactive Mobile'</div><div>I would say this would be good name... as the name lets you know exactly what it is. Its probably a Retro theme and its mobile.</div>
<div><br></div><div>'Futurizmo Pet Store'</div><div>Again I would say that this is a good name as you can see from the title that this theme is likely to be futuristic and pet store related.</div><div><br></div><div>
but for example...</div><div><br></div><div>If a theme is named just</div><div> 'Mobile'</div><div>without anything else I would say that this was not a good name for use in the repository where other themes may also benefit from using that word descriptively.</div>
<div><br></div><div>So maybe a possible guideline idea would be:</div><div><br></div><div>- Allowed: Descriptive Web Terms used as part of an original theme name (eg Retroactive Mobile) </div><div><br></div><div>- Not Allowed: Descriptive Web Terms used on their own (eg Mobile)</div>
<div><br></div><div>This would keep the namespace of commonly used and descriptive web terms fair and open for all.</div><div><br></div><div><br></div><div><div class="gmail_quote"><div class="im">On Thu, Jan 31, 2013 at 10:19 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
</div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">And that is the reason for the wording against overly generic "related" terms in Theme names. "Responsive" is pretty close to that line, for exactly the reasons being brought up here.<div>
<br></div><div>(And this sort of thing is the reason that I've always tried to push for Guidelines to be as objective as feasible: the Theme Name guideline is very much subjective, and thus a potential source of confusion, disagreement, and inconsistency. Though, I don't know that the Theme Name guideline could feasibly be made any less-subjective/more-objective.)</div>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 30, 2013 at 6:42 PM, Stuart Wider <span dir="ltr"><<a href="mailto:stuartwider@gmail.com" target="_blank">stuartwider@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Emil,<div><div>I would say that Twenty Eleven is a subtly different kind of name, when its usage is for themes, </div>
<div>
Twenty Eleven is not commonly used as a web design or theme related term.</div><div>Whereas for example, Responsive or Mobile are commonly used web or theme design terms and therefore useful in titles so that users know exactly what kind of theme it is just by looking at the name .</div>
<div><div>
<div><br><div class="gmail_quote">On Thu, Jan 31, 2013 at 9:43 AM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><font color="#333333"><font><font face="arial,helvetica,sans-serif">Hi Stuart,</font></font></font><div>
<font color="#333333"><font><font face="arial,helvetica,sans-serif"><br></font></font></font></div><div>
<font color="#333333"><font><font face="arial,helvetica,sans-serif">Here's me speaking from TRT point of view and taking "Responsive" out.</font></font></font></div><div><font color="#333333"><font><font face="arial,helvetica,sans-serif"><br>
</font></font></font></div><div><font color="#333333"><font><font face="arial,helvetica,sans-serif">Twenty Eleven is a number "2011", even more common than the word</font></font></font></div><div><font color="#333333"><font><font face="arial,helvetica,sans-serif">"Responsive", but we still can't use "Super Twenty Eleven".</font></font></font></div>
<div><font color="#333333" face="arial, helvetica, sans-serif"><br></font></div><div><font color="#333333" face="arial, helvetica, sans-serif">Thanks,</font></div><div><font color="#333333" face="arial, helvetica, sans-serif">Emil</font></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Wed, Jan 30, 2013 at 5:03 PM, Stuart Wider <span dir="ltr"><<a href="mailto:stuartwider@gmail.com" target="_blank">stuartwider@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div><span style="line-height:22px;font-size:13px;font-family:sans-serif">Hi Guys,</span></div>
<div><span style="line-height:22px;font-size:13px;font-family:sans-serif">I note that in the theme review guidelines that is says...</span></div>
<span style="line-height:22px;font-size:13px;font-family:sans-serif">"Themes are </span><b style="line-height:22px;font-size:13px;font-family:sans-serif">not</b><span style="line-height:22px;font-size:13px;font-family:sans-serif"> to use related Theme names (e.g. </span><i style="line-height:22px;font-size:13px;font-family:sans-serif">WP Twenty Eleven</i><span style="line-height:22px;font-size:13px;font-family:sans-serif">, </span><i style="line-height:22px;font-size:13px;font-family:sans-serif">Twenty Eleven WP</i><span style="line-height:22px;font-size:13px;font-family:sans-serif">, </span><i style="line-height:22px;font-size:13px;font-family:sans-serif">The Twenty Eleven</i><span style="line-height:22px;font-size:13px;font-family:sans-serif">, etc.) in their name"</span><div>
<br></div><div>Does this mean that if a theme on the repository already has used a particular word in its name that it cannot be used in another themes name?</div><div><br></div><div>Lets take Emil's theme for example.. The word 'Responsive' is a common usage word.</div>
<div><br></div><div>Does the rule above intend that no other theme could use a common usage word such as 'Responsive' in their title, and that Responsive theme itself has the only rights to use that word in a title, on first come first served basis?</div>
<div><br></div><div>Here's some quick made up examples of what I mean...</div><div><br></div><div>Super Responsive</div><div>Mobile Responsive</div><div>Responsive to the Max</div><div><br></div><div>Would those pass as theme names with the above rule? or not allowed?</div>
<div><br></div><div>If those names were not allowed then it would follow that if I decided to release a theme called 'Mobile' then no one else would be able to name their theme with the word 'Mobile' in it eg. Ultra Mobile, Mobile Plus, Mega Mobile.</div>
<div><br></div><div>To sum up...</div><div>I'm seeking clarification on whether common usage words can be included in new theme name, even if an existing theme uses the common usage word. </div><div><br></div><div>Its an interesting conundrum ;)</div>
<div><br></div><div>Many Thanks,</div><div>Stuart</div>
<br></div></div>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>