Outstanding Tasks

[Rabia2219]

Overview

We need this issue to have a place to put outstanding tasks

Action Items

• [ ]

Resources/Instructions

[ExperimentsInHonesty]

• I setup knowledgebase@hackforla.org, and added the 2fa to it, but not the recover codes. please do the rest of the setup

[ExperimentsInHonesty]

In TDM

• Create a new issue for Exchanging access between the two teams
  • see slide in 2025-09-30 release deck

  ### Overview
  We need to exchange information with Michelle so that we can get added to resources, and we can add them to our resources.
  
  ### Action Items
  - [x] Create spreadsheet
  - [x] Send spreadsheet
  - [ ] Add city team members to HfLA resources
     - [ ] Google Drive
     - [ ] 1Password
     - [ ] GitHub
  - [ ] Get added by Michelle to City Resources
     - [ ] Google Drive
     - [ ] GitHub
     - [ ] ?
  
  ### Resources/Instructions
  - [Resource Roster for Hand Over](https://docs.google.com/spreadsheets/d/1FPD0dFHTlPoTkZB16-sW9hE7B5nSV6ntpnWHm6uePXI/edit?gid=0#gid=0)
  

[ExperimentsInHonesty]

for TDM

• Make agendas for Monday, Wednesday and Thursday meetings for this week
• review the items in the Done-no PR required with the label "deck: staging" to see if they got added to a release deck, or they need to be added. If they have a slide in the staging deck, update the slide and put a comment on it. If they don't have a slide, add the link to the issue in this comment.
• Make sure all the issue in the technical review are properly updated in the slides, and if they need images added, that you put the ready for assignment on spreadsheet

[ExperimentsInHonesty]

for TDM - Bonnie to do

• update Update TDM's 2025 Timeline hackforla/tdm-calculator#2071
• annotate Wiki: Team Questions hackforla/tdm-calculator#2276

[Rabia2219]

• I setup knowledgebase@hackforla.org, and added the 2fa to it, but not the recover codes. please do the rest of the setup

@ExperimentsInHonesty
what vault are the credentials in?

[Rabia2219]

For Action Item "review the items in the P: TDM: project board (view) to see if they got added to a release deck, or they need to be added. If they have a slide in the staging deck, update the slide and put a comment on it. If they don't have a slide, add the link to the issue in this comment." Above

• http://github.com/hackforla/tdm-calculator/issues/2615

  • has the 'deck: staging' label
  • link to staging deck doesn't work
  • in the staging deck it is with the 'Not for Stakeholder' issues
  • in the spreadsheet it is marked 'not for stakeholder'
  • comment on issue says 'This has already been solved by pr 2586 truncate cells hackforla/tdm-calculator#2613 and should be closed'
  • 2613 is linked to issue 2586, which has been released and was in the 2025-09-02 Release deck

• in the Holding until Product Documentation Wiki is finished section of the staging deck

  • Update WIKI with technical details: Update Account hackforla/tdm-calculator#2504
  • Update WIKI with technical details: Create Project - page 1 hackforla/tdm-calculator#1863
  • Update WIKI with technical details: Create Project - Page 2  hackforla/tdm-calculator#2024
  • Update WIKI with technical details: Create Project - Page 3  hackforla/tdm-calculator#2025
  • Update WIKI with technical details: Create Project - page 4 hackforla/tdm-calculator#2027
  • Update WIKI with technical details: Create Project - Page 5 hackforla/tdm-calculator#2026
  • Update WIKI with technical details: Security Admin page hackforla/tdm-calculator#1865
  • Update WIKI with technical details: FAQ hackforla/tdm-calculator#1866
  • Update WIKI with technical details: Login hackforla/tdm-calculator#1861
  • Add Technical detail in Wiki under Product Documentation - About hackforla/tdm-calculator#1864
  • Update WIKI with technical details: Checklist hackforla/tdm-calculator#1870
  • Update WIKI with technical details: Feedback page hackforla/tdm-calculator#1867

• Product: Audit Inconsistent Wording of "Number" vs. "#" Across Pages hackforla/tdm-calculator#1886

  • in 2025-04-29 Release Deck
  • I updated the deck label to stakeholder presentation in the issue

• http://github.com/hackforla/tdm-calculator/issues/2356

  • in 2025-05-27 Release Deck
  • I updated the deck label to stakeholder presentation in the issue

• Redesign the Snapshot submission page from submitting to displaying submitted snapshots  hackforla/tdm-calculator#2004

  • in 2025-03-18 Release Deck
  • I updated the deck label to stakeholder presentation in the issue

• Research: Create Research Plan for Download Project to CSV File Usability Testing hackforla/tdm-calculator#1965

  • had both the deck: staging and deck: staging not for stakeholder labels
  • removed the deck: staging label
  • no link to slide in staging deck
  • in the staging deck it is with the 'Not for Stakeholder' issues
  • in the spreadsheet it is marked 'not for stakeholder'

• Create Glossary of Terms (Ubiquitous Language) hackforla/tdm-calculator#19

  • in 2025-05-13 Release Deck and 2025-05-27 Release Deck
  • I updated the deck label to stakeholder presentation in the issue

• Decide on Snapshot Submission Email Format & Details hackforla/tdm-calculator#2346

  • had both the deck: staging and deck: stakeholder presentation labels
  • removed the deck: staging label
  • in 2025-04-15 Release deck

• Content: Revise the "Try hovering over a term" text on Create Project page 1 hackforla/tdm-calculator#2425

  • had both the deck: staging and deck: stakeholder presentation labels
  • removed the deck: staging label
  • in 2025-04-29 Release deck

[ExperimentsInHonesty]

• create an issue, work on the issue

### Overview  
We need to create a spreadsheet to rationalize all FigJam files. This will allow us to track file names, associated teams, acronyms, and ownership status. The spreadsheet will help us ensure files are properly managed, attributed to the right team, and internally owned when possible.  

### Action Items  
- [ ] Create a spreadsheet to track FigJam files.  
- [ ] Add columns for:  
  - File name  
  - Associated team  
  - Team acronym  
  - Owner name  
  - Owner email address  
  - Ownership status (formula-driven TRUE/FALSE)  
- [ ] Implement formula for ownership column: returns TRUE if email ends in `@hackforla.org`, otherwise FALSE.  
- [ ] Populate spreadsheet with existing FigJam file data.  
- [ ] Review with team leads to confirm accuracy of associations and ownership.  

### Resources/Instructions  
- Formula for ownership column in Google Sheets:  
  ```
  =IF(REGEXMATCH(E2,"@hackforla\.org$"),TRUE,FALSE)
   ```

[Rabia2219]

• create an issue, work on the issue

### Overview  
We need to create a spreadsheet to rationalize all FigJam files. This will allow us to track file names, associated teams, acronyms, and ownership status. The spreadsheet will help us ensure files are properly managed, attributed to the right team, and internally owned when possible.  

### Action Items  
- [ ] Create a spreadsheet to track FigJam files.  
- [ ] Add columns for:  
  - File name  
  - Associated team  
  - Team acronym  
  - Owner name  
  - Owner email address  
  - Ownership status (formula-driven TRUE/FALSE)  
- [ ] Implement formula for ownership column: returns TRUE if email ends in `@hackforla.org`, otherwise FALSE.  
- [ ] Populate spreadsheet with existing FigJam file data.  
- [ ] Review with team leads to confirm accuracy of associations and ownership.  

### Resources/Instructions  
- Formula for ownership column in Google Sheets:  

=IF(REGEXMATCH(E2,"@hackforla.org$"),TRUE,FALSE)

New Issue

• HfLA: Rationalize all FigJam files hackforla/admin-governance#108

[Rabia2219]

Website Team

• look at the 10 am PST Sunday meeting for the Website team and figure out why anyone other than the merge team and the leads are invited
  • 9 and 10 am, 10 am is a registration meeting, and general members are supposed to register for it, not be on the calendar invite

[Rabia2219]

• create a new Figma account with internship+1@hackforla.org
  • was a success
  • verification email was sent to internship@hackforla.org
  • added new login to P: TWE (Legacy) with credentials

[Rabia2219]

For Bonnie to do before October 9th

• make a personal Figma account
  • move all personal Figma files to this account
• turn drafts into 100 page Figma files so that there is a place to grad new Figma files and add them to a team (there are 27)
  • move them into new account e.g. projects+1@hackforla.org

[Rabia2219]

Tables

• https://docs.google.com/spreadsheets/d/15ByO77F032kr5xBiX_xJw3BXz8Yd1A-gDUASyI9mAiw/edit?pli=1&gid=1276183169#gid=1276183169 add to CoPs
• note who was already added

[Rabia2219]

Tables team agenda

• need to talk about how this particular tab works
• what has been automated already

[Rabia2219]

For 311

• Step 1: Accept the invitation

1. Important: You must accept the invitation within a week or it expires.
2. On your computer, open Gmail.
3. Check your inbox for an invitation email with the subject line: "[Owner's name] has granted you access to their Gmail account."
4. Open the email.
5. Click the confirmation link.

---

• Send these to Ryan Chase by adding a new item that says Review Email Account for 311 About Page. Message him privately letting him know that we've added this to the 311 vault that will help with sharing. Please reach out to Bonnie through text when you have time and she will walk you through it.

• add as a note to 311-data vault
  Step 2: Open the delegated inbox

1. On your computer, sign in to your Gmail account.
2. At the top right, click your Profile picture .
3. In the menu, find the account that’s marked as "Delegated."
4. Click the delegated account's name.
5. A new tab opens that shows the owner’s inbox.
6. To confirm if you’re in the correct account, at the top, check the email address.

[Rabia2219]

• Update the labels and milestone Project Onboarding log hackforla/product-management#391