Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

People Depot Team Meeting Agenda 2024 #103

Open
Neecolaa opened this issue Nov 22, 2022 · 97 comments
Open

People Depot Team Meeting Agenda 2024 #103

Neecolaa opened this issue Nov 22, 2022 · 97 comments

Comments

@Neecolaa
Copy link
Member

Neecolaa commented Nov 22, 2022

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.
@Neecolaa

This comment was marked as outdated.

@Neecolaa

This comment was marked as outdated.

@AzaniaBG

This comment was marked as outdated.

@fyliu

This comment was marked as outdated.

@Neecolaa Neecolaa pinned this issue Dec 2, 2022
@joey-ma

This comment was marked as outdated.

@joey-ma

This comment was marked as outdated.

@joey-ma

This comment was marked as outdated.

@joey-ma

This comment was marked as outdated.

@joey-ma

This comment was marked as outdated.

@fyliu

This comment was marked as outdated.

@fyliu

This comment was marked as outdated.

@fyliu

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@fyliu

This comment was marked as outdated.

@Neecolaa

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty

This comment was marked as outdated.

@fyliu

This comment was marked as duplicate.

@dmartin4820
Copy link
Member

dmartin4820 commented Sep 10, 2024

For team meeting, 2024-09-12

@ethanstrominger
Copy link
Member

ethanstrominger commented Sep 10, 2024

  • 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
Copy link
Member

shmonks commented Sep 11, 2024

Weekly Meeting Agenda for 2024-09-12

Before the Meeting

Agenda

Update and Review

  • Brief updates from team members present
  • Review of:
  • 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

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
Copy link
Member

shmonks commented Sep 13, 2024

@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
Copy link
Member

shmonks commented Sep 18, 2024

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

@shmonks
Copy link
Member

shmonks commented Sep 18, 2024

Weekly Meeting Agenda for 2024-09-19

Before the Meeting

  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:
  • Accountability and support check
  • Review meeting agenda - add/delete/prioritize agenda items?

Items for Discussion: Dev Lead

Items for Discussion: Other Team Members

Notes from the Meeting

  • Add meeting notes in a new comment below

Next Steps / Action Items

@shmonks
Copy link
Member

shmonks commented Sep 24, 2024

Weekly Meeting Agenda for 2024-09-26

Before the Meeting

  • A. Look at issues assigned to you:

  • 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?"
      1. Blockers: "Difficulties or errors encountered."
      1. Availability: "How much time will you have this week to work on this issue?"
      1. ETA: "When do you expect this issue to be completed?"
      1. 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:
  • 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

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
Copy link
Member

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
Copy link
Member

shmonks commented Oct 3, 2024

Weekly Meeting Agenda for 2024-10-03

Before the Meeting

  • A. Look at issues assigned to you:

  • 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?"
      1. Blockers: "Difficulties or errors encountered."
      1. Availability: "How much time will you have this week to work on this issue?"
      1. ETA: "When do you expect this issue to be completed?"
      1. 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:
  • 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

@dmartin4820
Copy link
Member

dmartin4820 commented Oct 4, 2024

Progress:

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

@fyliu
Copy link
Member

fyliu commented Oct 10, 2024

Weekly Meeting Agenda for 2024-10-10

Before the Meeting

Agenda

