Epic: Issues Dashboard

[Samhitha444]

Overview

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

Action Items

• [x] 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.
• [x] Copy all of the link lists from the issues into a comment on this issue
• [x] Remove duplicates
• [ ] ~Remove the public private status~
• [ ] Revise Issues Dashboard Roadmap

Resources/Instructions

• P: HfLA Dashboards: Project Board, Issues
• HfLA website: Dashboard Roadmap: Issues
• HfLA website: HfLA Dashboard Development Roadmap
• All Dashboards Epic: https://github.com/hackforla/website/issues/6614

[github-actions[bot]]

Hi @Samhitha444.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[Samhitha444]

• [ ] 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/data-science/issues/160
• [ ] https://github.com/hackforla/website/issues/4921
• [ ] https://github.com/hackforla/website/issues/7505

[ExperimentsInHonesty]

Copy the items in the chart (don't copy the check boxes)

HfLA website: Dashboard Roadmap: Org Dashboard

[HackforLABot]

@Samhitha444

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 Tuesday, October 15, 2024 at 12:04 AM PST.}

[Samhitha444]

I have copied the items in the chart on the HfLA website: Dashboard Roadmap: Issues

[ExperimentsInHonesty]

@Samhitha444 Copy all the links in from the issues to this comment, excluding duplicates

Issue links

• https://github.com/hackforla/live-dashboard-automation/actions/workflows/schedule_run_to_update_data.yaml
  • [ ] Have access, its located in ____
  • [x] public
  • [x] organized
• Live Project Board Issues Dashboard (Current)
  • [ ] Have access, its located in ____
  • [x] public
  • [x] organized
• https://github.com/hackforla/live-dashboard-automation/blob/main/.github/workflows/schedule_run_to_update_data.yaml#L56-L58
  • [ ] Have access, its located in ____
  • [x] public
  • [x] organized

• Repo: live-dashboard-automation, tab: Actions

  • [ ] Have access, its located in ____
  • [x] public
  • [x] organized

  ---

  • https://github.com/hackforla/live-dashboard-automation
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• Live Project Board Issues Dashboard (Current)
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• Labels for Weekly Label Check
  • [x] Have access - in Dashboard folder
  • [ ] public
  • [x] organized
