website Initiative: Dashboards planning

Overview

We need to identify and start building a roadmap for all the website dashboards, so that we can prioritize, manage and recruit.

Details

There are:

live dashboards
dashboards in dev
proposed dashboards
dashboard ideas

See resources for all the issues we were able to find

Action Items

[x] Find all dashboard issues
- [ ] rationalize labels on repos other than website, so that they match the website repo's name of label
- [ ] make sure all issues that come up in a search for dashboard on the target repo, have the specific dashboard label
- [ ] review each issue within each dashboard label and add the relevant issues to the Resources section below (relevant is defined by being useful to present and future management of the dashboards. e.g., an closed/resolved issue to fix a spelling mistake on the dashboard).
- Places to check
  - [x] Internship project
  - [x] Data Science
  - [x] Website
  - [ ] Team Analytics
[ ] Find any related WIKI pages (checking same repositories)
Create Roadmap
- [x] Create Google doc for roadmap
- [x] Format Document
  - [ ] Separate Users and Location into two Headings under each roadmap
- [ ] organize in order of priority
- [ ] Identity what information is missing
- [ ] ??
[ ] Create or revise issues for each dashboard

Resources/Instructions

A shortcut to the new dashboard Google Drive from the Website Team Google DriveGoogle Drive, Website, PM, Dashboard
Google Drive, HfLA: Dashboards
- HfLA website: HfLA Dashboard Development Roadmap
  - HfLA website: Dashboard Roadmap: Skills / Productivity
  - HfLA website: Dashboard Roadmap: Issues
  - HfLA website: Dashboard Roadmap: Org Dashboard
  - HfLA website: Dashboard Roadmap: Participant Record
  - [HfLA website: Dashboard Roadmap: Repo Statistics]

List of Repos involved

https://github.com/hackforla/website
https://github.com/hackforla/internship
https://github.com/hackforla/data-science
https://github.com/hackforla/team-analytics

Dashboard Summary

skills / productivity ladder: A daily snapshot of a software developer’s journey on the website team. It will show where they are on their ladders for issues, PRs, PR reviews, issue making, and team leadership responsibilities and what specific that are skills obtained not obtained by completing the assignments as well as efficacy of their PR reviews and aggregate performance of peers.
- users: interns, website volunteers, all open source volunteers (mvp is website/interns, v1 is all hfla projects, v2 is a generic version for any open source project)
- location: internship and website team project boards
dashboard (needs to be renamed org dashboard): organizational data about Hack for LA appears at hackforla.org/dashboard
- users: see doc
- location: see doc
issues dashboard:
- audit of issues, showing where they are on the project board, and any that have anomalies. We use this dashboard to know which issues to clean up.
- Summary stats of how many issues are in each column by role and size. Which enables us to see where we need to make
  - users: leads
  - location: website team project board new issues.
participant record dashboard: For viewing the amount of time you self reported working on the project. Used in connection with a participant record google form. This dashboard was used in the 2022 Internship team cohort only. The purpose was to teach interns how to use participant records and to incentivize them to put in the time they promised, given that we did not have set hours for the internship.
- users: interns and people who need verification of their hours by an external entity (school, justice system, visa, etc.)
- location: Internship project board, in offer letter
repo statistics: this dashboard shows maturity of repository and areas for improvement
- users: repository managers (PM, maintainers, etc.)
- location: Civic Tech Structure website

Dashboard URLs

skills / productivity
dashboard
issues dashboard
- Spreadsheet: Labels for Weekly Label Check List of labels that have to be updated if labels change or are added
ladder progress dashboard
participant record dashboard
- TWE: IS22 Participant Record - makeup entry - form

Project board for all Dashboard Issues

https://github.com/orgs/hackforla/projects/88/views/1

Website

All Dashboards
- wiki pages
  - https://github.com/hackforla/website/wiki/Introduction-to-the-Project - contains history of the website and will need to be updated when new dashboards are added to the website.
skills / productivity dashboard
- label: feature: skills / productivity ladder dashboard
- Issues
  - https://github.com/hackforla/website/issues/4532
    - Google Drive folder for the issue 4532
Dashboard
- label: p-feature: Dashboard
- Issues
  - https://github.com/hackforla/website/issues/6229
  - https://github.com/hackforla/website/issues/4537
  - https://github.com/hackforla/website/issues/4276
  - https://github.com/hackforla/website/issues/542
  - https://github.com/hackforla/website/issues/503
