Skip to content

Update Project Profile: HackforLA Site #8789

Closed
0 of 1 issue completed
Closed
Update Project Profile: HackforLA Site#8789
0 of 1 issue completed
Assignees
computarisis
Labels
Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelIssue Making: Level 1Make issues from a template and a spreadsheetP-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)epicgood first issueGood for newcomersnon-PR contributionFor wiki additions/revisions, audit spreadsheet contributions, issue-making ERs and Epics, etc.ready for productrole: back end/devOpsTasks for back-end developersrole: front endTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hourstime sensitiveNeeds to be worked on by a particular timeframe
Milestone
03.02 Onboarding flow

Description

@daras-cu
daras-cu
opened on Sep 16, 2026

Prerequisite

  1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started Page.
  2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

The Hackforla.org Website project team 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 3, find the project on the https://www.hackforla.org/projects/ page
      • click on its link
      • copy link
      • replace brackets on resource 3 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

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: Sushma Ramachandra Hegde
GitHub Handle: sushma110396
Role: Merge Team
Slack Member ID: U0AUC3E1D2R

Project Status

Active

Activity

  1. daras-cu
    added
    role: front endTasks for front end developers
    role: back end/devOpsTasks for back-end developers
    P-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)
    time sensitiveNeeds to be worked on by a particular timeframe
    Complexity: SmallTake this type of issues after the successful merge of your second good first issue
    epic
    size: 0.25ptCan be done in 0.5 to 1.5 hours
    Issue Making: Level 1Make issues from a template and a spreadsheet
    Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty level
    on Sep 16, 2026
  2. github-project-automation
    moved this to New Issue Approval in P: HfLA Website: Project Boardon Sep 16, 2026
  3. github-project-automation
    added this to P: HfLA Website: Project Boardon Sep 16, 2026
  4. daras-cu
    added
    good first issueGood for newcomers
    non-PR contributionFor wiki additions/revisions, audit spreadsheet contributions, issue-making ERs and Epics, etc.
    and removed
    Complexity: SmallTake this type of issues after the successful merge of your second good first issue
    on Sep 16, 2026
  5. daras-cu
    moved this from New Issue Approval to ERs and epics that are ready to be turned into issues in P: HfLA Website: Project Boardon Sep 16, 2026
  6. computarisis
    self-assigned this
    on Sep 16, 2026

  7. HackforLABot commented on Sep 16, 2026

    @HackforLABot
    HackforLABot
    on Sep 16, 2026
    Contributor

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

  8. computarisis commented on Sep 16, 2026

    @computarisis
    computarisis
    on Sep 16, 2026
    Member

    Availability for this week: Every day after 8PM ET
    My estimated ETA for completing this issue: Thu, Sep 17th by 10pm

  9. computarisis
    added this to the 03.02 Onboarding flow milestone on Sep 18, 2026
  10. computarisis
    added a parent issue on Sep 18, 2026
  11. computarisis
    added
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Sep 18, 2026

  12. computarisis commented on Sep 18, 2026

    @computarisis
    computarisis
    on Sep 18, 2026
    Member

    Adding Leader issues

    -#8791

    Complete

    • Check this when all the Add leader issues have been made
  13. computarisis
    moved this from ERs and epics that are ready to be turned into issues to Questions / In Review in P: HfLA Website: Project Boardon Sep 18, 2026
  14. daras-cu
    removed a parent issue on Sep 20, 2026
  15. daras-cu
    added a sub-issue on Sep 20, 2026

  16. daras-cu commented on Sep 20, 2026

    @daras-cu
    daras-cu
    on Sep 20, 2026
    MemberAuthor

    @computarisis thanks for working on this, the issue you created looks good. One small thing, you set the new issue as the parent of this issue, when it should have been the opposite. I fixed it so you're good to go.

  17. daras-cu
    closed this as completedon Sep 20, 2026
  18. github-project-automation
    moved this from Questions / In Review to QA in P: HfLA Website: Project Boardon Sep 20, 2026
  19. daras-cu
    added
    ready for product
    and removed
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Sep 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelIssue Making: Level 1Make issues from a template and a spreadsheetP-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)epicgood first issueGood for newcomersnon-PR contributionFor wiki additions/revisions, audit spreadsheet contributions, issue-making ERs and Epics, etc.ready for productrole: back end/devOpsTasks for back-end developersrole: front endTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hourstime sensitiveNeeds to be worked on by a particular timeframe

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions