VRMS: PM/Design Lead Meeting Agenda #1519

JackHaeg · 2023-09-21T19:49:56Z

Overview

This issue tracks the agendas and notes from the weekly PM/Design Lead Meeting

Template

## YYYY-MM-DD Agenda and Notes 

### Participants:
- [ ] Julia
- [ ] Jack
- [ ] Steph
- [ ] Rohan
- [ ] Bonnie
- [ ] Josh
- [ ] Trillium (optional)


### Issues to discuss: 

### Notes from meeting:

### Tasks to do:

### Items for next meeting agenda:

Old Team Meetings:

Previous Team Meeting Agendas (from 2022) that were previously stored on the VRMS Wiki have been preserved in this issue.

The text was updated successfully, but these errors were encountered:

JackHaeg · 2023-09-28T22:18:20Z

2023-09-28 Agenda and Notes

Participants:

Issues to discuss:

Slack Channels to drop (everything but vrms & vrms-tech used for security - rename channel. Also, discuss vrms-design with Julia):

Slack Channels	Responsible	Status	Public or private	Last Message Date
vrms-ops	vrms	Dormant	public	2020-11-10
vrms-ui	vrms	Dormant	public	2021-01-16
vrms-test	vrms	Dormant	public	2021-06-11
vrms-devs	vrms	Dormant	public	2021-07-08
vrms-tech	vrms	Active	private	2023-08-07
vrms	vrms	Active	public	2023-09-11
vrms-design	vrms	Dormant	public	2023-02-02

Julia: Brainstorm screen size (addition with dashboard screen)
Julia: potentially discuss new lo-fi designs
Trillium: How to change AWS secrets? Not sure if we can change our secrets, or if we need to put them into some environment elsewhere. Usually, AWS will have a place. Probably some secrets for VRMS, one of them is JWT secret that we use to sign Javascript web tokens (email is signed by our secret). Need to change this secret to make it more secure.

Notes from meeting:

AWS secrets - check with Ops Community of Practice for this info. Also provided him with access to 1password
Bonnie recommends finishing up "milestone" labelling first, followed by "feature" labels and any other missing labels, which will aid in the prioritization process. Apply labels to all open issues (even if outside of current project).
Decided to use REM instead of PX in designs, recommend designing for smallest common phone size (e.g., iphone 14), and also provide gap size / percentages to devs with designs going forward.

Tasks to do:

Items for next meeting agenda:

JackHaeg · 2023-10-05T22:40:41Z

2023-10-05 Agenda and Notes

Participants:

Issues to discuss:

Julia: I've finished my "in progress" issues

Notes from meeting:

Reviewed Julia's issues as a group and provided feedback on designs.

Tasks to do:

Discuss recruiting new developers with Trillium

Items for next meeting agenda:

JackHaeg · 2023-10-12T18:45:50Z

2023-10-12 Agenda and Notes

Participants:

Issues to discuss:

Potentially review & complete remaining missing labels with Rohan / Bonnie
VRMSbot email has no emails within inbox (also nothing in sent folder, calendar, etc.) See issue here: research useage of vrms-bot@hackforla.org #581

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg · 2023-10-19T21:02:18Z

JackHaeg · 2023-10-26T21:26:51Z

2023-10-26 Agenda and Notes

Participants:

Issues to discuss:

Updates:

