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

PeopleDepot Team Meeting Agenda 2025 #461

Open
shmonks opened this issue Jan 24, 2025 · 3 comments
Open

PeopleDepot Team Meeting Agenda 2025 #461

shmonks opened this issue Jan 24, 2025 · 3 comments
Assignees
Labels
complexity: small Small changes with all steps laid out in detail; new member can complete in <1.5 hours feature: agenda role: back end role: db architect role: design role: dev lead role: dev ops role: dev role: product role: technical writing s: PD team stakeholder: People Depot Team size: 0.25pt Can be done in 1.5 hours or less

Comments

@shmonks
Copy link
Member

shmonks commented Jan 24, 2025

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]

## Preparation for Meeting: PMs
- [ ] #375 and offboard if needed
- [ ] #137  
- [ ] #386 
- [ ] Make sure that all issues in the New Issue Review column either have: 
    - [ ] [A `ready for...` label](https://github.com/orgs/hackforla/projects/61/views/7?filterQuery=status%3A%22%F0%9F%86%95New+Issue+Review%22+-label%3A%22ready+for+product%22+-label%3A%22ready+for+dev+lead%22+-label%3A%22ready+for+db+architect%22+-label%3A%22ready+for+marketing+lead%22+-label%3A%22ready+for+prioritization%22+). If this link contains any issues, they need to be given the appropriate "ready for..." label or...
    - [ ] A draft label and the author/someone assigned to them
- [ ] Make sure that all items in the Questions/Review column have [a `ready for...` label](https://github.com/orgs/hackforla/projects/61/views/7?filterQuery=status%3A%22%E2%9D%93Questions%2FReview%22+-label%3A%22ready+for+prioritization%22+-label%3A%22ready+for+dev+lead%22+-label%3A%22ready+for+db+architect%22+-label%3A%22ready+for+marketing+lead%22+-label%3A%22ready+for+product%22). If this link contains any issues, they need to be given the appropriate "ready for..." label.
- [ ] Review the issues with the following labels on the whole project board and either address them now or add to this agenda to discuss.
   - [ ] [`Ready for Product`](https://github.com/orgs/hackforla/projects/61/views/7?filterQuery=label%3A%22ready+for+product%22)
   - [ ] [`Ready for Prioritization`](https://github.com/orgs/hackforla/projects/61/views/7?filterQuery=label%3A%22ready+for+prioritization%22)
- [ ] Check for new issues in the Questions/Review column. Add a link to the question-asking comment from each new issue to the the agenda below


## Preparation for Meeting: All team members
- [ ] **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 shmonks added complexity: small Small changes with all steps laid out in detail; new member can complete in <1.5 hours feature: agenda role: product s: PD team stakeholder: People Depot Team size: 0.25pt Can be done in 1.5 hours or less labels Jan 24, 2025
@github-project-automation github-project-automation bot moved this to 🆕New Issue Review in P: PD: Project Board Jan 24, 2025
@shmonks shmonks self-assigned this Jan 24, 2025
@shmonks shmonks moved this from 🆕New Issue Review to Ongoing in P: PD: Project Board Jan 24, 2025
@shmonks shmonks added this to the 04. Project Setup milestone Jan 24, 2025
@shmonks
Copy link
Member Author

shmonks commented Jan 24, 2025

Weekly Meeting Agenda for 2025-01-23

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

  • For Fang: Set up mkdocs site in Engineering CoP #165 (comment)
  • Ethan:
    • superuser is intended for users with permissions to execute any API, including those that don't use project security. Can we use this instead of the "adminGlobal" permission
    • should other fields that may have a use be included in response? is_active, is_staff
    • 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

Notes from the Meeting

  • We replaced the "quick link to bottom of page" link in this agenda issue.
  • We made sure everyone has something ready to be worked on.

Next Steps / Action Items

  • Add next steps or action items here

@shmonks
Copy link
Member Author

shmonks commented Jan 30, 2025

Weekly Meeting Agenda for 2025-01-30

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

Next Steps / Action Items

  • Add next steps or action items here

@shmonks
Copy link
Member Author

shmonks commented Feb 7, 2025

Weekly Meeting Agenda for 2025-02-06

Preparation for Meeting: PMs

Preparation for Meeting: All team members

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

  • 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: small Small changes with all steps laid out in detail; new member can complete in <1.5 hours feature: agenda role: back end role: db architect role: design role: dev lead role: dev ops role: dev role: product role: technical writing s: PD team stakeholder: People Depot Team size: 0.25pt Can be done in 1.5 hours or less
Projects
Status: Ongoing
Development

No branches or pull requests

5 participants