Identify HfLA issues to move to CTS

[Rabia2219]

Overview

We need to identify issues in HfLA repositories that are better suited to be in CTS repositories so that they are in the proper place.

Action Items

• [x] Create a spreadsheet with the following schema
  • A; Original URL of issue
  • B: Name of Issue
  • C: Summary of issue (optional)
  • D: New URL once moved to the HfLA Transfer Repo
  • E: Receiving CTS repo
• [x] Hide D-E columns
• [x] Review each repository in the resources
• [x] Identify issues that need to be moved to CTS and annotate spreadsheet
• [x] review issues with org
• [x] Release the dependency on #6
• [x] Add link to spreadsheet to
  • [x] #6
  • [x] #8

Resources/Instructions

• CTS drive, Issue Cleanup
• HfLA: Issue transfer to CTS Spreadsheet

  Repos to look at

• https://github.com/hackforla/brigade-offboarding-process
• https://github.com/hackforla/admin
• https://github.com/hackforla/civic-opportunity
• https://github.com/hackforla/governance
• https://github.com/hackforla/brigade2point0

[Rabia2219]

Issues Identified as of 2023-09-29, 1:00 PM

• https://github.com/hackforla/brigade-offboarding-process/issues?q=is%3Aopen+is%3Aissue+label%3A%22move+to+CTS%22
• https://github.com/hackforla/admin/issues?q=is%3Aopen+is%3Aissue+label%3A%22move+to+CTS%22
• https://github.com/hackforla/civic-opportunity/issues?q=is%3Aopen+is%3Aissue+label%3A%22move+to+CTS%22 (none)
• https://github.com/hackforla/governance/issues?q=is%3Aopen+is%3Aissue+label%3A%22move+to+CTS%22 (none)
• https://github.com/hackforla/brigade2point0/issues?q=is%3Aissue+label%3A%22move+to+CTS%22+is%3Aclosed