People Depot Team Meeting Agenda

[Neecolaa]

Note: This is only a template.
For most recent agenda, see last comment - quick link to bottom of page

Overview

This issue tracks the agenda for team meetings

Issue Template

## Weekly Meeting Agenda for [date of meeting]

## Before the Meeting
- [ ] **A. Provide a written update on any issues assigned to you WITHIN the issues themselves**, by responding to the questions already posted in the issue's final comment OR by copying the Update Template below into a new comment and writing your update
  - [ ] [Sonali Agle](https://github.com/hackforla/peopledepot/issues/assigned/sonaliagle)
  - [ ] [Vanessa Avviles](https://github.com/hackforla/peopledepot/issues/assigned/vanessaavviles)
  - [ ] [Delgira Dordzhieva](https://github.com/hackforla/peopledepot/issues/assigned/del9ra)
  - [ ] [drakeredwind01](https://github.com/hackforla/peopledepot/issues/assigned/drakeredwind01)
  - [ ] [Nicole Dubin](https://github.com/hackforla/peopledepot/issues/assigned/neecolaa)
  - [ ] [Fang Liu](https://github.com/hackforla/peopledepot/issues/assigned/fyliu)
  - [ ] [Denzal Martin](https://github.com/hackforla/peopledepot/issues/assigned/dmartin4820)
  - [ ] [Sarah Monks](https://github.com/hackforla/peopledepot/issues/assigned/shmonks)
  - [ ] [Ethan Strominger](https://github.com/hackforla/peopledepot/issues/assigned/ethanstrominger)
  - [ ] [Bonnie Wolfe](https://github.com/hackforla/peopledepot/issues/assigned/experimentsinhonesty)

 - [ ] **B. Move any issues that need group discussion or mentorship** into the **New Issue Review** column

## Agenda

### Update and Review
- [ ] Brief updates from team members present
- [ ] Review of:
  - [ ] Issues in [New Issue Review](https://github.com/orgs/hackforla/projects/61/views/17) 
  - [ ] Issues in [Questions/Review](https://github.com/orgs/hackforla/projects/61/views/18)
  - [ ] Unassigned issues [In Progress](https://github.com/orgs/hackforla/projects/61/views/19?filterQuery=status%3A%22%F0%9F%8F%97In+progress+%28actively+working%29%22+no%3Aassignee)
  - [ ] Status of [PRs](https://github.com/orgs/hackforla/projects/61/views/13) - and assign reviewers
- [ ] Accountability and support check
- [ ] Review meeting agenda - add/delete/prioritize agenda items?

### Items for Discussion: Dev Lead
- [ ] Add links to any comments above 
- [ ] Add any other items for discussion

### Items for Discussion: Other Team Members
- [ ] **Name:** Add links to comments, or any items for discussion

### Notes from the Meeting
- [ ] Add any non-action meeting notes in a new comment below

### Next Steps / Action Items
- [ ] Add next steps or action items here

Update Template

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 or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."

* remember to add links to the top of the issue if they are going to be needed again.

[shmonks]

From 2024-06-13

Notes

Project board migration

• Created new 'Ongoing' column (to hold links to meetings)
• Deleted old project board classic
• Moved former 'Start Here' column contents to wiki and edited
• Added updated 'Ready for X' links to Quick Links/Questions section of wiki
• Added updated 'Ready for X' links to Quick Links/Issues section of wiki
• Need to update links to project board in templates for Team and PM meetings
• Need to create project board README explaining how board works
• Need to update wiki sidebar

[fyliu]

2024-08-01 notes

• write a criteria for what goes in the wiki and what goes into mkdocs
• add links so that the wiki and the mkdocs point to each other
• move the mkdocs pages from wiki to mkdocs so Sarah can work on the wiki Add cognito authentication and API endpoint pages #356
• Fang is working on reorganizing the mkdocs site

[fyliu]

For next meeting

• New team members: Vanessa Aviles (PM), Sonali Agle (UI), and Denzal Martin and Priya Kumbham (both Dev)
• might need another issue for @dmartin4820
  • Add name and external_id fields to project_url #289 is actually not a coding issue
• issue Create API for KB to read, update, create, and deactivate users and read groups. #331 PR review
  • Description is incomplete, but it doesn't feel right. Looks like knowledgebase is requiring peopledepot to implement a simpler, non-cognito-based security API to access the user and group lists from PD.
    • It's not linked to any knowledgebase issue about the KB feature that requires it nor made clear why cognito security is inadequate in this case.
  • The PR Secure API for listing users and groups #338 is implementing a security key mechanism. I don't know a lot about security but so my advice and the advice I've seen over the years is to not implement your own unless you know what you're doing and has lots and lots of test cases to prove it. So I would advise to use a popular and well-tested library for this.
    • There's no mechanism to prevent the a client from accessing ALL PD data using this mechanism
    • There are other issues with the code
  • Update: Ethan will switch to using djangorestframework-api-keys package. It's not secure by itself but will require configuration done to make it secure
• PR Add seed data permission type 278 #303 - just waiting for a small fix and it'll be good to merge
  • Update: Fix is committed and code is approved and merged
• Should we implement a simple example frontend that goes through login, get access token, and API request?
• PR reviews that are good for new devs to do
  • Convert doc pages to mkdocs #244 contains updates that are useful for new developers adding new models
  • Run migration check as test #349 is good first review since there's not many things to do
  • docs: project structure #350 is useful for someone new to the project to understand the files in it
• Do we need a Stakeholder Meeting Agenda: VRMS issue in the Ongoing column to keep track of all the things that were talked about?
• Update Table: technology (rename to stack_element) #204 by @AzaniaBG - we might need to fix and merge the code if she's busy.
• question for Implement delete security #371
• we need to scope out permissions for KB server in PD. If we implement Create API for KB to read, update, create, and deactivate users and read groups. #331, it will be a set of permissions that's independent of users and admins.
  • need input from @ethanstrominger on what KB server needs access to in the PD API.

[Neecolaa]

Consideration for next meeting:

• We want to include a way to indicate whether or not a project's github repo is archived. If a project has multiple github repos, each repo can have an archive indicator. See stakeholder meeting notes.
• Do we need to update our agenda template so it's usable again? (i.e. updating the team roster, updating project board links, restructuring the template)

[shmonks]

For team meeting, 2024-08-29

• Discussion of PeopleDepot branding possibilities c/o Sonali

[shmonks]

For team meeting, 2024-09-05

• Ethan's PR Implement user_permissions model, api, and test #342 and Bonnie's comment at the end about defined names on the PermissionType sheet (Ethan asking especially about adminGlobal and memberGeneral?)

[dmartin4820]

Do we need a Stakeholder Meeting Agenda: VRMS issue in the Ongoing column to keep track of all the things that were talked about?

• Yes, let's make an issue for VRMS agendas and each agenda will go in a new comment.

• PD: VRMS Stakeholder Meeting Agenda and Notes #377

[shmonks]

For team meeting, 2024-09-12

• Clarify current incubator/AWS status of PD backend with @fyliu, so I can report back to Sudha to update incubator status sheet
• Sample/demo/sandbox site for PD frontend - how to proceed?

[dmartin4820]

For team meeting, 2024-09-12

• Create a task to revisit switch to alpine image #275
• Determine whether ended_on is the same as created_at or updated_at. Create Table: project_sdg_xref #66.
  • This came up in Create table project_program_area_xref #376 (comment) as well. There was a question of whether other DateTimeFields not named created_at and updated_at need to be included in newly created Django models or not.
  • The created_at and updated_at fields are inherited through the AbstractBaseModel in https://github.com/hackforla/peopledepot/blob/main/app/core/models.py#L20.

[ethanstrominger]

• Verify read API for project area, practice area, and similar tables do not need any security. This makes it simpler to code and simpler to read.

[shmonks]

Weekly Meeting Agenda for 2024-09-12

Before the Meeting

• 1. Look at issues assigned to you:
  • Sonali Agle
  • Vanessa Avviles
  • Delgira Dordzhieva
  • drakeredwind01
  • Nicole Dubin
  • Fang Liu
  • Denzal Martin
  • Sarah Monks
  • Ethan Strominger
  • Bonnie Wolfe
• 2. Move any issues that need group discussion or mentorship into the New Issue Review column

Agenda

Update and Review

• Brief updates from team members present
• Review of:
  • Issues in New Issue Review
  • Issues in Questions/Review
  • Unassigned issues In Progress
  • Status of PRs - and assign reviewers
• Accountability and support check
• Review meeting agenda - add/delete/prioritize agenda items?

Items for Discussion: Dev Lead

• Add links to any comments above
• Add any other items for discussion

Items for Discussion: Other Team Members

• Ethan Strominger: People Depot Team Meeting Agenda #103 (comment)
• Denzal Martin: People Depot Team Meeting Agenda #103 (comment)
• Sarah Monks: People Depot Team Meeting Agenda #103 (comment)
• Sarah Monks: What do we think about this revised agenda template?
• Nicole Dubin: People Depot Team Meeting Agenda #103 (comment)

During/After the Meeting

• url_status_type: new table to store the status of URLs (such as githubs or wikis).
  Action items for Nicole:
  • Need to add a tab to the spreadsheet once we determine which specific types are to be added (active, archived, 404, ..?). Link to tab
  • Need to add url_status_type to erd
  • Need to add url_status_type to spreadsheet (tables and fields tabs)
  • Need to make a new "Create Table: url_status_type" issue Create Table: url_status_type #384
  • Add status_id FK to project_url table
• @fyliu to make issues for sample demo frontend. Maybe just login and get a list of projects or something public
• pure xref tables dont need new django models
  • @fyliu: all affected issues now have comments about this
• need decision record for "ended on" vs "ended at" for naming data fields
• create milestone 0.01.01 - deployment of initial setup AWS
  • after AWS initial version milestone is achieved
    • revisit alpine issue - can attach to milestone in milestone issue
• write guide for how to evaluate dependency updates
  • @fyliu can record desktop on how to do it so that someone else can make it into a guide

[shmonks]

@ethanstrominger In the following:

Verify read API for project area, practice area, and similar tables do not need any security. This makes it simpler to code and simpler to read

We are going to assume you mean program area because there is no project area

Program area and practice area do not need any security. We don't know what you mean by 'similar tables'.

[shmonks]

Further notes and action items from 2024-09-12 meeting

• Re: moving towards AWS work, return to this once the DevOps onboarding guide is satisfactory
• Re: @sonaliagle's post-draft changes for PD logo, request to show slides 12, 15, 17, and 18 again for fuller discussion - plus favicon if ready?
• See During/After Meeting section of People Depot Team Meeting Agenda #103 (comment)

[shmonks]

Weekly Meeting Agenda for 2024-09-19

Before the Meeting

• A. Look at issues assigned to you:

  • Sonali Agle
  • Vanessa Avviles
  • Delgira Dordzhieva
  • drakeredwind01
  • Nicole Dubin
  • Fang Liu
  • Denzal Martin
  • Sarah Monks
  • Ethan Strominger
  • Bonnie Wolfe

• B. Consider the following questions and add a comment below if.you want to update or ask the team about your issue(s):

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

• C. Move any issues that need group discussion or mentorship into the New Issue Review column

Agenda

Update and Review

• Brief updates from team members present
• Review of:
  • Issues in New Issue Review
  • Issues in Questions/Review
  • Unassigned issues In Progress
  • Status of PRs - and assign reviewers
• Accountability and support check
• Review meeting agenda - add/delete/prioritize agenda items?

Items for Discussion: Dev Lead

• Add links to any comments above
• Add any other items for discussion
• BW to FL: DevOps wants to kick this back to us. Is there a reason we Confirm Schema provisioning sql commands  incubator#85

Items for Discussion: Other Team Members

• Sarah Monks: Next meeting with VRMS stakeholder (inc. for feedback about Swagger vs redoc UI for documentation)?
• Sarah Monks: Move @cnk's Research how permissions is implemented in Django and DRF #149 from In Progress - to Closed?

Notes from the Meeting

• Add meeting notes in a new comment below

Next Steps / Action Items

• @Neecolaa to look at Update Table: user (replace role association with practice area) #172
• @ExperimentsInHonesty to discuss Confirm Schema provisioning sql commands  incubator#85 with CoP DevOps
• @fyliu @vanessaavviles @shmonks to create a slide deck about Swagger vs Redoc for distribution to BW, and then other stakeholders
• @sonaliagle to create examples of favicon designs within the team's main Figma file, so we can see how they look 'in situ'

[shmonks]

Weekly Meeting Agenda for 2024-09-26

Before the Meeting

• A. Look at issues assigned to you:

  • Sonali Agle
  • Vanessa Avviles
  • Delgira Dordzhieva
  • drakeredwind01
  • Nicole Dubin
  • Fang Liu
  • Denzal Martin
  • Sarah Monks
  • Ethan Strominger
  • Bonnie Wolfe

• B. Consider the following questions and add a comment below if.you want to update or ask the team about your issue(s):

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

• C. Move any issues that need group discussion or mentorship into the New Issue Review column

Agenda

Update and Review

• Brief updates from team members present
• Review of:
  • Issues in New Issue Review
  • Issues in Questions/Review
  • Unassigned issues In Progress
  • Status of PRs - and assign reviewers
• Accountability and support check
• Review meeting agenda - add/delete/prioritize agenda items?

Items for Discussion: Dev Lead

• Add links to any comments above
• Add any other items for discussion
• Need better process/template for PR creation
  • The PR description is information that helps the PR reviewer by providing context of the change
  • Test Plan section (How to test the new changes to show that it's ready for merging into main)
  • Checklist add "self-review" item
• Suggest practice change when coding new models:
  • Don't add the new code at the bottom. Maybe use alphabetical order starting from the bottom model name?
  • Reason: we're getting merge conflict always at the bottom of the changed files. We can avoid some of that by adding new code in different places. There's 24 more "create table" issues left.
• Is there design/requirements documentation available on what data and API capability KnowledgeBase needs from PD to be able to function as intended?

  • I'm currently finding out about potential needs at a late stage where the design's already been coded as a PR. Link to comment.

  • It's a first comer's burden to run into cases where we don't, but possibly need some additional processes in planning/project management.

  • Proposed process

    click to expand

    • Process (needs input from team)
      • describe the need: In a "stakeholder requirement" issue, describe the requirement in the context of what KB is doing or is planning to do with it
      • response/negotiate: either the PD team can readily provide the capability/data or figure out a way to accommodate the need
        • workaround: if PD can't accommodate, both teams should explore other ways that KB can proceed (with alternate data or without the data).
      • create work issue and implement. Link to the requirement issue so the PR reviewer knows what functionality should be tested.
        • tests should reflect the requirements (acceptance tests)
      • acceptance test: done by stakeholder to verify it's working (KB)
    • For example:
      • description: users (of all permission tiers) can login to KB and add an article. The article would then have the user as the author and display the author's first and last names in the article display.
      • requirements:
        1. data: complete users list (fields: uuid, first_name, last_name)
           • complete list because all permission tiers should be able to login
           • uuid because it uniquely identifies a user in PD, which is how KB syncs a user with PD
           • first and last names because they're needed in the page display
        2. capability: retrieved at regular intervals and on demand (at least 100 times a day)
           • once a day to sync the data
           • at least 99 more times for cases where a new un-synced user logs into KB and KB needs to retrieve the user's data
           • for above the API limit, KB plans to gracefully degrade to using the id provided by Cognito, and switching to the PD uuid later
      • response: first and last names are PII and won't be sent without user opt-in. If you need a friendly identifier to display, maybe we can add an optional display name for users and you can display those instead.

Items for Discussion: Other Team Members

• Sarah Monks: What user data should currently be shareable with KB? See Secure API for listing users and groups #338

Notes from the Meeting

• Add any non-action meeting notes in a new comment below

Next Steps / Action Items

• Add next steps or action items here

[dmartin4820]

Progress: Need to resolve conflicts on current PR.
Blockers: So far, the merge conflicts are not too disruptive.
Availability: Flexible between 5pm - 9pm on weekdays.
ETA: I should be able to finish this soon and get back to Del either tonight or before the weekend.

[shmonks]

Weekly Meeting Agenda for 2024-10-03

Before the Meeting

• A. Look at issues assigned to you:

  • Sonali Agle
  • Vanessa Avviles
  • Delgira Dordzhieva
  • drakeredwind01
  • Nicole Dubin
  • Fang Liu
  • Denzal Martin
  • Sarah Monks
  • Ethan Strominger
  • Bonnie Wolfe

• B. Consider the following questions and add a comment below if.you want to update or ask the team about your issue(s):

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

• C. Move any issues that need group discussion or mentorship into the New Issue Review column

Agenda

Update and Review

• Brief updates from team members present
• Review of:
  • Issues in New Issue Review
  • Issues in Questions/Review
  • Unassigned issues In Progress
  • Status of PRs - and assign reviewers
• Accountability and support check
• Review meeting agenda - add/delete/prioritize agenda items?

Items for Discussion: Dev Lead

• Add links to any comments above
• Add any other items for discussion
• Copied over from last week, as agreed Need better process/template for PR creation
  • The PR description is information that helps the PR reviewer by providing context of the change
  • Test Plan section (How to test the new changes to show that it's ready for merging into main)
  • Checklist add "self-review" item

Items for Discussion: Other Team Members

• Name: Add links to comments, or any items for discussion

Notes from the Meeting

• Add any non-action meeting notes in a new comment below

Next Steps / Action Items

• @shmonks to create issues relating to setup django-test-migrations #374 and Epic: collect needed documentation #378
• @shmonks and @ExperimentsInHonesty to look at Suggestion on note taking #143
• @shmonks and @ExperimentsInHonesty to discuss (needed) PD design role issues
  • @ExperimentsInHonesty and @sonaliagle to discuss (upcoming) design issues
• @fyliu to update PR template with new instructions
• @fyliu to look at Create Table: project_program_area_xref #45

[dmartin4820]

Progress:

• Create table project sdg xref 66 #385: Resolved merge conflicts and fixed issue with data migrations. Then Del reviewed it. Just need to merge.
• Create Table: url_type #77: Assigned to self

Blockers: None yet
Availability: Flexible between 5pm - 9pm on weekdays.
ETA: Will work over the weekend