hackforla / hackforla/engineering

Create guide for new leads

Open
#69 0 comments 0 reactions 0 assignees View on GitHub
documentation role: lead
Dominant language
No language data
Stars
42
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Overview
HfLA volunteers typically stay for 6-12 months, so we need a plan in place to train new leads to keep this community going.

### Action Items
- Write guide:
- [ ] Background on Hack for LA and Engineering CoP
- [ ] Introduction to the GitHub and Slack
- [ ] Community Space Management
- Slack
- Maintaining the wiki and readme
- Welcoming new members
- Project Boards
- Open Roles board
- Guides board
- Community of Practice board
- [ ] Community meetings management
- Weekly CoP meetings schedule
- Speaker meetings
- Lightning Talks
- Mentor Nights
- Calendaring / scheduling
- Weekly admin duties (agendas, leads meetings)
- [ ] Review with leads team
- [ ] Transfer onto a new wiki page and create a link to it in the index

### Resources/Instructions
- Example guide: [AtD PM Guide](https://github.com/hackforla/access-the-data/wiki/PM-Guide)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.