<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><a href="https://themes.trac.wordpress.org/ticket/20784#comment:5">https://themes.trac.wordpress.org/ticket/20784#comment:5</a><div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style=" orphans: 2; widows: 2; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">--Trent Lapinski<br>=============<br>CEO of CyberChimps Inc.</div><div style=" orphans: 2; widows: 2; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">http://CyberChimps.com</div><div style=" orphans: 2; widows: 2; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Twitter @trentlapinski</div><div style=" orphans: 2; widows: 2; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><span style="font-size: 12px;">Skype: mobiletrent</span><br></div></div></div>
</div>
<br><div style=""><div>On Sep 26, 2014, at 7:49 PM, Zulfikar Nore <zulfikarnore@live.com> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="hmmessage" style="font-size: 12pt; font-family: Calibri; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div dir="ltr">Can we get a list of what would break listed in ticket please?<br><br>Installed Responsive, downloaded Responsive II and renamed to Responsive with version set to the latest version. Deleted the original Responsive from the site and replaced with renamed one on viewing the site and admin area the only "breaking" I can see is the new layout.<br><br>Are we classing the loss of the old Responsive layout as "breaking" sites?<span class="Apple-converted-space"> </span><br><br>Zulf<br><br><div><hr id="stopSpelling">From: trent@cyberchimps.com<br>Date: Fri, 26 Sep 2014 19:43:52 -0700<br>To: theme-reviewers@lists.wordpress.org<br>Subject: Re: [theme-reviewers] Why can't theme authors have a second version of a theme?<br><br><div>Cais,</div><div><br></div><div>Slippery slope argument does not apply here. I am not asking to use someone else’s theme name. I am asking to use my own name.</div><div><br></div><div>Again, I see no logical reason why a theme author cannot release multiple themes under the same brand.</div><div><br></div><div>If the issue is using a number or Roman numerals, then can I use a letter or letters instead?</div><div><br></div><div>"Responsive HD" for example?</div><div><br></div><div>If you admins are going to enforce ridiculous rules like this, then you need to provide us with a solution that doesn’t result in breaking millions of peoples websites, or forcing me to release the next version of my product under a brand name no one will be able to identify.</div><div><br></div><div>Someone here needs to purpose an actual solution that is acceptable. Otherwise we’re just going in circles here.</div><div><br></div><div>I just need someway to communicate that this is the new version of the Responsive theme without breaking millions of websites. </div><div><br></div><div>My team and I have debated this, and there is no easy solution. We could build a plugin to change the update API and switch it to Github, we could do a number of things to try and provide backwards compatibility, but all of those “solutions” are compromises that will bloat our code, and force us to release an inferior product.</div><br><div><div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;"><div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;"><div style="orphans: 2; widows: 2; word-wrap: break-word;">--Trent Lapinski<br>=============<br>CEO of CyberChimps Inc.</div><div style="orphans: 2; widows: 2; word-wrap: break-word;"><a href="http://cyberchimps.com/" target="_blank">http://CyberChimps.com</a></div><div style="orphans: 2; widows: 2; word-wrap: break-word;">Twitter @trentlapinski</div><div style="orphans: 2; widows: 2; word-wrap: break-word;"><span style="font-size: 12px;">Skype: mobiletrent</span><br></div></div></div></div><br><div><div>On Sep 26, 2014, at 7:30 PM, Edward Caissie <<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>> wrote:</div><br class="ecxApple-interchange-newline"><blockquote><div dir="ltr">TL;DR: The idea of a version number in the theme name as not acceptable is a valid point.<div><br></div><div>Do we really need to write a new guideline (or re-write the existing) to make this more clear. I can go do that right now if necessary but I think some common sense should be applied in much the same way that the plugin repository does not allow for it. Granted the two repositories have their differences but there is no reason not to follow common sense and shared ideals.<div><br></div><div>I can appreciate your concern about potentially breaking some (all?) sites if this theme was released as an update to its predecessor but simply put if it is that vastly different and there is no backward compatibility then it really is a new theme and should have its own name. Let its code; its layout; and, its poetry stand on its own merits.</div><div><br></div><div>I'm not looking to carry this argument on wether or not the theme name is valid ... in this case I do not consider it to be acceptable.</div></div><div><br></div><div>We're not stopping you from using your "brand" ... by all means feel free to release a theme named Responsive II wherever you would like. We're just saying it's not an acceptable name in the WordPress Theme repository. Nothing against CyberChimps, its actually something that I would like to view as a benefit for your "brand" as well as other theme author's "brand" names. We should not be allowing most anything similarly named to another theme when used, as in this specific example, with the Responsive name foremost. We're not telling you no specifically. We're telling everyone, "No one can submit a theme named Responsive II", because quite simply if we allow you to submit Responsive II we would be setting a precedent to allow someone else to submit Responsive III ... and that would be a different rabbit hole again.</div></div><div class="ecxgmail_extra"><br clear="all"><div>Edward Caissie<br>aka Cais.</div><br><div class="ecxgmail_quote">On Fri, Sep 26, 2014 at 10:14 PM, Trent Lapinski<span class="Apple-converted-space"> </span><span dir="ltr"><<a href="mailto:trent@cyberchimps.com" target="_blank">trent@cyberchimps.com</a>></span><span class="Apple-converted-space"> </span>wrote:<br><blockquote class="ecxgmail_quote" style="border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><div style="word-wrap: break-word;">Daniel,<div><br></div><div>Why don’t the admins “let it go” and let me name my own products with my own brands. :-p</div><div><span><br><div><div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;"><div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; word-wrap: break-word;"><div style="word-wrap: break-word;">--Trent Lapinski<br>=============<br>CEO of CyberChimps Inc.</div><div style="word-wrap: break-word;"><a href="http://cyberchimps.com/" target="_blank">http://CyberChimps.com</a></div><div style="word-wrap: break-word;">Twitter @trentlapinski</div><div style="word-wrap: break-word;"><span style="font-size: 12px;">Skype: mobiletrent</span><br></div></div></div></div><br></span><div><div class="h5"><div><div>On Sep 26, 2014, at 7:12 PM, Daniel Fenn <<a href="mailto:danielx386@gmail.com" target="_blank">danielx386@gmail.com</a>> wrote:</div><br><blockquote><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">After watching this fight I felt like telling trent to listen to the<br>song "let it go" from the movie frozen :)<br><br>*Sits back and watches*<br><br>On 9/27/14, Emil Uzelac <<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>> wrote:<br><blockquote>probably the last time where TRT is turned into (politely said) brothel!<br><br>On Friday, September 26, 2014, Philip M. Hofer (Frumph) <<a href="mailto:philip@frumph.net" target="_blank">philip@frumph.net</a>><br>wrote:<br><br><blockquote> Just going to giggle at this., and not cause any waves about it.<br><br>*From:* Otto <javascript:_e(%7B%7D,'cvml','<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>');><br>*Sent:* Friday, September 26, 2014 5:54 PM<br>*To:* Discussion list for WordPress theme reviewers.<br><javascript:_e(%7B%7D,'cvml','<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>');><br>*Subject:* Re: [theme-reviewers] Why can't theme authors have a second<br>version of a theme?<br><br> On Fri, Sep 26, 2014 at 7:42 PM, Trent Lapinski <<a href="mailto:trent@cyberchimps.com" target="_blank">trent@cyberchimps.com</a><br><javascript:_e(%7B%7D,'cvml','<a href="mailto:trent@cyberchimps.com" target="_blank">trent@cyberchimps.com</a>');>> wrote:<br><br><blockquote>The TRT has been over ruled by the WordPress Foundation, Matt himself,<br>and has been greatly influenced by Automattic and Audrey Capitol.<br><br></blockquote><br>Trent, let's be a bit more civil than that. The Foundation, Matt, and<br>those at Automattic have not done any such thing.<br><br>If Emil and the other admins want to change the rules, then nobody's<br>going<br>to stop them. I personally think it's a bad idea, and I'll say so, but<br>I'm<br>not going to use any form of veto power for something that is ultimately<br>so<br>silly.<br><br>When I want the rules to be changed, then I have to email those admins<br>and<br>convince them. Done it before.<br><br>The only time I've ever been really adamant about anything with regards<br>to<br>the review guidelines was on the security aspects. No using eval and<br>base64<br>and such. Things like that. Those are pretty obvious and sell themselves,<br>really. Those security things are the *only* thing I've ever pushed into<br>the guidelines (via theme-check) unilaterally.<br><br>My point was that talking to Emil and the other admins about it, in<br>ticket, is far from pointless. They do have the power to give you an<br>exception. They do have the power to change the guidelines. They do have<br>the power to ignore any or all of the guidelines based on their best<br>judgment. That's why they're the admins. I'm not going to stop them, nor<br>is<br>the Foundation, or Automattic. As for Matt, he likely doesn't have an<br>opinion on the matter either way and would probably have no issue with<br>it.<br><br>There is no need to be quite so extremely confrontational like this every<br>time you run into a minor disagreement. You don't need to convince me,<br>but<br>you probably could convince them.<br><br>-Otto<br><br><br>------------------------------<br>_______________________________________________<br>theme-reviewers mailing list<br><a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br><javascript:_e(%7B%7D,'cvml','<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><br></blockquote><br></blockquote><br><br>--<span> </span><br>Regards,<br>Daniel Fenn<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></div></blockquote></div><br></div></div></div></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>_______________________________________________<br>theme-reviewers mailing list<br><a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<br></blockquote></div><br><br>_______________________________________________ theme-reviewers mailing list<span class="Apple-converted-space"> </span><a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><span class="Apple-converted-space"> </span><a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a></div></div>_______________________________________________<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">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a></div></blockquote></div><br></div></body></html>