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
- [ ] 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 [email protected] #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, 3-60 characters, allowable symbols: "- , ' " numbers, letters") - #1268
Project Description	YES	COMPLETE (250 Characters)
GitHub Identifier	YES (Change to NOT REQUIRED to be filled, but keep this field)	Requested - no issue (unsure of how to verify)
GitHub URL	YES	Requested - Issue written, but has been closed #1367
Slack Channel Link	YES	Requested - Issue written #1368
Google Drive URL	NO (Change to REQUIRED field)	Requested - issue written #1369
HFLA Website URL	NO	Requested - issue written #1370

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 · 2024-06-13T20:41:11Z

JackHaeg · 2024-06-20T22:41:05Z

JackHaeg · 2024-07-16T19:33:20Z

As requested by @ExperimentsInHonesty - during our next PM meeting, we should update the Weekly Audit of Labels and milestones with a some new items to check. (See comment here: Weekly Audit of labels and milestones #1168 (comment))
Evaluate VRMS suitability and readiness for internship #1697

JackHaeg · 2024-08-08T21:23:58Z

JackHaeg · 2024-08-15T22:42:31Z

ExperimentsInHonesty · 2024-08-23T15:26:21Z

Please add to next agenda

Discuss why there are three issues about the same thing https://github.com/hackforla/VRMS/issues?q=is%3Aopen+is%3Aissue+label%3A%22p-feature%3A+User+Permissions%22
Where is the issue to have a list of all people who have PM access. (is it this one? Fix the api for projects to include project users #1163) I need this so that I can look up a project, and
- see who I might need to offboard (which currently, I would have to look up each PM that is marked inactive on the roster for the team)
- see if all the pms are currently onboarded (although I can currently look up a few people manually)

JackHaeg · 2024-08-29T21:33:26Z

2024-08-29 Agenda and Notes

Participants:

Issues to discuss:

Is this the issue to have a list of users who have PM access on a project? Fix the api for projects to include project users #1163
- (pending feedback from Trillium) - Yes, this issue appears to may be partially linked to this request to see a list of users with PM access on a project (pending confirmation from Trillium on this). I believe this would be the first step in the process, as it would enable VRMS to display such information, as well as the following issues tied to promoting and demoting PMs
  - This is partially linked to the below duplicate issues:
Discuss duplicates of same issue:
- PMs need to be able to give other PMs access #1243 & Allow project managers to assign new project managers to projects they manage #1231 are exact copies. However PMs need to be able to give other PMs access #1243 has additional information at the top of the issue.
- Create ability for Admins to promote and demote Admins #1486 Appears to be an issue written by Trillium that is specific to Admins promoting another user to Admin (i.e., Bonnie promotes Jack to admin) as opposed to PMs being able to provide PMs access.
  - Confirm if okay with implementing on the edit user page.
  - Thus, I would recommend the following:
    - Dropping one of these two issues** (PMs need to be able to give other PMs access #1243 or Allow project managers to assign new project managers to projects they manage #1231) as they are exact copies.
    - Develop / refine designs linked to this issue (either with Figma screenshot below, or modal approach. Note that the Figma screenshot is from an older issue (As a HforLA admin, I need to be able to assign a lead PM to be able to assign admin permission to other project PMs #1273) that was closed as unplanned due to being a duplicate.

Figma Screenshot

Also recommend keeping Create ability for Admins to promote and demote Admins #1486, potentially adding the same screenshot.
As for Stakeholder Feedback: Define User Access Levels (UAL) #1534, this is an issue re: User Access Levels, which is blocked until UALs are fully defined by People Depot.
Action item"
- That said, we could use clarity on next steps, re: moving ahead with these issues (list of PMs, with existing UALs (i.e., base-level user, PM, Admin), or place in icebox until UALs can be finalized?

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

ExperimentsInHonesty · 2024-08-29T23:42:47Z

When you click User you get this

If you click the first link you get this

If you click the second link you would get this

and if you clicked the Results by PM you would get this

to make someone an admin, you would go to their user record and toggle.

JackHaeg · 2024-09-05T22:53:48Z

2024-09-05 Agenda and Notes

Participants:

Issues to discuss:

Closed PMs need to be able to give other PMs access #1243 as this is a duplicate.
Slightly refined wording on Allow project managers to assign new project managers to projects they manage #1231 and placed in icebox with the dependency to complete once the "Permission Management" issues (Results by Admin & Results by PM) are complete.
- Note that currently, PMs can only see the "projects" tab, they do not see the "users" tab (this is reserved for Admins only at the moment). Thus to enable something like Allow project managers to assign new project managers to projects they manage #1231 , we would need to:
  - 1. Open up access to "User Management" screen for PMs (however, do not allow access to "Permission Management" screen). PMs to see the "Users" tab and the "User Management" screen to search by user (see all users or perhaps only filtered to users on their team), and then add a user to only their project within the user profile screen (again, only allowing.
  - 2). Enable another flow for PMs entirely?
  - ANSWER: This issue has been placed in the icebox for now and will be revisited after implementing this Permission Management fix.
Discuss epic creation for new Permission Management features refine draft together": Epic - User Permission Search #1737
- Should "User Permission Management" be searchable, or provide a list format? If so, will need to add search component.
  - YES, add search component.
  - Results by Admin:
    - Display full list, alphabetical order by user name
    - Search by user name
  - Results by PM:
    - search by project name only.
    - Change title to "Results by Project Lead"
- Should this existing issue be added to the epic? Create ability for Admins to promote and demote Admins #1486
  - Yes, this should be added to the epic (to be implemented directly after the "results by Admin" feature is completed).
  - However, it needs to be reviewed further with Bonnie during next week's PM call.
- Timeline - kick off with design first for mid-fi screens, or move ahead with existing screens?
  - Move ahead with implementation based on
- Displaying PMs with multiple projects?
  - Repeat the User Name for each project they are on.
    - Alphabetical order, organized by project, and then organized by user name.

Notes from meeting:

Bonnie's mockups: https://docs.google.com/presentation/d/1oPP7mXDb09le3vVyaB4YUzOYYDa7sqDVCmvW5Srg30k/edit#slide=id.g2f7a654f994_0_14
Build out "Results by Admin" & Admin

Tasks to do:

Refine Bonnie's mockups for quick implementation. Per Bonnie - no additional UI/UX required for this implementation, as this is a hotfix that will be revised in the future.

Items for next meeting agenda:

Review existing issue that will be part of epic: Create ability for Admins to promote and demote Admins #1486
Discuss epic
Confirm default display of Results by Admin and Results by Project Lead (prior to entering a search query) = full list of users. Believe this is the case, as the request was for Bonnie to be able to access a list of all Admins, and a list of all PMs on each project. Given that only Admins will be able to access these features, not sure if there are any issues associated with displaying full list.

JackHaeg · 2024-09-12T21:17:23Z

2024-08-12 Agenda and Notes

Participants:

Issues to discuss:

Discuss epic: Epic - User Permission Search #1737
- Review Jack's updated designs of original (updated with search bar, refined filter labels - dropped "Results by", and clean UI)
- Explore questions:
  - Should search be name & email or just name? (currently User search is divided into name OR email - so if we stick with existing functionality, perhaps name would be best?)
    - ANSWER: Just name
  - Should search for "Project Leads" allow for searching based on project name?
    - ANSWER: Name OR Project
  - Confirm default view (prior to entering search query). Should this be a list of all relevant users (e.g., ALL admins, and ALL project leads?)
    - Believe this was the case given that the requests from Bonnie were:
      - "to see who I might need to offboard (which currently, I would have to look up each PM that is marked inactive on the roster for the team)"
      - "to see if all the pms are currently onboarded (although I can currently look up a few people manually) was to be able to access a list of all admins and alist of all PMs on each project."
      - Also, given that only Admins will be able to access these features, this may limit any issues associated with displaying a full list of users - discuss further.
    - ANSWER: YES - we need to see everything here (show full list of admins, and show project leads full list
  - Discuss placement of "VRMS Admin" toggle on "EditUsers" screen
    - ANSWER: Yes - use new placement
  - Review existing issues that may be part of this epic (pending confirmation from Trillium ATM): Create ability for Admins to promote and demote Admins #1486 & Fix the api for projects to include project users #1163
    - ANSWER: Create ability for Admins to promote and demote Admins #1486 is relevant & a linked issue. Fix the api for projects to include project users #1163 is not relevant for this epic
- Julia to present alternate options / brainstorm ideas on how to streamline this process from a UI/UX perspective (e.g., unifying "User Management" and "User Permission Management" on one page, and implementing a series of 4 different filters to take care of all processes).

Notes from meeting:

Discussed new super admin user feature to secure the admin promotion/demotion process and ensure we never lose control of the system. Jack to create issue and discuss with the team.

Tasks to do:

Items for next meeting agenda:

JackHaeg · 2024-09-19T22:31:40Z

JackHaeg · 2024-09-26T20:53:09Z

JackHaeg · 2024-10-03T22:21:00Z

JackHaeg · 2024-10-10T22:06:01Z

2024-10-10 Agenda and Notes

Participants:

Issues to discuss:

Epic: Marketing: VRMS marketing#70
Demo of Admin Toggle feature: https://dev.vrms.io/login (Jack Haeger-PM account)
Update on Vite Build Issue:
- Build system is now fixed and working, no impact on current functionality. Can merge & build again.
- CI/CD unit test suite is not building, Trillium working on getting the test suite runner working again.

Notes from meeting:

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

Tasks to do:

Items for next meeting agenda:

Just met with PD, lets followup on this hackforla/peopledepot#417 (comment)

ExperimentsInHonesty · 2024-10-16T20:30:20Z

Add to next agenda.

Talk about VRMS: Active projects as of 2023-01 and Product Management CoP Weekly Agenda 2024 product-management#379
Why I can't update the Food Oasis UXR meeting from Friday at 3pm to Thursday at 12pm, every other week, with a new zoom link.

JackHaeg · 2024-10-17T22:37:15Z

2024-10-17 Agenda and Notes

Participants:

Issues to discuss:

Notes from meeting:

Tasks to do:

Make a feature for deleting a project (only super admins can use this feature). The below task will have to be completed until the feature is implemented.
Create the following labels:
- test projects: unknown
- test projects: yes
- test projects: no
- test projects: removed
- test projects: added to sheet
- test projects: marked as closed in sheet

Add "unknown" label to all dev issues

Add instruction text to a comment on the issue:

  - Did you create test projects in this issue?
    - [ ] Yes
    - [ ] No
  - If YES, Rename the project name by appending this name format "Test-[ISSUE NUMBER]" to the end of the project name in the following locations:
    - [ ] dev.vrms.io
    - [ ] Spreadsheet

Check if dev said yes or no
- If "no" then add the label "test projects: no"
- If "yes" then
  - Edit the issue (add a checkbox to the issue that says "once merged, update column E of the spreadsheet")
  - Add label: "test projects: yes"
Check to see that the issue number has been added to the sheet. If it has, add the "test projects: added to sheet" label
When issue is closed, if they have the "yes" label, confirm that the spreadsheet was updated with it marked as closed.
- Double check closed issues that don't have the "added to sheet"

Notes:

When an issue is labeled as "test projects: no" then can ignore that issue. Only review the "test projects: yes" & "unknown" labeled issues
- Issues with the following labels test projects: "yes" "no" and "unknown" are the only exclusive labels, other labels are to be added on top of these labels.
- Can add additional labels as needed (e.g., "yes", "added to sheet", "marked as closed in sheet")

Items for next meeting agenda:

ExperimentsInHonesty · 2024-10-24T01:35:27Z

Discuss the open PR at incubator Vrms client terraform migration incubator#29

JackHaeg · 2024-10-31T22:13:43Z

2024-10-31 Agenda and Notes

Participants:

Issues to discuss:

Vrms client terraform migration incubator#29
Updates on User Permissions Epic

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

JackHaeg · 2024-11-07T23:54:07Z

JackHaeg · 2024-11-14T23:37:44Z

2024-11-14 Agenda and Notes

Participants:

Issues to discuss:

Plan to post open dev role next week - will be looking to onboard in January, but can post ahead. Previously took a vote and the team opted out of meeting during Thanksgiving Week, meaning that next Monday (Nov 18th) may be our last meeting for the year (i.e., likely no team meeting following onboarding call on 19th of November).
- Assume that new issues should be created each time a role posting is available vs. re-opening previous posting (e.g., VRMS: Open Role for: Back End Developer #1673)
Re: Terraform - Angela went to the DevOps meeting. Her update is as follows:
- "The team asked me to make minor changes to Tyson's branch and push them up. They’d like to review the GitHub Action errors and troubleshoot from there. Later in the meeting, after a discussion between Bonnie and the leads, they agreed to take this issue back to Ops and put it in the icebox. There’s no harm in proceeding with the trigger."
  - Asked Angela to post a comment on the PR with this status update.
  - Mentioned that the team agreed to take this issue(Assist with migrating deployment to Terraform #1497) back to Ops and put it in the icebox.
    - Question: Should we place this issue in the icebox on the VRMS project board and un-assign Angela & other assignees?
Trillium out this week - have sent a prioritized list of tasks / knowledge transfer. Requested rebuild of PROD. Plan to discuss during next Monday's call.
Team to reference for Accomplishments Epic?

Notes from meeting:

Re: Open Dev Role:
- Create a new issue. Within the main issue, you should have a copy of the draft of the issue.
- Post the open role after the 19th
Re: Terraform:
- Angela should do a commit to refresh the PR, as this will aid in finding out why it is failing and provide feedback
- The Ops team will go in and place this issue (Assist with migrating deployment to Terraform #1497) in the icebox, and un-assign users from the issue
- Angela does not need to do anything with this issue in particular, just the PR. Recommend working independently as opposed to partnering with someone.
Re: Trillium:
- Potentially create an open role for Co-Lead Developer or Lead developer after discussing with Trillium. Post this role before Jan 6.
Re: Accomplishments Epic:
- Check out Civic Tech Jobs as a reference.

Tasks to do:

Items for next meeting agenda:

JackHaeg · 2024-11-21T23:49:00Z

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

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

JackHaeg added this to P: VRMS: Project Board Jun 13, 2024

JackHaeg moved this to General Information/Resources in P: VRMS: Project Board Jun 13, 2024

ExperimentsInHonesty mentioned this issue Oct 19, 2024

Epic: Marketing: VRMS hackforla/marketing#70

Open

17 tasks

VRMS: PM/Design Lead Meeting Agenda #1519

VRMS: PM/Design Lead Meeting Agenda #1519

Comments

JackHaeg commented Sep 21, 2023 • edited Loading

Overview

Old Team Meetings:

This comment was marked as outdated.

JackHaeg commented Sep 28, 2023 • edited Loading

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 Loading

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 Loading

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 Loading

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 Loading

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 Loading

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 Loading

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 Loading

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 Loading

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 Loading

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 Loading

2024-01-25 Agenda and Notes

Participants:

JackHaeg commented Sep 21, 2023 •

edited

Loading

JackHaeg commented Sep 28, 2023 •

edited

Loading

JackHaeg commented Oct 5, 2023 •

edited

Loading

JackHaeg commented Oct 12, 2023 •

edited

Loading

JackHaeg commented Oct 19, 2023 •

edited

Loading

JackHaeg commented Oct 26, 2023 •

edited

Loading

JackHaeg commented Nov 2, 2023 •

edited

Loading

JackHaeg commented Nov 9, 2023 •

edited

Loading

JackHaeg commented Nov 15, 2023 •

edited

Loading

JackHaeg commented Nov 30, 2023 •

edited

Loading

JackHaeg commented Jan 4, 2024 •

edited

Loading

JackHaeg commented Jan 25, 2024 •

edited

Loading

JackHaeg commented Feb 1, 2024 •

edited

Loading

JackHaeg commented Feb 8, 2024 •

edited

Loading

JackHaeg commented Feb 15, 2024 •

edited

Loading

JackHaeg commented Feb 22, 2024 •

edited

Loading

JackHaeg commented Feb 29, 2024 •

edited

Loading

JackHaeg commented Mar 28, 2024 •

edited

Loading

JackHaeg commented Apr 4, 2024 •

edited

Loading

JackHaeg commented Apr 11, 2024 •

edited

Loading

JackHaeg commented Apr 18, 2024 •

edited

Loading