The argument is sometimes made here that, "yes, but I've already started promoting my theme under that name, and it would just be confusing for my users, so please change the WP theme repo for me". <div><br></div>
<div>I really don't think it's the theme repo's responsibility to adjust to those that decide to name a theme something that is already taken in the repo. It's easy to check if the name already exists or not; just add the slug to the repo svn URL, as Chip pointed out above. And every developer can, of course, decide to use that name anyways to promote their theme; it just won't include the theme repo.</div>
<div><br></div><div>As a developer, I would not want to lose a name in the repo because a newer dev and Otto decided I don't deserve it anymore (no offense Otto). At the very least, if a theme has not been updated in so long, the dev should be contacted and given a deadline to either update their theme (as it's part of the requirements to keep all submitted themes up to date), or relinquish it. </div>
<div><br></div><div>Maybe the repo is due for a culling, as we've somewhat discussed before; but devs still deserve the chance to update their themes instead of losing their slug.</div><div><br><br><div class="gmail_quote">
On 23 July 2012 10:29, Daniel Tara <span dir="ltr"><<a href="mailto:contact@onedesigns.com" target="_blank">contact@onedesigns.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I would like to say something about this, if I'm allowed to do so: I<br>
understand allocating theme names is a matter of first come, first<br>
served and also that changing theme ownership affects internal<br>
organization of the repository but there are just that many catchy<br>
names that one can find and with all the recommendations at one point<br>
or another theme names are going to clash and situations like this are<br>
going to arise. And sometimes due to branding elements and other<br>
keyword connections changing theme names is really not that easy. I<br>
think it would make for a better policy if authors willing to<br>
contribute with good quality themes would be given more consideration<br>
than authors who came, left their mark and left.<br>
<br>
I understand this could be more inconvenient than not and that it may<br>
affect the repository's organization as much as it would affect theme<br>
authors. I'm just giving my 2 cent and hope it might help.<br>
<br>
Sent from my iPhone<br>
<div class="HOEnZb"><div class="h5"><br>
On 23.07.2012, at 17:13, Otto <<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>> wrote:<br>
<br>
> On Sun, Jul 22, 2012 at 10:55 PM, Bryce <<a href="mailto:brycead@gmail.com">brycead@gmail.com</a>> wrote:<br>
>> Hey Otto,<br>
>><br>
>> Is there any way you could remove the old one and give me Onec?<br>
><br>
> No, I can't, because the name of the existing theme is fixed as "oneC".<br>
><br>
> I *really* suggest you change the name of your theme instead.<br>
><br>
> -Otto<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>
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>
</div></div></blockquote></div><br></div>