generated from hackforla/.github-hackforla-base-repo-template
-
-
Notifications
You must be signed in to change notification settings - Fork 4
Open Roles Templates
Bonnie Wolfe edited this page Jun 14, 2024
·
51 revisions
Open Roles Templates
All teams should have this issue on their repo only once
Recruit volunteers for team open roles draft
#### latest draft
### Dependency
- [ ] need to recruit new team members to website 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 WIKI: https://github.com/hackforla/communities-of-practice/wiki/Open-Roles-Templates
- 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 [Replace with NAME OF TEAM] 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]
```
#### Title
[Replace with PROJECT INITIALS]: Open Role for: [Replace with NAME OF ROLE]
#### Body
[Replace with PROJECT LOGO]
**Project Name**: [Replace with NAME OF PROJECT]
**Name of Role**: [Replace with NAME OF ROLE]
**Volunteer Opportunity**: [Replace with CUSTOM RECRUITMENT MESSAGE]
**Duration**: [Replace with On-going, or SPECIFY DURATION]
**Meeting Times**: [Replace with the MEETING TIMES THAT THIS ROLE MUST ATTEND AND ANY OPTIONAL MEETINGS, MARKING THEM AS OPTIONAL)
**Who to communicate your interest to**
- Slack channel link: [#[Replace with NAME OF SLACK CHANNEL]]([Replace with LINK TO YOUR SLACK CHANNEL])
- Slack name of person to contact in the channel: see who this issue is assigned to and @ message them in the channel above
[Read more about the project](https://www.hackforla.org/projects/[Replace with page name on hackforla.org website)