Create Issues to add new variable github-handle for members in vrms.md

[roslynwythe]

Prerequisites

1. You must be a member of Hack for LA to work on an issue. If you have not joined yet, please follow the steps on our Getting Started page.
2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

As developers we need to create issues to update each project team member in vrms.md with a the new github-handle variable, that will eventually replace the github and picture variables, reducing redundancy in the project file.

Action Items

• [x] For each team member listed in _projects/vrms.md that does not have a variable github-handle, create an issue using the template
• [x] For each issue:
  • [x] In the title, replace [INSERT MEMBER NAME] with the member's name
  • [x] In the title, replace [INSERT PROJECT FILE] with vrms.md
  • [x] Under Action Items, replace [INSERT MEMBER NAME] with the member's name (in 2 places)
  • [x] Under Action Items, replace [INSERT PROJECT FILE] with vrms.md
  • [x] Under Resources, replace [INSERT-PROJECT-FILE] with vrms.md
  • [x] Under Resources, replace [INSERT-PROJECT-FILENAME-WITHOUT-.MD-EXTENSION] with vrms.md
  • [x] Apply the following labels: "ready for dev lead", "good first issue", "role: front end", "role: back end/devOps", "size: 0.25pt", "P-Feature: Project Info and Page"
  • [x] List the issue number in #5441 under Good First Issues
• [x] When all issues have been created and listed, move this issue to the "Questions/In Review" column of the Project Board, and apply the label "ready for dev lead"

Resources/Instructions

https://github.com/hackforla/website/wiki/project.md-file-template https://jekyllrb.com/ Webpage: https://www.hackforla.org/projects/vrms

• This issue is part of #5441

[github-actions[bot]]

Hi @roslynwythe.

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:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[HackforLABot]

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

[t-will-gillis]

Hi @pluto-bell Great job- you have created new issues for adding the github-handle: variable where missing in vrms.md and have listed these issues on #5441. Looks great! Thanks for working on this.

Closing this issue as successfully completed.