All milestones and feature labels have been completed across all issues, size is missing on 13 issues currently (https://github.com/hackforla/VRMS/issues?q=is%3Aopen+is%3Aissue+label%3A%22size%3A+missing%22)
Josh is reviewing old issues over the next week: https://github.com/hackforla/VRMS/issues?q=is:open+is:issue+-project:hackforla/vrms/12+

Other issues to discuss:

Bonnie: We will plan to close this issue as it is related to the larger check-in bug and duplicates the same behavior: The Guides team meeting is not available for checkin #1530
Bonnie: New issues created re: stakeholder feedback:
- Project Status definitions: Stakeholder Feedback: Define Project Status #1532
- UAL from project details: Stakeholder Feedback: Define User Access Levels (UAL) #1534
- Cadence definitions: Stakeholder Feedback: Define Event Cadence #1533
Bonnie: Mentioned that feature labels are confused. Discuss required changes.

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg · 2023-11-02T19:31:12Z

2023-11-02 Agenda and Notes

Participants:

Issues to discuss:

Bonnie - discuss feature labels: https://docs.google.com/spreadsheets/d/14fd47047A42vycujTc03MeahFZyHHqM2ke-B3VaqH4w/edit#gid=0 and Label Review: Create Feature Repository Labels List and Label Review: Create Feature Repository Labels List and #1537
Bonnie - FYI provided Guides group with info on how to manually allow check in to meetings at the meantime: The Guides team meeting is not available for checkin #1530
Julia - review screens & specs

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg · 2023-11-09T21:32:15Z

2023-11-09 Agenda and Notes

Participants:

Issues to discuss:

Julia - review final designs and collect remaining feedback from Bonnie (the majority of the meeting should be dedicated to this)
Bonnie: Check in on progress of issue here / collaborate with Julia on how additional info should be added to the issue: Stakeholder Feedback: Define User Access Levels (UAL) #1534
Bonnie - discuss feature labels and changes to feature labels required: https://docs.google.com/spreadsheets/d/14fd47047A42vycujTc03MeahFZyHHqM2ke-B3VaqH4w/edit#gid=0 and Label Review: Create Feature Repository Labels List and Label Review: Create Feature Repository Labels List and Label Review: Create Feature Repository Labels List and #1537
Josh - (if in attendance and time permits) check in on reviewing of issues - what to do with issues that are still relevant, but only for v4? Josh suggested adding another column to the current project that would be reserved for these issues. Alternatively, we could keep them in their existing separate project.
Note (bug fix) - Trillium merged his PR that should address Bug: Users Cannot Check In #1411 & The Guides team meeting is not available for checkin #1530. This fix has been implemented on dev, but has yet to be pushed to Prod. However, based on Jack's initial testing by comparing the times listed on recurring times vs manual check in times on dev, they do not appear to match up, indicating the timing bug may still be an issue.

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg · 2023-11-15T22:27:15Z

JackHaeg · 2023-11-30T20:46:48Z

JackHaeg · 2024-01-04T21:09:10Z

JackHaeg · 2024-01-25T23:40:05Z

2024-01-25 Agenda and Notes

Participants:

Issues to discuss:

Share Holiday party CSV with Bonnie
Open developer roles (1-2 full stack devs required based on recent attendance)

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg · 2024-02-01T22:20:47Z

JackHaeg · 2024-02-08T23:09:24Z

JackHaeg · 2024-02-15T23:54:23Z

JackHaeg · 2024-02-22T22:56:45Z

JackHaeg · 2024-02-29T23:47:31Z

JackHaeg · 2024-03-28T22:02:46Z

JackHaeg · 2024-04-04T22:43:28Z

JackHaeg · 2024-04-11T22:37:23Z

JackHaeg · 2024-04-18T22:02:24Z

JackHaeg · 2024-04-25T21:33:43Z

JackHaeg · 2024-05-16T21:31:43Z

JackHaeg · 2024-05-23T22:51:33Z

2024-05-23 Agenda and Notes

Participants:

Issues to discuss:

Check in re: Privacy Policy
Collect additional info on Zoom URL API issue (specific page?)
Review validation requirements for Project Management screen
- HfLA website URL & Google URL: Recently, we removed validation & dropped requirements for the HfLA Website URL and Google Drive URLs because not all projects will have these links and a user cannot . However, we have some older issues that request form validation for both of these fields.
  - Form Validation - Google Drive URL #1369
  - Form Validation - HFLA Website URL #1370
  - Based on ChatGPT, it sounds like it is possible to require validation of the text in a text input field while also allowing the field to remain optional (i.e., not requiring it to be filled out) by applying conditional validation logic. If I can confirm this is the case, would this type of conditional validation be preferred?
Double check other required fields on Project Management screen and validation:

Field Name	Required Currently?	Validation?
Project Name	YES	Requested - issue written (no duplicates, minimum 4 characters, allowable symbols: "- , ' " numbers, letters") - should we have Max Char?
Project Description	YES	COMPLETE (250 Characters)
GitHub Identifier	YES - Needed field? We have old issues mentioning dropping #1371 & #1366	Requested - no issue (unsure of how to verify)
GitHub URL	YES	Requested - no Issue (weblink)
Slack Channel Link	YES	Requested - Issue written (weblink)
Google Drive URL	NO	Requested - issue written (weblink)
HFLA Website URL	NO	Requested - issue written (weblink)

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg · 2024-05-30T22:22:23Z

JackHaeg · 2024-06-06T19:59:24Z

2024-06-06 Agenda and Notes

Bonnie unavailable to meet, meeting has been postponed to next week.

Participants:

Issues to discuss:

Review Google Drive URL Spreadsheet
- Note duplicate URLs, and Test accounts.
GitHub Migration
- Any changes in how we build & deploy based on this change?
- Will all links be broken?
Check In re: Privacy Policy
Check In re: HfLA July break.
Steph update

Notes from meeting:

Bonnie's Slack message re: GitHub migration - 2024.06.06

@channel The Product Management Community of Practice is helping projects to properly migrate their project boards. Please reach out to the [#product-management](https://hackforla.slack.com/archives/C010LNXH2JY) Slack channel for help scheduling a meeting for that, if you are unable to attend our Friday meetings.

Things to be aware of:

Each project will get one project board (unless given an exception by the admin team). You can create as many views of your project board as you need.
- If you already have a project board on the new scheme, but your main project board is still on classic, please reach out in the #product-management channel for help rationalizing them into 1 board.
Do not create test boards. If you have created a test project board, open or closed, please be aware, it is visible at the org level. Here is how it works:
- You see any project boards you have created
- You see any project boards that your teams have been granted access to
- The org admins see all project boards even if they are marked private. There is no way to organize the boards (other than what we devise). So given the difficulty of managing the boards, please stop creating test boards.
  - If you want to understand how project boards work for orgs, you can setup your very own org and test them there.
  - We reserve the right to delete any project boards, that are not specifically designated to a team without notification to the author or team members. See the next bullet on how to connect a project board to your team's repo.
Connect the project board to your team
- Add the URL of your repo to the next project boards once the migration is complete. See Food Oasis as an example: https://github.com/orgs/hackforla/projects?query=is%3Aopen+food+oasis. You do this through the settings once you are looking at the open project board (click three dots, choose settings).
- Make sure that the project is connected to the repo. This will happen automatically if you are migrating the project board. If the board is a fresh board (which there should not be any fresh boards). You do that connection from the repository itself.
Cards are not available on the new project boards. All cards will be converted to draft issue, and for the most part, you don't want that.
- If you have a column on your project board with cards (e.g., a start here colum). Create an issue to copy the content from the cards to the issue, so that you can delete them prior to the migration see this wiki page for general details https://github.com/hackforla/product-management/wiki/GitHub-Project-Board-Migration-Issue.
- If you have a card at the top of a column, that explains the column, there is a details option in the new project boards columns where you can put that text. During the weekly product-management meetings we can show you how to implement those.
- If you have a board that is all cards, we recommend you create a spreadsheet and move the content to the sheet with the column names being a selection in column B (e.g., HUU: Persona board transfer spreadsheet)
Members of your team will need to be granted access to the project board. In the settings for the board, you add the names of your GitHub teams, not individual members. That way when a team member is offboarded from the team, they only have to be removed from the Google Drive, GitHub-write team, and Figma. The boards are already publicly visible, so prior volunteers can still see that, as can future team members.
Rename the project board before the migration. The name convention is initials of the team: project board (e.g., Civic Tech Jobs Project board would be CTJ: project board). If you already have more than one board on the new project, please keep the same naming convention (CTJ: project board - pimary, and CTJ: project board - secondary to be rationalized.)

Tasks to do:

Items for next meeting agenda:

JackHaeg added role: Product feature: Agenda role: UI/UX design size: 0.25pt Can be done in 1.5 hours or less labels Sep 21, 2023

JackHaeg added this to the 05.01 Team Workflow milestone Sep 21, 2023

JackHaeg added this to New Issue Approval in VRMS - Active Project Board via automation Sep 21, 2023

JackHaeg moved this from New Issue Approval to General Information/Resources in VRMS - Active Project Board Sep 21, 2023

github-actions bot moved this from General Information/Resources to New Issue Approval in VRMS - Active Project Board Sep 21, 2023

JackHaeg moved this from New Issue Approval to General Information/Resources in VRMS - Active Project Board Sep 21, 2023

This comment was marked as outdated.

Sign in to view

ExperimentsInHonesty changed the title ~~PM/Design Lead Meeting Agenda~~ VRMS: PM/Design Lead Meeting Agenda Sep 26, 2023

JackHaeg modified the milestones: 05.01 Team Workflow, 03.01 Project Management Apr 4, 2024

JackHaeg mentioned this issue May 16, 2024

Remove old Meeting Agendas from Wiki #1636

Closed

4 tasks

JackHaeg self-assigned this May 24, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

VRMS: PM/Design Lead Meeting Agenda #1519

VRMS: PM/Design Lead Meeting Agenda #1519

JackHaeg commented Sep 21, 2023 •

edited

This comment was marked as outdated.

JackHaeg commented Sep 28, 2023 •

edited

JackHaeg commented Oct 5, 2023 •

edited

JackHaeg commented Oct 12, 2023 •

edited

JackHaeg commented Oct 19, 2023 •

edited

JackHaeg commented Oct 26, 2023 •

edited

JackHaeg commented Nov 2, 2023 •

edited

JackHaeg commented Nov 9, 2023 •

edited

JackHaeg commented Nov 15, 2023 •

edited

JackHaeg commented Nov 30, 2023 •

edited

JackHaeg commented Jan 4, 2024 •

edited

JackHaeg commented Jan 25, 2024 •

edited

JackHaeg commented Feb 1, 2024 •

edited

JackHaeg commented Feb 8, 2024 •

edited

JackHaeg commented Feb 15, 2024 •

edited

JackHaeg commented Feb 22, 2024 •

edited

JackHaeg commented Feb 29, 2024 •

edited

JackHaeg commented Mar 28, 2024 •

edited

JackHaeg commented Apr 4, 2024 •

edited

JackHaeg commented Apr 11, 2024 •

edited

JackHaeg commented Apr 18, 2024 •

edited

JackHaeg commented Apr 25, 2024 •

edited

JackHaeg commented May 16, 2024 •

edited

JackHaeg commented May 23, 2024 •

edited

JackHaeg commented May 30, 2024 •

edited

JackHaeg commented Jun 6, 2024 •

edited

VRMS: PM/Design Lead Meeting Agenda #1519

VRMS: PM/Design Lead Meeting Agenda #1519

Comments

JackHaeg commented Sep 21, 2023 • edited

Overview

Old Team Meetings:

This comment was marked as outdated.

JackHaeg commented Sep 28, 2023 • edited

2023-09-28 Agenda and Notes

Participants:

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg commented Oct 5, 2023 • edited

2023-10-05 Agenda and Notes

Participants:

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg commented Oct 12, 2023 • edited

2023-10-12 Agenda and Notes

Participants:

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg commented Oct 19, 2023 • edited

2023-10-19 Agenda and Notes

Participants:

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg commented Oct 26, 2023 • edited

2023-10-26 Agenda and Notes

Participants:

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg commented Nov 2, 2023 • edited

2023-11-02 Agenda and Notes

Participants:

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg commented Nov 9, 2023 • edited

2023-11-09 Agenda and Notes

Participants:

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg commented Nov 15, 2023 • edited

2023-11-15 Agenda and Notes

Participants:

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg commented Nov 30, 2023 • edited

2023-11-30 Agenda and Notes

Participants:

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg commented Jan 4, 2024 • edited

2024-01-04 Agenda and Notes

Participants:

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg commented Jan 25, 2024 • edited

2024-01-25 Agenda and Notes

Participants:

JackHaeg commented Sep 21, 2023 •

edited

JackHaeg commented Sep 28, 2023 •

edited

JackHaeg commented Oct 5, 2023 •

edited

JackHaeg commented Oct 12, 2023 •

edited

JackHaeg commented Oct 19, 2023 •

edited

JackHaeg commented Oct 26, 2023 •

edited

JackHaeg commented Nov 2, 2023 •

edited

JackHaeg commented Nov 9, 2023 •

edited

JackHaeg commented Nov 15, 2023 •

edited

JackHaeg commented Nov 30, 2023 •

edited

JackHaeg commented Jan 4, 2024 •

edited

JackHaeg commented Jan 25, 2024 •

edited

JackHaeg commented Feb 1, 2024 •

edited

JackHaeg commented Feb 8, 2024 •

edited

JackHaeg commented Feb 15, 2024 •

edited

JackHaeg commented Feb 22, 2024 •

edited

JackHaeg commented Feb 29, 2024 •

edited

JackHaeg commented Mar 28, 2024 •

edited

JackHaeg commented Apr 4, 2024 •

edited

JackHaeg commented Apr 11, 2024 •

edited

JackHaeg commented Apr 18, 2024 •

edited