<div dir="ltr">I&#39;m fine with that &quot;guideline&quot; being added immediately ... as noted, we missed putting it in before and it is more clarification than anything else.<br></div><div class="gmail_extra"><br clear="all">

<div>Edward Caissie<br>aka Cais.</div>
<br><br><div class="gmail_quote">On Fri, Mar 1, 2013 at 10:05 AM, Chip Bennett <span dir="ltr">&lt;<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div dir="ltr">We do wait for the release cycle for new or significantly changed Guidelines; anything that&#39;s a clarification, omission, or especially egregious (such as some new critical security issue) can generally be added when needed.</div>

<div class="HOEnZb"><div class="h5">
<div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 1, 2013 at 9:47 AM, 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">
    No, not really.  I just figured we&#39;d wait since we generally add
    guidelines when WP is updated.  I don&#39;t see any reason why it
    couldn&#39;t go in right now though.<div><div><br>
    <br>
    <div>On 3/1/2013 8:43 AM, Chip Bennett
      wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">That is clearly an oversight from a previously held
        discussion/decision, and should be added. Is there any
        particular reason to wait until 3.6 to do so?</div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">
          On Fri, Mar 1, 2013 at 9:39 AM, 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"> I would be on board
              with that too (enhancing but not combining widgets).  <br>
              <br>
              We should nail out a guideline for this for the 3.6
              guideline updates.  Here&#39;s the text from our original
              guideline for this that was never added to the theme
              review page:<br>
              <pre style="line-height:normal;text-indent:0px;letter-spacing:normal;text-align:start;font-variant:normal;text-transform:none;font-style:normal;font-weight:normal;word-spacing:0px">Themes may OPTIONALLY unregister core Widgets
If unregistered, Themes are REQUIRED to replace these Widgets with their own (extended) version</pre>
              I think that should cover it.
              <div>
                <div><br>
                  <br>
                  <div>On 3/1/2013 8:14 AM, Chip Bennett wrote:<br>
                  </div>
                  <blockquote type="cite">
                    <div dir="ltr">I agree with Cais that *enhancing*
                      core Widgets is one matter, and inherently
                      acceptable, and that *combining&quot; core Widgets is a
                      separate matter, and not acceptable.
                      <div><br>
                      </div>
                      <div>From the end user&#39;s perspective: changing the
                        active Theme should not change the list of
                        default core Widgets. If the user sees core
                        &quot;Archives&quot; and &quot;Recent Posts&quot; Widgets listed
                        with Theme A active, the user should still see
                        &quot;Archives&quot; and &quot;Recent Posts&quot; Widgets listed
                        with Theme B active.</div>
                      <div><br>
                      </div>
                      <div>This conversation has motivated me to push my
                        Category and Tag Widget improvements back
                        upstream, along with Oenology&#39;s &quot;Post Formats&quot;
                        widget. If they are accepted into core, I&#39;d love
                        to be able to remove them from the Theme. (Less
                        code to maintain FTW.)</div>
                      <div><br>
                      </div>
                      <div>As for cluttering up the Widgets screen:
                        well, IMHO it&#39;s already a huge mess. What would
                        a few extra Widgets matter? :)</div>
                    </div>
                    <div class="gmail_extra"><br>
                      <br>
                      <div class="gmail_quote"> On Fri, Mar 1, 2013 at
                        8:49 AM, Edward Caissie <span dir="ltr">&lt;<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.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 dir="ltr">
                            <div>
                              <div>
                                <div>Although I did agree with the idea
                                  of replacing default core widgets with
                                  &quot;enhanced&quot; versions of the same
                                  widget, given this conversation I
                                  believe this can be expanded upon.<br>
                                  <br>
                                </div>
                                First, I do not agree with multiple
                                &quot;default&quot; widgets being replaced with a
                                single &quot;enhanced&quot; widget. As far as I am
                                concerned this is not acceptable.<br>
                                <br>
                              </div>
                              Second, if the default widget is going to
                              be &quot;replaced&quot; it should be in the sense
                              the new &quot;enhanced&quot; widget is simply
                              extending the default widget.<br>
                              Lets take the default &quot;Categories&quot; widget
                              as an example, an extended version should
                              provide exactly the same functionality as
                              the default version when it is initiated.<br>
                              The enhanced version then may add on top
                              of that functionality additional options
                              such as an include or exclude option,
                              again just as an example using the
                              Categories widget, there are much better
                              enhancements that could be implemented,
                              such as RSS feeds (h/t Chip)<br>
                              <br>
                            </div>
                            That being said, I also happen to agree with
                            Otto on why lose out on the opportunity to
                            self-promote with a custom widget that may
                            be exclusive to the theme ... even adding in
                            three or four theme widgets will not really
                            clutter up the widget window that much; and,
                            if they are prefaced with the theme name
                            (IIRC this is not covered in the guidelines)
                            they will also naturally be grouped together
                            as well.<span><font color="#888888"><br>
                              </font></span></div>
                          <div class="gmail_extra"><span><font color="#888888"><br clear="all">
                                <div>Edward Caissie<br>
                                  aka Cais.</div>
                              </font></span>
                            <div>
                              <div> <br>
                                <br>
                                <div class="gmail_quote">On Fri, Mar 1,
                                  2013 at 5:58 AM, Dane Morgan <span dir="ltr">&lt;<a href="mailto:dane@danemorganmedia.com" target="_blank">dane@danemorganmedia.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>
                                      <div>On 2013-02-28 22:50, 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 10:45 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"> It
                                            can be an archive widget,
                                            posts widget, or something
                                            like that.  Another<br>
                                            good example is a
                                            combination of the tags and
                                            categories widgets into a<br>
                                            super-cool taxonomy/terms
                                            widget.  That&#39;d be neat to
                                            see.<br>
                                          </blockquote>
                                          Those should be *entirely new
                                          widgets*, labeled with the
                                          name of the<br>
                                          theme in front of them..<br>
                                          <br>
                                          Why would you be intentionally
                                          incompatible *and* ignore
                                          freebie<br>
                                          branding opportunities? I just
                                          don&#39;t get it at all.<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>
                                      </div>
                                    </div>
                                    +1<br>
                                    <br>
                                    I think Otto has this one right.
                                    Maybe some users don&#39;t agree that
                                    your enhancement is an enhancement.
                                    Give them the option and let them
                                    try you out, don&#39;t confuse them and
                                    take away default choices.
                                    <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>
                                      </div>
                                    </div>
                                  </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>
                      <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" 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>
      <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" 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">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>