Create Issues to add new variable github-handle for members in lucky-parking.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 lucky-parking.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

• For each team member listed in _projects/lucky-parking.md that does not have a variable github-handle, create an issue using the template
• For each issue:
  • In the title, replace [INSERT MEMBER NAME] with the member's name
  • In the title, replace [INSERT PROJECT FILE] with lucky-parking.md
  • Under Action Items, replace [INSERT MEMBER NAME] with the member's name (in 2 places)
  • Under Action Items, replace [INSERT PROJECT FILE] with lucky-parking.md
  • Under Resources, replace [INSERT-PROJECT-FILE] with lucky-parking.md
  • Under Resources, replace [INSERT-PROJECT-FILENAME-WITHOUT-.MD-EXTENSION] with lucky-parking
  • Apply the following labels: "ready for merge team", "good first issue", "role: front end", "role: back end/devOps", "size: 0.25pt", "P-Feature: Project Info and Page"
  • List the issue number in Epic: Create issues to add github-handle to leadership teams #5441 under Good First Issues
• 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 merge team"

Resources/Instructions

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

• This issue is part of Epic: Create issues to add github-handle to leadership teams #5441

[HackforLABot]

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

[Kle012]

i. Availability: EOD
ii. ETA: within 2 weeks

[jphamtv]

Great work creating these issues @Kle012. They're well-written and ready for the team to prioritize.