Update and Review

  • Brief updates from team members present
  • Review of:
  • 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
  • [testing permissions] need a simple set of tests for the permissions PR
    • should we start with object level first?
    • ethan said he can separate some of it into separate PRs to make reviewing them easier and then review the main permissions logic
  • [API design/audit] we do need to start planning a frontend implementation as a form of auditing to make sure we have all the functionality needed to create a basic api client
    • user registration
    • user login
    • get a public resource like projects list
    • error handling example if relevant, like if a field is restricted and isn't part of the results
  • [API design, Events] for the next VRMS meeting: ask about how they currently use Events
    • the purpose is to get a get a better idea of how to design the API
      • the Event API is not just a pass through to the storage backend. There's logic in it.
      • this is what Tracker: Deck Profile Card product-management#143 is trying to push for: API design from talking to stakeholders and coming up with requirements from use cases.
    • what does the frontend ask for and expect to get back
      • can they show us the parts of their code that does this
    • what does the backend do, processing wise. PD should do that and probably more
      • can they show us the parts of their code that does this.
  • [DR] we decided to host PM docs in the wiki separate from the code docs for now
    • reasoning being to conform to hackforla activity to standardize PM docs across the organization
    • mkdocs was considered: there's more work to using it than using the wiki. eg. one-time setup, per-session local server, git knowledge to apply changes. These can be made better but will be non-zero. If at a later time we are able to accept these costs, we may revisit this decision.
  • [standardization, xref] new ABC for through (xref) tables
    • Create Table: project_program_area_xref #45 (comment)
    • none of the xref tables can use the Django-auto-generated through tables for many-to-many relationships. They won't have created_at and updated_at fields if generated automatically.
    • add an ended_at field
    • standardize the name and type of the field
    • it's a way to soft-delete the relationship that every xref table should have, in case we decide to implement it rather than just deleting the relationship.
  • [automation, process improvement] is there a standard HfLA way to generate release notes?
    • it would be helpful to have a way to quickly generate status update reports for the present time since we don't have true releases yet.
    • I looked into existing options to do that at TDM-Calculator. It usually means taking the Issue titles or commit logs, so we should be in the habit of making the target text "release note-ready". Another option we have is the "what did you do" lists in PRs
    • I was thinking of having a script to take in a date range and generate a wiki page with everything that happened during that time, with links to more details. Then manually edit that and copy it to a more long term area.
  • definition for milestones
    • I'm still assigning a lot of issues to "Team Workflow" because I'm not sure if there's another milestone they should fall under
      • documentation issues for example
  • documentation style guide
    • where (directory structure) to add pages - contributor docs are contained in one folder, client docs has the top level folder
    • voice style: maybe inclusive for tutorial, conversation for how-to guide, 3rd person for reference. We should check a few well-regarded documentation sites to see what they do.
    • complete sentences or fragments okay
      • keep section titles short and don't write a sentence
      • write sentences in description texts
      • each step in a multi-step guide should be sentences?
    • when to use callouts and which to use
      • callout icon set - design a set for PD/HfLA?
    • configuration
      • color scheme for PD/HfLA?
      • callout icon set - design a set for PD/HfLA?
    • markdown syntax style (examples mostly already exists)
    • special considerations like use something other than [] for placeholder tags because mdformat incorrectly tries to add more characters for []
    • keep in mind the type of documentation when writing it (explaining a concept, tutorial to create something, how-to guide to do a specific thing, reference doc, FAQ, ...)

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

@ExperimentsInHonesty
Copy link
Member

  • Home Unite us team is committing all of their SSO for using Cognito via Terraform to Incubator which the DevOps CoP team has agreed to accept.
    • Then will refactor out their Cognito into a service for everyone. That will just be a service that when you are writing files for Terraform for VRMS that we can just specify using a service and all the code is already written for it. Just have to format user pool this way, secrets, etc., but the idea is that Cognito coding will not have to be written by each project.
    • Customization will have to be done for VRMS to get authorization through People Depot, which will then be useful as a model for Civic Tech Jobs and Tables.

@Neecolaa
Copy link
Member Author

Neecolaa commented Oct 14, 2024

Weekly Meeting Agenda for 2024-10-17

Before the Meeting

Agenda

Update and Review

  • Brief updates from team members present
  • Review of:
  • Accountability and support check
  • Review meeting agenda - add/delete/prioritize agenda items?

Items for Discussion: Dev Lead

  • Add links to any comments above
  • [Events] Determine what tables and fields are used for events.
    • We made this spreadsheet tab to figure out which fields we'll have. In its current state it requires explaining from Bonnie or Nicole

    • Questions about Implement a solution for cancelled events #151 and Discuss our requirements for permissions #150 (comment) for Fang from Nicole:

      • Would the event table have a RecurrenceField inside it (named something like recurrence)
        • A: The model would have a RecurrenceField, but it represents the functionality provided in 3 tables in the db. I need to try doing a few things with the package to make sure it meets our needs or what is still needed.
      • Do you know how this would be stored in postgresql?
        • A: django-recurrence creates 3 tables to provide the functionality. If we use the RecurrenceField interface, maybe we don't really need to set permissions on those tables, but only on the field.
          See Next Steps//Action Items below
    • It might be useful to put them in sequence diagrams in documentation?

      click to expand
      sequenceDiagram
          participant D as Database
          participant T as VRMS or Tables team
          participant G as GitHub
          participant M as Member
      
          critical Invite member to org
              T->>+G: Send invite
              G->>-M: Hack for LA invites you to the organization
          option Accepts invite
              M->>+G: Accept
              G->>-G: Set accepted /write date
          option No response
              G->>G: Wait
          end
      
          Note over T: Time passes? How do I know when to check for acceptance?
      
          critical Check Member accepted /write date
              T->>+G: Does Member have accepted /write date?
          option No
              G->>-T: No
              critical Send reminder if not accepted
                  T->>+G: Send out reminder
                  G->>-M: Hack for LA reminds you to accept the invitation
              option Accepts invite
                  M->>+G: Accept
                  G->>-G: Set accepted /write date
              option No response
                  G->>G: Wait
              end
          option Yes
              G->>T: Yes
              T->>D: Write something to the database
          end
      
      Loading
  • 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

