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.

Sign up for GitHub

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

Jump to bottom

Updating Github Triage Procedures: Lead Delegation #4282

Closed
mekarpeles opened this issue Dec 15, 2020 · 2 comments
Closed

Updating Github Triage Procedures: Lead Delegation #4282

mekarpeles opened this issue Dec 15, 2020 · 2 comments
Assignees
@mekarpeles
Labels
Lead: @mekarpeles Issues overseen by Mek (Staff: Program Lead) [managed] Needs: Community Discussion This issue is to be brought up in the next community call. [managed] Priority: 2 Important, as time permits. [managed]

Comments

@mekarpeles
Copy link
Member

Describe the problem that you'd like solved

Right now we have too many issues which are at risk of falling through the cracks. This issue outlines possible managed label changes and Lead assignments which will help split our ~500 issues into blocks which team Leads may help better triage and manage. This also includes discussion and communication of proposed triage processes w/ team leads.

Proposal & Constraints

Additional context

Stakeholders
@mekarpeles mekarpeles added Priority: 2 Important, as time permits. [managed] Needs: Community Discussion This issue is to be brought up in the next community call. [managed] Lead: @mekarpeles Issues overseen by Mek (Staff: Program Lead) [managed] labels Dec 15, 2020
@mekarpeles mekarpeles added this to the Active Sprint milestone Dec 15, 2020
@mekarpeles mekarpeles self-assigned this Dec 17, 2020
@cdrini cdrini modified the milestones: Active Sprint, Next (proposed) Jan 4, 2021
@mekarpeles
Copy link
Member Author

See: #3984 Leads will manage their own email outreach to volunteers + propose & manage their own Epics, and set good first issues.

Should be codified in getting started or wiki lead table?

@mekarpeles
Copy link
Member Author

mekarpeles commented Jan 19, 2021 •
edited
Loading

I think we arrived at some basic Lead responsibilities which include:

  1. Triaging issues which are marked Lead: @you and Needs: Triage -- i.e. adding labels, removing the Needs: Triage label, and adding a Priority: tag according to the priority descriptions
  2. Adding a section to https://openlibrary.org/volunteer which represents (a) their team, (b) with a link to documentation (e.g. Communications Guide or Librarians Guides + how to get started on your team (e.g. Getting Started), (c) a link to email them + @mekarpeles, (d) some way (e.g. a github prepared issue link w/ labels) to identify Good First & Help Wanted issues
  3. Replying to emails from https://openlibrary.org/volunteer page cc'ing @mekarpeles w/ friendly messaging + some of the info above (how to get started)
  4. Maintaining and coordinating comments on issues which are Lead: @you -- this does not mean the Lead must do the work, just that they're responsible for coordinating with volunteers, code reviewing, closing stale issues, bring up questions or blockers to the right teammates, etc.
  5. Maintaining Epic issues for their larger plans / efforts (like Python3, Provisioning & Deployment Book Notes, Accessibility, etc) which group + outline related major issues (so anyone at a glance knows the state of a project and the important issues + blockers). e.g.

These items to be formalized in:

This was referenced Jan 20, 2021
Merged
Closed
@mekarpeles mekarpeles removed this from the Next (proposed) milestone Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mekarpeles mekarpeles

Labels
Lead: @mekarpeles Issues overseen by Mek (Staff: Program Lead) [managed] Needs: Community Discussion This issue is to be brought up in the next community call. [managed] Priority: 2 Important, as time permits. [managed]
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mekarpeles @cdrini