website icon indicating copy to clipboard operation
website copied to clipboard
verified publisher icon hackforla

Epic: Issues Dashboard

Open Samhitha444 opened this issue 1 year ago • 61 comments

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

Time Sensitive

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

V1

V2 Dashboard (looker)

Documentation

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

Data

GitHub Actions that support Dashboard

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
    • 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 https://github.com/hackforla/data-science/issues/160
    • Google Drive folder: Data Science (community of practice) > Data Science (community of practice) > labels audit
    • 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

Samhitha444 avatar Sep 22 '24 18:09 Samhitha444

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:

github-actions[bot] avatar Sep 22 '24 18:09 github-actions[bot]

List of issue related to the issue dashboard. Can also be seen on the P: HfLA Dashboards: Project Board, Issues tab

  • [ ] 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

Samhitha444 avatar Oct 06 '24 17:10 Samhitha444

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

HfLA website: Dashboard Roadmap: Org Dashboard

ExperimentsInHonesty avatar Oct 06 '24 18:10 ExperimentsInHonesty

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

HackforLABot avatar Oct 18 '24 07:10 HackforLABot

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

Samhitha444 avatar Oct 20 '24 16:10 Samhitha444

@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
  • [x] 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
  • [x] 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
  • [x] 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
  • [x] 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
    • [x] 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
    • [x] 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
    • [x] 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
    • [x] 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
    • [x] 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
    • [x] 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
    • [x] 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

ExperimentsInHonesty avatar Oct 20 '24 17:10 ExperimentsInHonesty

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

Samhitha444 avatar Oct 27 '24 08:10 Samhitha444

Time Sensitive

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

V1

V2 Dashboard (looker)

Documentation

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

Data

GitHub Actions that support Dashboard

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
    • 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 https://github.com/hackforla/data-science/issues/160
    • Google Drive folder: Data Science (community of practice) > Data Science (community of practice) > labels audit
    • 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

ExperimentsInHonesty avatar Nov 03 '24 18:11 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)

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

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

Overview from issue: We need to survey labels across the organization so that we can rationalize and do automation and org-wide audits.

  • [x] Spreadsheet: combined_csv - google sheet
  • [x] CSV file downloads (if you click on these files it will download a .csv file)
    • [x] https://github.com/hackforla/data-science/files/9245408/label.csv
    • [x] https://github.com/hackforla/data-science/files/8829277/combined_csv.csv
  • [x] 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)

  • [x] https://crontab.guru/
  • [x] What is the name of each of these videos

ExperimentsInHonesty avatar Nov 03 '24 18:11 ExperimentsInHonesty

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

HackforLABot avatar Nov 08 '24 07:11 HackforLABot

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):

Samhitha444 avatar Nov 10 '24 18:11 Samhitha444

  • [ ] 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

ExperimentsInHonesty avatar Nov 10 '24 19:11 ExperimentsInHonesty

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

HackforLABot avatar Nov 22 '24 07:11 HackforLABot

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. https://github.com/hackforla/website/issues/7505#issuecomment-2453521749

ExperimentsInHonesty avatar Nov 27 '24 21:11 ExperimentsInHonesty

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

HackforLABot avatar Feb 07 '25 07:02 HackforLABot

Links we still have to sort out

  • [x] https://leonardomontini.dev/github-action-manual-trigger/
  • [x] https://docs.python.org/3/library/urllib.parse.html
  • [x] https://duckdb.org/docs/api/python/overview.html
  • [x] https://console.cloud.google.com/cloud-resource-manager?authuser=4
  • [x] https://github.com/hackforla/live-dashboard-automation/blob/main/Project%20Board%20Dashboard%20Script%20Editable.ipynb
  • [x] https://github.com/hackforla/data-science/files/10762498/Labels.Survey.Analysis.pdf
  • [x] https://www.youtube.com/watch?v=6WemQlusrJQ&t=1253s

Completion notes

  • All links got added to summary of links comment https://github.com/hackforla/website/issues/7505#issuecomment-2453521636
    • the summary comment will eventually get hidden when the summary gets added to the top of this issues

ExperimentsInHonesty avatar Feb 09 '25 18:02 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 avatar Feb 09 '25 20:02 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

ExperimentsInHonesty avatar Feb 09 '25 20:02 ExperimentsInHonesty

@amen-ikamba

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 10, 2025 at 11:04 PM PST.

HackforLABot avatar Feb 14 '25 07:02 HackforLABot

  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.

amen-ikamba avatar Feb 14 '25 12:02 amen-ikamba

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.

ExperimentsInHonesty avatar Feb 16 '25 19:02 ExperimentsInHonesty

  • 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
  • Google Drive folder: Data Science (community of practice) > Data Science (community of practice) > labels audit
  • Repo: Data Science
    • 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

ExperimentsInHonesty avatar Feb 16 '25 20:02 ExperimentsInHonesty

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

HackforLABot avatar Feb 28 '25 07:02 HackforLABot

@amen-ikamba

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, March 3, 2025 at 11:04 PM PST.

HackforLABot avatar Mar 07 '25 07:03 HackforLABot

@amen-ikamba

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, March 11, 2025 at 12:05 AM PST.

HackforLABot avatar Mar 14 '25 07:03 HackforLABot

@amen-ikamba

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, March 18, 2025 at 12:05 AM PST.

HackforLABot avatar Mar 21 '25 07:03 HackforLABot

Progress: I have created the requirements issue and have started on the comparative analysis document Blockers: I have had a confusion around the V1 and V2 features when it came to the comparative analysis Availability: 2 hours ETA: By the end of March

amen-ikamba avatar Mar 23 '25 09:03 amen-ikamba

@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 Tuesday, April 1, 2025 at 12:05 AM PST.

HackforLABot avatar Apr 04 '25 07:04 HackforLABot

@amen-ikamba

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, April 8, 2025 at 12:05 AM PST.

HackforLABot avatar Apr 11 '25 07:04 HackforLABot

@amen-ikamba

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, April 15, 2025 at 12:05 AM PST.

HackforLABot avatar Apr 18 '25 07:04 HackforLABot