Pre-work Checklist: Developer: Kim Le

[Kle012]

Prerequisite

We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.

Overview

As a new developer on the HfLA website team, fill in the following fields as you complete each onboarding item.

Special Notes

1. It may take you a few weeks to finish this issue, because part of it is learning how to provide updates on issues that take more than a week to complete. Please keep this issue open until you have been able to do all the steps.
2. Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues.
3. The action items listed below should mostly be worked on in a sequential order. However, you don't have to wait on one if you can proceed with the others, For instance, you don't have to wait for attending a weekly meeting before setting up your dev environment.

Action Items

• Add yourself to the #hfla-site and #hfla-site-pr Slack channels
  • To find contact information for the merge team members and technical leads, please take a look at our Meet the Team wiki page
• Add yourself to the team roster
• After you have finished adding yourself to the roster, let a merge team member or a technical lead know you have added yourself to the roster and would like to be added to the website-write and website teams on GitHub
• Self Assign this issue (gear in right side panel)
• Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
• Add this issue to the Project Board under the Projects section (gear in right side panel)
• Signup for a Figma account
• Attend weekly team meetings:
  • Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
  • (Optional) Office Hours, Thursdays 7-8pm PST
  • All team meeting (UX, Development, Product), Sunday 10am-12pm PST
• Note: There are no meetings on the 1st-7th of every month.
• Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know (through a slack message in the hfla-site channel as well as an @ mention in a comment of the issue that you would be working on) if you are planning to take a week off or a longer vacation.
• Complete steps 1.1 - 1.6 in Part 1: Setting up the development environment within Contributing.md
  • OPTIONAL: If you run into any issues, use 4.1 How do I ask for help within Contributing.md as a visual example to get a hold of our HfLA website leadership team. That way we can help you resolve any set up issues immediately.
• Read section 2.1 - 2.4 in Part 2: How the Website team works with GitHub issues within Contributing.md
  • Follow the steps in section 2.3 Where can I find GitHub issues to work on? to assign yourself your first issue under the Project Board's Prioritized Backlog column and use 2.7 Working on a Issue within Contributing.md to start working on your issue
  • Read 2.6 What to do when you need to stop mid issue
• Once you take a good first issue, you will provide estimates and progress reports. Also, once you finish providing your "Estimate" action item below, please answer the question in the "Time spent so far" action item (also below).
  • Estimate: Copy the below and put it in the "good first issue" that you picked.
    Check this box when you have completed this task so that we can identify if you understood the instructions and know what to do on all subsequent issues upon assignment. (Note: Please provide estimates on all the issues that you pick up, going forward.)

  Availability for this week:
  My estimated ETA for completing this issue:
  

  • Time spent so far: Copy the question below into a new comment below (in this pre-work issue only) and answer it. This is just to get feedback on how long it took you to get to this point on this pre-work. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace.

  How many hours did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue, including attending your first meetings?
  

  • Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report. If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. This update should be done every week for every issue that you are assigned to. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.

  Provide Update
  1. Progress
  2. Blockers
  3. Availability
  4. ETA
  

• Read sections 3.1.a - 3.1.c in 3.1 How to make a pull request to learn more about how to make a pull request (PR) for the issue that you are working on and how to make changes to your PR if changes are requested by the reviewer
• Additional notes:
  • Please don't forget to review pull requests whenever you are able to. The How to review Pull Requests guide will teach you how to review pull requests.
  • Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.
• Read and understand how we progress through issues. Then, you can check this off.
  Progress through issues in the prioritized backlog only with increasing complexity in the following order:
  • Good first issue (two per person)
  • Small (one per person, with some exceptions, see below)
  • Medium (you can work on more than one medium issue, but only one at a time)
  • Large (you can work on more than one large issue, but only one at a time)
    • The reasons for this progression are:
      • The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
      • We are trying to teach you the team methodology through the issues themselves.
      • It ensures you understand what we expect and the quality of contributions.
    • You can work on back-to-back small issues if it meets the following criteria:
      • You are learning something new and need to work on an issue of a lesser complexity
      • Special request by a lead or pm
• Read the Start Here - Developers in Figma
• Go familiarize yourself with the Hack for LA Design System page in Figma (where you can see components and their SCSS classes)
• Once all tasks are completed, close this issue. This issue will remain open until you get through your first progress report. Once you have done that, we are confident you know how to keep the momentum going on your issue and keep your team informed.

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

• First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
• Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
• Also, you can post your question on the hfla-site slack channel and link the issue you're working on, so other developers can see and respond.
• Lastly, you can add the issue to the "Development team meeting discussion items" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.

Resources/Instructions

