Skip to content

2022-2023 Ops Community of Practice Agendas #12

Closed
Closed
2022-2023 Ops Community of Practice Agendas#12
Assignees
JasonEbRankazze
Labels
complexity: mediumfeature: agendarole: CoP leadsize: 0.5ptCan be done in 3 hours or less
Milestone
03 Project Management

Description

@JasonEb
JasonEb
opened on Jan 24, 2022

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."

Activity

  1. JasonEb
    self-assigned this
    on Jan 24, 2022
  2. JasonEb
    pinned this issue on Jan 24, 2022

  3. JasonEb commented on Jan 27, 2022

    @JasonEb
    JasonEb
    on Jan 27, 2022
    ContributorAuthor

    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

  4. JasonEb commented on Feb 3, 2022

    @JasonEb
    JasonEb
    on Feb 3, 2022
    ContributorAuthor

    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

  5. JasonEb commented on Feb 6, 2022

    @JasonEb
    JasonEb
    on Feb 6, 2022
    ContributorAuthor

    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

  6. JasonEb commented on Feb 15, 2022

    @JasonEb
    JasonEb
    on Feb 15, 2022
    ContributorAuthor

    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

  7. JasonEb commented on Feb 20, 2022

    @JasonEb
    JasonEb
    on Feb 20, 2022
    ContributorAuthor

    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

  8. JasonEb commented on Mar 9, 2022

    @JasonEb
    JasonEb
    on Mar 9, 2022
    ContributorAuthor

    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

    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

  9. JasonEb commented on Mar 23, 2022

    @JasonEb
    JasonEb
    on Mar 23, 2022
    ContributorAuthor

    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

  10. JasonEb commented on Mar 31, 2022

    @JasonEb
    JasonEb
    on Mar 31, 2022
    ContributorAuthor

    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

    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

  11. JasonEb
    added
    role: missing
    size: missing
    feature: missing
    on Apr 3, 2022
  12. ExperimentsInHonesty
    removed
    role: missing
    size: missing
    on Apr 10, 2022

  13. 75 remaining items

  14. JasonEb commented on Nov 28, 2023

    @JasonEb
    JasonEb
    on Nov 28, 2023
    ContributorAuthor

    2023-11-29 Meeting Agenda

    Prework to prep for meeting

    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

    • Permissions for Terraform

    FYIs

    Notes from Meeting

    Task Items

  15. ExperimentsInHonesty commented on Jan 11, 2024

    @ExperimentsInHonesty
    ExperimentsInHonesty
    on Jan 11, 2024
    Member

    Status for the new year

  16. ExperimentsInHonesty commented on Jan 11, 2024

    @ExperimentsInHonesty
    ExperimentsInHonesty
    on Jan 11, 2024 · Hidden as outdated

  17. ExperimentsInHonesty commented on Jan 11, 2024

    @ExperimentsInHonesty
    ExperimentsInHonesty
    on Jan 11, 2024 · Hidden as outdated

  18. ExperimentsInHonesty commented on Jan 11, 2024

    @ExperimentsInHonesty
    ExperimentsInHonesty
    on Jan 11, 2024
    Member

    export the list of services currently running on incubator and divide the permissions up by groups, so that we can provide them appropriately to teams.

  19. ExperimentsInHonesty commented on Jan 18, 2024

    @ExperimentsInHonesty
    ExperimentsInHonesty
    on Jan 18, 2024
    Member

    Create Levels

    Join HfLA and DevOps

    1. Fundamentals and Concepts
      1. Deploy a Terraform hello world project
      2. Get read access to infrastructure organization (see resources)

    Get assigned to project as their DevOps person

    1. Administration
      1. get access to do stuff to that projects' deployment

    Become a mentor across all projects DevOps people

    1. expert level
      1. Ability to do stuff to any project

    Permissions and Resources management

    1. IAM supervisor / Services Supervisor (is added to the
      Management Group on AWS)
      1. Dispenses new permissions and removes permissions for user
      2. Add new services in partnership with Owner
    2. Billing (owner) (is added to the Cost Management Group)
  20. chelseyklein
    changed the title [-]Ops: Team Meeting Agenda[/-] [+]2022-2023 Ops Community of Practice Agendas[/+] on Jan 23, 2024

  21. chelseyklein commented on Jan 24, 2024

    @chelseyklein
    chelseyklein
    on Jan 24, 2024
    Member

    Please use 2024 agenda. I moved the recent conversations there.

  22. chelseyklein
    closed this as completedon Jan 24, 2024
  23. robinglov
    unpinned this issue on Jan 29, 2024
  24. ExperimentsInHonesty
    added this to CoP: DevOps: Project Boardon Jun 14, 2024
  25. ExperimentsInHonesty
    moved this to Done in CoP: DevOps: Project Boardon Jun 14, 2024
  26. ExperimentsInHonesty
    added
    complexity: missing
    on May 19, 2025
  27. ale210
    added
    complexity: medium
    and removed
    complexity: missing
    on Aug 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

complexity: mediumfeature: agendarole: CoP leadsize: 0.5ptCan be done in 3 hours or less

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions