Recruit volunteers for team open roles
オープン
まだ誰も着手していません。
評価
この issue はまだ評価されていません。
説明
complexity: small
feature: recruitment
role: CoP lead
size: 0.25pt
status: updated
Dependency
- need to recruit new team members to DevOps Community of Practice 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
- Replace the text
- 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
- 1.02 [Replace with OPEN ROLE TEMPLATE]
- 1.03 HfLA: Open Roles board
- 1.04 Copy to post in CoP Slack Channels when there is an open role
Hi, the DevOps Community of Practice 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]
- 主要言語
- PowerShell
- スター
- 8
- フォーク
- 10
- 平均マージ
- 7時間 30分
- マージ済み PR(30日)
- 22
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
hackforla/devops のほかの issue
-
Fix CONTRIBUTING.md's "Getting write access" section - it contradicts the fork bot and the wiki オープンcomplexity: small feature: Onboarding good first issue role: DevOps Engineer size: 1pt
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
-
complexity: small feature: maintenance role: DevOps Engineer size: 1pt
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
-
complexity: small feature: maintenance role: DevOps Engineer size: 1pt
難易度 3/5 1〜2日 初心者へのやさしさ 58/100
-
complexity: medium feature: security role: DevOps Engineer size: 3pt
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
-
Migrate the Terraform S3 backends off dynamodb_table onto use_lockfile and delete the lock tables オープンcomplexity: medium feature: maintenance role: DevOps Engineer size: 2pt
難易度 5/5 1週間以上 初心者へのやさしさ 45/100