Create wiki pages describing merge team/dev lead tasks

[roslynwythe]

Overview

We need a wiki page describing merge team/dev lead tasks, to expedite onboarding and increase merge team engagement

Action Items

• We are currently in the process of moving the old wiki to the new website-wiki repo, so we will not be making any changes or additions to the old wiki at this time. Thus, we will be adding wiki content through a different process now. Read How to Contribute to the Wiki
• Create a wiki page with the following sections:
  • review onboarding prework issues
  • review prework issues in progress
  • review 2 weeks inactive issues (excluding prework issues)
  • Questions/In Review column
  • Help Wanted review
  • New Issue Approval review (ready for merge team or ready for dev lead )
  • ER column review
  • lead onboarding meetings
  • lead Tuesday dev-only meetings
  • lead Thursday office hours
  • lead Sunday dev/PM meetings
  • dependabot issues
  • onboard new merge team members
  • escalation of Slack questions
  • escalation of PR problems

Resources/Instructions

https://docs.google.com/spreadsheets/d/1phPsEd_RVjQlHI4hsPJVEqqi4Ua-4WI7lhXNggtuc24/edit#gid=664707926

[github-actions]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[roslynwythe]

Review onboarding prework issues

During onboarding, prework issues (which have the label `Complexity: Prework) need to be checked to ensure the following are correct:

• developer has completed a row in the roster
• developer's name is in the title
• developer is a public member of Hack for LA (confirm by hovering over GitHub handle)
• developer assigned to issue
• developer has assigned role: frontend, role: back end/devOps or both
• issue is on the Project Board
• there are no Missing labels
  If any of the above are incorrect, create a comment asking the dev to fix the problem. When all the above are correct, do the following:
• assign the milestone 08. Team workflow
• move the issue to the In Progress column
• add the developer's name to Onboard & Offboard: Junior Developers #3175

[roslynwythe]

Review prework issues in progress

• Check for comments from the developer indicating that they need help
• If a developer is waiting for an issue of a particular complexity, do the following:
  • Provide shortcut link for sorting the Project Board for appropriate issues
  • Apply the appropriate "needs" label (e.g "needs issue: medium")
  • Suggest that while waiting for an issue, they can create issues. Suggest that they check the column "ERs and Epics that are ready to be turned into issues"
• If the developer is going on a hiatus, move the issue to `Questions/In Review'
• The prework issue is closed when the developer is no longer active in HackforLA

[roslynwythe]

Review 2 weeks inactive issues (excluding prework issues)

• Review 2 weeks inactive issues in the In Progress column:
  • Read issue comments to determine if the developer needs assistance
  • Check the roster to make sure that the developer is still active with the project. If not, unassign the developer and skip to the action "After unassigning the developer from an issue" below
  • Create a comment requesting a progress update. There should be a recent bot comment that the developer can refer to for the required elements of a progress update.
    • Indicate that if the developer does not provide an update before a specific deadline, they will be unassigned from the issue. For a time-sensitive issue, the deadline should be in a few days. For other issues, the deadline can be longer, especially if it is a larger issue and the developer has clearly done a lot of work on the issue.
  • If the deadline has passed, unassign the developer from the issue
  • After unassigning a developer from an issue, move the issue to New Issue Approval and apply the ready for dev lead label so that it can be prepared for prioritization
  • To prepare the issue for prioritization
    • clean up the comments, hiding any comments that are outdated
    • consider whether the issue was confusing or should be labelled with a different complexity label. Make required changes to address those problems. Also edit as needed, for instance to uncheck Action Item checkboxes
    • apply the ready for prioritization label
• Review 2 weeks inactive issues in other columns
  • Read issue comments to determine if the developer needs assistance
  • Check the roster to make sure that the developer is still active with the project. If not, unassign the developer and skip to the action "After unassigning the developer from an issue" above
  • Create a comment requesting a progress update. There should be a recent bot comment that the developer can refer to for the required elements of a progress update.

[roslynwythe]

Questions/In Review column

• Use this shortcut linkto display the Questions/In Review column https://github.com/hackforla/website/projects/7#column-8178690
• Focus on issues with ready for dev lead label. Ignore issues with ready for product label.
• If comments indicate that the developer has a blocker, provide assistance as needed. If you are unable to answer a question, refer the developer to another merge team member or the dev lead. When the developer is able to resume work on the issue, move the issue back to In Progress and remove ready for dev lead label if it was applied
• Perform a review if required. For example, for an auditing issue, the action items will often call for the assignee to populate information on a spreadsheet or in a comment in the issue. Examine such results for completeness and accuracy. When complete, create a comment and close the issue "as completed". If changes are requested, remove the ready for dev lead label and instruct the developer to apply that label after the requested changes are complete or if more help is needed.
• If comments indicate that the developer was on hiatus, and the planned date of return has passed, create a comment requesting a status update

[roslynwythe]

Help Wanted review

• Use this shortcut link to locate issues with the `Status: Help Wanted" label https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22status%3A+help+wanted%22
• Focus on items in In Progress or Questions/In Review
• Provide assistance as needed. If you are unable to answer a question, refer it to another merge team member or to the dev lead. If help is needed from the product team, suggest that the developer bring the issue to a Sunday All-team meeting. If you are able to answer a question, then remove the Status: Help Wanted label

[ExperimentsInHonesty]

Why is this issue closed?