• https://www.youtube.com/watch?v=3wC-SCdJK2c&t=250s
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized
• https://www.youtube.com/watch?v=sVURhxyc6jE&t=2s
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized
• https://www.datacamp.com/tutorial/how-to-analyze-data-in-google-sheets-with-python-a-step-by-step-guide
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• Spreadsheet: GitHub Project Board Issues - Data Analysis
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• https://leonardomontini.dev/github-action-manual-trigger/
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized
• https://github.com/hackforla/website/issues/4921
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• https://github.com/hackforla/website/labels?q=ignore
  • [ ] Have access, it's located in ____
  • [x] public
  • [x organized
• https://github.com/hackforla/live-dashboard-automation/tree/main/.github/workflows
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• https://docs.python.org/3/library/urllib.parse.html
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized
• https://shillelagh.readthedocs.io/en/latest/index.html
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized
• https://duckdb.org/docs/api/python/overview.html
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized
• https://github.com/hackforla/live-dashboard-automation/pull/60
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• spreadsheet: GitHub Project Board Issues - Data Analysis, Dataset 2 (locked)
  • [x] Have access, it's located in dashboard folder
  • [ ] public
  • [x] organized

• spreadsheet: GitHub Project Board Issues - Data Analysis, Missing Label Audit tab

  • [x] Need Access, it's located in HackforLA.org website > HackforLA.org website folder > 5 - Data Science > GitHub Data Analysis > Dashboard
  • [ ] public
  • [x] organized

  ---

  • https://github.com/hackforla/website/issues/5810
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
  • GitHub website repo, issue tab, with filter: is:issue is:open no:project
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
  • folder: HackforLA.org website > HackforLA.org website folder > 5 - Data Science > GitHub Data Analysis > Dashboard
  • [x] Need access, located in Dashboard
  • [ ] public
  • [x] organized

---

• https://github.com/hackforla/website/issues/6454
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• https://console.cloud.google.com/cloud-resource-manager?authuser=4
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized
• https://github.com/hackforla/website/issues/5812
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• https://github.com/hackforla/live-dashboard-automation/blob/main/Project%20Board%20Dashboard%20Script%20Editable.ipynb
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized
• https://github.com/hackforla/live-dashboard-automation/blob/main/.env
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• Presentation: GitHub Class on Dashboard Creation 11/13/2023
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• https://github.com/hackforla/website/issues/6454
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized

---

• https://github.com/hackforla/ops/issues/15
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• folder: Data Science (community of practice) > Data Science (community of practice) > labels audit
  • [ ] Need access
  • [x] public
  • [x] organized
• Spreadsheet: combined_csv - google sheet
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized
• https://github.com/hackforla/data-science/files/9245408/label.csv (if you click on thsi file it will download a csv)
  • [x] Have access, it's located in ____
  • [ ] public
  • [ ] organized
• 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
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• https://github.com/hackforla/data-science/files/8829277/combined_csv.csv
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized
• https://github.com/hackforla/data-science/tree/160-survey-repo-labels/labels-survey
  • [ ] Need access
  • [x] public
  • [x] organized
• https://github.com/hackforla/data-science/files/10762498/Labels.Survey.Analysis.pdf
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized

---

• Spreadsheet: Labels for Weekly Label Check - the dashboard uses this to indicate authorized labels
  • [ ] Need access
  • [x] public
  • [x ] organized
• https://crontab.guru/
  • [ ] Have access, it's located in ____
  • [x] public
  • [ ] organized
  • https://github.com/orgs/community/discussions/26096
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
  • https://www.youtube.com/watch?v=6WemQlusrJQ&t=1253s
  • [ ] Have access, it's located in ____
  • [ ] public
  • [ ] organized
  • https://github.com/hackforla/website/issues/4152
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
  • https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels#applying-a-label
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
  • https://github.com/hackforla/website/wiki/How-to-create-issues
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
  • https://github.com/hackforla/website/wiki/How-to-read-and-interpret-labels
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
  • https://github.com/hackforla/onboarding-github-issues (got renamed to https://github.com/hackforla/live-dashboard-automation
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
  • https://github.com/hackforla/website/issues/2698
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
  • https://github.com/hackforla/website/issues?q=is%3Aopen+is%3Aissue+label%3A%22ready+for+dev+lead%22
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized
• Live Project Board Issues Dashboard (Current)
  • [ ] Have access, it's located in ____
  • [x] public
  • [x] organized

[Samhitha444]

@ExperimentsInHonesty I have copied all the links from the issues to the above comment, excluding the duplicates.

[ExperimentsInHonesty]

Time Sensitive

• https://github.com/hackforla/website/issues/6454

V1

• https://github.com/hackforla/website/issues/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)

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

Related Projects

• Default Labels
  • https://github.com/hackforla/ops/issues/15 (we will want the dashboard to work for new teams straight away, so having default labels will ensure that)
• Label Survey
  • Repo: data-science, code: labels-survey

Tutorials/Helpfiles and Community Discussion boards

• Presentation: GitHub Class on Dashboard Creation 11/13/2023 - made by the creator of the original dashboard
  • 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

[ExperimentsInHonesty]

Links for you to review and rename

What is the issue number these links come from

Issue 2 (Create a Chart in Looker Dashboard Visualizing Audit of Issues with Missing Labels Over Time #5813)

• Guide on adding workflow dispatch event/button
• Using Urllib.parse
• Documentation on Shillelagh library
• DuckDB API
• What is the name of each of these videos
  • Google Sheets API Automation in Python : Google Sheets API Automation in Python (why did we bookmark it at 250 seconds : the presenter discusses the process of enabling the Google Sheets API and creating the necessary credentials for API access.)
  • Update Google Sheets Using A Service Account With Google Sheets API In Python 🐍 : https://www.youtube.com/watch?v=sVURhxyc6jE&t=2s

Issue 4 (Create Label Report in Google Spreadsheet #5810)

• Google Cloud Console
• Editable version of Python script - no longer resolves

Issue 5 (CoP: Data Science: Survey: Repo Labels #160)

• Spreadsheet: combined_csv - google sheet
• CSV file downloads (if you click on these files it will download a .csv file)
  • https://github.com/hackforla/data-science/files/9245408/label.csv
  • https://github.com/hackforla/data-science/files/8829277/combined_csv.csv
• Labels Survey Analysis.pdf - Author Joshua Susanto
  • I have uploaded it to the folder: Data Science (community of practice) > Data Science (community of practice) > labels audit

Issue 6 (Create Project Board Looker Dashboard for Different Roles #4921)

• https://crontab.guru/
• What is the name of each of these videos
  • Reference 2

[HackforLABot]

@Samhitha444

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, November 4, 2024 at 11:04 PM PST.}

[Samhitha444]

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: I worked on the previous comment titled "Links for you to review and rename". I updated the names of the issues, titles of the youtube links that were there, reason for why the bookmarks that were created. Also figured out the author for one of the links
2. Blockers: None
3. Availability: Atleast 10hrs
4. ETA:
5. Pictures (if necessary):

[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 https://github.com/hackforla/website/issues/7640

• [ ] work on the issue you create

[HackforLABot]

@Samhitha444

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, November 18, 2024 at 11:04 PM PST.}