Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recruit volunteers for team open roles #98

Open
22 tasks
ExperimentsInHonesty opened this issue Jun 22, 2024 · 3 comments
Open
22 tasks

Recruit volunteers for team open roles #98

ExperimentsInHonesty opened this issue Jun 22, 2024 · 3 comments
Labels

Comments

@ExperimentsInHonesty
Copy link
Member

Dependency

  • need to recruit new team members to Engineering Community of Practice

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

@ExperimentsInHonesty
Copy link
Member Author

Post from previous UI/UX Design open roles board, Filled column

copy code
**Project Name**: Engineering Community of Practice Logo

**About the Project**: Logo Design |
 Issue[#62](https://github.com/hackforla/engineering/issues/62)

**Volunteer Opportunity**: We are looking for a designer to design a logo for the organization

**Duration**: 1 month

**Who to communicate your interest to**
- #engineering
- AJ Price, Micah Elm, Harrison Katz, Alejandro Gomez

https://github.com/hackforla/engineering
viewable code

Project Name: Engineering Community of Practice Logo

About the Project: Logo Design |
Issue#62

Volunteer Opportunity: We are looking for a designer to design a logo for the organization

Duration: 1 month

Who to communicate your interest to

  • #engineering
  • AJ Price, Micah Elm, Harrison Katz, Alejandro Gomez

https://github.com/hackforla/engineering

@ExperimentsInHonesty
Copy link
Member Author

Post from previous Engineering open roles board, Community Lead column

copy code
**Engineer Mentors**

**Volunteer Opportunity**: 
The Engineering Community of Practice is looking for mentors to help answer community questions about
- Software Engineering
- Career Development
- their Hack for LA projects

**Responsibilities include**: 
* Working with the Engineering CoP leads to nurture the community and mentorship program
* Interacting with the engineering community on Slack
* Answering questions at Mentor Nights

**Duration**:  Open-ended

**Time commitment**: 2-3 hours a month
* 1 50-minute Engineering CoP meeting a month
* 1 or 2 15-minute meetings with leads to give feedback on CoP meetings a month
* other time spent answering questions on Slack or working with leads on development as needed

[MORE INFORMATION](https://github.com/hackforla/engineering/wiki/Community-Leads-Roles#engineering-mentors-wanted)
viewable code

Engineer Mentors

Volunteer Opportunity:
The Engineering Community of Practice is looking for mentors to help answer community questions about

  • Software Engineering
  • Career Development
  • their Hack for LA projects

Responsibilities include:

  • Working with the Engineering CoP leads to nurture the community and mentorship program
  • Interacting with the engineering community on Slack
  • Answering questions at Mentor Nights

Duration: Open-ended

Time commitment: 2-3 hours a month

  • 1 50-minute Engineering CoP meeting a month
  • 1 or 2 15-minute meetings with leads to give feedback on CoP meetings a month
  • other time spent answering questions on Slack or working with leads on development as needed

MORE INFORMATION

@ExperimentsInHonesty
Copy link
Member Author

ExperimentsInHonesty commented Jul 23, 2024

Post from previous Engineering open roles board, Filled column

Post 1

copy code
**Engineering CoP Community Co-Lead**
**Volunteer Opportunity:** The Hack for LA Engineering Community of Practice is in need of a Community Lead team member to help plan and lead weekly meetings. A community lead is someone who can roll up their sleeves and work with others to create a space that supports and energizes the Engineers who make sure the Hack for LA projects are a success. 

**Duration:** At least 6 months

**Time commitments:** 2-3 hours a week
- 1 50-minute Engineering CoP meeting a _week_ - Thursdays
- 1 25-minute Engineering CoP leads meeting a _week_ - Thursdays
- 1 50-minute HfLA CoP leads meeting a _month_ - First Wednesdays (rotating)
- 1-2 hours of task work a _week_

[GO HERE FOR MORE INFORMATION](https://github.com/hackforla/engineering/wiki/Community-Leads-Roles#engineering-cop-community-co-lead)
viewable code

Engineering CoP Community Co-Lead
Volunteer Opportunity: The Hack for LA Engineering Community of Practice is in need of a Community Lead team member to help plan and lead weekly meetings. A community lead is someone who can roll up their sleeves and work with others to create a space that supports and energizes the Engineers who make sure the Hack for LA projects are a success.

Duration: At least 6 months

Time commitments: 2-3 hours a week

  • 1 50-minute Engineering CoP meeting a week - Thursdays
  • 1 25-minute Engineering CoP leads meeting a week - Thursdays
  • 1 50-minute HfLA CoP leads meeting a month - First Wednesdays (rotating)
  • 1-2 hours of task work a week

GO HERE FOR MORE INFORMATION

Post 2

copy code
**Engineering CoP Community Co-Lead**
**Mentor Coordinator**

**Volunteer Opportunity:** The Hack for LA Engineering Community of Practice is in need of a Community Lead team member to help organize Mentor Nights. A community lead is someone who can roll up their sleeves and work with others to create a space that supports and energizes the Engineers who make sure the Hack for LA projects are a success.

**Duration:** At least 6 months

**Time commitments:** 5-6 hours a week
- 1 50-minute Engineering CoP meeting a _week_ - Thursdays
- 1 25-minute Engineering CoP leads meeting a _week_ - Thursdays
- 1 50-minute HfLA CoP leads meeting a _month_ - First Wednesdays
- 3-4 hours of task work a _week_

[GO HERE FOR MORE INFORMATION](https://github.com/hackforla/engineering/wiki/Community-Leads-Roles#engineering-cop-community-co-lead---mentor-coordinator)
viewable code

Engineering CoP Community Co-Lead
Mentor Coordinator

Volunteer Opportunity: The Hack for LA Engineering Community of Practice is in need of a Community Lead team member to help organize Mentor Nights. A community lead is someone who can roll up their sleeves and work with others to create a space that supports and energizes the Engineers who make sure the Hack for LA projects are a success.

Duration: At least 6 months

Time commitments: 5-6 hours a week

  • 1 50-minute Engineering CoP meeting a week - Thursdays
  • 1 25-minute Engineering CoP leads meeting a week - Thursdays
  • 1 50-minute HfLA CoP leads meeting a month - First Wednesdays
  • 3-4 hours of task work a week

GO HERE FOR MORE INFORMATION

Post 3

copy code
**Engineering CoP Community Co-Lead Speaker Series Coordinator**
**Volunteer Opportunity:** The Hack for LA Engineering Community of Practice is in need of a Community Lead team member to help organize Speaker Series. A community lead is someone who can roll up their sleeves and work with others to create a space that supports and energizes the Engineers who make sure the Hack for LA projects are a success. See previous speakers [here](https://github.com/hackforla/engineering/wiki/Previous-Engineering-CoP-Speakers)

**Duration:** At least 6 months

**Time commitments:** 5-6 hours a week
- 1 50-minute Engineering CoP meeting a _week_ - Thursdays
- 1 25-minute Engineering CoP leads meeting a _week_ - Thursdays
- 1 50-minute HfLA CoP leads meeting a _month_ - First Wednesdays
- 3-4 hours of task work a _week_

[GO HERE FOR MORE INFORMATION](https://github.com/hackforla/engineering/wiki/Community-Leads-Open-Roles#engineering-cop-community-co-lead---speaker-coordinator)
viewable code

Engineering CoP Community Co-Lead Speaker Series Coordinator
Volunteer Opportunity: The Hack for LA Engineering Community of Practice is in need of a Community Lead team member to help organize Speaker Series. A community lead is someone who can roll up their sleeves and work with others to create a space that supports and energizes the Engineers who make sure the Hack for LA projects are a success. See previous speakers here

Duration: At least 6 months

Time commitments: 5-6 hours a week

  • 1 50-minute Engineering CoP meeting a week - Thursdays
  • 1 25-minute Engineering CoP leads meeting a week - Thursdays
  • 1 50-minute HfLA CoP leads meeting a month - First Wednesdays
  • 3-4 hours of task work a week

GO HERE FOR MORE INFORMATION

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant