hackforla
VRMS: Accomplishment Summary for HfLA Website 2020-2024
Overview
We need to write brief summaries of project accomplishments for each year of the project's life, to go on the website's accomplishments page.
Action Items
- [x] 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
- Find and review all previous onesheets
- [x] Find all the one sheets (check Project's Google Drive resource 1.03) and link the folder to resource 1.04.03. If there are multiple folders, create 1.04.03.01, 1.04.03.02, etc. indented under 1.04.03)
- [x] Review all previous project onesheet drafts under 1.04 (including edit history)
- Search the project's repo for any accomplishment issues, add any links you find to a comment
- [x] Go to the project repo issue tab (resource 1.05)
- [x] review all closed issues, looking for details of your project's progress that you could use in your accomplishment summary, noting the accomplishment and date of completion
- [x] Put the links relevant to that search under the below heading in chronological order
### Project or CoP's repo issue searches - for each search you perform, indicate what you searched in the filter bar to get the result and link it to the URL (e.g.,)
#### Searches - [Replace with what you searched for in the Filter bar] - [Replace with what you searched for in the Filter bar] - [Replace with what you searched for in the Filter bar] - [x] Draft a brief paragraph describing what the project accomplished for each year
- Update the epic issue (resource 1.01)
- [ ] Add the following comment
We have completed the accomplishments for 2020-2024- [ ] Add the label
updated - [ ] Add the label
ready for org rep - [ ] Move to the questions/review column on the Team Tasks project board
Resources/Instructions
- 1.01 Accomplishments epic: https://github.com/hackforla/admin-accomplishments/issues/10
- 1.02 Hackforla.org website, about page, accomplishments section: https://www.hackforla.org/about/#accomplishments
- 1.03 VRMS project Google Drive
- 1.04 One Sheets:
- 1.04.01 One sheet from product-management repo: https://github.com/hackforla/product-management/blob/master/project-one-sheets/VRMS-One-Sheet.pdf
- 1.04.02 One sheet link from Hack for LA website (Overview): https://www.hackforla.org/assets/pdfs/VRMS-One-Sheet.pdf
- 1.04.03 Folder with One sheet drafts on VRMS' Google Drive:
- 1.05 VRMS repo, Issues tab
- Initial Commit Dec 5, 2019
- What was the date that people could first setup accounts and sign in at VRMS?
@JackHaeg For the first bullet point, 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: what is resource 1.02, where can I find that?
Hi @kkchu791!
Please scroll to the bottom of the issue above and you will see the “Resources / Instructions” section. There you can find resource 1.02, which has a link you can access: https://www.hackforla.org/about/#accomplishments
Also, if you are planning to work on this issue, please assign yourself to the issue and change the status to “in progress”.
Thanks!
Hi @JackHaeg, I was wondering if this would be acceptable for the accomplishments summary?
Searches
- [https://github.com/hackforla/VRMS/issues?q=is%3Aissue%20state%3Aclosed%20type%3AFeature]
Accomplishments Paragraph
Over the past couple of months, we wrapped up several front-end and design updates that make project management smoother and easier to use. On Aug 26, new UI/UX designs for project members and admins were completed, laying the groundwork for a cleaner experience. Then, throughout September and early October, we rolled out multiple front-end improvements — including adding and alphabetizing project members (#2026, Oct 1) and updating the Project Page title to display the actual project name instead of a generic label (#2025, Oct 1). We also converted the Project Management sections into collapsible MUI accordions (#2022, Oct 1) and added a new “On/Offboard Forms” section to simplify team transitions (#2015, Oct 6). Finally, by early October, we closed out a major feature allowing project members and admins to manage members directly from the Project Details page (#1984, Oct 1). Altogether, these updates improved navigation, organization, and collaboration across the platform — nice step forward for usability and project flow.
Hi @kkchu791 - Thanks for taking on this issue! Just following up with a bit of feedback below that we'll discuss on the call:
- [ ] Issue search needs to be different (issue type is a new feature on GitHub, and limits all closed issues).
- [ ] Date range needs to go from 2020 - 2024.
- [ ] Create a checkbox list of each issue, so that we can review and go through all issues that are related to features
- [ ] This is a good example: People Depot: Accomplishment Summary for HfLA Website 2020-2024 peopledepot#416 (comment)
- (can just be a list of issues - don’t need to type them out like in the Accomplishment summary that seem to be relevant to software features that benefit the end user)
Updates after speaking with Bonnie last week:
- When a user selects "All", it will display each year as a separate paragraph (they will not be combined)
- There is no specific character count to abide by, but Bonnie asked that we keep it fairly short (like
Write for AllorUndebate). According to Bonnie, 311-Data was a little long. Refer to this page. - No specific guidelines on what stakeholders are looking for (note that Jack & Trillium will try to obtain relevant metrics like total users, events checked into, etc. which Bonnie thought could be helpful
- No need to use the checkbox approach I discussed above - Okay to just write a paragraph that summarizes the team's progress over the course of a year. However, please be sure to provide links to issues that are are referenced in the summary.
- If nothing happened in a single year (or if no interest to funders), then we can leave a year blank, however this is pretty rare
Re accomplishments, I wanted to some ideas of what types of data we are looking to glean from the production db info.
Active users? Accounts generated? Etc
Hi @trillium!
When possible, can you please provide the following metrics:
- Annual and Total(overall) metrics for:
- Users added
- Events created
- Events
- Check ins
- Volunteer hours? (May not be necessary)
Hi @JackHaeg!
Here are the requested metrics from the VRMS database:
📊 Annual Metrics (2020-2025)
Year 2020
- Users Added: 480
- Events Created: 1,124
- Check-ins: 2,999
- Event Hours: 1,739
Year 2021
- Users Added: 577
- Events Created: 2,614
- Check-ins: 3,173
- Event Hours: 3,691
Year 2022
- Users Added: 558
- Events Created: 3,320
- Check-ins: 1,385
- Event Hours: 4,485
Year 2023
- Users Added: 680
- Events Created: 10,489
- Check-ins: 1,219
- Event Hours: 12,849
Year 2024
- Users Added: 110
- Events Created: 3,412
- Check-ins: 196
- Event Hours: 4,160
Year 2025 (partial year, through November)
- Users Added: 74
- Events Created: 1,373
- Check-ins: 91
- Event Hours: 1,669
📈 Overall Totals (All Time)
- Total Users Added: 2,479
- Total Events Created: 22,335
- Total Check-ins: 9,063
- Total Event Hours: 28,593
📊 Year-over-Year Growth Analysis
User Growth (Year-over-Year)
| Year | Users Added | Change from Previous Year | % Change |
|---|---|---|---|
| 2020 | 480 | - | - |
| 2021 | 577 | +97 | +20.2% |
| 2022 | 558 | -19 | -3.3% |
| 2023 | 680 | +122 | +21.9% |
| 2024 | 110 | -570 | -83.8% |
| 2025* | 74 | -36 | -32.7% |
Events Created (Year-over-Year)
| Year | Events Created | Change from Previous Year | % Change |
|---|---|---|---|
| 2020 | 1,124 | - | - |
| 2021 | 2,614 | +1,490 | +132.6% |
| 2022 | 3,320 | +706 | +27.0% |
| 2023 | 10,489 | +7,169 | +215.9% |
| 2024 | 3,412 | -7,077 | -67.5% |
| 2025* | 1,373 | -2,039 | -59.8% |
Check-ins (Year-over-Year)
| Year | Check-ins | Change from Previous Year | % Change |
|---|---|---|---|
| 2020 | 2,999 | - | - |
| 2021 | 3,173 | +174 | +5.8% |
| 2022 | 1,385 | -1,788 | -56.4% |
| 2023 | 1,219 | -166 | -12.0% |
| 2024 | 196 | -1,023 | -83.9% |
| 2025* | 91 | -105 | -53.6% |
Event Hours (Year-over-Year)
| Year | Event Hours | Change from Previous Year | % Change |
|---|---|---|---|
| 2020 | 1,739 | - | - |
| 2021 | 3,691 | +1,952 | +112.3% |
| 2022 | 4,485 | +794 | +21.5% |
| 2023 | 12,849 | +8,364 | +186.5% |
| 2024 | 4,160 | -8,689 | -67.6% |
| 2025* | 1,669 | -2,491 | -59.9% |
Note: 2025 is a partial year (through November), so year-over-year comparisons should be interpreted with that context.
Key Insights
- Peak Year: 2023 showed the highest activity across most metrics (events, event hours)
- User Growth: Strongest user growth occurred in 2023 (+21.9%)
- Event Growth: Significant event creation spike in 2023 (+215.9%)
- Recent Trends: Significant declines in 2024-2025 across all metrics may indicate changes in tracking methodology, organizational shifts, or actual activity reduction
📝 Methodology & Notes
Data Collection
- All metrics were extracted from the production database
- Database investigation performed: November 24, 2025
Metric Definitions
-
Users Added: Count of users created in each year based on
createdDatefield -
Events Created: Count of events created in each year based on
createdDatefield -
Check-ins: Count of check-in records in each year based on
createdDatefield -
Event Hours: Sum of the
hoursfield from all events created in each year- Note: 99.7% of events (22,260 out of 22,335) have duration data
- This represents total event hours offered, not volunteer hours contributed
Important Distinction
The "Event Hours" metric currently represents the total duration of all events created in that year. For example, if 100 events were created and each lasted 2 hours, this would show 200 hours.
To calculate actual volunteer hours contributed, we would need to multiply each event's duration by the number of attendees (check-ins) for that event. This would give us total person-hours contributed by volunteers.
Would you like me to calculate the actual volunteer hours contributed instead?
Let me know if you need any additional metrics, breakdowns, or clarifications!
Unassigning @kkchu791 to work on other Dev issues for now. Placing back in the prioritized backlog.
Hi @JackHaeg!
Here's the analysis of closed issues for the VRMS repository, organized by year and month:
📋 Closed Issues Summary (2019-2025)
Total Closed Issues: 1,120
Summary by Year
| Year | Issues Closed |
|---|---|
| 2025 | 130 |
| 2024 | 176 |
| 2023 | 177 |
| 2022 | 302 |
| 2021 | 160 |
| 2020 | 174 |
| 2019 | 1 |
📅 Monthly Breakdown
2020
| Month | Count |
|---|---|
| December | 66 |
| November | 33 |
| October | 15 |
| September | 7 |
| August | 2 |
| July | 4 |
| June | 7 |
| May | 12 |
| April | 11 |
| March | 14 |
| February | 3 |
2021
| Month | Count |
|---|---|
| December | 8 |
| November | 3 |
| October | 9 |
| September | 12 |
| August | 16 |
| July | 23 |
| June | 12 |
| May | 17 |
| April | 21 |
| March | 19 |
| February | 11 |
| January | 9 |
2022
| Month | Count |
|---|---|
| November | 9 |
| October | 1 |
| August | 5 |
| July | 8 |
| June | 6 |
| May | 17 |
| April | 1 |
| March | 5 |
| February | 17 |
| January | 233 |
Note: January 2022 had an exceptionally high number of closed issues (233), which may indicate a cleanup effort or mass closure event.
2023
| Month | Count |
|---|---|
| December | 3 |
| November | 11 |
| October | 27 |
| September | 14 |
| August | 15 |
| July | 28 |
| June | 33 |
| May | 7 |
| April | 6 |
| March | 27 |
| February | 5 |
| January | 1 |
2024
| Month | Count |
|---|---|
| November | 6 |
| October | 16 |
| September | 12 |
| August | 18 |
| July | 7 |
| June | 12 |
| May | 21 |
| April | 55 |
| March | 8 |
| February | 15 |
| January | 6 |
2025 (Partial Year - through November)
| Month | Count |
|---|---|
| November | 2 |
| October | 17 |
| September | 7 |
| August | 7 |
| July | 4 |
| June | 19 |
| May | 14 |
| April | 1 |
| March | 26 |
| February | 13 |
| January | 20 |
📊 Key Insights
Peak Activity Periods
- Highest Monthly Closure: January 2022 (233 issues)
- Most Active Year: 2022 (302 issues total)
- Recent Activity: 2025 has closed 130 issues so far (partial year)
Trends
- 2020-2021: Steady activity with consistent monthly closures
- 2022: Major spike in January, then returned to normal levels
- 2023: More balanced distribution across the year
- 2024: Strong April activity (55 issues)
- 2025: Good start to the year with 130 issues closed through November
Average Monthly Closures
- 2020: ~14.5 issues/month
- 2021: ~13.3 issues/month
- 2022: ~25.2 issues/month (heavily skewed by January)
- 2023: ~14.8 issues/month
- 2024: ~16.0 issues/month
- 2025: ~11.8 issues/month (through November)
📄 Full Detailed Report
A complete issue-by-issue breakdown organized by year and month has been generated and saved to:
-
closed-issues-report.md- Full markdown report with all issue links -
closed-issues-data.json- Structured JSON data for further analysis
The full report includes:
- All 1,120 closed issues with links
- Issue titles
- Issue labels (first 3)
- Organized by year → month → issue number
Data Source: GitHub API via gh CLI tool
Analysis Date: November 24, 2025
Total Issues Analyzed: 1,120 closed issues
Let me know if you need any additional breakdowns or specific analysis of these issues!