PD: PM's Agenda and Meeting Minutes

[fyliu]

Overview

This issue tracks the agenda for our weekly meetings
Quick Link to bottom of page

Issue Template

## [Date]  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 each Team member
      - [ ] [Name of Person]
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard 
   - [ ]  #

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

### FYIs
-

### Notes from Meeting

### Task Items

Links to other agenda issues for your team

(so that you can easily post on their agendas items that come up at yours)

Previous Meetings (link to each comment with the date)

[fyliu]

[Date ] 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 each Team member
    • Bonnie
    • Fang
    • Nicole
• finish adding labels to the issue that are still missing them (see audit links above)
• review issues with [epic label] and define how to break down further
• Review to see if there are any members to Onboard or Offboard
  • Onboard & Offboard: Product #33

New Items

• We need Bonnie/admin support to create team google calendar, 1password vault, if they're required to onboard Eric.
• We have more people in the team and more structure would be good Create milestones and labels for PeopleDepot #34
• Carry over Items to next meeting that don't get addressed

FYIs

• Fang will be away/mostly unavailable for a month's time in less than 2 months. Projected date is Oct 16.
• Roadmap for the near future

Notes from Meeting

Task Items

[ExperimentsInHonesty]

• The template for the team meeting agenda needs an update People Depot Team Meeting Agenda 2024 #103
• Update README.md and Contributing.md #98
• Turn this comment by CNK into an ER to store. 2022-2023 Ops Community of Practice Agendas ops#12 (comment)
  Issues its related to it Set Up CRUD functionality for a Users Model #12
• Bonnie and Kathleen will review the all team agenda to determine what was the last steps we were supposed to take re the naming of people depo. People Depot Team Meeting Agenda 2024 #103
• Suggestion on note taking #143 is now ready for product's review

[luca-navarrete]

Add to the next agenda:

- [ ] Review with Bonnie 
  - [ ] Slack channels (active/dormant/archived)
  - [ ] Slack channel pins and bookmarks

[shmonks]

While the Monday PM meeting is focused on tables, PD PMs will meet separately on Tuesdays @ 11am PST from Sept 10 2024. Agenda items will be posted here.

[shmonks]

2024-09-10 PM Buffer meeting notes - @fyliu, @vanessaavviles, @shmonks

• Discussed progress on revising both the PD wiki and mkdocs site
• Re: mkdocs: the Contributing section is too long, and needs splitting up into separate pages
  • Perhaps we should have a Contributing folder instead, with general info for all-comers, and then separate pages/subfolders for developers, so it's not too much information for those who don't need it?
  • Perhaps we should have separate pages/folders with info for users and possibly PMs too (though perhaps better to keep all PM info on the wiki where it can be more easily edited)?
  • Perhaps the Tools and Developer Guides sections should be moved to the top level of the structure?
  • Perhaps all the coding-related info should be moved into a folder of its own?
  • Perhaps we should use a top-level main menu bar like this example (to keep left-hand menu clean and relevant), and include a Contents section/page on the PD mkdocs hompage?
• Re: wiki, I will do pre-issue work to gauge best scope and action steps then write an issue about thorough revision
• Once @fyliu has got to a point where he feels OK with the mkdocs site, we'll think again about the best way to structure it
• Once we've got both mkdocs and wiki closer to complete, we'll coordinate to get them properly linked to each other (ideally, with links from wiki developer-related pages to mkdocs pages, so we keep the wiki clean)

[fyliu]

Next PM Buffer meeting Agenda

• Fang: We should have an ADR (Architectural/All Decision Records) area in mkdocs to hold decisions that are applicable to the software project
  • We already have some DRs (Decision Records) in the wiki. Maybe that one decision should be moved to mkdocs
  • I feel we need to capture a little more context in the ADRs (there's templates out there we can customize and adopt)
    • number (just sequential numbers. doesn't even have to be earliest date first. Sometimes there are prior decision written down after the fact)
    • status (accepted, adopted, rejected, superceded by ADR #)
    • date (I made some prior ones that can be current date maybe with a note)
    • people involved (sometimes people forget what they agreed to, but mainly to show it's a consensus of these people)
    • problem context (GH issue #, what's the problem)
    • decision drivers (what we consider to be important at this time. These should probably be tied to organization or team goals)
    • alternatives considered (list pros and cons)
    • impact (to current way of doing things, to future work)
    • decision summary (what's the decision, why, acceptable tradeoff)
  • Some decisions:
    • Adopt ADR format
    • Keep ADRs in mkdocs
    • Use ReDoc for API docs (or Swagger UI)
    • Make Mac users build x64 Docker images
    • Django timestamp field naming (ended_on vs. ended_at)
    • Docs that go into mkdocs vs. wiki (we're still trying to figure this out I think?)