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.

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

Guides: Meeting Agenda & Minutes #136

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

Guides: Meeting Agenda & Minutes #136

edwardsarah opened this issue Sep 1, 2023 · 41 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

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

## Attendance

- [ ] Bonnie
- [ ] Sarah E
- [ ] Rhoda
- [ ] Jesus

### Recurring Items
Review work by each team member
   - [ ] [Bonnie](https://github.com/hackforla/guides/issues/assigned/ExperimentsInHonesty)
   - [ ] [Sarah E](https://github.com/hackforla/guides/issues/assigned/edwardsarah)
   - [ ] [Rhoda](https://github.com/hackforla/guides/issues/assigned/the-techgurl)
   - [ ] [Jesus](https://github.com/hackforla/guides/issues/assigned/jessiethecleric)

## Agenda
- [ ] 
- [ ] 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
@edwardsarah
Copy link
Member Author

edwardsarah commented Jan 11, 2024

2023-01-11

Meeting cancelled due to PM absence.

@edwardsarah
Copy link
Member Author

edwardsarah commented Jan 19, 2024

2023-01-19

Attendance

  • Bonnie
  • Sarah E
  • Claire W
  • Rhoda
  • Ayma

Agenda

Meeting Minutes

  • took the template back to internship and told them to reintegrate it
  • so we should be more easily able to copy their work, do not need to redo that right now
    • Timeline for this?
  • Decided on the dark blue (far left), make one mock up and we'll try to print it
  • Try the dark blue as well, we'll try printing it with text in p
  • Need to look at the default research roadmap template

Ayma

  • Ayma is liaison to BOP team for Guides team

  • knowledge base team is building infrastructure to house guides of all types. they are creating back end for guides on the hack for LA toolkit page

  • BOP team has its own interface, Guides team will use the toolkit as its own interface

  • someone redoing toolkit page, knowledge base APis for that

  • Ayma + Bonnie need to make sure that the knowledge base has all of the right fields that we need to display the guides on the toolkit page

  • NEED AN ISSUE SIMILAR to this one: BOP: knowledgebase search: requirements civictechindex/BOP#274

  • Review Toolkit page today:

    • Knowledge Base requirements we're reviewing this document
  • New issue: Guides: Knowledgebase Search  #154

  • Putting a pin in this until Ayma comes back
    142 145, 147 all need document templates

  • Create another epic for taking the template and puts them on their own documents

  • mention in slack to bonnie when the document templates are done so she can try printing them and seeing what happens

  • sarah will make document templates (both blue versions, make sure footer is white text) and issues, then rhoda will make documents from the issues

  • test the first issue, do the steps, then revise the copy block before the rest of the issues are made

  • add correct labels to the issues we created today

Items for next agenda

@edwardsarah
Copy link
Member Author

edwardsarah commented Jan 26, 2024

2023-01-26

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda

Agenda

Meeting Minutes

  • Bonnie has a migraine, so will not make it!
  • Darker one seems better so we'll go with that
  • Sarah will need to adjust the logo

Items for next agenda

@ExperimentsInHonesty
Copy link
Member

@edwardsarah Not sure if everything from the last meeting got covered, or if you plan to reuse the agenda. So adding this new agenda item here: hackforla/knowledgebase#69

@edwardsarah
Copy link
Member Author

edwardsarah commented Feb 2, 2024

2023-02-02

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda

Agenda

Meeting Minutes

Document access has been fixed so Rhoda can finish updating the rest of the templates
How are we organizing the guides?

  • all guides will go in the guides folder
  • will additionally have folders by practice area with shortcuts to each of the guides
  • there is a note about this in the knowledgebase-content 'Read first'
  • Put Ethan through how to make a guide after Rhoda has developed the research roadmap
  • Set up a new issue for Rhoda to work on the roadmap Guides: Research Roadmap: Guide Creators #164

Items for next agenda

@aymarmsba
Copy link
Member

aymarmsba commented Feb 2, 2024

Date 2024-02-09

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda

Agenda

Use this image

image

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

Meeting Minutes

  • Roadmap vs Research Plan:
    • Roadmap is brainstorming document naming all of the research we're planning on doing with this group
    • Background should work for all research for the specific group, not focused on the individual research goals
    • Eventually, will need another roadmap for the external audience
    • Research plans are more about execution
    • Permanent document that we keep adding to to brainstorm about research we might do, then we can plan how we want to execute and decide many research plans we need
    • 30000ft research planning

Items for next agenda

@aymarmsba
Copy link
Member

aymarmsba commented Feb 16, 2024

2024-02-15

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda

Agenda

Meeting Minutes

  • epic issue for the internships team templates.
    • Bonnie reviewed the epic, the issues need to be revised so that people can work on them. Even though they are in the prioritized backlog, they are not actually ready to work on.
    • After Bonnie revises, send the following message
    @Ying O When do you think that the current work you and Annie are doing, will be finished, so that you can start on the issues in this epic? https://github.com/hackforla/internship/issues/530 and is there anything I can do to help, sort of fixing them myself (i.e., get another person, reprioritize Annie's work, etc.)
    
  • Reviewed and left Sarah comments Migrating Product Guides to New Repo #139 (comment). This issue is not yet ready for Ayma
  • Reviewed the draft for Guides: Research Roadmap: Guide Creators #164 and added comments for Rhoda.

Tasks

  • Go through all the guides documents and the repo looking for the product names and making sure they are properly capitalized (unless its in a url)
    • GitHub
    • Google Drive
    • Slack

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Feb 16, 2024

Date 2024-02-23

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda

Agenda

Meeting Minutes

  • Reviewing the issue for Ayma
    • Need to figure out the process for migrating guides - how do we make it feasible for Ayma to do?
    • Everything related to research is going to be trashed since internship team is
    • People need very specific guidance for making guides, otherwise content will be quite random
    • Need a working template for guide issues, we're looking at the one from
    • Google has a limit for 600 people in a google shared drive, so we can't just add everyone to the same drive, will need to assign and remove people
    • Website team automation for update on issues, we automatically put them on a list saying they'll be removed, 60 days later removed from repository - there's another part to this automation that isn't working yet, i believe
    • Relative links will break, so we still need to search for all references to it and note that so it can be changed to the new link
    • Removing some issue templates and
    • Label History & where it was on the board. So screenshot that and paste it in the bottom of the issue so we know
    • update wiki so that it doesn't say into the next comment
    • Update wiki with steps to all of the processes
    • Initial step: decide it we need to gather examples or not. if it doesn't, go straight to drafting a guide
    • Triage into right phase, additional triage as necessary, leave it in the needs to be triaged

Items for next agenda

@edwardsarah
Copy link
Member Author

edwardsarah commented Mar 1, 2024

Date 2023-03-01

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda
  • Mary

Agenda

Meeting Minutes

  • Mary is a new PM at Hack for LA joining the team! Will be focused on delivery of workshops for Guides team
  • Pick up the migration issue next week, do a walkthrough and see how much Ayma is able to do on her own
    • Make it pretty prescriptive
    • Have her walk through it and revise instructions from there
  • There's a limit of 600 people to work on a guide, so we need to maintain space
  • Everyone will be able to view the guides, but if they're going to work on it, they'll need to get access
  • Danger of us giving it out, it could get out into the wild and someone could get contributor access
  • We give them permissions using a form equivalent to the roster, so then it makes a roster for us
  • Do this in tables
  • We go in, click the checkbox,
  • CoP leads administer this?
  • No one can assign themselves an issue unless they're in Hack for LA's issue
    • They assign them to an issue, create an automation to add people to drive based on assignment
    • Create an automation to remove them from the drive based on unassignment
      • Create an issue to make automation for assignment/unassignment
      • Another issue with a dependency that does a one-time add and cleanup for people working on guides.
      • Bonnie will make a tables issue for stop adding them to a drive, a second issue for adding them to the knowledgebase-content repo after onboarding
      • Issue for push permission - tell tables to stop adding people to the drive, and instead add them to the knowledgebase-content repo
      • create branch protections on the repository to prevent write members from merging

Items for next agenda

@edwardsarah
Copy link
Member Author

edwardsarah commented Mar 8, 2024

2024-03-08

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda
  • Mary

Agenda

Meeting Minutes

Items for next agenda

  • Ayma tries guidance with a more complicated issue
  • Guide for Figma for Beginners

@edwardsarah
Copy link
Member Author

edwardsarah commented Mar 8, 2024

2024-03-15

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda
  • Mary

Agenda

Meeting Minutes

  • Reviewed criteria for labelling guides with Ayma, decided to put instructions into a document rather than a comment in a guide issue
  • Overview of basic PM tasks with Mary - how to do onboarding, making issues, the wiki, etc.
  • Submitted ER: Update Project Profile: Guides Team website#6466

Items for next agenda

@edwardsarah
Copy link
Member Author

edwardsarah commented Mar 22, 2024

2024-03-22

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda
  • Mary

Agenda

  • Check if Ayma still has problems adding issues to the project board
  • Add anything we did not get to today, to next weeks agenda

Meeting Minutes

  • Not much happening with knowledgebase-content
  • Ayma will work on migrating another guide to the knowledgebase-content
  • For 4/5: Define Mary's PM responsibilities with respect to the workshop and Rhoda's research - how involved should she be in the research process, versus delivery of the workshop
    • Mary is gone next week so we'll follow up the week after
  • Ask Bonnie if she still wants to have the meeting next week via slack
  • The document isn't opening for Rhoda, she wanted to confirm where we're at for the research roadmap, will continue working on putting down ideas for what to research and start with the first research plan
  • See if there's a team with a full research roadmap and plan for reference? fine if not

Items for next agenda

  • Review Rhoda's progress on the research roadmap and research plan

@edwardsarah
Copy link
Member Author

edwardsarah commented Mar 29, 2024

2024-03-29 (got canceled)

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda
  • Mary

Agenda

  • Review Rhoda's progress on the research roadmap and research plan
  • Add anything we did not get to today, to next weeks agenda

Meeting Minutes

Items for next agenda

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Apr 12, 2024

2024-04-05

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda
  • Mary

Agenda

  • guest - Julia, UI/UX Community of Practice co-lead
  • Add anything we did not get to today, to next weeks agenda

Meeting Minutes

Guest came to discuss their plans for having people work on guides. We reviewed where we are in the process and shared the training materials that are on the wiki. And talked about the workshop we will do.

Items for next agenda

  • Review Rhoda's progress on the research roadmap and research plan

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Apr 12, 2024

Date 2024-04-12

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda
  • Mary

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

  • Rhoda is pre-assigned to issues. Instead they should be in the prioritized backlog for research, and she can assign each one as she is finished with the prior issue
  • Reviewed Research Roadmap draft, next week we will look at it again.
  • Reviewed the PM templates and guides board (05) and moved some issues that were not guides, off of it.
  • Added Ayma to the product drive as a manager so she could move guides

Items for next agenda

  • Update on where Ayma is on the move
  • Review Research Roadmap draft
  • Get Mary assigned to an issue

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Apr 12, 2024

Date 2024-04-19

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda
  • Mary

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@edwardsarah
Copy link
Member Author

edwardsarah commented Apr 26, 2024

Date 2024-04-26

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Ayma
  • Rhoda

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@edwardsarah
Copy link
Member Author

edwardsarah commented May 3, 2024

Date 2024-05-03

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Rhoda

Recurring Items

Review work by each team member

Agenda

  • Reviewing RP2 and RP5 - does the split here make sense, is there anything we need to modify
  • Add anything we did not get to today, to next weeks agenda

Meeting Minutes

Reviewing the goals for each of the research plans:

  • RP 1 - How are guide creators managing the transition in organization for guides from COPs to knowledgebase?
  • RP 2 - Do the expectations new volunteers have coming into Hack for LA match the work they are doing?
  • RP 3 - What skills do new volunteers have coming into HfLA?
  • RP 4 - How are volunteers progressing through the workshops? Where are the blockers and what's causing dropouts?
  • RP 5 - Did volunteers complete the work they were supposed to between workshops?
  • RP 6 - Exit Survey: What have they learned from the workshops?
  • RP. 7 - Post Workshop Survey: Has what they learned been useful to their work at Hack for LA?

Created new survey for participants after each workshop, set up issue #167 for new surveys

  • Key action item is to identify points in the gather examples workshops where we want to evaluate their progress in a particular skill
    Will need to create a survey for whether or not they've finished the work between workshops as well

Items for next agenda

@edwardsarah
Copy link
Member Author

Date 2024-05-10

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Rhoda

Recurring Items

Review work by each team member

Agenda

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

Meeting Minutes

  • Ask Bonnie about access to research roadmaps on internship team slack + via text, so Rhoda can finish the research roadmap
  • Rhoda will come up with some alternative wording for questions to make sure volunteers aren't confused about the difference between 2.1 + 2.2
  • Sarah will look at the different topics in the workshop presentations to identify clear sections to evaluate confidence + competency in for the interim surveys

Items for next agenda

@edwardsarah
Copy link
Member Author

edwardsarah commented May 17, 2024

Date 2024-05-17

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Rhoda

Recurring Items

Review work by each team member

Agenda

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

Meeting Minutes

  • Meeting cancelled due to team absences

Items for next agenda

@edwardsarah
Copy link
Member Author

edwardsarah commented May 17, 2024

Date 2024-05-24

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Rhoda

Recurring Items

Review work by each team member

Agenda

  • Research Roadmap:
    • Can we get access to the internship team's documents? If not, how do we move forward?
  • Survey Points for Gather Examples Workshop Participants #167
    • Review suggested sections - does this cover everything?
    • Discuss if we want another survey for soft skills
    • Questions for additional form evaluating work done between sessions
  • Offboarding Ayma - removal from 1Password
    • Impact on the team? Do we have her responsibilities covered?
  • Add anything we did not get to today, to next weeks agenda

Meeting Minutes

  • Sarah will make an issue to remove old PMs from website
  • Remove her from resources
  • All past team members should be removed from write team but maintain access to read team, use roster to check this
  • Check email & figma to make sure everyone is correctly offboarded
  • internship team is working on issues that will be the foundation of our work, check here: TWE: template for revising issue templates [name of template] internship#530
  • when closed, we will customize them for the guides team, approx 1 issue per week
  • Rhoda unable to make the meeting time for June, we will re-evaluate after next week to see if we should shift the meeting time

Items for next agenda

@edwardsarah
Copy link
Member Author

edwardsarah commented May 31, 2024

Date 2024-05-31

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Rhoda

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Project Boards

  • Guides Board Migration #168
  • GitHub is sunsetting old project boards, so we need to review our project boards and figure out what we're doing with them
  • Cards are converted to draft issues, which cannot be edited only turned into issues
    • Content should be moved to the wiki before we migrate it
  • Copy all project board card text into a new issue, migrate the board, then figure out where everything goes
  • identify anything that will break/not work anymore
  • Column headers still exist on new project boards
    • headers cannot be too long before they make the column useless, as they're frozen at the top of the column
    • headers also cannot have any formatting in them
  • Wiki pages may be suitable for much of the project board card info

CoP Guides + Templates Boards

  • We will move the issues, but CoPs will have to manage putting their project board cards in their own wikis
  • Bonnie has migrated the old Guides Tracker Board
    • Guides Tracker Classic
    • Guides Tracker New
  • CoP Templates and Guides Board Migration #169
  • Use Guides Tracker Completeness to make sure all guides are on both boards
    • Don't forget to check closed issues!
  • For each repo, add the label of the COP (from kb-c) to each issue, so we can sort by that label
  • place it on their issues\make sure their issues are on all the right boards
  • Delete their old boards when done
  • We tested transferring an issue from the UI/UX repo, and it was fine
  • Deliverables: add labels to CoPs, use the wiki links to make sure the guide issues are on all three boards, create the next view
  • Get it done before Wednesday of next week
  • Bonnie will check with CoP leads on Wednesday what the leads want to do

Items for next agenda

  • Transfer Guides team board
  • Review transfer of CoP boards

@edwardsarah
Copy link
Member Author

edwardsarah commented Jun 11, 2024

Date 2024-06-11

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Rhoda
  • Jesus

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Items for next agenda

@edwardsarah
Copy link
Member Author

edwardsarah commented Jun 14, 2024

2024-14-06

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Rhoda
  • Jesus

Recurring Items

Review work by each team member

Agenda

  • Review progress on CoP Templates and Guides Board Migration #169 + more clear instructions
  • Discuss templates and guides for Data Science and Ops - what do we do with them?
  • Guides team board migration
  • Add anything we did not get to today, to next weeks agenda

Meeting Minutes

Whole meeting’s worth of time for the open roles, Bonnie is still working out the kinks for unifying them across the system

option 1:

  • create an issue with all of the titles as potentially new guides
  • (Sarah will do this)
    • checkbox list for each of these
      option 2:
  • migrate it to a new board to make draft issues, downside is all of these draft issues not triaged which then have to be turned into issues
  • do we think all of these things should be made into issues?
  • these are things that CoP leads (awhile ago) thought might be useful as guides
  • don’t really have time

Data Science and Engineering: they will make more wiki pages, not guides,

Create an epic for managing migration of the CoPs

  • individual boards for project board cards that go somewhere
    At some point, will need to figure out what guides need to be labeled with multiple communities of practice

Jesus has confirmed all of the project board card text has been copied

Guides team migration needs to follow the format listed here: https://github.com/hackforla/product-management/wiki/GitHub-Project-Board-Migration-Issue

Guide boards checked:

  • product
  • ui/ux
  • ops
  • data science
  • revenue
  • marketing
  • engineering
  • marketing
  • admin

All projects should have a link to the CoP or repo

look at all of the cards from all of the templates and guides boards, so we can decide what we want the headings to be

  • show up on every view for each status, so we need to figure out the generic thing we want to say
  • see what formatting we can use for the column headers

Items for next agenda

@edwardsarah
Copy link
Member Author

edwardsarah commented Jun 21, 2024

2024-06-21

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Rhoda
  • Jesus

Recurring Items

Review work by each team member

Agenda

Meeting Minutes

Notes from Sarah:

  • Top Priority: migrating the Guides Team Project Board
  • To Jesus: very sorry I wasn't able to update last week's meeting minutes or get action items in time for you to do much this week, I'll be better about this in the future!
  • Issue Guides Board Migration #168 has been updated so each project board card is a separate comment, and is ready for us to go through them and make decisions on where each should end up
  • The UI/UX guide suggestions have been added to issue Guide Suggestions: UI/UX #172, so the old UI/UX project board can be deleted. All of its project board cards have now been preserved either in this issue or in CoP Templates and Guides Board Migration #169
  • Converting CoP Templates and Guides Board Migration #169 into an epic that tracks the project board cards across the different COPs is a work in progress, if there are any updates before the meeting I will add them here

Items for next agenda

@edwardsarah
Copy link
Member Author

2024-06-28

Prework

  • Review any open questions and if answers are needed by person other than the one doing the review, add to agenda Team Questions #149

Attendance

  • Bonnie
  • Sarah E
  • Rhoda
  • Jesus

Recurring Items

Review work by each team member

Agenda

  • [ ]
  • Add anything we did not get to today, to next weeks 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

7 participants