website icon indicating copy to clipboard operation
website copied to clipboard

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

Open JessicaLucindaCheng opened this issue 2 years ago • 8 comments

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

  • #5132

Date discovered

2023-Aug-06

Did you have to do something temporarily

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

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

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

  • #7072

JessicaLucindaCheng avatar Aug 28 '23 21:08 JessicaLucindaCheng

@hackforla/website-pm After the CoP page's meeting times are updated using VRMS data, is the following wording what you want to be added to the "Resources" section of the Communities of Practice information updates form?

If you need to update your meeting times, names, dates, or frequency, please see the VRMS 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

I wasn't sure if this was the correct process for CoP leads to update their meeting times in VRMS.

JessicaLucindaCheng avatar Aug 28 '23 21:08 JessicaLucindaCheng

@JessicaLucindaCheng YES

ExperimentsInHonesty avatar Sep 26 '23 00:09 ExperimentsInHonesty

@JessicaLucindaCheng I made changes to item 1 under potential solutions and added Resources 5 to indicate the location of the VRMS data. We are trying to get away from pull the data directly from VRMS live and instead pull it from our own data store (which pulls it nightly from VRMS).

ExperimentsInHonesty avatar Feb 11 '24 19:02 ExperimentsInHonesty

@ExperimentsInHonesty

@JessicaLucindaCheng I made changes to item 1 under potential solutions and added Resources 5 to indicate the location of the VRMS data. We are trying to get away from pull the data directly from VRMS live and instead pull it from our own data store (which pulls it nightly from VRMS).

Good catch! Sorry, I missed that. Thanks for making the edits!

JessicaLucindaCheng avatar Feb 11 '24 21:02 JessicaLucindaCheng

@roslynwythe

I addressed Bonnie's comment and I made some minor edits to clarify the anticipated complexity of the issues under "Potential Solutions". It is ready for you to review to see if it is ready for prioritization. Thanks.

JessicaLucindaCheng avatar Feb 11 '24 21:02 JessicaLucindaCheng

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

github-actions[bot] avatar Jun 23 '24 17:06 github-actions[bot]

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

  • ER: https://github.com/hackforla/website/issues/6687
  • Large issue: https://github.com/hackforla/website/issues/6775

ExperimentsInHonesty avatar Jun 23 '24 17:06 ExperimentsInHonesty

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

del9ra avatar Jun 27 '24 17:06 del9ra

@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

t-will-gillis avatar Aug 10 '24 19:08 t-will-gillis

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

del9ra avatar Aug 12 '24 21:08 del9ra

Closing this ER. 2 issues created: small https://github.com/hackforla/website/issues/7273 and large https://github.com/hackforla/website/issues/7072

del9ra avatar Aug 18 '24 17:08 del9ra