Open JackHaeg opened 12 months ago
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 |
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 |
Updates:
Other 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: https://github.com/hackforla/VRMS/issues/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 #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 #1411 & #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.
Issues that were missed during Monday call:
[x] Bonnie - Review feature label updates: https://github.com/hackforla/VRMS/issues/1537 (updates made on internal features: https://docs.google.com/spreadsheets/d/14fd47047A42vycujTc03MeahFZyHHqM2ke-B3VaqH4w/edit#gid=0)
[ ] Are any fields missing from Project Details screen, and are there any that can be dropped (e.g., GitHub Identifier)?
[ ] Review functionality on Project Details screen based on UALs.
[x] Okay to have UALs based on per project? Perhaps only for UAL 3 (PM) and lower UAL...admins would always be labeled as such?
[ ] RE: designs - which UALs should be included?
[ ] For Project Details screen, should we include all Project members, or just project leads?
Project Details screen
If time permits, discuss the following issue
Bonnie's feedback re: PMs being able to edit project details on current VRMS build.
Delete/restore Icons:
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 |
[x] Julia OOO until June 19
[x] Steph responded to request & removed Otter.AI from Zooms. Interested in staying on the team.
[x] GitHub Migration to the new Projects experience?
[x] Re: Google Drive URL on Project Management screen - last week, you mentioned that this should be a required field, however we recently dropped that requirement, as it was blocking changes to project information for projects without a Google Drive URL.
[ ] Check in re: Privacy Policy
Bonnie unavailable to meet, meeting has been postponed to next week.
@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](https://hackforla.slack.com/archives/C010LNXH2JY) 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](https://docs.google.com/spreadsheets/d/1wJg1u7pBLRaiuebMPzkg-juLu3RRspEegRYlkE3LBx8/edit#gid=0) 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.)
Please add to next agenda
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.
Overview
This issue tracks the agendas and notes from the weekly PM/Design Lead Meeting
Template
Old Team Meetings:
Previous Team Meeting Agendas (from 2022) that were previously stored on the VRMS Wiki have been preserved in this issue.