Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor JavaScript so that Project Meetings page sources meeting data from vrms_data.json #6059

Open
6 tasks done
roslynwythe opened this issue Jan 4, 2024 · 8 comments · May be fixed by #7873
Open
6 tasks done
Assignees
Labels
Complexity: Medium P-Feature: Project Meetings https://www.hackforla.org/project-meetings role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Jan 4, 2024

Dependency

Overview

As developers we need to refactor the JavaScript behind the Project Meetings page, so that it retrieves meeting data from the file data/external/vrms_data.json, in order to reduce the latency and improve the reliability of the webpage.

Action Items

  • For reference, view the code in assets/js/right-col-content.js and understand how the event data is retrieved from assets/js/utility/vrms-events.js
  • Refactor the code in assets/js/project-meetings.js to source data from data/external/vrms_data.json, using function(s) in assets/js/utility/vrms-events.js and perform testing to confirm that functionality on the Project Meetings webpage 1 is unchanged.
  • Note that events from all projects should be displayed, except for events with the project name "test" or "Hack4LA".
  • Open the file assets/js/right-col-content.js and refactor the code to reference the function(s) in assets/js/utility/vrms-events.js and perform testing to confirm that functionality on the Project pages[^2] is unchanged.

Resources/Instructions

Footnotes

  1. Project Meetings webpage

@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing Draft Issue is still in the process of being created role missing Complexity: Missing Complexity: Medium labels Jan 4, 2024

This comment has been minimized.

@roslynwythe roslynwythe added role: front end Tasks for front end developers Complexity: Medium P-Feature: Project Meetings https://www.hackforla.org/project-meetings size: 1pt Can be done in 4-6 hours Dependency An issue is blocking the completion or starting of another issue and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing Draft Issue is still in the process of being created role missing Complexity: Missing labels Jan 4, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the Draft Issue is still in the process of being created label Mar 4, 2024
@roslynwythe roslynwythe removed the Draft Issue is still in the process of being created label Apr 10, 2024
@daras-cu daras-cu moved this from Ice box to New Issue Approval in P: HfLA Website: Project Board Sep 24, 2024
@daras-cu daras-cu added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Dependency An issue is blocking the completion or starting of another issue labels Sep 24, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to Make Issues: ERs and epics in P: HfLA Website: Project Board Sep 24, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from Make Issues: ERs and epics to New Issue Approval in P: HfLA Website: Project Board Sep 24, 2024
@aadilahmed aadilahmed self-assigned this Oct 31, 2024
@HackforLABot HackforLABot moved this from Prioritized backlog to New Issue Approval in P: HfLA Website: Project Board Oct 31, 2024
@aadilahmed aadilahmed moved this from New Issue Approval to In progress (actively working) in P: HfLA Website: Project Board Oct 31, 2024
@aadilahmed aadilahmed self-assigned this Oct 31, 2024
@HackforLABot HackforLABot moved this from In progress (actively working) to New Issue Approval in P: HfLA Website: Project Board Oct 31, 2024
@HackforLABot

This comment has been minimized.

@aadilahmed aadilahmed moved this from New Issue Approval to Prioritized backlog in P: HfLA Website: Project Board Oct 31, 2024
@theogguu theogguu self-assigned this Nov 12, 2024
@HackforLABot

This comment has been minimized.

@HackforLABot HackforLABot moved this from Prioritized backlog to New Issue Approval in P: HfLA Website: Project Board Nov 12, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to Prioritized backlog in P: HfLA Website: Project Board Jan 21, 2025
@innith innith self-assigned this Jan 22, 2025
@HackforLABot

This comment has been minimized.

@innith
Copy link
Member

innith commented Jan 22, 2025

Hi @innith, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

Availability (PST):
Wednesday: 4:30 AM to 9:30 AM
Friday: 7:30 PM to Saturday 4:30 AM
Saturday: 7:30 PM to Sunday 4:30 AM
ETA:
expected by Sunday.

@innith innith moved this from Prioritized backlog to In progress (actively working) in P: HfLA Website: Project Board Jan 22, 2025
@innith

This comment has been minimized.

@HackforLABot HackforLABot added the To Update ! No update has been provided label Jan 31, 2025
@HackforLABot
Copy link
Contributor

@innith

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

innith added a commit to innith/website that referenced this issue Feb 2, 2025
…oject-Meetings-page-sources-meeting-data-from-vrms_data.json-hackforla#6059
@innith innith removed the To Update ! No update has been provided label Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium P-Feature: Project Meetings https://www.hackforla.org/project-meetings role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours
Projects
Status: In progress (actively working)
8 participants