Next meeting

  • discuss with @Neecolaa Update Project Profile: Civic Opportunity Project  website#927 and standardizing all the ended_on, ended_at fields
  • create clearer requirements for Events (it helps drive design decisions)
    • ok to get list of only non-deleted event instances for mvp
      • may need to get all instances with deleted flag in future milestone
    • need the ability to checkin users to event instances
      • mainly the ability to identify instances uniquely even if the instance object is not created
      • maybe something like event.id and "event".start_time
    • ability to modify events?
      • [future instances] gcalendar will set the end date on the existing event and create a new copied event for the modified one. Sort of a copy-on-write solution.
      • [all instances] if we allow modifying the actual original event as in "modify all instances", what would happen to all the checkins where the start_time is now modified? We can't really have that. The new event may also need to point to the old event for lookup
    • recurrence capabilities
      • single occurrence
      • weekly (Team)
      • monthly (CoP-Leads)
      • biweekly alternating Mon-Tues (onboarding)
      • exclusion rrule? (Team - CoP-Leads) - exrrule is deprecated in RFC33xx but doesn't mean we don't need it or can't have it if needed

@shmonks
Copy link
Member

shmonks commented Oct 24, 2024

Weekly Meeting Agenda for 2024-10-24

Before the Meeting

Agenda

Update and Review

  • Brief updates from team members present
  • Review of:
  • Accountability and support check
  • Review meeting agenda - add/delete/prioritize agenda items?

Items for Discussion: Dev Lead

Items for Discussion: Other Team Members

Notes from the Meeting

Next Steps / Action Items

@shmonks
Copy link
Member

shmonks commented Oct 31, 2024

Weekly Meeting Agenda for 2024-10-31

Before the Meeting

Agenda

Update and Review

  • Brief updates from team members present
  • Review of:
  • Accountability and support check
  • Review meeting agenda - add/delete/prioritize agenda items?

New Issues

  • Review "corrected_field" column and CSV tab in spreadsheet
  • Issue 149

Items for Discussion: Dev Lead

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

Items for Discussion: Other Team Members

Notes from the Meeting

  • @ethanstrominger found that some model fields are present in the django database but missing in the spreadsheet fields. He added a new column for them in the Permissions sheet. Example of the User model fields below

    click to expand

    user

  • @sonaliagle presented favicon design options, and majority voted for design 1 (blue and red) - she will work on project logo in this colorway

  • @ethanstrominger added as reviewer to Create table user status type 35 #427

Next Steps / Action Items

@shmonks
Copy link
Member

shmonks commented Nov 6, 2024

Weekly Meeting Agenda for 2024-11-07

Before the Meeting

Agenda

Update and Review

  • Brief updates from team members present
  • Review of:
  • 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 and Nicole: Review "corrected_field" column and CSV tab in spreadsheet

Notes from the Meeting

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

Next Steps / Action Items

@shmonks
Copy link
Member

shmonks commented Nov 13, 2024

Weekly Meeting Agenda for 2024-11-14

Before the Meeting

Agenda

Update and Review

  • Brief updates from team members present
  • Review of:
  • 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

Notes from the Meeting

  • Add any non-action meeting notes in a new comment below
  • discussion on Update Table: User #429: user model/table has 3 emails
    • email matches the email a user first signed up with (Cognito email or not?)
    • gmail matches gmail that's needed for calendar invites, shared drive, etc.
    • preferred_email is one of the above chosen by the user as their preferred email for communication
  • we want to allow users to change their emails, so they'll need a separate username that they can login with
    • we may need a separate field to store the cognito email
  • Cognito requires email
    • should allow changing the email. People change their emails and we need a solution that allows them to change that in their account
    • can we change username in cognito?

Next Steps / Action Items

  • need another issue to investigate changing login name in cognito, as well as the email address

@ExperimentsInHonesty ExperimentsInHonesty changed the title People Depot Team Meeting Agenda People Depot Team Meeting Agenda 2024 Nov 15, 2024
@shmonks
Copy link
Member

shmonks commented Nov 19, 2024

Weekly Meeting Agenda for 2024-11-21

Before the Meeting

Agenda

Update and Review

  • Brief updates from team members present
  • Review of:
  • Accountability and support check
  • Review meeting agenda - add/delete/prioritize agenda items?

Items for Discussion: Dev Lead

  • Security for fields that are not user or project related - will look for permission type for any project for current user
  • Security for fields that are project related - user must be assigned to the project with the specified role.
  • For adminVRMS or adminBrigade, will project and user security apply?
  • Are there other types of security?
  • Stakeholder API, System, Action cannot be performed, and blank all mean not updatable - except for a few cases are system fields. In those cases, change to System.
  • There are cases where READ is blank. Except for a few cases, this should at a minimum be adminGlobal.
  • There are cases for non-system fields where all fields are blank - this would mean it never gets populated.
  • Should unverified user for READ be no authentication required
  • Three cases where “VRMS” is used
  • Update Table: User #429

Items for Discussion: Other Team Members

  • Sarah: I would like to look at issues in the Questions/Review column, and see if we can process some of them so they can be reprioritized!
  • Bonnie: Can we see Mkdocs with AWS?

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment