Skip to content

Initiative: Dashboards planning #6614

@ExperimentsInHonesty

Description

@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

List of Repos involved

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

Project board for all Dashboard Issues

P: HfLA Dashboards: Project Board (view)

Website

Internship

Data Science

team-analytics


All dashboard epics

Participant Record

Org

Skills/Productivity Dashboard

Issues Dashboard

Metadata

Metadata

Type

No type

Projects

Status

In progress (actively working)

Relationships

None yet

Development

No branches or pull requests

Issue actions