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

ER: Use VRMS data to update the meeting times on the CoP page #5328

Closed
4 of 5 tasks
JessicaLucindaCheng opened this issue Aug 28, 2023 · 11 comments
Closed
4 of 5 tasks
Assignees
Labels
Complexity: Large Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request Issue Making: Level 2 Make issue(s) from an ER or Epic P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice role: back end/devOps Tasks for back-end developers size: 0.5pt Can be done in 3 hours or less

Comments

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Aug 28, 2023

Emergent Requirement - Problem

Currently, the meeting times on the Communities of Practice (CoP) page 1 are manually updated in the yml files under _data/internal/communities 2. This can make the meeting times out of date with the meeting times on the Events page 3.

Issue you discovered this emergent requirement in

Date discovered

2023-Aug-06

Did you have to do something temporarily

  • YES
  • NO

Who was involved

@JessicaLucindaCheng

What happens if this is not addressed

We have to continue manually editing the CoP yml files to update meeting times.

Recommended Action Items

  • Make 2 new issues. See "Potential solutions [draft]" section
  • Discuss with team
  • Let a Team Lead know

Potential solutions [draft]

  1. Write an issue with "Complexity: Large" to start pulling the meeting time from the VRMS data similar to how the project's pages 4 using the VRMS data from _data/external/vrms_data.json 5.
  2. Write another issue with a "Complexity: Small" label needs to be written that adds the note below to the "Communities of Practice information updates" form's template 6 "Resources" section. Also, add a "Dependency" section at the top of the issue and add a link to the issue you wrote in 1 above.
If you need to update your meeting times, names, dates, or frequency, please see the [VRMS User Guide](https://github.com/hackforla/VRMS/wiki/User-Guide). The HackforLA.org website gets the meeting times from the updates made to each Community of Practice's meeting data in vrms.io

Resources

Footnotes

  1. Communities of Practice (CoP) page

  2. _data/internal/communities

  3. Events page

  4. https://www.hackforla.org/projects/311-data

  5. https://github.com/hackforla/website/blob/gh-pages/_data/external/vrms_data.json

  6. .github/ISSUE_TEMPLATE/communities-of-practice-information-updates.yml

@JessicaLucindaCheng JessicaLucindaCheng added role: back end/devOps Tasks for back-end developers P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice size: 0.5pt Can be done in 3 hours or less Issue Making: Level 2 Make issue(s) from an ER or Epic Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level labels Aug 28, 2023
@JessicaLucindaCheng

This comment was marked as resolved.

@JessicaLucindaCheng JessicaLucindaCheng changed the title ER: Use VRMS data to update the meeting times on the COP page ER: Use VRMS data to update the meeting times on the CoP page Aug 28, 2023
@wanyuguan wanyuguan added this to the 03.02 Onboarding flow milestone Sep 3, 2023
@kimberlytanyh kimberlytanyh added the ER Emergent Request label Sep 10, 2023
@ExperimentsInHonesty

This comment was marked as resolved.

@JessicaLucindaCheng JessicaLucindaCheng added Draft Issue is still in the process of being created and removed ready for product labels Sep 26, 2023
@JessicaLucindaCheng JessicaLucindaCheng added ready for issue making Complexity: Large Complexity: Small Take this type of issues after the successful merge of your second good first issue and removed Draft Issue is still in the process of being created labels Oct 23, 2023
@ExperimentsInHonesty

This comment was marked as resolved.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels Feb 11, 2024
@JessicaLucindaCheng

This comment was marked as resolved.

@JessicaLucindaCheng

This comment was marked as resolved.

@ExperimentsInHonesty ExperimentsInHonesty removed the ready for dev lead Issues that tech leads or merge team members need to follow up on label May 7, 2024
@del9ra del9ra self-assigned this Jun 23, 2024
Copy link

Hi @del9ra, 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 :)

@ExperimentsInHonesty
Copy link
Member

Here is an example ER and the Large issue that was created from it

@ExperimentsInHonesty ExperimentsInHonesty moved this to ERs and epics that are ready to be turned into issues in P: HfLA Website: Project Board Jun 23, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from ERs and epics that are ready to be turned into issues to In progress (actively working) in P: HfLA Website: Project Board Jun 24, 2024
@del9ra
Copy link
Member

del9ra commented Jun 27, 2024

i. Availability: Monday-Friday 10AM - 3PM
ii. ETA: June 30

@t-will-gillis
Copy link
Member

@del9ra @JessicaLucindaCheng Just want to confirm. I merged #7169 fixes #7072 which addresses Item 1 above. Is there supposed to be an issue for Item 2 as well?

Screenshot 2024-08-10 125651

@del9ra
Copy link
Member

del9ra commented Aug 12, 2024

@del9ra @JessicaLucindaCheng Just want to confirm. I merged #7169 fixes #7072 which addresses Item 1 above. Is there supposed to be an issue for Item 2 as well?

Screenshot 2024-08-10 125651

Hi Will @t-will-gillis , I created a small issue for item 2 #7273

@del9ra
Copy link
Member

del9ra commented Aug 18, 2024

Closing this ER. 2 issues created: small #7273 and large #7072

@del9ra del9ra closed this as completed Aug 18, 2024
@github-project-automation github-project-automation bot moved this from In progress (actively working) to QA in P: HfLA Website: Project Board Aug 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request Issue Making: Level 2 Make issue(s) from an ER or Epic P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice role: back end/devOps Tasks for back-end developers size: 0.5pt Can be done in 3 hours or less
Development

No branches or pull requests

6 participants