Create a Summary of Guides Achievements for 2025

[yashhR]

Dependency

• 2025-11-01

Overview

We need to write brief summaries of project accomplishments for 2025, to go on the website's accomplishments page.

Action Items

• Review the accomplishments on resource 1.02 to see how they are worded, and note the following: Accomplishments on the Hack for LA website are:

  • readable even if you don't know anything about the project
  • short
  • clearly articulated achievements that funders would care about
  • list partners if available

• Review all completed issues from 2025

  • Go to the project repo issue tab (resource 1.05)
  • Filter by closed issues in 2025
  • Identify themes, achievements, and high-impact work from each issue
  • Copy links and summaries for reference

• Review the accomplishments draft document and cross-reference with issues

• Draft a brief bullet-point summary of what the project accomplished in 2025, following the style of previous years

• Add the new 2025 accomplishments section to the accomplishments issue draft

• Request feedback from PM or team lead, and update based on suggestions

• Update the epic issue (resource 1.01)

  • Add the following comment:

Resources/Instructions

• 1.01 Accomplishments epic: Create project and CoP Accomplishment Epics admin-accomplishments#3
• 1.02 Hackforla.org website, about page, accomplishments section: https://www.hackforla.org/about/#accomplishments
• 1.03 Guides Team Google Drive
• 1.04 One Sheets:
  • 1.04.01 One sheet from product-management repo
  • 1.04.02 One sheet link from Hack for LA website (Overview)
  • 1.04.03 Folder with One sheet drafts on Guides Team's Google Drive
• 1.05 Guides, Issues tab
• 1.06 Guides: Accomplishment Summary for HfLA Website 2020-2024 #192

[yashhR]

🏆 Draft SUMMARY of Accomplishments – 2025

[INSERT CONSOLIDATED DRAFT HERE]

🏆 Accomplishments ISSUES – 2025

• Established an identity access management (IAM) system for the Guides team by auditing and organizing GitHub and Drive permissions. This ensured only active contributors had access to sensitive documentation, mitigating the risk of data loss and improving governance.
  Related: #193

• Completed final migration efforts by centralizing remaining Admin and Marketing guides into the unified knowledgebase-content repository. Standardized issue naming conventions were applied for improved readability and consistency across the backlog.
  Related: #184, #182, #176

• Maintained knowledge tracking infrastructure by continuing work on the New Guides Tracker to ensure issues are clearly labeled, properly scoped, and visible across CoPs. This improved long-term coordination and content sustainability.

---

🔗 Reference Issues

• Cleanup knowledgebase content drive assignee board #193 – IAM Cleanup
• Migrating Admin Guides to New Repo #184 – Admin Guide Migration
• Migrating Marketing Guides to New Repo #182 – Marketing Guide Migration
• Renaming Guides Issues Titles For Consistency #176 – Guide Title Standardization

[ExperimentsInHonesty]

• Review all issues with this search is:issue updated:>2025-01-01 -label:"feature: trackers" -label:"p-feature: accomplishments" to find any that belong 2025 and list below
  • Epic: Update the Template and Instructions #202 Updating all the issues with relevant template instructions
  • Bonnie needs to check the label:"CoP label: check needed" #201 - making sure all the guide issues are properly tagged with the relevant cop
  • Final Check On Each CoP To Make Sure No Guides Are Left Behind #199 - finish the migration of all guides
  • Need to check if all issues have their Google Folders and shortcut links #198 - standardize storage references
  • Review the Instructions on How to Work With Guides #197 - Documenting the instructions on how to work with guides
  • Identify all Issues with the label "drive: shared with me" and document their owners #194 - gain control of documents still owned by authors
  • Review Names of the Google Drive Folders to Have Consistent Titles #190 - standardize storage naming architecture
  • Identify the document owners of shared with me" files, add to kb-content drive and invite to move files #189 - gain control of documents still owned by authors
  • Setup Mailing List for HfLA Research Ethics Guides notification #188 - creating a subscriber list
  • Different Repos Need Issue Template for Future Guides #186 - updating guide issues templates to better reflect the process that guide requires
  • Agenda for Meeting w/ CoP Leads #130 - meet with CoP lead stakeholders to do ?
  • Find Glossary Words Across Presentations #125 - glossary words across all guides guidance
  • Icon Legend #124 - standardize iconography across guides guidance
  • Fix Formatting: Text Should Be Directly in Shapes #119 - update guides guidance styling for consistency
  • Fix Formatting: Guide Presentations Body Text in HfLA Dark Blue, 14pt Arial #116 - update guides guidance styling for consistency
  • Fix Formatting on Gather Examples Presentations #113 - update guides guidance styling for consistency
  • Guide Templates: Propose a new section #74 - create structure for new guide section proposals
  • Wiki: Create a Glossary #88 - created the glossary draft

