<div dir="ltr">I agree that the outcome was definitive, otherwise I would have removed it from Oenology as well. I replace the core Categories and Tags Widgets, so that I can add RSS feed links. (Yeah, I should probably push that back upstream into core, eh...?)</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 28, 2013 at 8:56 PM, Justin Tadlock <span dir="ltr">&lt;<a href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    It seemed pretty definitive to me since several us agreed on what
    was allowed and wrote up a new guideline.  I thought we had already
    added it to the rest of the Theme Review Guidelines.  Otherwise, I
    would&#39;ve made a note that we forgot to add it.<div><div class="h5"><br>
    <br>
    <div>On 2/28/2013 7:06 PM, Emil Uzelac
      wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">Not really sure if this was decided or not, but we
        talked about this for sure.
        <div>Please see: <a href="http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/009455.html" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/009455.html</a></div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Thu, Feb 28, 2013 at 6:26 PM, Justin
          Tadlock <span dir="ltr">&lt;<a href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It is OK.
             This was decided by the theme review team last year:<br>
            <a href="http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/009450.html" target="_blank">http://lists.wordpress.org/pipermail/theme-reviewers/2012-June/009450.html</a>
            <div>
              <div>
                <br>
                <br>
                On 2/28/2013 6:18 PM, Paul Appleyard wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  I thought it was OK to extend core functionality - as
                  long as it RETAINED the original functionality; ie
                  didn&#39;t break when they switched themes. So, replacing
                  a widget with a custom one of the same name that had
                  the original functionality but with some added powers.<br>
                  <br>
                  Paul<br>
                  <br>
                  On 1/03/2013 9:34 AM, Otto wrote:<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    On Thu, Feb 28, 2013 at 5:14 PM, Justin Tadlock<br>
                    &lt;<a href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.com</a>&gt;
                    wrote:<br>
                    <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      I disagree.  If we don&#39;t want developers ...<br>
                    </blockquote>
                    There is more than one type of developer.<br>
                    <br>
                    Removing widgets makes perfect sense to be available
                    for plugins<br>
                    territory. Doesn&#39;t make sense for themes. Yet
                    another form of<br>
                    vendor-lock-in.<br>
                    <br>
                    -Otto<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>
                  </blockquote>
                  <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>
                </blockquote>
                <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>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
    </blockquote>
    <br>
  </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>