Epic: Issues Dashboard

[Samhitha444]

Overview

We need to manage the work for the issue dashboard, so that we can prioritize and recruit.

Action Items

• Review prior work including Wiki
• Go the issue tab for issue dashboard and copy all of the links in the issue to a comment in the bottom of the issue and indicate whether they are public or private.
• Copy all of the link lists from the issues into a comment on this issue
• Remove duplicates
• Remove the public private status
• Revise Issues Dashboard Roadmap

Resources/Instructions

• P: HfLA Dashboards: Project Board, Issues
• HfLA website: HfLA Dashboard Development Roadmap
  • HfLA website: Dashboard Roadmap: Issues
• All Dashboards Epic: Epic: Dashboards planning #6614

Time Sensitive

• Epic: Refactoring GHA - JavaScript files to use common key: value JSON #6454

V1

• Weekly Label Check #2698
  • GitHub website repo, issue tab, with filter: is:issue is:open no:project
  • GitHub website repo, issue tab, with filter: is:open is:issue label:"ready for dev lead"

V2 Dashboard (looker)

• Live Project Board Issues Dashboard (Current)

Documentation

• WIKI https://github.com/hackforla/data-science/wiki/Interactive-Looker-Dashboard-for-the-HackforLA.org-Website-Team

Data

• Spreadsheet: GitHub Project Board Issues - Data Analysis - all the issue by issue data that looker uses to display the dashboard this spreadsheet is located in located in HackforLA.org website > HackforLA.org website folder > 5 - Data Science > GitHub Data Analysis > Dashboard
  • Spreadsheet: GitHub Project Board Issues - Data Analysis
  • spreadsheet: GitHub Project Board Issues - Data Analysis, Dataset 2 (locked)
• spreadsheet: GitHub Project Board Issues - Data Analysis, Missing Label Audit tab
• Spreadsheet: Labels for Weekly Label Check - the dashboard uses this to indicate authorized labels
  • See the current ignore labels on the Repo: website, Tab: labels ignore...

GitHub Actions that support Dashboard

• https://github.com/hackforla/live-dashboard-automation/actions/workflows/schedule_run_to_update_data.yaml
• https://github.com/hackforla/live-dashboard-automation/blob/main/.github/workflows/schedule_run_to_update_data.yaml#L56-L58
• Repo: live-dashboard-automation - former name: onboarding-github-issues
• Repo: live-dashboard-automation, tab: Actions
• Repo: live-dashboard-automation, tab: code /.github/workflows
• Repo: live-dashboard-automation, tab: code .env file

Google Drive and Folder Links

• folder: HackforLA.org website > HackforLA.org website folder > 5 - Data Science > GitHub Data Analysis > Dashboard
• folder: Data Science (community of practice) > Data Science (community of practice) > labels audit

Google Cloud

• Google Cloud Console - We try not to use AWS or Google Cloud for this project wherever possible. However, if its is deemed necessary and the Admin of Hack for LA approves it you would use it via [email protected]

Related Projects

• Default Labels
  • Define: Default Repo Labels ops#15 (we will want the dashboard to work for new teams straight away, so having default labels will ensure that)
• Label Survey CoP: Data Science: Survey: Repo Labels data-science#160
  • Google Drive folder: Data Science (community of practice) > Data Science (community of practice) > labels audit
    • Google Sheet: Label.csv - a Google Sheet version of the label.csv file
      • CSV file: label.csv - a file created by the script of labels.
    • Google Sheet: combined.csv - a Google Sheet version of the label.csv file
      • CSV file: combined.csv - a file created by the script of labels.
    • Labels Survey Analysis.pdf - Author Joshua Susanto
  • Repo: data-science, code: labels-survey
    • Folder for Labels Survey project: https://github.com/hackforla/data-science/tree/main/labels-survey
      • Getting labels: https://github.com/hackforla/data-science/blob/main/labels-survey/get_labels.py
      • Getting the repositories: https://github.com/hackforla/data-science/blob/main/labels-survey/repos.py
      • Getting the output: https://github.com/hackforla/data-science/blob/main/labels-survey/output.csv
      • Label analysis: https://github.com/hackforla/data-science/blob/main/labels-survey/Label_Analysis.ipynb

Tutorials/Helpfiles and Community Discussion boards

• Presentation: GitHub Class on Dashboard Creation 11/13/2023 - made by the creator of the original dashboard
  • A early version of the presentation Labels Survey Analysis.pdf
• Tutorial: https://www.datacamp.com/tutorial/how-to-analyze-data-in-google-sheets-with-python-a-step-by-step-guide
• GitHub Docs: REST API endpoints for Projects (classic) - this was used to create the dashboard, but we migrated to the new project boards, so this guidance should be used to understand the current code and help rewrite it to use new project board technical requirements
• GitHub Docs: Managing labels, Applying a label
• GitHub Community Discussions: Pip dependencies not getting cached even after successful restore
• Hack for LA website wiki documentation - written by website team
  • How to create issues
  • How-to-read-and-interpret-labels
• YouTube: Google Sheets API Automation in Python
  • YouTube: Google Sheets API Automation in Python at 250s the presenter discusses the process of enabling the Google Sheets API and creating the necessary credentials for API access.
• YouTube: Update Google Sheets Using A Service Account With Google Sheets API In Python 🐍
• Youtube: How to cache python dependencies to speed up GitHub workflows
• PythonDocs: 3.13.2 Documentation » The Python Standard Library » Internet Protocols and Support » urllib.parse — Parse URLs into components
• Tutorial: Manually Trigger a GitHub Action with Workflow Dispatch - Guide on adding workflow dispatch event/button
• DuckDB Documentation: Python API Overview for the DuckDB product
• Shillelagh Documentation: Shillelagh Python library and CLI Overview a Python library and CLI that allows you to query many resources (APIs, files, in memory objects) using SQL.
• Tutorial and Calculator: - https://crontab.guru Resource for Figuring Out Cron Job Expression

[ExperimentsInHonesty]

• Create a new issue for requirements

This is the spreadsheet you will use
Dashboard - Issues - Competitive or Comparative Analysis Template

• this issue as an example Requirements for the Time Card Dashboard v3 #7640

• work on the issue you create

[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 - except

There are also some links in a comment (above) that have not been properly categorized yet. #7505 (comment)

[ExperimentsInHonesty]

@amen-ikamba Please watch the presentation: Presentation: GitHub Class on Dashboard Creation 11/13/2023 - made by the creator of the original dashboard.

Add questions that you have, after watching to a comment below.

[ExperimentsInHonesty]

Next week, we will:

• Resolve all unresolved comments with links
• Compile final list of links into the top of the issue
• Compare the links in our issue with the links on https://github.com/hackforla/data-science/wiki/Dashboard-Resources and add any that are present in our issue but are missing from the wiki, to the wiki.
• Review questions from latest presentation review

[amen-ikamba]

1. Progress: Went through the presentation of the original dashboard
2. Question: Is the dashboards different depending on someone’s role or everyone can check it on one dashboard?

Looking forward to resolving all issues in our next meeting.

[ExperimentsInHonesty]

Q1: Is the dashboards different depending on someone’s role or everyone can check it on one dashboard?

A1: It is the same for everyone, anyone can access it. There are different pages on the dashboard that might be useful for different roles, and we will probably expand the dashboard to include more role specific pages.

[HackforLABot]

@amen-ikamba

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, February 24, 2025 at 11:05 PM PST.}