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.

Sign up for GitHub

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

Jump to bottom

VRMS: PM/Design Lead Meeting Agenda #1519

Open
JackHaeg opened this issue Sep 21, 2023 · 39 comments
Open

VRMS: PM/Design Lead Meeting Agenda #1519

JackHaeg opened this issue Sep 21, 2023 · 39 comments
Assignees
@JackHaeg
Labels
feature: Agenda role: Product role: UI/UX design size: 0.25pt Can be done in 1.5 hours or less
Milestone
03.01 Project Man...

Comments

@JackHaeg
Copy link
Member

JackHaeg commented Sep 21, 2023 •
edited
Loading

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
- [ ] 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.
@JackHaeg JackHaeg added this to the 05.01 Team Workflow milestone Sep 21, 2023
@JackHaeg

This comment was marked as outdated.

Sign in to view
@ExperimentsInHonesty ExperimentsInHonesty changed the title PM/Design Lead Meeting Agenda VRMS: PM/Design Lead Meeting Agenda Sep 26, 2023
@JackHaeg
Copy link
Member Author

JackHaeg commented Sep 28, 2023 •
edited
Loading

2023-09-28 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

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
Copy link
Member Author

JackHaeg commented Oct 5, 2023 •
edited
Loading

2023-10-05 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

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
Copy link
Member Author

JackHaeg commented Oct 12, 2023 •
edited
Loading

2023-10-12 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

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
Copy link
Member Author

JackHaeg commented Oct 19, 2023 •
edited
Loading

2023-10-19 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

  • Julia - discuss specs / design issues
  • Refine remaining feature labels.
  • Explore changed milestones / add to current project?

Notes from meeting:

  • Reviewed Julia's latest designs, explored specs, interactions, and logic together for meetings & project flows.

