Update Project Profile: HackforLA Site

[daras-cu]

Overview

The project team from Hack for LA website needs its project leadership variable information updated, so that the current team members can be properly displayed on the Hack for LA website.

Action Items

• Review the Project Update Data below and then follow the instructions for either adding or deleting team members from the project's .md

Adding new volunteers to team page

• Create a new issue using the add new leader to project template
• Customize the title with name of project and person to add
• Customize the body
  • In the ER, go to the value under the line "Project Card URL"
    • Copy the file name
    • On the line that starts "- [ ] In your IDE…" replace brackets with the copy (the text we are expecting is a file name with the extension .md)
  • In the copy block below the line that starts, "Find the leadership variable and add the following profile." add all the information from the ER for the person you are adding.
  • On the checkbox line below, "- [ ] Verify the changes by viewing..." replace with name of project
  • to Resource 2, find the project on the https://www.hackforla.org/projects/ page
    • click on its link
    • copy link
    • replace brackets on resource 2 with the URL
• Choose Create button
• Under Relationships, add this epic or ER as a parent to the issue you just created
• Add milestone 03.02 Onboarding flow
• Review, and if ready, apply label ready for merge team
• At the bottom of this issue description, next to "Create sub-issue", click the drop-down menu arrow. Then, click "Add existing issue", search for the issue you just created, and select that issue to add as a sub-issue.
• Add the URL to a comment on this ER
  • if this is the first add leader issue to be created, paste this into a comment and add the URL of the issue you just created.

### Adding Leader issues
-

### Complete
- [ ] Check this when all the Add leader issues have been made

• if the above comment already exists, just add your new issue URL to the list.
• Check off the box, if it's the last one that needed to be created.

Removing volunteers from team page

• Create a new issue using the remove leader from project template
• Customize the title with name of project and person to remove
• Customize the body
  • In the epic, go to the value under the line "Project Card URL"
    • Copy the file name
    • On the line that starts "- [ ] In your IDE…" replace brackets with the copy (the text we are expecting is a file name with the extension .md)
  • Go to https://github.com/hackforla/website/tree/gh-pages/_projects and find and click on the file
    • click on code view
    • copy the code block
    • highlight the text on your new issue where it says [Insert the lines of code to remove the specified leadership member] and delete it and replace with the copy block
  • On the checkbox line below, "- [ ] Verify the changes by viewing..." replace with name of project
  • to Resource 2, find the project on the https://www.hackforla.org/projects/ page
    • click on its link
    • copy link
    • replace brackets on resource 2 with the URL
• Choose Create button
• Under Relationships, add this epic or ER as a parent to the issue you just created
• Add milestone Onboarding flow
• Review, and if ready, apply label ready for merge team
• At the bottom of this issue description, next to "Create sub-issue", click the drop-down menu arrow. Then, click "Add existing issue", search for the issue you just created, and select that issue to add as a sub-issue.
• Add the URL to a comment on this ER
  1. if this is the first remove leader issue to be created, paste this into a comment on this issue and add the URL of the issue you just created.

### Removing Leader issues
-

### Complete
- [ ] Check this when all the removal issues have been made

• if the above comment already exists, just add your new issue URL to the list.
• Check off the box, if it's the last one that needed to be created.

• When you have completed making all the add and remove issues
  • move this issue into the Questions/Review column
  • add the ready for merge team label

For Merge Team Members

• Check each sub-issue created for this ER/epic
  • For each sub-issue that is ready, apply a ready for prioritization label
• If all sub-issues have been created so that the request in this ER/epic has been fulfilled, apply a ready for product label to this ER/epic

Project Update Data

---

Project Name

Hackforla.org Website

Project Card URL

website.md

Update the Title?

NO

Title

No response

Update the Description?

NO

Description

No response

Update the Hero Image?

NO

Hero Image

No response

Update the Image?

NO

Image

No response

Update the Technologies?

NO

Technologies (maximum 26 characters per technology name)

No response

Update the Partner(s)?

NO

Partners

No response

Update the Tools?

NO

Tools

No response

Update GitHub Link?

NO

GitHub Link

No response

Do you have any additional (other than your primary) GitHub repositories that your volunteers make issues or PRs against?

NO

If yes, list the repo URLs here

No response

Update Slack Link?

NO

Slack Link

No response

Update Test Site Link?

NO

Test Site Link

No response

Update Demo Site Link?

NO

Demo Site Link

No response

Update Site Link?

NO

Site link

No response

Remove person(s) and info from Leadership?

YES

If YES on remove person(s), edit the below to provide the information required. If NO, delete the template in the field below:

Name: Ryan Keller

Add person(s) and info to Leadership?

YES

If YES on add person(s), edit the below to provide the information required. If NO, delete the template in the field below:

Name: Jose Santiago
GitHub Handle: santi-jose
Role: Merge Team
Slack Member ID: U091RQ37UBC

Name: Maleah Castillo Smith
GitHub Handle: castillios
Role: Merge Team
Slack Member ID: U0AUK3E8K6Y

Project Status

Active

Additional Instructions for Website Team Leads After This Issue is Submitted (do NOT edit text below)

Here are the instructions for how to process this request to make it ready for issues to be made out of it: #7478 (comment)