Issues dashboard
- label: feature: Issues dashboard
- issues:
  - https://github.com/hackforla/website/issues/6229
  - https://github.com/hackforla/website/issues/5813
  - https://github.com/hackforla/website/issues/5812
  - https://github.com/hackforla/website/issues/5810
  - https://github.com/hackforla/website/issues/4921
ladder progress dashboard
- label: feature: ladder progress dashboard
- Issues
  - https://github.com/hackforla/website/issues/4152

Internship

skills / productivity dashboard
- label: feature: skills / productivity dashboard
- wiki pages general
  - https://github.com/hackforla/internship/wiki/Business-Analyst-Data-Science - landing page for business analyst on internship programs to find links relevant to their work.
  - https://github.com/hackforla/internship/wiki/The-2022-Internship-Program-Process-Overview - history and improvements to the internship project. Update this WIKI page when needed to add information about the skills dashboard.
- wiki pages
  - RP016: https://github.com/hackforla/internship/wiki/Research-Plan-16:-Intern-Productivity-Dashboard-Survey
    - Issues:
      - none
- wiki page
  - RP017: https://github.com/hackforla/internship/wiki/Research-Plan-17:-Activity-Dashboard-Interviews
    - Issues
      - https://github.com/hackforla/website/issues/7460
      - https://github.com/hackforla/internship/issues/493
      - https://github.com/hackforla/internship/issues/475 (if this issues results in a finished presentation of findings artifact, we will need to review that)
    - https://github.com/hackforla/internship/issues/442 (we should review this plan to see what other research about the dashboard is needed)
    - https://github.com/hackforla/internship/issues/271 (relevant because it has a link to the one recorded interview)
- wiki pages
  - RP002: https://github.com/hackforla/internship/wiki/Research-Plan-2:-Hack-for-LA-volunteers-transferrable-skills
    - Issues
      - https://github.com/hackforla/internship/issues/63
- Issues general
  - https://github.com/hackforla/internship/issues/291
ladder progress dashboard
- label: [feature: ladder progress dashboard]
- will be used by the internship project when it's working on website team activity
participant record dashboard
- label: feature: participant record dashboard
- Issues
  - https://github.com/hackforla/internship/issues/254
  - https://github.com/hackforla/internship/issues/213
  - https://github.com/hackforla/internship/issues/193
  - It's possible that there are research findings for the participant record that would have been collected during the exit interviews. Review with internship research lead when appropriate.

Data Science

All Dashboards
- wiki pages
  - https://github.com/hackforla/data-science/wiki/Introduction-to-Keeping-Confidential-Information-Safe-on-GitHub%3A-GitHub-secrets-and-.env-files - developer resource for all dashboards.
Issues Dashboard
- label: feature: Issues Dashboard
- wiki pages
  - https://github.com/hackforla/data-science/wiki/Our-Work - every dashboard that is completed should be linked to this page
  - https://github.com/hackforla/data-science/wiki/Interactive-Looker-Dashboard-for-the-HackforLA.org-Website-Team - related to issues dashboard
- Issues
- https://github.com/hackforla/data-science/issues/160

team-analytics

org dashboard
- label: [P-Feature: Dashboard]
- Issues
  - https://github.com/hackforla/team-analytics/issues/2
  - https://github.com/hackforla/team-analytics/issues/1
  - https://github.com/hackforla/team-analytics/issues/3

All dashboard epics

Participant Record

Epic: https://github.com/hackforla/website/issues/7509
Assignee: Sofiat

Org

Epic: https://github.com/hackforla/website/issues/7506
Assignee: Eleftherios

Skills/Productivity Dashboard

Epic: https://github.com/hackforla/website/issues/7539
Assignee: Phalguni

Issues Dashboard

Epic:https://github.com/hackforla/website/issues/7505
Assignee: Amen

Apr 09 '24 20:04 ExperimentsInHonesty

left off at need to

[x] review the issues feature: skills / productivity dashboard from the internship project to determine if we are adding them to our resources

Apr 09 '24 22:04 ExperimentsInHonesty

@kellyc9 see comment above

Apr 09 '24 22:04 ExperimentsInHonesty

As a test with @t-will-gillis

