Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next Step Bot #10229

Open
mekarpeles opened this issue Dec 30, 2024 · 0 comments
Open

Next Step Bot #10229

mekarpeles opened this issue Dec 30, 2024 · 0 comments
Assignees
Labels
Lead: @mekarpeles Issues overseen by Mek (Staff: Program Lead) [managed] Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Detail Submitter needs to provide more detail for this issue to be assessed (see comments). [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Theme: Project Management Type: Proposal

Comments

@mekarpeles
Copy link
Member

mekarpeles commented Dec 30, 2024

Proposal

TL;DR before assigning issues to contributors who may be likely to bounce, add one step of useful friction / engagement before assignment that requires the contributor to put skin in the game, engage with a useful prompt, and help us improve the issue or identify questions first.

Issues on Open Library github get assigned to contributors and then become stale and it’s hard to know when they’re stale. One solution is to engage more with contributors prior to assigning them. We hypothesize some of this process may be automated.

Furthermore, by automating some of this process, we may be able to get contributors to take actionable next steps which help us:

  1. have confidence they understand the issue (and have skin in the game)
  2. identify / understand where they may be stuck
  3. enlist the contributor to at least participate in breakdown (to the extent they're able)

This might mean:

  • proposing designs for feedback
  • identifying (or asking) which files are relevant to the project
  • proposing or explaining their approach to addressing the issue (for feedback)
  • asking the contributor if they have any question or are blocked by anything

Justification

Why do contributors ask to be assigned to issues and then not follow through?

Contributors may forget or get busy... For these cases, we may be able to automatically add the Needs: Review Assignee Issues that may have been abandoned by assignees label to these issues (or exemptions) as per:

In my experience, a more common reason is that a contributor stalls because they may be expecting a mentor to help guide them step-by-step or provide additional guidance.

Why do they need additional guidance?

Because the issue may be complicated, overwhelming, or require further breakdown, and it may be difficult to know what question to even ask in order to get started.

Why are next steps unclear?

Because staff sometimes doesn’t provide sufficient breakdown for issues and often times no direction is communicated to the contributor to help them know what followup question to ask.

Breakdown

When someone asks to be assigned to an issue, depending on the format, have Next Step Bot respond to the patron with a followup to make sure they can succeed once assigned.

@mekarpeles mekarpeles added Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Lead: @mekarpeles Issues overseen by Mek (Staff: Program Lead) [managed] Theme: Project Management labels Dec 30, 2024
@mekarpeles mekarpeles added this to the 2025 (Provisional) milestone Dec 30, 2024
@mekarpeles mekarpeles added Type: Proposal Needs: Detail Submitter needs to provide more detail for this issue to be assessed (see comments). [managed] and removed Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed] labels Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Lead: @mekarpeles Issues overseen by Mek (Staff: Program Lead) [managed] Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Detail Submitter needs to provide more detail for this issue to be assessed (see comments). [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Theme: Project Management Type: Proposal
Projects
None yet
Development

No branches or pull requests

2 participants