<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    So did we ever decide on how to prioritize reviews?<br>
    (I was still mentally / notification catching up after 0.18.1)<br>
    <br>
    There are some really important issues to tackle, often with
    proposed solutions, not no reviews!<br>
    It's hard for everybody to keep the big picture in mind with such a
    full issue tracker.<br>
    I think it might be helpful if Joel and me prioritize issues.
    Obviously that will only make<br>
    sense if the other team members check up on it when deciding what to
    review / work on.<br>
    <br>
    Do we want to try to seriously use the project feature?<br>
    <a class="moz-txt-link-freetext" href="https://github.com/scikit-learn/scikit-learn/projects/5">https://github.com/scikit-learn/scikit-learn/projects/5</a><br>
    <br>
    On my monitor I can fit four columns and the "add cards" tab.<br>
    I tried using five columns (separating in-progress and stalled PRs)
    but then I could access the right-most column when<br>
    the "add cards" was open.<br>
    The whole interface is a bit awkward but maybe the best we have (for
    example moving something from the bottom<br>
    to the top is easiest by moving it to a different column, then
    scrolling up, then moving it back)<br>
    <br>
    wdyt?<br>
    Andy<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 09/29/2016 11:05 PM, Joel Nothman
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAAkaFLWsK+zSeGJPKsE8kHTTgL_+7+w_h3C4egdMxobO9s9GDA@mail.gmail.com"
      type="cite">
      <div dir="ltr">The spreadsheet seems to have some duplications and
        presumably some missing rows, with apologies. I assume some is
        due to the github pagination, and some may be my error. Not a
        big enough error to fix up.</div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On 30 September 2016 at 05:15, Raphael
          C <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:drraph@gmail.com" target="_blank">drraph@gmail.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">My
            apologies I see it is in the spreadsheet. It would be great
            to see<br>
            this work finished for 0.19 if at all possible IMHO.<br>
            <span class="HOEnZb"><font color="#888888"><br>
                Raphael<br>
              </font></span>
            <div class="HOEnZb">
              <div class="h5"><br>
                On 29 September 2016 at 20:12, Raphael C <<a
                  moz-do-not-send="true" href="mailto:drraph@gmail.com">drraph@gmail.com</a>>
                wrote:<br>
                > I hope this isn't out of place but I notice that<br>
                > <a moz-do-not-send="true"
                  href="https://github.com/scikit-learn/scikit-learn/pull/4899"
                  rel="noreferrer" target="_blank">https://github.com/scikit-<wbr>learn/scikit-learn/pull/4899</a>
                is not in the<br>
                > list. It seems like a very worthwhile addition and
                the PR appears<br>
                > stalled at present.<br>
                ><br>
                > Raphael<br>
                ><br>
                > On 29 September 2016 at 15:05, Joel Nothman <<a
                  moz-do-not-send="true"
                  href="mailto:joel.nothman@gmail.com">joel.nothman@gmail.com</a>>
                wrote:<br>
                >> I agree that being able to identify which PRs
                are stalled on the<br>
                >> contributor's part, which on reviewers' part,
                and since when, would be<br>
                >> great. I'm not sure we've come up with a way
                that'll work though.<br>
                >><br>
                >> In terms of backlog, I've wondered if just
                getting things into a spreadsheet<br>
                >> would help:<br>
                >><br>
                >> <a moz-do-not-send="true"
