Assign bot v2 - suggestions

[yangwao]

I guess would be nice to reflect on what other things should be tackled for the next version of assign bot tho

• [x] One thing could be if previous participants made like 10 PRs merged in the upstream main branch, would be nice to give them like 24h or 50%-100% time bonus as original ideation was to prevent issue blockers who try act do issue and then bailout and first-timers who would not deliver anything at all.

Case

https://github.com/kodadot/nft-gallery/issues/2921 https://github.com/kodadot/nft-gallery/pull/2931#issuecomment-1114181188

Other suggestion

From https://github.com/kodadot/nft-gallery/issues/2448#issuecomment-1088473732

Offtopic thoughts would be nice (optional) for v2 assign bot. Bot would not assign higher priority issues, i.e. if we have p2 issues, some pool of issues which is significantly bigger than p3+, would not assign for p3+ or make it as a lower bound paid out issue, not sure how to handle this most efficiency.

I get that some p3 are easily solvable, but if projects would have ton of p2 open and people start working p5 probably it's not what they want to see being done on the short-term horizon from perspective of project

But this could be a highly controversial topic, but projects out there would help steer where they want to be if they set some priority labels for example.

[petersopko]

This is fairly easy to setup, my only concern would be that we're disadvantaging new devs right at the beginning (time pressure). Maybe add similar time boost for issues labelled "good first issue" as well?

[petersopko]

• [x] One thing could be if previous participants made like 10 PRs merged in the upstream main branch, would be nice to give them like 24h or 50%-100% time bonus as original ideation was to prevent issue blockers who try act do issue and then bailout and first-timers who would not deliver anything at all.

Added this as we discussed yesterday, 10+ merged PRs or issues labelled "good first issue" -> +50% bounty time.

[petersopko]

@yangwao are merged branches getting automatically deleted or was this one done manually? The initial bot setting was done, so that bot has always one branch running where the updates would be performed and from which PR would be opened.

It can be done in a different way, but this one seemed reliable. Found out about this when bot failed to update leaderboard/burnrate.

2909 <- happened here

[petersopko]

:wave:

[kodabot]

ASSIGNED - @petersopko 🔒 LOCKED -> Monday, May 16th 2022, 21:30:11 UTC -> 36 hours

[petersopko]

ignore

[kodabot]

ISSUE IGNORED - issue #2932 will be ignored.

[petersopko]

@yangwao added the requested modification, if you @vikiival or @kodabot does the assigning, bot will ignore it and won't register it as something he should track

[vikiival]

Idea: Issues with label research should not be assignable

WDYT: @yangwao @petersopko ?

[petersopko]

Idea: Issues with label research should not be assignable

WDYT: @yangwao @petersopko ?

added this, @yangwao lmk if you don't agree

[KngZhi]

One thing could be if previous participants made like 10 PRs merged in the upstream main branch, would be nice to give them like 24h or 50%-100% time bonus as original ideation was to prevent issue blockers who try act do issue and then bailout and first-timers who would not deliver anything at all.

I was thinking maybe for the time bonus, using $ label as a standard, like if one reaches 30 $ total we consider grant this feat. Since for different $ label, the merged difficulty is very much different.

[petersopko]

bot started unassigning with expired message, after the issue was completed and merged in the last couple of weeks, should be fixed now ✅

[vikiival]

Woah, nice job!