Epic: Dashboards planning

[ExperimentsInHonesty]

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

• 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
    • Internship project
    • Data Science
    • Website
    • Team Analytics
• Find any related WIKI pages (checking same repositories)
• Create Roadmap
  • Create Google doc for roadmap
  • 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: Time Card
    • [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.
• time card dashboard: For viewing the amount of time you self reported working on the project. Used in connection with a time card google form. This dashboard was used in the 2022 Internship team cohort only. The purpose was to teach interns how to use time cards 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
• time card dashboard
  • TWE: IS22 Time Card - 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
    • ER: Create a skills dashboard #4532
      • Google Drive folder for the issue 4532
• Dashboard
  • label: p-feature: Dashboard
  • Issues
    • ER: Fix dashboard data script (workflow) #6229
    • ER: Add analytics about how many people we reach to the Dashboard #4537
    • ER: Get Google Data Studio up to date so that we can use it for insights and its ready for launch #4276
    • Create Organizational Dashboard page #542
    • Setup Google Analytics on website #503
• Issues dashboard
  • label: feature: Issues dashboard
  • issues:
    • ER: Fix dashboard data script (workflow) #6229
    • Create a Chart in Looker Dashboard Visualizing Audit of Issues with Missing Labels Over Time #5813
    • Create Landing Page for Anomaly Report in Looker Dashboard #5812
    • Create Label Report in Google Spreadsheet #5810
    • Create Project Board Looker Dashboard for Different Roles  #4921
• ladder progress dashboard
  • label: feature: ladder progress dashboard
  • Issues
    • Analysis: Collecting Data on Issue Completion per Prework Author and Creating Looker Dashboards to Uncover Insights #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
        • Interns Skill dashboard requirements #7460
        • TWE: Research: RP017: Data: Analyze internship#493
        • [TEST] TWE: IS22: RP017: Presentation Slide Deck: Create internship#475 (if this issues results in a finished presentation of findings artifact, we will need to review that)
      • TWE: Create Research Plan for RP017 internship#442 (we should review this plan to see what other research about the dashboard is needed)
      • RP017: Productivity Dashboard Intern 005 Interview Upload internship#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
        • Extrapolate the skills for the interns internship#63
  • Issues general
    • TWE: Research Structure for RP017: Productivity Dashboard Interviews internship#291
• ladder progress dashboard
  • label: [feature: ladder progress dashboard]
  • will be used by the internship project when it's working on website team activity
• time card dashboard
  • label: feature: time card dashboard
  • Issues
    • TWE: IS22: Create a customized time card dashboard internship#254
    • Set up intern time card Data Studio dashboard and Google Sheet  internship#213
    • TWE: Draft time card setup solution for interns internship#193
    • It's possible that there are research findings for the time card 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
  • CoP: Data Science: Survey: Repo Labels data-science#160

team-analytics

• org dashboard
  • label: [P-Feature: Dashboard]
  • Issues
    • MVP Requirements for Type of Data team-analytics#2
    • MVP for GitHub Actions (GHA) team-analytics#1
    • MVP User Stories for Issue/PR Velocity Analytics via GitHub API team-analytics#3

---

All dashboard epics

Time Card

• Epic: Epic: Time Card Dashboard #7509
• Assignee: Sofiat

Org

• Epic: Epic: Org Dashboard #7506
• Assignee: Eleftherios

Skills/Productivity Dashboard

• Epic: Epic: Skills/Productivity Dashboard  #7539
• Assignee: Phalguni

Issues Dashboard

• Epic:Epic: Issues Dashboard #7505
• Assignee: Amen

[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 Epic: Refactoring GHA - JavaScript files to use common key: value JSON #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

[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

[ExperimentsInHonesty]

Add this to the skills dashboard issue

### Interview details
- WIKI page: [Research Plan 17: Activity Dashboard Interviews](https://github.com/hackforla/internship/wiki/Research-Plan-17:-Activity-Dashboard-Interviews)
- Research Plan: [Research Plan 17 - Activity Dashboard Interview](https://github.com/hackforla/internship/wiki/Research-Plan-17:-Activity-Dashboard-Interviews)
- Recording: [Interview Recording on 2022-07-13](https://drive.google.com/drive/folders/1QqvHWGfyxrf-8hUBdhv5Vf1l18iaYvS2?usp=sharing)
- Transcript: [De-identified Transcript](https://docs.google.com/document/d/1viYsf2eXufRWzH1wY_UFtxP6PYunKmi3QhzgvZT2fCQ/edit?usp=sharing)

[ExperimentsInHonesty]

Instructions

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

1. Progress: We have made progress on the individual dashboard Epics. Also meeting with Rabia on cleaning up and handing over some data for the next set of developers
2. Blockers: not enough PMs yet for full coverage
3. Availability: Sundays at 9am PST for a couple of hours with PMs. Mid week with Rabia
4. ETA: 6 months
5. Pictures (if necessary): none

[ExperimentsInHonesty]

We created a new page in the Hack for LA Data Science repo wiki, called Dashboard Resources - this page has all the tutorial links from each of the issues.

[ExperimentsInHonesty]

@ExperimentsInHonesty This project has been on pause because I am out sick.

[HackforLABot]

@ExperimentsInHonesty, @sofiatajide, @Eleftherios06, @Tusharachada1406, @Samhitha444, @Eleftherios01

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. 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 Monday, January 27, 2025 at 11:04 PM PST.}

[HackforLABot]

@ExperimentsInHonesty, @sofiatajide, @Eleftherios06, @Tusharachada1406, @Samhitha444, @Eleftherios01

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. 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 Monday, February 3, 2025 at 11:04 PM PST.}