2022-2023 Ops Community of Practice Agendas

[JasonEb]

This agendas page is deprecated

See: 2024 Ops Community of Practice Agendas

---

Overview

This issue tracks the agenda for team meetings

Issue Template

## [Date]  Meeting Agenda

### Prework to prep for meeting
- [ ] Everyone updates their issue before the meeting, and puts any issues that need group discussion or mentorship into the Review column

### Recurring items: Happens on the Wednesday meeting
 - [ ] review any issues that are in the [new issue approval column](https://github.com/hackforla/ops/projects/4#column-17567052)
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for (whoever showed up to the team meetings)
       - [ ] [Bonnie](https://github.com/hackforla/ops/issues/assigned/ExperimentsInHonesty)
       - [ ] [Jason](https://github.com/hackforla/ops/issues/assigned/JasonEb)

### New Items
- [ ] 
- [ ] Carry over Items to next meeting that don't get addressed

### FYIs
-

### Notes from Meeting

### Task Items

Use this for your issue updates

Please provide update
1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

[JasonEb]

01/26/2022 Meeting Agenda

Prework to prep for meeting

• [ ]

Recurring items: Happens on the __________ meeting

• review any issues that are in the new issue approval column
• Accountability and Support Check.
  • Review assignments for (whoever showed up to the team meetings)

New Items

• Civic Tech Jobs dockerizing
• People Depot tasks
• Make job posting for Python/Django/Docker Developers
• Are we going to make a frontend to test the API or use one of the frontend projects (Civic Tech Jobs, VRMS)? This is mainly to work out any cors issues.
• Repo config: Can we disable regular merges and require rebase merges? This will keep the commit history linear and readable. Merging hides commit history and requires the maintainer rather than developers to resolve merge conflicts.
• Is it a good idea to link the project wiki to the repo? The advantage is that code and documentation changes are tracked together, sort of. See example.
• Carry over Items to next meeting that don't get addressed

FYIs

• Some django tips from meeting with Cynthia Kiser
  • Authentication
    • Start with user model only, get authentication (AWS cognito) working before adding more models. Example
    • Figure out how to integrate frontend and backend with just the user model
    • Figure out development vs production authentication
  • Project setup
    • Don't use cookiecutter to generate the project
    • Put non-django stuff a level above django stuff
    • Don't run migrations automatically in entrypoint script. Do it manually.
  • Data models
    • Keep all models in one app since there's a lot of interrelationships
    • Start with user model without relations and add other models and relations when functionality requires them. Essentially, front end-driven. Add stuff when they're going to be used.
  • Model data fields
    • Check similar projects for ideas https://djangopackages.org/grids/g/crm/
    • Some fields like user status should be django choice fields rather than a separate table. Example, 2nd part
    • Some model data need to start off as nullable
    • Multiple relations to the same table need to set different related_names in django (practice area current, practice area target)
    • Timezone data could use lookup table of canonical name rather than entering UTC offset numbers
      • searchable select input field

Notes from Meeting

Task Items

[JasonEb]

02/2/2022 Meeting Agenda

Prework to prep for meeting

• [ ]

Recurring items: Happens on the __________ meeting

• review any issues that are in the new issue approval column
• [x ] Accountability and Support Check.
  • Review assignments for (whoever showed up to the team meetings)

New Items

• Civic Tech Jobs dockerizing discussion

• Setup a meeting with Darren / Ava

• People Depot tasks

  • Make job posting for Python/Django/Docker Developers

• Are we going to make a frontend to test the API or use one of the frontend projects (Civic Tech Jobs, VRMS)? This is mainly to work out any cors issues.

• Repo config: Can we disable regular merges and require rebase merges? This will keep the commit history linear and readable. Merging hides commit history and requires the maintainer rather than developers to resolve merge conflicts.

• [ x] Is it a good idea to link the project wiki to the repo? The advantage is that code and documentation changes are tracked together, sort of. See example.

• Carry over Items to next meeting that don't get addressed

FYIs

• Some django tips from meeting with Cynthia Kiser
  • Authentication
    • Start with user model only, get authentication (AWS cognito) working before adding more models. Example
    • Figure out how to integrate frontend and backend with just the user model
    • Figure out development vs production authentication
  • Project setup
    • Don't use cookiecutter to generate the project
    • Put non-django stuff a level above django stuff
    • Don't run migrations automatically in entrypoint script. Do it manually.
  • Data models
    • Keep all models in one app since there's a lot of interrelationships
    • Start with user model without relations and add other models and relations when functionality requires them. Essentially, front end-driven. Add stuff when they're going to be used.
  • Model data fields
    • Check similar projects for ideas https://djangopackages.org/grids/g/crm/
    • Some fields like user status should be django choice fields rather than a separate table. Example, 2nd part
    • Some model data need to start off as nullable
    • Multiple relations to the same table need to set different related_names in django (practice area current, practice area target)
    • Timezone data could use lookup table of canonical name rather than entering UTC offset numbers
      • searchable select input field

Notes from Meeting

• need access to enable rebase merges
• need to look into github wiki implementation
• need to look into Swagger docs front-end for testing APIs
• next meeting over people depot, go over FYIs

Task Items

[JasonEb]

02/9/2022 Meeting Agenda

Prework to prep for meeting

• Everyone updates their issue before the meeting, and puts any issues that need group discussion or mentorship into the Review column

Recurring items: Happens on the Wednesday meeting

• review any issues that are in the new issue approval column
• Accountability and Support Check.
  • [] Review assignments for (whoever showed up to the team meetings)

New Items

• Civic Tech Index Update
  • project is pushed back
• Cover FYI's shared from Fang
• Plan Incubator workshop with Darren
• Carry over Items to next meeting that don't get addressed

FYIs

• Some django tips from meeting with Cynthia Kiser
  • Authentication
    • Start with user model only, get authentication (AWS cognito) working before adding more models. Example
    • Figure out how to integrate frontend and backend with just the user model
    • Figure out development vs production authentication
  • Project setup
    • Don't use cookiecutter to generate the project
    • Put non-django stuff a level above django stuff
    • Don't run migrations automatically in entrypoint script. Do it manually.
  • Data models
    • Keep all models in one app since there's a lot of interrelationships
    • Start with user model without relations and add other models and relations when functionality requires them. Essentially, front end-driven. Add stuff when they're going to be used.
  • Model data fields
    • Check similar projects for ideas https://djangopackages.org/grids/g/crm/
    • Some fields like user status should be django choice fields rather than a separate table. Example, 2nd part
    • Some model data need to start off as nullable
    • Multiple relations to the same table need to set different related_names in django (practice area current, practice area target)
    • Timezone data could use lookup table of canonical name rather than entering UTC offset numbers
      • searchable select input field

Notes from Meeting

• Next steps : setup an Installation workshop in preparation for the Incubator workshop.
• Check-in with necessary tools: aws-cli, 1password, terraform
• Need to groom some tickets/tasks for People Depot
• [ ]

Task Items

[JasonEb]

02/16/2022 Meeting Agenda

Prework to prep for meeting

• Everyone updates their issue before the meeting, and puts any issues that need group discussion or mentorship into the Review column

Recurring items: Happens on the Wednesday meeting

• review any issues that are in the new issue approval column
• Accountability and Support Check.
  • Review assignments for (whoever showed up to the team meetings)

New Items

• Incubator Prep with Installation
  • Terraform, AWS-CLI, Docker Desktop
  • 1password vault access, aws hfla access

People Depot Development

• create tasks for continued development of people depot

  • API CRUD routes for User model
  • Swagger Documentation for User model API
  • SPIKE research on implementing AWS Cognito with People Depot

• Carry over Items to next meeting that don't get addressed

Notes from Meeting

Task Items

[JasonEb]

02/23/2022 Meeting Agenda

Prework to prep for meeting

• Everyone updates their issue before the meeting, and puts any issues that need group discussion or mentorship into the Review column

Recurring items: Happens on the Wednesday meeting

• review any issues that are in the new issue approval column
• Accountability and Support Check.
  • Review assignments for (whoever showed up to the team meetings)

New Items

• Incubator Prep with Installation
  • Terraform, AWS-CLI, Docker Desktop
  • 1password vault access, aws hfla access

People Depot Development

• create tasks for continued development of people depot

  • API CRUD routes for User model
  • Swagger Documentation for User model API
  • SPIKE research on implementing AWS Cognito with People Depot

• Carry over Items to next meeting that don't get addressed

Notes from Meeting

Need to create a people depot roadmap in order to be able to prioritize the issues in the new issues column (same for Ops)
Discussed VRMS slackbot from issue #1, created #16

Task Items

• People Depot: disable default merging. Disable merge commit in repo peopledepot#11

[JasonEb]

03/9/2022 Meeting Agenda

Prework to prep for meeting

• Everyone updates their issue before the meeting, and puts any issues that need group discussion or mentorship into the Review column

Recurring items: Happens on the Wednesday meeting

• review any issues that are in the new issue approval column
• Accountability and Support Check.
  • Review assignments for (whoever showed up to the team meetings)

New Items

• Check in with Slackbot monitoring
  • Slack app for monitoring backend services #1
  • Review Current VRMS Slackbot Implementation #16

People Depot Development

• create issues for continued development of people depot

  • API CRUD routes for User model
  • Swagger Documentation for User model API
  • SPIKE research on implementing AWS Cognito with People Depot

• Figure out who in the People Depot wants to handle deployment, development

• People Depot Roadmap/Milestones

• Carry over Items to next meeting that don't get addressed

Notes from Meeting

Need to create a people depot roadmap in order to be able to prioritize the issues in the new issues column (same for Ops)
Discussed VRMS slackbot from issue #1, created #16

Task Items

• People Depot: disable default merging. Disable merge commit in repo peopledepot#11

[JasonEb]

03/23/2022 Meeting Agenda

Prework to prep for meeting

• Everyone updates their issue before the meeting, and puts any issues that need group discussion or mentorship into the Review column

Recurring items: Happens on the Wednesday meeting

• review any issues that are in the new issue approval column
• Accountability and Support Check.
  • Review assignments for (whoever showed up to the team meetings)

New Items

• AWS Credentials Setup

• Check-In with People Depot

• Review Issues

• Carry over Items to next meeting that don't get addressed

Notes from Meeting

Task Items

[JasonEb]

04/13/2022 Meeting Agenda

Prework to prep for meeting

• Everyone updates their issue before the meeting, and puts any issues that need group discussion or mentorship into the Review column

Recurring items: Happens on the Wednesday meeting

• review any issues that are in the new issue approval column
• Accountability and Support Check.
  • Review assignments for (whoever showed up to the team meetings)

New Items

• Discuss Ops Roadmap

• Check-In with People Depot

• Review CivicTechJobs installation

  • https://hackforla.github.io/CivicTechJobs/developer/installation/

• Review Incubator setup and scripts

  • Look for previous recordings

• Carry over Items to next meeting that don't get addressed

Notes from Meeting

• CTJ
• webpack needs to use nginx
• should hard code the postgres version as 13
• webpack needs to install as a binary
• Set up a meeting 4/14 between Ops and CivicTechJobs

Task Items