---

• Issues with no substantial update but has reason
  • Cleanup Guide templates #14 - standardize guide templates

---

• issues that were updated with movement on the board, or milestone, or label, but no substantial updates
  • Clean Up Guide Issues for Triage #174
  • Guide Suggestions: UI/UX #172
  • CoP Templates and Guides Board Migration #169
  • Epic: Research Document Templates #155
  • Update List of Active Projects #140
  • Clean Up Guides for Pilot #138
  • Piloting New Guidance on Gathering Examples #137
  • Updating Guide Issues #131
  • Guidance on Guides: How to Ask for Peer Review #129
  • Clean Up the Project Board #127
  • Review old document created by HfLA Dev Lead in 2021 #126
  • Feature Suggestion: Index of complete guides in the wiki #110
  • Missing/Broken Guide tracker links in Wiki #109
  • We Need to Sort Out Guide Issues With Action Items That Are Too Complex to Address With One Guide #107
  • Outstanding items for the Gather Examples presentation #105
  • Requirements building for how to run a brigade #104
  • Wiki: Create a Glossary #88
  • Presentation: Start working on a new guide #72
  • Cleanup Guide: How to make a pr #45
  • Cleanup Guide template: making a press release for your open source project #8 #34
  • Cleanup Guide template: Template for making composite images in our HfLA guides #55 #31
  • Cleanup Guide template: How to setup Figma for teams #280 #29
  • Cleanup Guide template: Terms and Conditions for your project #114 #27
  • Cleanup Guide template: Figma Effective Practices #20 #25
  • Cleanup Guide template: Website Style Guide and Design System #24 #24
  • Cleanup Guide template:Defining Hack for LA identity #1 #23
  • Cleanup Guide template: Designers Toolkit #25 #22
  • Cleanup Guide template: Figma for developers (written by their friends at UI/UX) #27 #20
  • Cleanup Guide template: Typography Effective Practices #48 #19
  • Cleanup Guide template: Figma Auto-Layout #62 #18
  • Cleanup Guide template: ui/ux #40 use Figma effectively on Open Source Volunteer Teams #16
  • Review all guides with Leadership Review status to provide feeback #11
  • Test of Markdown converter #10

[ExperimentsInHonesty]

No Action 2025

[ExperimentsInHonesty]

This week @yashhR is going to go find any of the issues that have 2025 updates and move the ones that don't into the next section #203 (comment)

Next week, we are going to review those issues to see if they are relevant to our Accomplishments and if so, the next step will be to figure out what got done and write a draft of the contribution to the accomplishment

[ExperimentsInHonesty]

2025 Summary so far

In 2025, we completed the migration and standardization of all Guides, adding consistent templates, glossary terms, iconography, and clearer instructions to make them easier to create and use. We also secured long-term governance by standardizing storage, transferring document ownership, and refining issue labels and templates—improving discoverability, safeguarding content, and lowering barriers for volunteers.

chatgpt for writing this: https://chatgpt.com/share/68a8955c-f908-8008-95ff-ed27c9363128