we added a label to the repo and this issue but did not add it to the spreadsheet feature: test label 2
we added a label to the spreadsheet and did not add it to the repfeature: test label neither of these showed up on this page of the issues dashboard, unofficial labels page.

We also noticed that although we have manually run the workflow, it still says Apr 10, 2024, 2:12:06 PM instead of 4:00 PM when we last ran it.

Relevant to Issues Dashboard Roadmap

once this epic is closed #6454 we can fix the dashboard so that it uses a
- Json file to store the label names, keys and GHAs that use them
- Spreadsheet Public - Website Labels 'Source of Truth' is under the hackforla bot account

Apr 10 '24 23:04 ExperimentsInHonesty

[ ] check this off when an issue has been made that addresses it, or it's been added to a list of issues to make.

It looks like someone has made the label role: full stack but it's not showing up on the issues dashboard, unofficial labels page. We will need to make a new ticket for fixing whatever logic is broken.

I did notice that if we add a label that is not on the spreadsheet, to an issue then it shows up on the report, but labels that are not on the spreadsheet, are on the repo and not on issues should still show up on the top section.

Relevant to Issues Dashboard Roadmap

Apr 14 '24 18:04 ExperimentsInHonesty

[ ] check this off when an issue has been made that addresses it, or it's been added to a list of issues to make.

on 2024-04-14 I was in the Labels for Weekly Label Check, noticed this note and realized the label got deleted. We need a confirmation that it didn't break any GHA

label_name	label_series	missing_series?	date_added	in_use?	Notes
prework	complexity	No	2023-08-04	No	Label temporarily kept for GitHub Actions. Please keep "in_use?" as "No" if you want dashboard to show issues with this label in anomaly report.

Relevant to Issues Dashboard Roadmap

Apr 14 '24 18:04 ExperimentsInHonesty

We left off on the internship project.

[x] We are currently going through the issues on the issue tab issues that have the word dashboard in them, excluding all issues that have the label feature: skills / productivity dashboard to look for issues that are either related to the skills / productivity dashboard and are not labeled correctly, or are another kind of dashboard.
[x] We found another dashboard (time card). We need to make a new label for it on the:
- [x] internship
- [x] website repo.
[x] Search the website repo and make sure that we didn't miss any issues related to time card. And label them if we did.
[x] label all time card dashboard issues on the internship project that require it. Do another issue search for the word time card, in that labeling process (as well as the dashboard search). issue search using "time card"
[x] add links to all relevant time card dashboard issues to the resources

Apr 14 '24 19:04 ExperimentsInHonesty

Internship issues with label: feature: time card dashboard

Apr 15 '24 20:04 ExperimentsInHonesty

[x] Check to see which repos the feature: ladder progress dashboard appears on
- [x] website
- [x] internship
- [x] Data Science

Apr 15 '24 20:04 ExperimentsInHonesty

[x] Go to data science repo
- [x] Create dashboard labels that are missing https://github.com/hackforla/data-science/labels?q=dashboard. Use the current list at https://github.com/hackforla/website/labels?q=dashboard

Apr 15 '24 21:04 ExperimentsInHonesty

[x] Go to all wikis for the repositories we have identified above and add relevant wiki page links below
[x] Add the wiki pages we found to the top part of issue

All Dashboards

https://github.com/hackforla/website/wiki/Introduction-to-the-Project - contains history of the website and will need to be updated when new dashboards are added to the website.
https://github.com/hackforla/data-science/wiki/Introduction-to-Keeping-Confidential-Information-Safe-on-GitHub%3A-GitHub-secrets-and-.env-files - developer resource for all dashboards.

skills / productivity Links

https://github.com/hackforla/internship/wiki/Business-Analyst-Data-Science - landing page for business analyst on internship programs to find links relelvant to their work.
https://github.com/hackforla/internship/wiki/The-2022-Internship-Program-Process-Overview - history and improvements to the internship project. Update this WIKI page when needed to add information about the skills dashboard.

issues dashboard links

https://github.com/hackforla/data-science/wiki/Our-Work - every dashboard that is completed should be linked to this page
https://github.com/hackforla/data-science/wiki/Interactive-Looker-Dashboard-for-the-HackforLA.org-Website-Team - related to issues dashboard

Apr 15 '24 21:04 ExperimentsInHonesty

Found another dashboard: - DPGOSCM: Program Impact: Repo Stats Dashboard, need to gather and add to the top of this issue:

