CoP DevOps: 2026 Leads and PM meeting Agenda
Offen
@ale210 arbeitet bereits daran.
Seit 19.12.2025.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
complexity: small
feature: agenda
role: CoP lead
size: 0.5pt
Overview
This issue tracks the agenda for our weekly roadmap meetings
Issue Template
## [Date ] Meeting Agenda
### Prework to prep for meeting
- Check [icebox](https://github.com/orgs/hackforla/projects/73/views/1?filterQuery=status%3A%22Ice+Box%22)
- [ ] all icebox issues should not be [missing the dependency label](https://github.com/orgs/hackforla/projects/73/views/1?filterQuery=status%3A%22Ice+Box%22+-label%3Adependency) and a defined dependency at the top
- [ ] all issues in the icebox reviewed for if they have a resolved dependency, and moved to new issue review
- [ ] Weekly Label check https://github.com/hackforla/devops/issues/23
- [ ] [project board, new issue approval, no ready for no draft](https://github.com/orgs/hackforla/projects/73/views/1?filterQuery=status%3A%22New+Issue+Review%22+-label%3A%22ready+for+CoP+Lead%22%2C%22ready+for+product%22%2C%22ready+for+prioritization%22+-label%3Adraft)
- [ ] checking in on people active on our [CoP DevOps Roster](https://docs.google.com/spreadsheets/d/1j6l2cdyAEZ73NCXw0CwwMnh8tZda-oE7tu8usBwv4Bs/edit?pli=1&gid=2032152864#gid=2032152864&fvid=1084044363)
- [ ] check to make sure that anyone who is either not [currently on the roster or has left has open issues on the project Board](https://docs.google.com/spreadsheets/d/1j6l2cdyAEZ73NCXw0CwwMnh8tZda-oE7tu8usBwv4Bs/edit?gid=1659030645#gid=1659030645)
### Recurring items
- [ ] review any issues that are in the [new issue approval column](https://github.com/orgs/hackforla/projects/73/views/1?filterQuery=status%3A%22New+Issue+Review%22)
- [ ] Accountability and Support Check.
- [ ] Review assignments for each PM
- [ ] [Bonnie](https://github.com/orgs/hackforla/projects/73/views/1?filterQuery=assignee%3AExperimentsInHonesty)
- [ ] [Alex](https://github.com/orgs/hackforla/projects/73/views/1?filterQuery=assignee%3Aale210)
- [ ] [Ryan](https://github.com/orgs/hackforla/projects/73/views/1?filterQuery=assignee%3ARSkuma)
- [ ] checking in on people active on our roster
- [ ] finish adding labels to the issue that are still missing them (see the audit links in the Weekly Label check above)
- [ ] status report for individual projects on incubator
### New Items
- [ ] Carry over Items to next meeting that don't get addressed
### FYIs
-
### Notes from Meeting
### Task Items
Resources
Previous Agendas
- Vorherrschende Sprache
- PowerShell
- Sterne
- 8
- Forks
- 10
- Ø Merge
- 2 Std. 9 Min.
- Gemergte PRs (30 T.)
- 9
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus hackforla/devops
-
Fix CONTRIBUTING.md's "Getting write access" section - it contradicts the fork bot and the wikiOffencomplexity: small feature: Onboarding good first issue role: DevOps Engineer size: 1pt
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
-
complexity: small feature: maintenance role: DevOps Engineer size: 1pt
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
-
Research: List incubator projects and their associated resourcesEvtl. vergeben @ale210 hat das vor 5 Tagen übernommen. Offencomplexity: medium feature: incubator role: DevOps Engineer size: 3pt
hackforla/devops#232 · 2 Kommentare · 1 zugewiesene Person ·
-
complexity: small feature: maintenance role: DevOps Engineer size: 1pt
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 58/100
-
complexity: medium feature: security role: DevOps Engineer size: 3pt
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100