search

hackforla / website

Hack for LA's website
https://www.hackforla.org
GNU General Public License v2.0
325 stars 778 forks source link

Epic: Dashboards planning #6614

Open ExperimentsInHonesty opened 7 months ago

ExperimentsInHonesty commented 7 months ago

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:

See resources for all the issues we were able to find

Action Items

Resources/Instructions

List of Repos involved

Dashboard Summary

Dashboard URLs

Project board for all Dashboard Issues

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

Website

Internship

Data Science

team-analytics

ExperimentsInHonesty commented 7 months ago

left off at need to

ExperimentsInHonesty commented 7 months ago

@kellyc9 see comment above

ExperimentsInHonesty commented 7 months ago

As a test with @t-will-gillis

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

ExperimentsInHonesty commented 7 months ago

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 commented 7 months ago

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

ExperimentsInHonesty commented 7 months ago

We left off on the internship project.

ExperimentsInHonesty commented 7 months ago
ExperimentsInHonesty commented 7 months ago
ExperimentsInHonesty commented 7 months ago
ExperimentsInHonesty commented 7 months ago

skills / productivity Links

issues dashboard links

ExperimentsInHonesty commented 7 months ago

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

The above link is a link to a spreadsheet.

github-actions[bot] commented 7 months ago

@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.

  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, April 30, 2024 at 12:06 AM PST.

ExperimentsInHonesty commented 7 months ago

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

github-actions[bot] commented 6 months ago

@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.

  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, May 14, 2024 at 12:06 AM PST.

github-actions[bot] commented 6 months ago

@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.

  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, May 21, 2024 at 12:06 AM PST.

github-actions[bot] commented 5 months ago

@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.

  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, June 4, 2024 at 12:06 AM PST.

github-actions[bot] commented 5 months ago

@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.

  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, June 11, 2024 at 12:06 AM PST.

github-actions[bot] commented 5 months ago

@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.

  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, June 18, 2024 at 12:06 AM PST.

github-actions[bot] commented 5 months ago

@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.

  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 Wednesday, June 19, 2024 at 1:48 PM PST.

ExperimentsInHonesty commented 4 months ago
ExperimentsInHonesty commented 4 months ago

@Eleftherios06,

ExperimentsInHonesty commented 4 months ago

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

github-actions[bot] commented 4 months ago

@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.

  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, July 30, 2024 at 12:05 AM PST.

github-actions[bot] commented 3 months ago

@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.

  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, August 6, 2024 at 12:04 AM PST.

HackforLABot commented 3 months ago

@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.

  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, August 13, 2024 at 12:14 PM PST.

ExperimentsInHonesty commented 3 months ago

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

They will need to be properly labeled later.

mayankt153 commented 3 months ago

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

mayankt153 commented 3 months ago

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.

ExperimentsInHonesty commented 2 months ago

Missing the Dashboard link for:

ExperimentsInHonesty commented 2 months ago

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

ExperimentsInHonesty commented 2 months ago

Go through the Dashboard project roadmap and review the issues links inside the issues for ORG https://github.com/orgs/hackforla/projects/88/views/4

Rabia2219 commented 2 months ago

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

A new project board view has been created HfLA Dashboards: Project Board, GitHub Org Repos Analysis

Samhitha444 commented 2 months ago

Found a link that was not public.

ExperimentsInHonesty commented 2 months ago

If you have an issue related to one of your dashboards that has an RP000 type number, look for its corresponding wiki page on this link and include it in your roadmap WIKI pages from TWE by research plan number

ExperimentsInHonesty commented 2 months ago

We need to sort out

ExperimentsInHonesty commented 2 months ago

There are some resources that are in this repo that would be helpful to all people working on writing api calls for looker dashaboards. Also we probably want to put all our looker dashboard python scripts in this repo so that we don't recreate the same scripts over and over, but that will require a rework of the readme, which right now is specific to the issues dashboard.

https://github.com/hackforla/live-dashboard-automation

Relevant to Issues Dashboard Roadmap

ExperimentsInHonesty commented 2 months ago

Mayank issues tab - Skills Org issues tab - Samhitha Timecard issues tab - Sofiat, done Timecrd roadmap - Sofiat Eleftherios - Org roadmap Samhitha - Issues roadmap

ExperimentsInHonesty commented 2 months ago

The Issues' dashboard had this as a goal, and we are thinking (at least for now) of making this a separate dashboard with its own requirements.

Notes: 2 week inactive label what do we do now what do we want to accomplish what kind of data would we need

ExperimentsInHonesty commented 2 months ago

Individual dashboard epics

ExperimentsInHonesty commented 1 month ago

Internship looker files. You can access them by logging into internship-ba@hackforla.org image

HackforLABot commented 1 month ago

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

HackforLABot commented 1 month ago

@mayankt153, @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 Tuesday, October 22, 2024 at 12:04 AM PST.

ExperimentsInHonesty commented 1 month ago

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)
HackforLABot commented 3 weeks ago

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

HackforLABot commented 2 weeks ago

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

ExperimentsInHonesty commented 1 week ago
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 commented 2 days ago

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.