hackforla / hackforla/knowledgebase
Recruit volunteers for team open roles
- Vorherrschende Sprache
- Python
- Sterne
- 2
- Forks
- 5
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Dependency
- [ ] need to recruit new team members to Knowledgebase team
### Overview
We need volunteer(s) to work on the open issues we have so that we can move the project forward.
### Action Items
#### Creating a new role post
- [ ] Copy the template post from the Community of Practice WIKI, Open Roles Templates (Resource 1.01)
- [ ] Paste the template in a comment below
- [ ] Customize the comment to reflect your open role
- [ ] Open a new issue by using the Open Role template (Resource 1.02)
- [ ] Copy and Paste your customized comment to the new issue
- [ ] Add the label for the role that you are recruiting for
- [ ] Submit the new issue
- [ ] Assign yourself to the new issue
- [ ] Add the issue to the HfLA: Open Roles project board (Resource 1.03)
- [ ] add the link of the new issue to the related comment on this issue
- [ ] keep yourself assigned to this issue until the role is filled
#### Marketing the new role post
- Post a link to the new issue in the Slack channel for the related Practice Area
- [ ] Copy the Slack message (Resource 1.04)
- [ ] Copy the message into the Slack Channel for the relevant Community of Practice (The Slack channels can be found on Resource 1.01)
- [ ] Replace the text `[Replace with LINK TO NEW ISSUE]` with link to the issue
- [ ] check your team Slack channel for people reaching out after every onboarding and at least every other day
#### Once Filled
- [ ] Hide the comment on this issue for the role you just filled
- [ ] Add the following comment to the role posting issue
```
This role has been filled by @[Replace with GITHUB HANDLE OF PERSON WHO IS TAKING ROLE]
```
- [ ] Close the role posting issue
- [ ] Unassign yourself from this issue
- If there are no open roles on this issue (i.e., if there are open roles, there will be unclosed comments)
- [ ] Add the label: Dependency and uncheck the dependency on top of this issue
- [ ] Move this issue to the icebox, on the project board
### Resources/Instructions
- 1.01 [Community of Practice WIKI, Open Roles Templates, Secondary Issue](https://github.com/hackforla/communities-of-practice/wiki/Open-Roles-Templates#secondary-issue)
- 1.02 [Replace with OPEN ROLE TEMPLATE]
- 1.03 [HfLA: Open Roles board](https://github.com/orgs/hackforla/projects/67)
- 1.04 Copy to post in CoP Slack Channels when there is an open role
```
Hi, the Knowledgebase has a volunteer posting, which includes details of how to get in touch with us if you are interested. [Replace with LINK TO NEW ISSUE]
```
Beitragsleitfaden
Rechercherichtung
Start with the Community of Practice Wiki's Open Roles Templates (Resource 1.01), then review the HfLA: Open Roles board (Resource 1.03) and the checklist in this issue. Done means creating and marketing the Knowledgebase role issue, linking it here, monitoring Slack, and completing the closure steps when the role is filled.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Bereich
- content
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 25/100