-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verify Required Attendees of HfLA Projects' Team Meetings #11
Comments
|
Progress: messaged all PMs |
@shinhope Please provide the allowable meeting types from the Attendee column. So Bonnie can decide if these Civic Tech Structure meeting type can fit in the existing category. |
@shinhope Can you let us know your progress in regards to this issue? Thank you =] Progress: |
Yes. |
Progress: almost done, just waiting for Civic Tech Structure |
@shinhope Can you let us know your progress in regards to this issue? Thank you =] Progress: |
@shinhope
|
Progress: still waiting for Civic Tech Structure |
Btw the team meetings spreadsheet linked in the top comment will be relevant to you @cherrijeong (& Ingrid) for the Roles board- it shows which team meetings are for which members, which is important for the schedule filter (because so far in the Events page a lot of the team meetings listed don't specify if they're for PM's, designers, devs, etc) |
I moved this issue from hackforla website for us to discuss at next team meeting |
@ExperimentsInHonesty , need your guidance on where this ticket should be queued. Does it even belong to Civic Tech Jobs? |
closing this issue because this has been solved and we are moving to retrieving project meeting time from VRMS. |
Dependency
Overview
We need to determine which team members are required to attend which HfLA project team meetings, so that we can create a more accurate project team meetings filter for the upcoming Volunteer Opportunities page.
Action Items
Resources/Instructions
Team meeting spreadsheet
Events page schedule
Upcoming Volunteer Opportunities page
The text was updated successfully, but these errors were encountered: