Skip to content

Guides: Meeting Agenda & Minutes #136

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

Open
1 task
edwardsarah opened this issue Sep 1, 2023 · 70 comments
Open
1 task

Guides: Meeting Agenda & Minutes #136

edwardsarah opened this issue Sep 1, 2023 · 70 comments
Assignees
Labels
feature: agenda role: Product size: 0.5pt Can be done in 2-3 hours or less

Comments

@edwardsarah
Copy link
Member

edwardsarah commented Sep 1, 2023

Quick link to bottom of page

Overview

Agendas and minutes for the Guides Team weekly meetings, Friday at 7:30AM Pacific Time.

Action Items

  • Copy the agenda template to a new comment below
# Date [format as YYYY-MM-DD]

### Prework
- [ ] Review any open questions and if answers are needed by person other than the one doing the review, add to agenda https://github.com/hackforla/guides/issues/149
- [ ] Daily: [look for issues that need pm lead review](https://github.com/hackforla/guides/issues?q=is%3Aopen+is%3Aissue+label%3A%22ready+for+pm+lead%22)
- [ ] https://github.com/hackforla/guides/issues/175

## Attendance

- [ ] Bonnie
- [ ] Rhoda
- [ ] Jesus
- [ ] France
- [ ] Aditya
- [ ] Kevin
- [ ] Emmanuel
- [ ] Akhila
- [ ] Yashwanth

### Recurring Items
Review work by each team member
   - [ ] [Bonnie](https://github.com/hackforla/guides/issues/assigned/ExperimentsInHonesty)
   - [ ] [Rhoda](https://github.com/hackforla/guides/issues/assigned/the-techgurl)
   - [ ] [Jesus](https://github.com/hackforla/knowledgebase-content/issues/assigned/jessethecleric)
   - [ ] [France](https://github.com/hackforla/guides/issues/assigned/fchan218)
   - [ ] [Aditya](https://github.com/hackforla/guides/issues/assigned/Aditya23Soni)
   - [ ] [Kevin](https://github.com/hackforla/knowledgebase-content/issues/assigned/knqti)
   - [ ] [Emmanuel](https://github.com/hackforla/guides/issues/assigned/3mmyrozay)
   - [ ] [Akhila](https://github.com/hackforla/guides/issues?q=is%3Aissue%20state%3Aopen%20assignee%3AAkhilaA12)
   - [ ] [Yashwanth](https://github.com/hackforla/guides/issues?q=is%3Aissue%20state%3Aopen%20assignee%3AyashhR)

## Agenda
- [ ] check to see if there are any issues with [drive: shared with me](https://github.com/hackforla/knowledgebase-content/labels/drive%3A%20shared%20with%20me) and [drive: shared drive](https://github.com/hackforla/knowledgebase-content/labels/drive%3A%20shared%20drive). This is a blocker to the body text being updated.
- [ ] Add anything we did not get to today, to next weeks agenda

## Meeting Minutes

## Items for next agenda

Past Agenda Issues

civictechindex/BOP#82
civictechindex/BOP#3

Previous Team Meetings

9/1/23
9/8/23
9/15/23

@edwardsarah edwardsarah added documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested labels Sep 1, 2023
@edwardsarah edwardsarah pinned this issue Sep 1, 2023
@edwardsarah
Copy link
Member Author

edwardsarah commented Sep 1, 2023

Friday September 1, 2023

Attendance

  • Bonnie
  • Sarah
  • Rhoda (late arrival)

Meeting Minutes

  • Bonnie talked to Ethan separately about a particular issue, would still be good to have him give a full status update

Transitioning Guides to New Repo

  • Why? Unified system of labels, all guides will live in one place that guides team monitors, no issues of people forgetting to add those guides to the project board

  • CoP Leads do not need to be consulted about shift to new repo, but should at least be notified

    • Only UI/UX and Product were making guides anyway
    • New iteration when Ethan is done: people suggest guides, it gets approved, goes into the database, we can get more information about status and everything once it's there
  • Aim: make the system as easy to facilitate as possible

  • Current documentation for guides is in CoP drives & folders

    • Will need to keep track of old issue numbers and titles so all of that stuff can be migrated without losing information
    • Rhoda's guide audit will help us achieve that because it has a list of issue numbers and CoPs already
  • How do we move the issues? How do we notify people

    • created the repo knowledgebase-content to serve as the new repo
    • all of the CoP-write teams have write access to the repo, so write permissions for that will just be handled through CoPs, that's fine
    • Notifying people: have a volunteer post on all open guide issues a survey that gives them the heads up we're moving things, then if they want to still continue working on it they will give us their info and we'll make sure they know where it's ended up
    • Survey: email address, github, guide issue name & number, community of practice
      • If nobody responds within a set period of time, just move it
      • second survey: if you want to be added to an issue once it's moved, we will give you the correct drive permissions
    • Need to make sure we don't break any links to things - keep a record of what the old issue numbers were! check CoPs for references to them
  • Bonnie made the new drive folder & set up an issue in Tables to make sure newly onboarded volunteers automatically get added to the drive

Issue Audit

Tutorials stay in Data Science because that's knowledge specific to their CoP, Revenue had no guide issues, has one github issue template but that's not what we're looking for
Rhoda will add the last marketing issue to the spreadsheet, we will go over the spreadsheet next week!

In the meantime, Sarah will put together a process for shifting issues & files to the new repo without losing information

@edwardsarah edwardsarah added feature: agenda and removed help wanted Extra attention is needed question Further information is requested labels Sep 8, 2023
@edwardsarah edwardsarah self-assigned this Sep 8, 2023
@edwardsarah edwardsarah added this to the 03. Project Management milestone Sep 8, 2023
@edwardsarah
Copy link
Member Author

edwardsarah commented Sep 15, 2023

Friday September 8, 2023

Attendance

  • Bonnie
  • Rhoda
  • Sarah

Guides Audit Spreadsheet

Reviewed and made progress labelling the guides from Engineering and Ops, still have more to look at in Product and UI/UX

Reminder on why we did the audit:

  • Audit was always going to become out of date very quickly, but it's useful to have a survey of all of the guides at this moment in time to understand what CoP we wanted to work with for the pilot project

On Guides Related to Professional Development

  • important that we aren't making guides on topics better addressed by resources outside of hack for LA - need to ask, what is unique about the way that we do it at Hack for LA, and what will someone get out of this guide that they could not get out of looking it up elsewhere
  • professional development guides can be tricky because they often go out of date very quickly, or they are too broad in scope. if a guide deals with professional development, it should be focused on using a specific tool
  • also focused on addressing the pain points (ex. finding a job) rather than what someone things the solution should be (ex. resume workshops), as often people don't know what the most helpful thing for them would actually be

Suggesting a Guide Workflow

  • Someone has an idea for a new guide
  • Reviews the list of previously suggested guides - one list for accepted guides, one list for rejected guides
  • If they don't see the guide they want, they use an issue template in the knowledge base content repo for suggesting the guide.
    • Issue template covers: what is the guide, why is it useful at hack for la
    • If they would like to suggest a guide that has been previously rejected, they need to give a new reason why this guide would be useful
  • Suggestion is then reviewed by the guides team, we ask questions if needed
  • Decision is made on prioritizing or rejecting the guide

New Guidance Pilot

  • Who are we testing it with?
    • Have to avoid scope creep - Bonnie would like to involve people from outside of Hack for LA, but it is probably best to limit it to about 10 volunteers for now and expand in future iterations
    • Need to have enough guide issues for each volunteer to work on one - will use the spreadsheet to identify which guide issues are best suited to this, then clean them up, add them to the new repo, make sure they're ready to go
    • Ideally, would be great to have 40 guides to work with, though this may not be feasible

Testing the Pilot

  • Rhoda will develop the research plan
  • Next Friday: importing the template from the internship project, starting to work on the roadmap
  • Key questions:
    • How can the system be improved? (Structure-wise, what issues and templates do we need for this to work?)
    • How do expectations need to be communicated to new PMs so they aren't disappointed?
    • What is missing from the setup?
    • What's not covered? (ex. what tools in github are they exposed to but not familiar enough with?)
    • What activities need to occur during training to keep it engaging and interactive?
    • How are we checking their work?
  • Overall goals: evaluate competency in tools before & after - can they create a guide, can they use github?

@edwardsarah
Copy link
Member Author

edwardsarah commented Sep 15, 2023

Friday, September 15, 2023

Attendance

  • Bonnie
  • Sarah E
  • Rhoda
  • Sarah L

Agenda

  • Intro to project for new PM + onboarding
  • Roadmap for research plan - new guidance pilot
  • Identifying guides for cleanup

Meeting Minutes

Onboarding Sarah L (Colby)

  • Sarah joined the team as a new PM. Will be our US-based PM, focused on the research pilot

New Guidance Pilot

  • Limiting the volunteers to just new PMs so that we can focus on creating a set of just PM guides to use for the pilot
  • Rhoda thinks 10 people is sufficient for the research plan, even with some dropout
  • Bonnie shared a slide deck with Rhoda about training researchers
    • Will not be recruiting until further down the line, but it's important for Rhoda to know about it up front
  • Reviewed PM guides on the New Guide Tracker to identify which ones will be useful to clean up & migrate for the pilot
  • Also reviewed Bonnie's list of wiki pages in the product management wiki that should be turned into guides
  • Knowledgebase-content google drive shared with the rest of the team members, so everyone should have access now

@luca-navarrete
Copy link

Add to the next agenda:

- [ ] Review with Bonnie 
  - [ ] Slack channels (active/dormant/archived)
  - [ ] Slack channel pins and bookmarks

@edwardsarah
Copy link
Member Author

edwardsarah commented Sep 22, 2023

Friday, September 22, 2023

Attendance

  • Bonnie
  • Sarah E
  • Sarah L
  • Rhoda

Agenda

  • Slack Channels + Pins & Bookmarks
  • Updating Active Project List
  • Updates on Work Done this Week
  • Research Plan
  • If time: structure for migrating issues over to new repo

Meeting Minutes

Slack Channels & Bookmarks

  • No problems with our slack channel! That's exciting
  • We are adding a reminder for ten minutes before our meeting (thanks Bonnie)

Active Project List

  • Actually already up-to-date. On hold labels were added to currently inactive projects.
  • Bonnie added a section for CoPs. Data science was already there, but the rest of the CoPs have now been added.

Updates on Work Done this Week

  • Rhoda looked at wiki pages, UI/UX google forms to get a sense on how to recruit while preserving privacy and expectations
  • Sarah L is not here so no updates on how she found going through the decks
  • Sarah E created the project board for the knowledgebase-content repo & added labels. we agreed today that we don't need the leadership review labels yet. the duplicate label will be replaced with a series of ignore labels from the website team. size labels will be added async

Access to the Knowledge Base Content Drive

  • made a new shared drive where the guides team is the owner, so if people request access then the guides team can review it and approve it. In previous drive, Bonnie was the owner, so any requests for access were likely to be lost among many other emails

Tasks for next week

Sarah is going to update the https://github.com/hackforla/guides/wiki/How-to-Gather-Examples to break it into seperate sections.

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Sep 22, 2023

Date 2023-09-29

Attendance

  • Bonnie
  • Sarah E
  • Sarah L
  • Rhoda

Agenda

Meeting Minutes

Want to pick issues that already have wiki pages for them so we can roll directly from gathering examples to making the guides. So we're checking the product management wiki pages against the list we made
Went through

Next week's agenda will be Bonnie walking Rhoda through what the pilot will cover.

  • Just Phase 1
  • What is it we're trying to get at with them?

@ExperimentsInHonesty
Copy link
Member

@edwardsarah
Copy link
Member Author

2023-10-6

Attendance

  • Bonnie
  • Sarah E
  • Sarah L
  • Rhoda

Agenda

  • [ ]
  • Add anything we did not get to today, to next weeks agenda

Meeting Minutes

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Oct 20, 2023

Date 2023-10-20

Attendance

  • Bonnie
  • Sarah E
  • Rhoda
  • Claire W

Agenda

  • [ ]
  • Add anything we did not get to today, to next weeks agenda

Meeting Minutes

Items for next agenda

- Check on issues to see if they got resolved
   - [ ] https://github.com/hackforla/website/issues/5743
   - [ ] https://github.com/hackforla/VRMS/issues/1530
   - [ ] https://github.com/hackforla/VRMS/issues/1531
- [ ] agenda just for product (there may already be one that is closed and needs to be reopened or create new).
 - [ ] Add current and former members to the wiki (create page if necessary), from [roster](https://docs.google.com/spreadsheets/d/1iUZOgQwXI-6Ljh3_00_tOxFoyjjurUGnJ5lenAl1AGg/edit#gid=2133647372)
 - [ ] Create research issue templates from internship project https://github.com/hackforla/internship/wiki/UX-Research-Guides-Templates

@jianwangcat
Copy link
Member

2023-10-23

Attendance

  • Bonnie
  • Sarah E
  • Claire W
  • Rhoda

Agenda

Meeting Minutes

Items for next agenda

@jianwangcat
Copy link
Member

jianwangcat commented Oct 30, 2023

Date 2023-10-30

Attendance

  • Bonnie
  • Sarah E
  • Claire W
  • Rhoda

Agenda

Meeting Minutes

Items for next agenda

@jianwangcat
Copy link
Member

2023-11-03 Meeting Agenda

  • 7:30 am PST Friday / 4:30 pm WAT Day of Meeting:

Prework to prep for meeting

Recurring items: Happens on every meeting

New Items

FYIs

Notes from Meeting

Task Items

@jianwangcat jianwangcat changed the title Guides Team: Friday All-Team Meeting Minutes Guides: Meeting Agenda & Minutes Oct 31, 2023
@jianwangcat jianwangcat added role: missing size: missing and removed documentation Improvements or additions to documentation labels Oct 31, 2023
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Sep 27, 2024

Date 2024-10-04

Prework

Attendance

  • Bonnie
  • Sarah E
  • Rhoda
  • Jesus
  • France
  • Aditya

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

  • France & Bonnie met to discuss France taking over as lead until her absence in November

  • Updated Jesus + Aditya's issues, so they will go to France for approval

  • Aditya has submitted issues for approval

  • France was saying they have to sort out

    • Bonnie + Sarah suggest both/and, keep as much communication as possible in the GitHub so that any progress is documented, slack is ephemeral
  • Keep communication in the Slack channel as much as possible

  • Reviewing team questions - Bonnie created a new saved reply for updates on issues

    • Aditya and Jesus will update their issues
  • create a new issue for creating issues for wiki pages that don’t have guide issues

  • Jesus’ issue is going to take several weeks to get up to snuff

  • Reviewing issues Aditya prepped for migration from Ops

    • the point is to be diligent and careful, not to go very quickly!
    • action items from Bonnie recorded in the issue
  • Still need to fix the milestones on the CoPs. they will not need all of the milestones listed above, but will need just the main one guide 5 milestone. kb-c content will have the milestones labeled by number, but the rest are unneceesary

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Oct 6, 2024

Date 2024-10-11

Prework

Attendance

  • Bonnie
  • Sarah E
  • Rhoda
  • Jesus
  • France
  • Aditya

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Oct 14, 2024

Date 2024-10-18

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

minutes:

  • Updated milestones in kb content and bonnie will go through and update the milestones as she triages
  • Individual COPs need label “feature: guide creation” to create new guides
  • FC: Need to make an issue to create a template for each Identify and Create Issues for future DevOps Guides ops#132
  • All guides in Ops have been moved
  • Post triage, we need to add the relevant issues to their project board so team members in that repo can work on creating guides as well
  • Aditya will work on migrating revenue and admin repos
  • If admin issues have prerequisites then it is okay to move
  • Leave all 1password guides in admin repo alone - do not move
  • Need to rename all other guides in the repo “Create a workflow guide” - these guides Bonnie will need to be interviewed for
  • Jesus will work on migrating marketing repo
  • Will leave data science repo for later - moved to ice box

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Oct 18, 2024

Date 2024-10-25

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

  • Need to make sure labels are correct to make triage easier
  • will no longer be using 'link status: inaccessible document' label - this has been replaced with new labels "drive:"
  • If a document is unable to move, then you know it is ‘shared with me’
  • New labels to use for documents that can or cannot be moved when transferring:
    • Drive: shared drive - when files are in knowledgebase content repo but not all
    • Drive: shared with me - when files are unable to be moved
    • Drive: knowledgebase - when all files are moved into knowledgebase content repo

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Oct 26, 2024

Date 2024-11-01

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Nov 1, 2024

Date 2024-11-08

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Dec 9, 2024

Date 2025-01-03

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

  • Jesus will be responsible for transferring UI/UX issues to knowledgebase content repo after steps 1-5 are complete
  • Jesus has approx 7-8 issues left to transfer
  • Kevin needs access to links for phase 1 of triaging his issue
  • Suggestion to write out template onto a wiki page so all information is located in one location/web page
    • may not be priority right now, but can be something done in the future
  • Aditya needs to review all issues in Ops, Admin, Revenue to ensure proper labels/project board assignments

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Jan 8, 2025

Date 2025-01-10

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Jan 10, 2025

Date 2025-01-17

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Jan 24, 2025

Date 2025-01-24

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Jan 28, 2025

Date 2025-01-31

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

  • Bonnie will make/review glossary so that Kevin can continue working on his issue
  • update migration guidance on:
    • removing label "drive: shared with me" or "drive: shared drive" once documents are transferred after access to CoP's drive is given
    • add comment to new issue linking which issues need Bonnie's attention regarding document transfer
  • created new issue: Cleanup knowledgebase content drive assignee board #193

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Jan 31, 2025

Date 2025-02-07

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Feb 7, 2025

Date 2025-02-14

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

  • Bonnie provided rough template for Kevin to work on creating guide for glossary
  • Jesus will be double checking Aditya's work Steps 1-14 and checking comment clean up for Ops
  • Aditya will clean up comments for Revenue, Admin, Marketing, UI/UX, and Product.
  • Jesus will double checking Aditya's work for Revenue, Admin, Marketing, UI/UX, and Product
  • Jesus will be leaving PM team and start working on a guide

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Feb 14, 2025

Date 2025-02-28

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Feb 28, 2025

Date 2025-03-07

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin
  • Emmanuel

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Mar 7, 2025

Date 2025-03-14

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin
  • Emmanuel

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Mar 20, 2025

Date 2025-03-21

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin
  • Emmanuel

Recurring Items

Review work by each team member

Agenda

  • interview 2 people
  • Add anything we did not get to today, to next weeks agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Mar 28, 2025

Date 2025-03-28

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin
  • Emmanuel
  • Akhila
  • Yashwanth

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

fchan218 commented Apr 4, 2025

Date 2025-04-04

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin
  • Emmanuel
  • Akhila
  • Yashwanth

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@fchan218
Copy link
Member

Date 2025-04-11

Prework

Attendance

  • Bonnie
  • Rhoda
  • Jesus
  • France
  • Aditya
  • Kevin
  • Emmanuel
  • Akhila
  • Yashwanth

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: agenda role: Product size: 0.5pt Can be done in 2-3 hours or less
Projects
Status: Weekly Tasks
Development

No branches or pull requests