href="https://docs.google.com/spreadsheets/d/1LdzNxQbn7A0Ao8zlUBgnvT42929JpAe9958YxKCubjE/edit"
                  rel="noreferrer" target="_blank">https://docs.google.com/<wbr>spreadsheets/d/<wbr>1LdzNxQbn7A0Ao8zlUBgnvT42929Jp<wbr>Ae9958YxKCubjE/edit</a><br>
                >><br>
                >> What other features of an Issue / PR would be
                useful to<br>
                >> sort/filter/pivottable on in a spreadsheet form
                like this?<br>
                >><br>
                >> (It would be extra nice if we could modify
                titles and labels within the<br>
                >> spreadsheet and have them update via the GitHub
                API, but I'm not sure I'll<br>
                >> get around to making that feature :P)<br>
                >><br>
                >><br>
                >> On 29 September 2016 at 23:45, Andreas Mueller
                <<a moz-do-not-send="true"
                  href="mailto:t3kcit@gmail.com">t3kcit@gmail.com</a>>
                wrote:<br>
                >>><br>
                >>> So I made a project for 0.19:<br>
                >>><br>
                >>> <a moz-do-not-send="true"
                  href="https://github.com/scikit-learn/scikit-learn/projects/5"
                  rel="noreferrer" target="_blank">https://github.com/scikit-<wbr>learn/scikit-learn/projects/5</a><br>
                >>><br>
                >>> The idea would be to drag and drop issues
                and PRs so that the important<br>
                >>> ones are at the top.<br>
                >>> We could also add an "important" column,
                currently the scrolling is pretty<br>
                >>> annoying.<br>
                >>> Thoughts?<br>
                >>><br>
                >>><br>
                >>><br>
                >>><br>
                >>> On 09/28/2016 03:29 PM, Nelle Varoquaux
                wrote:<br>
                >>>><br>
                >>>> On 28 September 2016 at 12:24, Andreas
                Mueller <<a moz-do-not-send="true"
                  href="mailto:t3kcit@gmail.com">t3kcit@gmail.com</a>>
                wrote:<br>
                >>>>><br>
                >>>>><br>
                >>>>> On 09/28/2016 02:21 PM, Nelle
                Varoquaux wrote:<br>
                >>>>>><br>
                >>>>>><br>
                >>>>>> I think the only ones worth
                having are the ones that can be dealt with<br>
                >>>>>> automatically and the ones that
                will not be used frequently:<br>
                >>>>>><br>
                >>>>>> - stalled after 30 days of
                inactivity [can be done automatically]<br>
                >>>>>> - in dispute [I don't expect it
                to be used often].<br>
                >>>>><br>
                >>>>> I think "in dispute" is actually
                one of the most common statuses among<br>
                >>>>> PRs.<br>
                >>>>> Or maybe I have a skewed picture of
                things.<br>
                >>>>> Many PRs stalled because it is not
                clear whether the proposed solution<br>
                >>>>> is a<br>
                >>>>> good one.<br>
                >>>><br>
                >>>> On the stalled one, sure, but there are
                a lot of PRs being merged<br>
                >>>> fairly quickly. So over all, I think it
                is quite rare. No?<br>
                >>>><br>
                >>>>> It would be great to have some way
                to get through the backlog of 400 PRs<br>
                >>>>> and<br>
                >>>>> I think tagging them might be
                useful.<br>
                >>>>> We rarely reject PRs, we could also
                revisit that policy.<br>
                >>>>><br>
                >>>>> For the backlog, it's pretty
                unclear to me how many are waiting for<br>
                >>>>> reviews,<br>
                >>>>> how many are waiting for changes,<br>
                >>>>> and how many are disputed.<br>
                >>>>> Tagging these might help people who
                want to review to find things to<br>
                >>>>> review,<br>
                >>>>> and people who want to code to pick<br>
                >>>>> up stalled PRs.<br>
                >>>><br>
                >>>> That sounds like a great use of labels,
                thought all of these need to<br>
                >>>> be tagged manually.<br>
                >>>><br>
                >>>>> ______________________________<wbr>_________________<br>
                >>>>> scikit-learn mailing list<br>
                >>>>> <a moz-do-not-send="true"
                  href="mailto:scikit-learn@python.org">scikit-learn@python.org</a><br>
                >>>>> <a moz-do-not-send="true"
                  href="https://mail.python.org/mailman/listinfo/scikit-learn"
                  rel="noreferrer" target="_blank">https://mail.python.org/<wbr>mailman/listinfo/scikit-learn</a><br>
                >>>><br>
                >>>> ______________________________<wbr>_________________<br>
                >>>> scikit-learn mailing list<br>
                >>>> <a moz-do-not-send="true"
                  href="mailto:scikit-learn@python.org">scikit-learn@python.org</a><br>
                >>>> <a moz-do-not-send="true"
                  href="https://mail.python.org/mailman/listinfo/scikit-learn"
                  rel="noreferrer" target="_blank">https://mail.python.org/<wbr>mailman/listinfo/scikit-learn</a><br>
                >>><br>
                >>><br>
                >>> ______________________________<wbr>_________________<br>
                >>> scikit-learn mailing list<br>
                >>> <a moz-do-not-send="true"
                  href="mailto:scikit-learn@python.org">scikit-learn@python.org</a><br>
                >>> <a moz-do-not-send="true"
                  href="https://mail.python.org/mailman/listinfo/scikit-learn"
                  rel="noreferrer" target="_blank">https://mail.python.org/<wbr>mailman/listinfo/scikit-learn</a><br>
                >><br>
                >><br>
                >><br>
                >> ______________________________<wbr>_________________<br>
                >> scikit-learn mailing list<br>
                >> <a moz-do-not-send="true"
                  href="mailto:scikit-learn@python.org">scikit-learn@python.org</a><br>
                >> <a moz-do-not-send="true"
                  href="https://mail.python.org/mailman/listinfo/scikit-learn"
                  rel="noreferrer" target="_blank">https://mail.python.org/<wbr>mailman/listinfo/scikit-learn</a><br>
                >><br>
                ______________________________<wbr>_________________<br>
                scikit-learn mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:scikit-learn@python.org">scikit-learn@python.org</a><br>
                <a moz-do-not-send="true"
                  href="https://mail.python.org/mailman/listinfo/scikit-learn"
                  rel="noreferrer" target="_blank">https://mail.python.org/<wbr>mailman/listinfo/scikit-learn</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
scikit-learn mailing list
<a class="moz-txt-link-abbreviated" href="mailto:scikit-learn@python.org">scikit-learn@python.org</a>
<a class="moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/scikit-learn">https://mail.python.org/mailman/listinfo/scikit-learn</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>