[ ] issues
[ ] check and rationalize labels
[ ] check wikis
[ ] create roadmap

The above link is a link to a spreadsheet.

[ ] Talk to Rabia about where the dashboard issue that made this sheet lives.

Apr 25 '24 00:04 ExperimentsInHonesty

@ExperimentsInHonesty, @kellyc9

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, April 30, 2024 at 12:06 AM PST.}

May 03 '24 07:05 github-actions[bot]

We have been on hiatus for a week. Now @KwameTaylor is onboarded, we will resume work on this Sunday.

May 03 '24 21:05 ExperimentsInHonesty

@ExperimentsInHonesty, @KwameTaylor

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, May 14, 2024 at 12:06 AM PST.}

May 17 '24 07:05 github-actions[bot]

@ExperimentsInHonesty, @KwameTaylor

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, May 21, 2024 at 12:06 AM PST.}

May 24 '24 07:05 github-actions[bot]

@ExperimentsInHonesty, @KwameTaylor

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, June 4, 2024 at 12:06 AM PST.}

Jun 07 '24 07:06 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, June 11, 2024 at 12:06 AM PST.}

Jun 14 '24 07:06 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, June 18, 2024 at 12:06 AM PST.}

Jun 21 '24 07:06 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Wednesday, June 19, 2024 at 1:48 PM PST.}

Jun 22 '24 20:06 github-actions[bot]

[x] go through all repos related to this epic
- [x] add the label for skills to all the ladder issues
- [x] remove the ladder label
- [x] rename the skills label to

feature: skills / productivity ladder dashboard

[x] https://github.com/hackforla/website/labels
- [x] add the label for skills to all the ladder issues
- [x] remove the ladder label
- [x] rename the skills label
[x] https://github.com/hackforla/internship/labels
- [x] rename the skills label
[x] https://github.com/hackforla/data-science/labels
- [x] remove the ladder label
- [x] rename the skills label
[x] https://github.com/hackforla/team-analytics/labels
- there are no skills or ladder labels on this repo

Jul 08 '24 20:07 ExperimentsInHonesty

@Eleftherios06,

[x] add the location and another other headings that are missing in the HfLA website: HfLA Dashboard Development Roadmap

Jul 08 '24 20:07 ExperimentsInHonesty

next time we get together we are going to continue to work on the goals in the roadmap

Jul 08 '24 20:07 ExperimentsInHonesty

@ExperimentsInHonesty, @Eleftherios06

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, July 30, 2024 at 12:05 AM PST.}

Aug 02 '24 07:08 github-actions[bot]

@ExperimentsInHonesty, @Eleftherios06

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, August 6, 2024 at 12:04 AM PST.}

Aug 09 '24 07:08 github-actions[bot]

@ExperimentsInHonesty, @Eleftherios06

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

Progress: "What is the current status of your project? What have you completed and what is left to do?"
Blockers: "Difficulties or errors encountered."
Availability: "How much time will you have this week to work on this issue?"
ETA: "When do you expect this issue to be completed?"
Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, August 13, 2024 at 12:14 PM PST.}

Aug 16 '24 19:08 HackforLABot

We are going to add three issues we found in https://github.com/hackforla/team-analytics repo to the HfLA Dashboards: Project Board

https://github.com/hackforla/team-analytics/issues/2
https://github.com/hackforla/team-analytics/issues/1
https://github.com/hackforla/team-analytics/issues/3

They will need to be properly labeled later.

Aug 22 '24 18:08 ExperimentsInHonesty

We have added some new issues to HfLA Dashboards: Project Board, Missing Dashboard Name tab

https://github.com/hackforla/team-analytics/issues/2
https://github.com/hackforla/team-analytics/issues/1
https://github.com/hackforla/team-analytics/issues/3
[x] Review each of the issues to identify if they belong to an identified dashboard or we need to create a new label

Aug 25 '24 17:08 mayankt153

Need to check the resources for all issues to make sure that their files and folders get moved and or shortcuts gets created to the new dashboard drive folders.

Aug 25 '24 18:08 mayankt153

Missing the Dashboard link for:

Time Card (ask Rabia)

Sep 08 '24 17:09 ExperimentsInHonesty

@Rabia2219 where are we keeping all the DPG analysis work that we were doing?

Sep 08 '24 17:09 ExperimentsInHonesty