Lucky Parking: PM/Org's Agenda and Meeting Minutes

MichelleRT commented 2 years ago

Overview

This issue tracks the agenda for our weekly meetings so that all team members can:

look back on the history
get up to speed faster
contribute more effectively

Issue Template

## [Date ]  Meeting Agenda

### Prework to prep for meeting
- [ ] Review New Issue Approval Column in preparation for talking to Bonnie

### Recurring items: Happens on the ________ meeting
 - [ ] review any issues that are in the [new issue approval column](https://github.com/hackforla/lucky-parking/projects/3#column-17941639)
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each Team member
       - [ ] [Gordon Ruby](https://github.com/hackforla/lucky-parking/issues/assigned/gordonruby)
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard 
      - [ ]  #

### New Items
- [ ] 
- [ ] Carry over Items to next meeting that don't get addressed

### FYIs
-

### Notes from Meeting

### Task Items
- Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

Links to other agenda issues for your team

(so that you can easily post on their agendas items that come up at yours)

Previous Meetings (link to each comment with the date)

MichelleRT commented 2 years ago

[2022-03-03] Meeting Agenda

(Thursdays at 7:30 AM)

Prework to prep for meeting

[ ] #

Recurring items:

[x] review any issues that are in the new issue approval column
[x] Accountability and Support Check.
- [x] Review assignments for each Team member
  - [x] Michelle Tse
  - [x] Tiffany Lin
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard
  - [ ] #

New Items

[ ]
[ ] Carry over Items to next meeting that don't get addressed

FYIs

-

Notes from Meeting

Created new issue approval column
Recorded video of this meeting
Bonnie got control of the luckyparking@hackforla.org email
Created this agenda issue
Tried to log in to luckyparking@hackforla.org but was unsuccessful

Task Items

[x] Bonnie will upload the recording to Zoom Meeting Recordings
[x] Michelle will log into luckyparking@hackforla.org in 24 hours and select text for authentication to Bonnie
- [x] Text Bonnie the authentication code (Bonnie's phone number is in 1Password)

ExperimentsInHonesty commented 2 years ago

Please add discussing this issue to the next agenda

https://github.com/hackforla/lucky-parking/issues/155

MichelleRT commented 2 years ago

[2022-03-10] Meeting Agenda

(Thursdays at 7:30 AM)

Prework to prep for meeting

[x] Review [2022-03-03] LP: PM/Org's Agenda and Meeting Minutes with Tiffany

Recurring items:

[ ] review any issues that are in the new issue approval column
- [ ] Review issue https://github.com/hackforla/lucky-parking/issues/155
[ ] Accountability and Support Check.
- [ ] Review assignments for each Team member
  - [ ] Michelle Tse
  - [ ] Tiffany Lin
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard
- [ ] Diedrich Chavarria as a Backend Developer
- [ ] Edwin Liu as a Data Scientist

New Items

[x] Questions from the team:
- [x] Is there supposed to be a widget?
- [x] Should the UX team have both wide desktop and mobile version designs?
[ ] Carry over Items to next meeting that don't get addressed

FYIs

-

Notes from Meeting

Bonnie explained we need to prioritize working on the linked website
- Reach out to Matt for the website
- The domain name luckparking.org should be owned by the org instead of an individual
Figure out how often the data is updated
The default date on the website should be either today's date or the latest available date from the data
There should be constraints on the dates for the data selection
After we get the website working, then we can go to the research team to get feedback
We should be trying to move the team towards one project board after the Offboarding and Team Members Cleanup
Every member's Github name (not handle) should be their LP roster name
UX should have a desktop, mobile and tablet version
We will need to eventually consolidate the three project boards into one
Other citizen engagement projects https://www.hackforla.org/citizen-engagement:
- 311 Data (on hold right now):
  - PM: Pras
  - PM: Eric Cho
  - Agile Coach: Bonnie Wolfe
- Access the Data:
  - PM: Lucy Chang
  - PM: AJ jPrice
  - UI/UX Lead: Melissa Murphy
  - UI/UX Lead: Joanna Pham
- Engage PM:
  - Bryon Heart
  - UI/UX lead: Ryan Mayott
  - Agile Coach: Bonnie Wolfe
- Open Community Survey:
  - PM: Kalyani
  - Agile Coach: Bonnie Wolfe

Task Items

[x] Discuss fixing the data pipeline with Matt and curtailing the dates with the available data
[x] Ask if Matt and Yen can join the next PM/Org meeting
[x] Create an Onboarding/Offboarding issue for all members (can copy and edit the PM issue)
- [ ] Can gather feedback from the team regarding everything needed for new members
[x] Offboarding and Team Members Cleanup issue https://github.com/hackforla/lucky-parking/issues/358
[x] Ask Matt about whether or not it's a problem to change the size labels (change to complexity)
[x] Ask if team leads are available for a one-time weekend cleanup for 2-3 hours with Bonnie
[x] Add bonnie@hackforla.org to the weekly meeting
[x] Make a new issue for tracking issues https://github.com/hackforla/internship/issues/128
- [ ] Need a Google Drive migrate issue template from product (ask Bonnie about this next week)

ExperimentsInHonesty commented 2 years ago

SDG for lucky parking 11 Sustainable Cities and Communities

Target: 11.2 By 2030, provide access to safe, affordable, accessible and sustainable transport systems for all, improving road safety, notably by expanding public transport, with special attention to the needs of those in vulnerable situations, women, children, persons with disabilities and older persons
Indicator: 11.2.1 Proportion of population that has convenient access to public transport, by sex, age and persons with disabilities.

MichelleRT commented 2 years ago

[2022-03-17] Meeting Agenda

(Thursdays at 7:30 AM)

Prework to prep for meeting

[x] Review notes and task items from the last PM/Org meeting

Recurring items: Happens on the ____ meeting

[ ] review any issues that are in the new issue approval column
[ ] Accountability and Support Check.
- [ ] Review assignments for each Team member
  - [ ] Michelle Tse
  - [ ] Tiffany Lin
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard
  - [ ] #

New Items

[x] Go over the labels (e.g., complexity).
[x] What is the workflow on weekly team meeting notes?
[x] Domain transfer from Simon
[x] Social media accounts and who owns/manages them
[x] Dates for a 2-3 weekend meeting
[x] Was the lucky parking email password updated?
[x] How should issues not assigned to an individual be handled?
[ ] Make issues from Agenda Task items (never closes) issue
[x] Need a Google Drive migrate issue template from product
[x] Let's discuss you adding this CTA to your team agenda
[x] Carry over Items to next meeting that don't get addressed

FYIs

-

Notes from Meeting

Task Items

[x] Confirm Matt can attend the Sunday 3 pm meeting with Bonnie to go over complexity labels
[x] Confirm size labels (e.g., 1pt) follow the PM wiki labels guide
[x] Create a team meeting agenda issue
[x] Ask Simon for the domain transfer code
[ ] Register @LuckyParkingLA on FB/Instagram/Youtube as an org page
[x] Once the website is up, ask Twitter to release @LuckyParking to us
[x] Make a poll to see if team leads/members are available on Saturday, 4/9 from 12 pm - 2pm PST for a meeting/hackathon with Bonnie
[ ] LP: drive migration invite these people to the next PM/Org meeting
[ ] Review the ice box issues to see if they should be moved to another column such as new issue approval
[ ] Show slide during the Monday team meeting https://docs.google.com/presentation/d/1UDHwTQ1C3y01CiNS0mvPjNBHJFlm2Txs/preview?slide=id.gf3a838ce5f_2_0

tmlin1 commented 2 years ago

Notes from Meeting

Gain Matt's permission to change size labels to complexity labels and see if there will be any automation to break.
Team meeting agenda should be a separate issue
Notes from meetings should be taken on the agenda issue itself
Ask Simon to issue a transfer code and give this to Bonnie
Have a marketing team now that is a CoP and they're working on branding
Checked social media platforms and @LuckyParkingLA is likely available; If we can get @LuckyParking across the platforms (except FB) then that would be a better
Register @LuckyParkingLA on FB/Instagram/Youtube as an org page
Once the website is up, ask Twitter to release @LuckyParking to us
2-3 hour meeting: Saturday, 4/9 between 12-2pm
New Folder: Google Drive Migration - make a new tab for each owner and fill out the sheet with the path

MichelleRT commented 2 years ago

The lucky parking email has been updated in 1password
Only PMs should be moving issues to the ice box; issues created by non-PMs should be placed in new issue approval unless there is a dependency on the issue (which must be completed)
Our end user is a community activist
Show slide during the next team meeting: https://docs.google.com/presentation/d/1UDHwTQ1C3y01CiNS0mvPjNBHJFlm2Txs/preview?slide=id.gf3a838ce5f_2_0

ExperimentsInHonesty commented 2 years ago

@MichelleRT @tmlin1 I have finished documenting all the people that need to move their files. Please invite all those people to our next meeting. Let them know that it will take between 1-5 min for them to move their files with our help. If they cannot do it at the time we normally meet, we will find another time for them, but we would like to take care of all the people that can do that time first. LP: drive migration - their email addresses are on each page.

Providence-o commented 2 years ago

Please add to your next agenda

Discuss with Bonnie you adding this CTA to your team agenda

MichelleRT commented 2 years ago

We received the auth code for luckyparking.org from Simon.

tmlin1 commented 2 years ago

[2022-03-24] Meeting Agenda

(Thursdays at 7:30 AM)

Prework to prep for meeting

[x] Review New Issue Approval Column in preparation for talking to Bonnie
[x] Create Social Media Accounts (FB, Instagram, Youtube, Twitter)
[x] Review Icebox issues and move to New Issue Approval
[x] Check for updates for issues

Recurring items: Happens on the ____ meeting

[ ] review any issues that are in the new issue approval column
[ ] Accountability and Support Check.
- [ ] Review assignments for each Team member
  - [ ] Michelle Tse
  - [ ] Tiffany Lin
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard
  - [ ] #

New Items

[ ] Simon's authorization code
[ ] Validate if Michelle and Tiffany will receive Github admin access
[ ] Check with Bonnie for Lucky Parking email access for Tiffany
[ ] Finalize agenda for 4/9 "Hackathon"
[ ] #369
[ ] Google Drive Migration - Greg recently reached out a few months ago.
[ ] Adding Size Labels process

FYIs

[ ] Submitted screenshot for Hack for LA Homepage Image

Notes from Meeting

Task Items

Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369
[ ] Move Lucky Parking roster from Excel to Google document
[ ] LP GDrive migration

MichelleRT commented 2 years ago

Hack for LA social media accounts spreadsheet: https://docs.google.com/spreadsheets/d/1ifv3PXk1XgfGQXOsoiq0QrxVVN0u4euiZ5usFys1QBY/edit#gid=341142762

MichelleRT commented 2 years ago

Facebook: https://www.facebook.com/Lucky-Parking-103903238940083 Instagram: https://www.instagram.com/luckyparking/ YouTube: https://www.youtube.com/channel/UCpck0nMZnSSHGr8nHam7iDA Twitter info on inactive usernames: https://help.twitter.com/en/forms/help/inactive-username

MichelleRT commented 2 years ago

We will need Simon to follow the steps here (we might need him to unlock the domain for transfer; ask if he can join the next meeting) https://support.google.com/domains/answer/3251236?hl=en&ref_topic=9003137
On Github, Michelle and Tiffany are listed as maintainers (can add others to the lucky parking repo) https://github.com/orgs/hackforla/teams/lucky-parking-managers/members
Members who got kicked out because of 2FA need to either go to a PM/org meeting or 45 minutes into an onboarding (next one is 4/12)
Tiffany was able to login to the lucky parking email
Members should not be removing themselves from the lucky parking team roster
Everyone needs to add their LinkedIn on the lucky parking team roster https://docs.google.com/spreadsheets/d/1OGhwJFgaNhgLfHF19E1e3JuF4wnbtfSo/edit#gid=1607893055
Under Dashboard, everyone should be member except for PMs who should be leader (under the lucky parking team roster)
Backfill the info for members on the lucky parking team roster (e.g., role(s), email)
Lucky parking team roster Excel document should be turned into a Google document
2022/04/09 from 12 - 2 PM "hackathon" meeting (sent Bonnie a zoom invite) and will need to spend time making an agenda during the PM/org meeting; by the 31st, we hope to have a complete agenda
We will spend 10 mins each PM/org meeting to go over our LinkedIns/resumes
FYIs should be used to notify what has been completed
Make issues from Agenda Task Items (never closes) # 369 is used to quickly make an issue during a meeting and should be included on all meeting agenda issues under Task Items (should be on the template)
Under "Issues to make" if we create a new item, we can convert the item into an issue
Make an issue for everything we need to do such as moving the lucky parking roster from Excel to Google documents (unless it's a very quick action item)
Make sure links/resources (issue link) are always linked to items on the agenda
LP: drive migration, need to add names and emails to the "People to invite" spreadsheet tab and invite them individually to the next PM/org meeting (Bonnie could show us how to properly move files as well)
Should pin team meeting agenda
Removed "complexity" from good first issue label
The person who creates the issue should determine the labels, otherwise, consult the subject matter expert lead
Bonnie will take be gone 21st - 27th of each month

MichelleRT commented 2 years ago

2022-03-31 Meeting Agenda

(Thursdays at 7:30 AM)

Prework to prep for meeting

[ ] Review New Issue Approval Column in preparation for talking to Bonnie

Recurring items: Happens on the ____ meeting

[ ] review any issues that are in the new issue approval column
[ ] Accountability and Support Check.
- [ ] Review assignments for each Team member
  - [ ] Michelle Tse
  - [ ] Tiffany Lin
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard
  - [ ] #

New Items

[x] Transfer domain to org from Simon https://support.google.com/domains/answer/3251236?hl=en&ref_topic=9003137
[x] Create an agenda for the 2022-04-09 "hackathon" https://github.com/hackforla/lucky-parking/issues/376
[ ] Excel to Google spreadsheet migration for Lucky Parking roster https://github.com/hackforla/lucky-parking/issues/380 https://docs.google.com/spreadsheets/d/1OGhwJFgaNhgLfHF19E1e3JuF4wnbtfSo/edit#gid=1607893055
[ ] See if we need to update the team page on the main Hack for LA website https://www.hackforla.org/projects/lucky-parking
[ ] Tiffany and Michelle LinkedIn/Resume review https://www.linkedin.com/in/michellerosetse/; https://www.linkedin.com/in/tiffanymlin/
[ ] Carry over Items to next meeting that don't get addressed

FYIs

The date part of the page is not fixed yet but the address part is fixed - Matt will try to fix the date this week.
http://www.luckyparking.org/ is the correct website

Notes from Meeting

Task Items

Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

MichelleRT commented 2 years ago

Simon was able to transfer the domain to Bonnie
UX leads need to coordinate with the other citizen engagement project UX leads since we have the same target audience (slack channel #citizen-engagement) to avoid repeat interview questions; we want to keep good relations with the neighborhood council
We need to determine how and who is interviewing the council
No specific person is currently in charge of the citizen-engagement UX lead coordination effort
We need to define which questions are specific to Lucky Parking
Distribution strategy: we could have our website embedded (with an iframe) in another website such as the Food Oasis project in foodcyclela.org/find-food/
Another placement opportunity/example: https://empowerla.org/data/
(Convey to Matt) Bonnie spoke to John Darragh from Food Oasis and others around shape files (provide info on geographic boundaries of a zip code); shape files for all the districts are needed for visual representation (Matt should speak to John about shape files and do the same thing for Lucky Parking)
We need to get all the issues properly labeled (can reference the hack for la PM wiki weekly label check) before the next meeting
Filter issues by a specific label (such as by all complexity labels) and copy and paste the URL if needed, then label ones with a missing label
Eventually we want no issues with the missing label
Weekly Label Check #382 issue action items role, size, feature, etc., needs to be updated with the proper link
Complexity label descriptions need to be updated
Milestones should be prioritized
We will set milestones in the next PM/Org meeting and talk about them in the 2022-04-09 workathon
We will combine the project boards into one and Bonnie will demonstrate how to properly use it
We will primarily make the feature labels together as a team during the workathon

MichelleRT commented 2 years ago

There will be mandatory PM events to learn specific practices (the first one will be on onboarding/offboarding)

ExperimentsInHonesty commented 2 years ago

open a issue on the hfla website team to update project data for LP

MichelleRT commented 2 years ago

2022-04-07 Meeting Agenda

(Thursdays at 7:30 AM)

Prework to prep for meeting

[ ] Review New Issue Approval Column in preparation for talking to Bonnie

Recurring items: Happens on the ____ meeting

[ ] review any issues that are in the new issue approval column
[ ] Accountability and Support Check.
- [ ] Review assignments for each Team member
  - [ ] Michelle Tse
  - [ ] Tiffany Lin
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard
  - [ ] #

New Items

[ ] See if we can go over an example for the Google Drive migration https://docs.google.com/spreadsheets/d/16k0T-eXzlHvM_g1drE_mZvyOI_j7YEyxXi8uIs63FsI/edit#gid=237835511
[ ] Carry over Items to next meeting that don't get addressed

FYIs

-

Notes from Meeting

Task Items

Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

ExperimentsInHonesty commented 2 years ago

@MichelleRT @tmlin1 Please review the messaging you are sending out re drive migration. It's not clear enough what you are asking for and is leading to people entering into an email dialog with us, which is a total waste of time (takes longer to answer their emails than it does to move the files) and in the case of Nathan, caused him to send us Word documents (exactly the opposite of what we are asking for).

Here is the message I used when asking people to help in the past

Hi ____

We are currently migrating all the files from an old Google Drive to a new UI/UX Google Drive. We are doing this so the Hack for LA Google account can take ownership of all the files. This will help us as we move forward in a volunteer capacity so as not to lose important data.

I'm reaching out to ask you, an owner of a file in the old drive, to migrate your files to the new drive. Let us know if you can join us for a few min to have us help you do it.

March 11th 12:pm PST on Friday [Zoom] (INSERTurl here)

Let us know if you might be able to join us, and I'll add you to the calendar invite.

Best

Bonnie

gregpawin commented 2 years ago

Hi Bonnie,

I've already tried reaching out to all of these parties and they have not replied. I've looked at these files and pretty much all of them are simply trial analyses as a part of exploratory data analysis. They are not linked anywhere else and simply exist in our Google Drive for historical reasons for people to see what has been done in the past. I don't think we should pursue this any longer because most of the original file owners will not reply.

Greg

On Thu, Mar 31, 2022 at 2:49 PM Bonnie Wolfe @.***> wrote:

What the heck?! Please review the messaging you are sending out re drive migration. Its not clear enough what we want. We just need them to show up for 5 min or less to help us to move their files. Its taking longer to respond that it is going to take to help them move the files. Please stress, that the process only takes a few min in person, and longer to explain via email.

Here is the message I used when asking people to help in the past

Hi ____

We are currently migrating all the files from an old Google Drive to a new UI/UX Google Drive. We are doing this so the Hack for LA Google account can take ownership of all the files. This will help us as we move forward in a volunteer capacity so as not to lose important data.

I'm reaching out to ask you, an owner of a file in the old drive, to migrate your files to the new drive. Let us know if you can join us for a few min to have us help you do it.

March 11th 12:pm PST on Friday [Zoom] (INSERTurl here)

Let us know if you might be able to join us, and I'll add you to the calendar invite.

Best

Bonnie

— Reply to this email directly, view it on GitHub https://github.com/hackforla/lucky-parking/issues/354#issuecomment-1085158337, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIUYPNLXW5D4PK2MBJAHU3DVCYMVDANCNFSM5P26ZHBA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

ExperimentsInHonesty commented 2 years ago

Let's discuss this at next meeting https://github.com/hackforla/lucky-parking/issues/303

gordonruby commented 2 years ago

April 19, 2022 Meeting Agenda

Prework to prep for meeting

[ ] Review New Issue Approval Column in preparation for talking to Bonnie

Recurring items: Happens on the ____ meeting

[ ] review any issues that are in the new issue approval column
[x] Accountability and Support Check.
- [ ] Review assignments for each Team member
  - [ ] Gordon Ruby
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [x] Review to see if there are any members to Onboard or Offboard
  - [ ] #

New Items

[ ]
[ ] Carry over Items to next meeting that don't get addressed

FYIs

-

Notes from Meeting

Next all team meeting,
- have a label bash (we all assign our own labels to our issues)
- ask the team which issues they haven't started on yet (on those, they can un-assign themselves and put the back in the prioritized backlog)
- ask the team to add all relevant context to the remaining issues
- have every team member unassign themselves from everything other than the one that is the most important
- Greg, can you help me figure out who’s all active on the team?
Go over the roster with Greg to update active / inactives
Determine who is communicating with stakeholders and how are they doing it:
- Figure out if Greg wants mail forwarding
- Figure out who Zach and Yen are and if they need to be in mail forwarding
- Decide if we need a UX email as a second email

Task Items

Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

gordonruby commented 2 years ago

[Date ] Meeting Agenda

Prework to prep for meeting

[ ] Review New Issue Approval Column in preparation for talking to Bonnie

Recurring items: Happens on the ____ meeting

[ ] review any issues that are in the new issue approval column
[ ] Accountability and Support Check.
- [ ] Review assignments for each Team member
  - [ ] Gordon Ruby
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard
  - [ ] #

New Items

[ ] Q: For the PM roles at Hack4La and for Lucky Parking, what do you see as the balance between project management effort VS product management effort?

The End user

[ ] What problem does Lucky Parking solve?
[ ] Who is this a problem for?
[ ] How did we decide on activists as our target user segment?
[ ] How big is this group?
[ ] How do we segment these pain points?
[ ] Without Lucky Parking, how does this group solve their problems now?
[ ] Q: Could we use 311 usage data to help Lucky Parking set a benchmark?
[ ] Q: Is there a chance we could do a broader survey across teams, such as Lucky Parking and 311?

The Roadmap

[ ] Q Is this aligned with where we think the product should go? https://whimsical.com/lucky-parking-roadmap-HWmnnES21uaUcxrt7kxWLv

The Project

[ ] Q: What is the goal of having everything on one project board?
[ ] Q: If we did create a new email for the UX team, can we establish how we would use it? Maybe people could send personal emails, but cc the UX@ email?
[ ] Q: Yen would like to stay on the Mail forwarding, especially if she might need to schedule anything with Bonnie.
[ ] Q: What are the value of Milestone on the project?
[ ] Q: What will the Sunday meeting be about?

The Team

[ ] Q: What else could we share with the team to bring more transparency and alignment to the project?
[ ] Carry over Items to next meeting that don't get addressed

FYIs

-

Notes from Meeting

Task Items

Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

ExperimentsInHonesty commented 2 years ago

Please add this to our next agenda. We need a project one sheet. See all the "overview" links on the hackforla.org website projects for reference. Also see https://github.com/hackforla/product-management/issues/74 . It looked like you had an issue that contained the requirement, but it was bound up in a lot of other stuff, no one worked on it and eventually was closed by Michelle, when she was trying to clean up. Which is why I don't want you to close issues without knowing why they exist.
https://github.com/hackforla/lucky-parking/issues/272

gordonruby commented 2 years ago

I need to remove team members from the write team only Github

gordonruby commented 2 years ago

May 6, 2022 Meeting Agenda

Prework to prep for meeting

[ ] Review New Issue Approval Column in preparation for talking to Bonnie

Recurring items: Happens on the ____ meeting

[ ] review any issues that are in the new issue approval column
[ ] Accountability and Support Check.
- [ ] Review assignments for each Team member
  - [ ] Gordon Ruby
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard
  - [ ] #

New Items

[ ]
[ ] Carry over Items to next meeting that don't get addressed

FYIs

-

Notes from Meeting

Task Items

Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

allthatyazz commented 2 years ago

@gordonruby I noticed that you have been using the zoom 3 account for your meeting. If you use one of HfLA's accounts, please update the spreadsheet so other teams would know which account is available.

gregpawin commented 2 years ago

Hi Yasaman,

We’ve been using Zoom 1.

Greg

On Thu, May 12, 2022 at 7:39 AM Yasaman Roostaeian @.***> wrote:

@gordonruby https://github.com/gordonruby I noticed that you have been using the zoom 3 account for your meeting. If you use one of HfLA's accounts, please update the spreadsheet https://docs.google.com/spreadsheets/d/15P3MYyNQ7Xn0pqdrTynDDipjrLl5LCN9xHVLhk9SWa8/edit?usp=sharing so other teams would know which account is available.

— Reply to this email directly, view it on GitHub https://github.com/hackforla/lucky-parking/issues/354#issuecomment-1125077871, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIUYPNL2ZNDQIG5KDTB54QDVJUJZXANCNFSM5P26ZHBA . You are receiving this because you commented.Message ID: @.***>

allthatyazz commented 2 years ago

Hi Greg! Zoom 3 account shows a recurring meeting for your team on Fridays. Please investigate the matter. Our team ran into trouble because of this. The screenshot is from Zoom 3. If you are not using a zoom account anymore, you have to delete that event from the schedule.

gordonruby commented 2 years ago

Hi Yasaman,

Thank you for flagging this issue. I've updated the sheet with the correct weekly meeting day and time for the LP: PM/Org Meeting.

Meanwhile, the LP Team does meeting weekly as well on Mondays at 6:00pm using Zoom1.

I hope this helps.

Please let me know if you have any questions.

On Thu, May 12, 2022 at 8:12 AM Yasaman Roostaeian @.***> wrote:

Hi Greg! Zoom 3 account shows a recurring meeting for your team on Fridays. Please investigate the matter. Our team ran into troubles because of this. [image: image] https://user-images.githubusercontent.com/100178353/168107947-77c596d3-b43f-438e-a208-475b66e660fa.png

— Reply to this email directly, view it on GitHub https://github.com/hackforla/lucky-parking/issues/354#issuecomment-1125116193, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK6SOI7Q6UN7YFOK33BHQY3VJUNU7ANCNFSM5P26ZHBA . You are receiving this because you were mentioned.Message ID: @.***>

-- Gordon Ruby (he/him/his) https://www.linkedin.com/in/gordonruby/ Schedule a Meeting with Me https://calendly.com/gordon-jd-ruby 604-353-1330

gordonruby commented 2 years ago

Tuesday, May 17, 2022 Meeting Agenda

Prework to prep for meeting

[ ] Review New Issue Approval Column in preparation for talking to Bonnie

Recurring items: Happens on the ____ meeting

[ ] review any issues that are in the new issue approval column
[ ] Accountability and Support Check.
- [ ] Review assignments for each Team member
  - [ ] Gordon Ruby
- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard
  - [ ] #

New Items

[x] Can all members who are not ACTIVE have their status changed in the Lucky Parking Drive?
[x] I removed anyone who wasn't on the ACTIVE roster from the Write section of LP. Do they need to be newly added to read section, or are they simply there by default?
[x] The team typically meets weekly and they tend to use the meeting to go into breakout rooms per team in order to touch base and align. How does that compare to the typical agenda we're expected to follow each week?
[x] Based on Slack, three new people have joined the team in the past week, but only one of them is committed to being on the team. The other two: Leslie Cintron (not responsive) and Yao Guan (who hasn't picked a team yet) are on the Slack channel, but I'm waiting to onboard them until I see more commitment and engagement from them.
[x] When onboarding know how to check for Public setting, but how do we check to see if they have 2FA?
[x] Do you recognize this product journey? Are we aiming to update something like this? Or just the one pager vision?
[x] The old PM Responsibilities file has a lot of blanks. Do we have something more detailed for other teams?
[ ] Can we go over a few of the instructions in this general onboarding doc? We could add more clarity
[x] Can Greg change his title from project/data lead to data lead?
[ ] Intro to Yaas on the Design team?
- [ ] Gordon to reach
[ ] Intro to website team to speak about a demo
[x] Intro to Volunteers from Hack for LA to UX Team
[x] Volunteers onboarding and Lucky Parking selection
[x] Capacity issues on Lucky Parking: Dev, Data, UX
- [x] Data has stalled without more people, according to Greg. Greg is the new lead, Marie has a new job)
- [x] Dev has lost their dedicated lead (Matthew)
- [x] UX could use one more person
[ ] Carry over Items to the next meeting that don't get addressed

FYIs

-

Notes from Meeting

[ ] Wait to remove people until we do the audit. For now, Bonnie has added me to the old drive. Gordon can also transfer any personal files to the Luck Parking Drive. See spreadsheet:TODO: Set up a Calendly to coordinate with People to Invite. (5 mins appts). Gordon to install mail merge on Lucky parking and figure how to use it.
[ ] Gordon to add everyone on the roster to Read.
[ ] Gordon to decide whether to meet with the leads each week or find another way to get alignment. 30 mins break out rooms THEN come together for 30 mins as a larger group. First question: does research or design have anything for the tech leads? If, no then ask the Dev team is they have anything for research and design? THEN let research and design go THEN more conversation with Dev and Product. Really, every team should meet twice. If people aren't meeting separately with the team lead in a separate meeting, then the team lead can't speak to the work the team is doing. As long as people talk to their lead during the week, it should be fine that they don't attend. Read the tickets but try to get more context from the leads.
[ ] Gordon to add new people to the weekly meeting calendar
[ ] Get shingles vaccine
[ ] Gordon to send the Product Journey in a google doc to Bonnie
[ ] Gordon to send the PM Responsibilities in a google doc to Bonnie
[ ] Gordon to ask the team to properly document the research being done. As a PM, I need to list what we've done, with links to roadmaps, milestones and other PM deliverables on a PM deliverables homepage.
[ ] Gordon to HOLD on any demos with the Website team. Follow up with Bonnie on this one.
[ ] Bonnie needs a research plan in order for LP to get volunteers from Hack for LA. Show this to Y
[ ] en: https://github.com/hackforla/internship/wiki/Research-Plan-1:-IS21-Interns
[ ] Greg to update a more generic description of the volunteer opportunity. It has to be exciting! Technologies, etc.
[ ] Gordon to add an open issue for every open role so that we can move it back and forth between the icebox and the Open Role job board. Example
[ ] Gordon to post more roles in open roles
[ ] Size = 1pt = 1 week = 6 hours of work
[ ] Need 8 weeks of work per person in the prioritized backlog across all resources (teams). 1pt is one week, per person on the team.
[ ] Issues with 13pts is way to big. That's 13 weeks of work with no visibility. Ask Marie and David about breaking this issue into smaller pieces and assigning each person to the issue. Need weekly updates and need the issues to be shorter, with no more than 5 pts max and ideally 1,2,3 points.
[ ] With people leaving, they need to do a download on the issue. This applies to Marie and Matthew.
[ ] Review the Pre-work checklist for Dev and find other ones
[ ] Figure out with Yen (and then Yuuwhether we need a Researcher based on Open UX-UI / Research UX-UI
[ ] Set up an interview with Heejung about open roles.

Task Items

Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

gordonruby commented 2 years ago

May 27, 2022 Meeting Agenda

New Items

[ ] Review the new One Pager
[ ] Q: What is the status of the district types project with John Darragh?
[ ] Review the roadmap Draft
[ ] Carry over Items to next meeting that don't get addressed

FYIs

-

Notes from Meeting

Task Items (to create as issues)

[x] Gordon needs to do a user test with the team of the low fidelity prototypes.
[x] Focus on the neighborhoods with transportation-related committee members
[x] Review Greg's Los Angeles Parking Research
[x] Reach out to the City of Los Angeles to understand the relationships between Community Impact Statements, City Council, NC Board members, Commissions and Committees
[x] Gordon to ask Access the Data team for Personas for NC board members, etc.
[x] Bonnie's availability to change to weekly office hours on Friday
[x] PM Weekly will be on Friday at noon PST, starting next week.
[ ]
Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

gordonruby commented 2 years ago

June 2, 2022 Meeting Agenda

Prework to prep for meeting

[ ] Review New Issue Approval Column in preparation for talking to Bonnie

New Items

[x] Received persona in from access the data, but they are in the process of redefining their personas
[x] Called LA City Council 311 Waiting for Feedback
[x] We have an old research plan that I'm trying to validate.
[x] Greg shared a competitor analysis document to add to the product strategy
[x] We have personas from August 2021 that might be out of date
[x] Goal is to share the current Product Strategy and ask the team to help fill in the blanks
[ ] Carry over Items to next meeting that don't get addressed

FYIs

Notes from Meeting

Task Items

Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

gregpawin commented 2 years ago

June 27, 2022 Meeting Agenda

Prework to prep for meeting

New Items

[ ] Gordon has stepped down and need to offboard him
[ ] UI/UX is preparing a report with responses from user interviews
[ ] New PM might join soon
[ ] Greg has prepared serialized dataset
[ ] Dietrich is working on adapting new dataset to frontend

FYIs

Notes from Meeting

Task Items

Add new issues to be created to https://github.com/hackforla/lucky-parking/issues/369

hackforla / lucky-parking