They're complementary. At least in the short term the spreadsheet can
help us get our current backlog under control. I'd like to at least be
thinking about tools that can help us when patch volume inevitably
grows to 2-3 times the current level.

On Thu, May 30, 2019 at 12:28 AM Micah Kornfield <[email protected]> wrote:
>
> That sounds great Wes, than you and your team for taking it on.
>
> Can you clarify, if you would prefer this approach to the one I proposed 
> above (i.e. should I delete the spreadsheet) or are they complementary?
>
> Thanks,
> Micah
>
> On Wed, May 29, 2019 at 12:07 PM Wes McKinney <[email protected]> wrote:
>>
>> On the call today we discussed possibly repurposing the Spark PR
>> dashboard application for our use
>>
>> * https://github.com/databricks/spark-pr-dashboard
>> * https://spark-prs.appspot.com/
>>
>> This is a project that my team could take on this year sometime
>>
>> On Wed, May 29, 2019 at 4:12 AM Fan Liya <[email protected]> wrote:
>> >
>> > Sounds like a great idea. I am interested in Java PRs.
>> >
>> > Best,
>> > Liya Fan
>> >
>> > On Wed, May 29, 2019 at 1:28 PM Micah Kornfield <[email protected]>
>> > wrote:
>> >
>> > > Sorry for the delay.  I created
>> > >
>> > > https://docs.google.com/spreadsheets/d/146lDg11c5ohgVkrOglrb42a1JB0Gm1qBRbnoDlvB8QY/edit#gid=0
>> > > as
>> > > simple way to distribute old PRs if you are interested in helping, please
>> > > add a comment under the language and I'll add you.
>> > >
>> > > PMC/Committers, I can share edit access if you let me know which e-mail
>> > > account I should grant access to.
>> > >
>> > > Thanks,
>> > > Micah
>> > >
>> > > On Tue, May 21, 2019 at 9:22 PM Micah Kornfield <[email protected]>
>> > > wrote:
>> > >
>> > > > I agree on hand curation for now.
>> > > >
>> > > >  I'll try to setup a sign up spreadsheet for shepherding old PRs and 
>> > > > once
>> > > > that done assign reviewers/ping old PRs.  I expect to have something to
>> > > > share by the weekend.
>> > > >
>> > > > On Tuesday, May 21, 2019, Wes McKinney <[email protected]> wrote:
>> > > >
>> > > >> I think maintainers or contributors should be responsible for closing
>> > > >> PRs, it also helps with backlog curation (sometimes when a stale PR is
>> > > >> closed the JIRA may also be closed if it's a Won't Fix)
>> > > >>
>> > > >> On Tue, May 21, 2019 at 1:12 PM Antoine Pitrou <[email protected]>
>> > > >> wrote:
>> > > >> >
>> > > >> >
>> > > >> >
>> > > >> > Le 21/05/2019 à 20:02, Neal Richardson a écrit :
>> > > >> > > Automatically close stale PRs? https://github.com/probot/stale
>> > > >> >
>> > > >> > That doesn't sound like a good idea to me.
>> > > >> >
>> > > >> > Regards
>> > > >> >
>> > > >> > Antoine.
>> > > >>
>> > > >
>> > >

Reply via email to