CoP DevOps: 2026 Leads and PM meeting Agenda
Ouverte
@ale210 y travaille déjà.
Depuis le 19/12/2025.
Évaluation
Cette issue n'a pas encore été évaluée.
Description
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
- Langage dominant
- PowerShell
- Étoiles
- 8
- Forks
- 10
- Merge moyen
- 2 h 9 min
- PR mergées (30 j)
- 9
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de hackforla/devops
-
Fix CONTRIBUTING.md's "Getting write access" section - it contradicts the fork bot and the wikiOuvertecomplexity: small feature: Onboarding good first issue role: DevOps Engineer size: 1pt
Difficulté 2/5 1-3 heures Accessibilité débutants 84/100
-
complexity: small feature: maintenance role: DevOps Engineer size: 1pt
Difficulté 2/5 1-3 heures Accessibilité débutants 88/100
-
Research: List incubator projects and their associated resourcesPeut-être pris @ale210 l’a pris il y a 5 jours. Ouvertecomplexity: medium feature: incubator role: DevOps Engineer size: 3pt
hackforla/devops#232 · 2 commentaires · 1 personne assignée ·
-
complexity: small feature: maintenance role: DevOps Engineer size: 1pt
Difficulté 3/5 1-2 jours Accessibilité débutants 58/100
-
complexity: medium feature: security role: DevOps Engineer size: 3pt
Difficulté 4/5 3-5 jours Accessibilité débutants 48/100