hackforla / hackforla/engineering

Create guide for new leads

Offen
#69 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
documentation role: lead
Vorherrschende Sprache
Keine Sprachdaten
Sterne
42
Forks
2
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### 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)

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start with the linked AtD PM Guide as the example, then review the Hack for LA and Engineering CoP topics listed in the action items. Draft the new-lead guide, have it reviewed by the leads team, transfer it to a new wiki page, and add the page to the wiki index.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Bereich
documentation
Issue-Typ
Dokumentation
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
38/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.