Create wiki page to document merge team responsibilities

[roslynwythe]

Overview

As dev leads, we need to create a wiki page to document merge team responsibilities. Currently our only resource for new merge team members is this google doc: HfLA-Website: Developer Roles and Responsibilities which is incomplete.

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
• The wiki should cover these responsibilities:
  • merging PRs: use this as a draft: google doc: HfLA-Website: Developer Roles and Responsibilities but it will require review
  • creating issues: link to Wiki: how to create issues but note - the wiki must be updated to include discussion of ERs - see Update Wiki page "How to Create Issues" to include Emergent Request issues and procedures #4916
  • Merge team members are expected to assist junior developers in various ways including:
    • Replying to questions posted in #hfla-site channel - see draft content in comment below
    • Questions/In Review` column - see draft content in comment below
    • Resolving blockers for issues with the Help Wanted label
    • Prework checklists - see draft content in comment below
    • Inactive issues and PRs - see draft content in comment below
  • Merge team members may be asked to lead team meetings and onboard junior devs.
• Once a draft has been posted as a comment in this issue, place the issue in the Questions/In Review column with the ready for dev lead label.

Resources/Instructions

• google doc: HfLA-Website: Developer Roles and Responsibilities

[roslynwythe]

Replying to questions posted in #hfla-site channel:
On their designated merge day, merge team members should scan the #hfla-site channel for questions that have not been answered in the past 24 hours. They should attempt to resolve the questions, or otherwise to refer the question to the merge team/dev lead designated for escalation of Slack questions.