Tasks to do:

  • Jack - move all closed issues on VRMS Research project to active VRMS project, then close VRMS research project on Git
  • Jack - write up an issue for Bonnie to define project statuses (on hold, archived, completed, active, deleted), assign to Bonnie.
  • Jack/Julia - coordinate to create an issue describing user access levels.
  • Move specs to Wiki on GitHub for all specs that have been decided upon (& potentially close current issue: VRMS specs and UI requirements #1473)

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Oct 26, 2023 •
edited
Loading

2023-10-26 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Updates:

Other issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Nov 2, 2023 •
edited
Loading

2023-11-02 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:

@JackHaeg
Copy link
Member Author

JackHaeg commented Nov 9, 2023 •
edited
Loading

2023-11-09 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:

@JackHaeg
Copy link
Member Author

JackHaeg commented Nov 15, 2023 •
edited
Loading

2023-11-15 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:

@JackHaeg
Copy link
Member Author

JackHaeg commented Nov 30, 2023 •
edited
Loading

2023-11-30 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Issues that were missed during Monday call:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Jan 4, 2024 •
edited
Loading

2024-01-04 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Notes from meeting:

Tasks to do:

  • Ask Josh / Trillium for a CSV of names & email addresses of people who attended the holiday parties (message sent, awaiting response)
  • Update any issues related to Slack functionality with a dependency (not priority, need to make an issue that include requirements).
  • Discuss with Trillium if this needs to be achieved across entire site (if using pixels instead of REMS), then this would be an issue for the dev team. Make VRMS designs responsive #1410

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Jan 25, 2024 •
edited
Loading

2024-01-25 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

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
Copy link
Member Author

JackHaeg commented Feb 1, 2024 •
edited
Loading

2024-02-01 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Notes from meeting:

  • Reviewed all feature labels with Bonnie. Everything has been labeled, with the exception of ~30 closed issues that are still missing features

Tasks to do:

  • Complete review of closed issues missing feature labels.

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Feb 8, 2024 •
edited
Loading

2024-02-08 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Project Details screen

See screenshot of added fields

First section of Project Details screen (existing fields)
Screenshot 2024-02-08 at 5 52 49 PM

New fields highlighted in red
Screenshot 2024-02-01 at 4 00 49 PM

  • RE: designs - which UALs should be included?
    • Should we design for the current UALs (3 levels) or with all new UALs?
    • Review functionality on Project Details screen based on UALs.
  • For Project Details screen, should we include all Project members, or just project leads?

If time permits, discuss the following issue

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Feb 15, 2024 •
edited
Loading

2024-02-15 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Notes from meeting:

  • ended meeting early due to illness

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Feb 22, 2024 •
edited
Loading

2023-02-22 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

  • Julia - catch up on designs / next steps.
  • Discuss milestone prioritization (currently, "Project Management" comes before "Existing features"
  • Discuss feature epic creation with Bonnie for "Events" feature and more (potentially with Event View and Event Edit as separate Epics).
    • Review current design vs upcoming design.
  • Confirm if future Project details screen should include ALL team members or ONLY project team leads, as this would impact designs.

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Feb 29, 2024 •
edited
Loading

2024-02-29 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

  • Met with Julia & Trillium separately this week.
  • Update on Check in bug - after further review, appears to have been solved and the fix should be going into PROD shortly. (given this is a bug fix and we are not introducing new functionality, what are QA testing requirements prior to PROD - are stakeholder's required?)
  • Updates to Login and Landing / Check in pages - both of these pages use outdated design. Given that there was already a request to fix the Login page, we elected to update the Checkin page as well. Low lift / high impact.
    • Discuss alternative logos?
    • Design audit of other screens to get this up to date
  • Discuss handling of Epic issues (new column created)
  • Review issues contained within the "Existing Features" Milestone:
    • Check if any issues are missing

Notes from meeting:

  • Bonnie was unavailable to meet for today's call. Jack & Trillium discussed next steps on the check in bug release to PROD, and login and landing check in page updates.

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Mar 28, 2024 •
edited
Loading

2024-03-28 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

  • Catch up (new team members, progress)
  • Check in Bug, Project Edit save status - both have made significant progress. Waiting for merge review on Project Edit save status, which has been fixed, all check-ins for onboarding are now working on-time. All other projects to be updated this week. Longterm fix for events checkins that will address daylight savings time has been discovered and will continue to be worked on.
  • Create a validation limiting event names from certain strings #1514 - Collect list of words commonly used in meeting descriptions from stakeholder.
  • Rohan working on Add privacy policy #506 - discuss next steps with stakeholder
    • Privacy policy being worked on by Bonnie currently, in icebox
  • Julia - present signup/login flow on Figma, also potentially explore re-use of archived designs.
  • FYI - Epic issues (new column created)
  • Discuss updates on People Depot (if any), how this may impact VRMS, and explore timeline for such changes.
  • Discuss milestones

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Apr 4, 2024 •
edited
Loading

2024-04-04 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:

@JackHaeg
Copy link
Member Author

JackHaeg commented Apr 11, 2024 •
edited
Loading

2024-04-11 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

  • Privacy policy check in.
  • Review "Project Status" updates Latest designs
    • what happens with OnHold / Completed / Archived events?
    • Restore modals
    • Project Lists - Julia mentioned whimsical / wireframes All Projects list #1545
  • Milestone cleanup continued

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Apr 18, 2024 •
edited
Loading

2024-02-18 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

  • Privacy policy check in
  • Julia - Additional updates to "Project Status"
  • Updates on Check In bug QA testing
  • Milestone cleanup (pending time)

Notes from meeting:

Bonnie's feedback re: PMs being able to edit project details on current VRMS build.

  • When testing VRMS with a Project Manager assigned to the Tables Project, PM was able to edit the project details.
    • PMs assigned to a project are not supposed to be able to edit anything about the project currently. PMs should only be able to edit/add/remove the events of a project in VRMS current state.
    • Reason: in the current state of VRMS, there is no review process for PM edits to project details, so we cannot allow PMs to make edits to Project details. In the future, we will allow for certain project edits by a PM because a PM's project edits will be passed on to an Admin to be reviewed/approved.
    • PM cannot edit project details…. (Can only view the rest of it).
      • Find the guidance… if it’s not everything, then review what it is.
      • IN Current state, there is no review process, so cannot be able to edit.
  • In summary: Any project edits should be LIMITED to admins only in CURRENT state.

Delete/restore Icons:

Tasks to do:

  • QA Test PM access to make project edits on projects using DEV/PROD.
  • Depending on results, create issue limiting project edit abilities on PM accounts (project edit limited to Admins only, PMs can only edit events).

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Apr 25, 2024 •
edited
Loading

2024-02-25 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Notes from meeting:

  • Julia unavailable this week due to competing meetings/obligations, will plan to finalize Project Status screens on Monday's call.

Tasks to do:

Items for next meeting agenda:

  • Check in with Bonnie re: HfLA Privacy Policy progress

@JackHaeg
Copy link
Member Author

JackHaeg commented May 16, 2024 •
edited
Loading

2024-05-16 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

  • Check in re: privacy policy creation by Bonnie.
    • Check in next week
  • Project status - any integration between website and VRMS required for initial release?
    • No integration required
  • Update - Josh / Brad attending DevOps CoP this week. Several issues being reviewed and addressed by the team (1099, 1497, 1493, 1544, 1469)
  • Fix to Project Details page on VRMS - now PMs cannot edit project details, only Admins are allowed to. Fix is in place in Dev, and will be in place in PROD once it is rebuilt.
  • As discussed, will remove old meeting agendas from Wiki: Remove old Meeting Agendas from Wiki #1636
  • Trillium: Any updates on status of People Depot taking over VRMS backend?
    • Problem solving has been pushed forward, two devs working on it are out at the moment. Check back in next week.

Notes from meeting:

  • Make an issue to stop publishing the Zoom link in the API (based on each event. Don't need to be available in the public API).

Tasks to do:

Items for next meeting agenda:

@JackHaeg JackHaeg mentioned this issue May 16, 2024
Closed
4 tasks
@JackHaeg
Copy link
Member Author

JackHaeg commented May 23, 2024 •
edited
Loading

2024-05-23 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

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
Screenshot 2024-05-23 at 5 28 03 PM

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@JackHaeg JackHaeg self-assigned this May 24, 2024
@JackHaeg
Copy link
Member Author

JackHaeg commented May 30, 2024 •
edited
Loading

2024-05-30 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

  • Julia OOO until June 19
  • Steph responded to request & removed Otter.AI from Zooms. Interested in staying on the team.
  • GitHub Migration to the new Projects experience?
Screenshot 2024-05-30 at 5 16 05 PM
  • 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.
    • A lot of the projects on VRMS do not currently include a Google Drive URL. By requiring a Google Drive URL in order to create/edit/save a project management form on VRMS, these existing projects will be locked from any changes on VRMS. Is this acceptable (we may need ALL projects on VRMS to update that info, or perhaps we can set up a time between the two of us to work on this together)?
    • Are there any occasions where a Google Drive URL will not be available? E.g., perhaps a “completed” / “on hold” / “archived” project or a test project does not have/need a Google Drive URL.
  • Check in re: Privacy Policy

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Jun 6, 2024 •
edited
Loading

2024-06-06 Agenda and Notes

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

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

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
Copy link
Member Author

JackHaeg commented Jun 13, 2024 •
edited
Loading

2024-06-13 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Notes from meeting:

  • New approach to Open Roles, handled by Recruit volunteers for team open roles #1670
    • All recruitment questions above answered within this issue and by this new approach.
  • Bonnie will have Rabia complete the Google Drive URL spreadsheet.

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Jun 20, 2024 •
edited
Loading

2024-06-20 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Rohan
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Notes from meeting:

  • reviewed open role boards with Bonnie & Deleted old open role cards

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Jul 16, 2024 •
edited by ExperimentsInHonesty
Loading

@JackHaeg
Copy link
Member Author

JackHaeg commented Aug 8, 2024 •
edited
Loading

2024-08-08 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Aug 15, 2024 •
edited
Loading

2024-08-15 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Aug 23, 2024 •
edited by JackHaeg
Loading

Please add to next agenda

@JackHaeg
Copy link
Member Author

JackHaeg commented Aug 29, 2024 •
edited
Loading

2024-08-29 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Figma Screenshot

Image

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Aug 29, 2024 •
edited
Loading

When you click User you get this
image

If you click the first link you get this
image

If you click the second link you would get this

image

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

image

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

@JackHaeg
Copy link
Member Author

JackHaeg commented Sep 5, 2024 •
edited
Loading

2024-09-05 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Bonnie
  • Josh
  • Trillium (optional)

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:

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
Copy link
Member Author

JackHaeg commented Sep 12, 2024 •
edited
Loading

2024-08-12 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Bonnie
  • Josh
  • Trillium (optional)

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:
            1. "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)"
            1. "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
    • 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
Copy link
Member Author

JackHaeg commented Sep 19, 2024 •
edited
Loading

2024-09-19 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

  • Making progress on the User Permission Epic
    • Already have a PR submitted for VRMS Admin Toggle feature
    • Currently have a developer working on Super Admin feature
    • Trillium out this week with an injury. But we are aiming to release ASAP.
  • Josh & Brad reviewed PRs during call with team, Josh to review throughout this week.
  • Any issues with how I submitted the team changes on the website? I may have a few more edits in the near future and can submit one issue per person going forward.
  • Audit of GitHub VRMS Write team.
  • Recruiting additional volunteers.

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Sep 26, 2024 •
edited
Loading

2024-09-26 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

  • Continued progress on Admin Promotion/Demotion Feature, Super User, User Permission Management work.
    • PRs moving in the right direction.
    • Trillium ran into issues rebuilding Dev Environment (failed to build), currently reviewing changes.
  • Audit of GitHub VRMS team - see Audit VRMS GitHub Roster #1763

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

@JackHaeg
Copy link
Member Author

JackHaeg commented Oct 3, 2024 •
edited
Loading

2024-10-03 Agenda and Notes

Participants:

  • Julia
  • Jack
  • Steph
  • Bonnie
  • Josh
  • Trillium (optional)

Issues to discuss:

Notes from meeting:

Tasks to do:

Items for next meeting agenda:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JackHaeg JackHaeg

Labels
feature: Agenda role: Product role: UI/UX design size: 0.25pt Can be done in 1.5 hours or less
Projects
P: VRMS: Project Board
Status: Agendas & Resources
Milestone
03.01 Project Management
Development

No branches or pull requests
2 participants
@ExperimentsInHonesty @JackHaeg