• Contributing.md - Hack for LA
• GitHub Project Board - Hack for LA
• GitHub Project Board Prioritized Backlog highlighted and sorted by Front End
• GitHub Project Board Prioritized Backlog highlighted and sorted by Back End/DevOps
• Figma - Hack for LA
• Google Drive - Hack for LA website team
• Agenda / Notes - Dev Team Tuesday meeting
• Agenda / Notes - All Team meeting
• How to review Pull Requests

[Kle012]

Update:

1. Progress: Completed steps 1.1 - 1.6. Read sections 2.1 - 2.4 and 2.6. Self-assigned myself to the first good issue, and completed the 'Estimate' comment in the self-assigned first good issue. Completed 'Time spent so far' and 'Progress Reports' comments in this pre-work issue.
2. Blockers: Unable to install Docker. Received help from the Slack HackforLA Engineering channel.
3. Availability: 5 hours this week to work on this issue
4. ETA: within 2 weeks

[Kle012]

How many hours did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue, including attending your first meetings?
7 weeks

[Kle012]

Completed.

[Kle012]

5 - GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES update

on what issue did you give your first weekly update?

• Pre-work Checklist: Developer: Kim Le #6341

return to section 5

[Kle012]

6 - PULL REQUESTS update

What is the number of your first merged pull request?

• Add GitHub-handle for Nandana Rao - #6174 #6629

Did you receive any reviews that required you to change anything on your PR?

• no
• yes (if yes, describe what you learned)

Comments:

return to section 6

[Kle012]

7 - ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES update

How many hours did it take you to finish this step?

A: 2 hours

Do you have any questions about what you read?

• yes, I had questions, and I left comments in the appropriate issues [WE NEED TO UPDATE THOSE TWO RESOURCES TO HAVE LINKS TO ISSUES WHERE PEOPLE CAN PUT QUESTIONS AND MOVE THE ISSUES TO THE QUESTIONS/REVIEW COLUMN]
• no, I did not have any questions

return to section 7

[Kle012]

8 - MOVE ON TO 2ND GOOD FIRST ISSUE update

What is the number of your 2nd merged pull request?

• Add github-handle for Melinda Sukosd #6678

Did you receive any reviews that required you to change anything on your PR?

• no
• yes (if yes, describe what you learned): I learned that in the "Why did you make the changes" section, I should be more descriptive in explaining why the change was necessary for the website

Comments: #6678 (comment)
"Hello @Kle012! Great job on your first issue. The changes requested on #5880 have been done correctly. However, in the "Why did you make the changes" section of this pull request description please describe why this change was necessary in regards to the overall website. For instance, you can put something like "To reduce redundancy in the project file" to make that section more clear."

return to section 8

[Kle012]

Progress: Completed 2nd good first issue. Need to reviews 5 good first issues
Blockers: N/A
Availability: 0
ETA: Within a month

[Kle012]

9 - PULL REQUEST REVIEWS - GFI - Update

There are currently no good first issue PRs to review, but ill check back later.

return to section 9

[Kle012]

10 - UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING update

Up to now we have just been getting you ready. Now the fun starts. Are you continuing?

• I'm so ready, bring it on (continuing)
• I am worn out from the setup and the good first issues but still game (continuing)
• I won't be continuing, (please let us know why and close this issue)

Comments:

return to section 10

[Kle012]

11 - SMALL update

What is the number of your small merged pull request?

• img Tag Refactor in Contributing.md page  #7068

Did you receive any reviews that required you to change anything on your PR?

• no
• yes (if yes, describe what you learned)

Comments: I learned how to handle backslashes glitch in VSCode by bypass it and fix the error on my Github PR on the files changed tab

return to section 11

[Kle012]

12 - PULL REQUEST REVIEWS - Small - Update

There are currently no small PRs to review, but i'll check back later.

return to section 12

[Kle012]

1. Progress: Working on section 13: making issues. Will need to check back for pull request review for first good issue and small
2. Blockers: Unable to find pull request to reviews
3. Availability: 4 hours
4. ETA: End of week, if found issues

[Kle012]

Progress: Working on section 13: making issues (waiting for ER to accept by the merge team).
Blockers: Need to check back for pull request review
Availability: NA
ETA: End of week, if the issue was created properly and accepted by the merge team

[Kle012]

13 - GET EXPERIENCE MAKING ISSUES - LEVEL 1 (GFI & Small) update

Which EPIC or ER did you work on (provide the issue number)

#7158

How many hours did it take you to make the issue(s)?

Number of hours: 1

Did you find anything required clarification or anything we could improve about the instructions?

Suggestions for improvement: N/A

return to section 13

[Kle012]

Progress: Completed section 13. Merge team approved
Blockers: None
Availability: None
ETA: N/A

[HackforLABot]

@Kle012

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, January 27, 2025 at 11:04 PM PST.}