Pre-work Checklist: Developer: Carlos Perez

[Carlos-A-P]

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.

Action Items

• Add the "role: front end" or "role: back end" label*(s) to this issue and remove the "role missing" label
• Add yourself to the #hfla-site and #hfla-site-pr Slack channels
• Share your Gmail address with the team lead so you can be added to the Google Drive
• (Once added to the Drive) Add yourself to the team roster
• Confirm with the team lead that they have added you to the zoom meeting calendar invites and GitHub repository
• Self Assign this issue (gear in right side panel)
• Add this issue to Projects: Project Board (gear in right side panel)
• Signup for a Figma account
• Attend weekly team meetings:
  • Developer (front-end/back-end) weekly team meeting, Tuesdays 7pm PST
  • (Optional) Office Hours, Thursdays 7pm PST
  • All team meeting (UX, Development, Product), Sunday 10am PST
• 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
  • Use the information from part 2 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
• Once you take a good first issue, you will providing estimates and progress reports.
  • 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.

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

  • 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. 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
  

• Go familiarize yourself with the Hack for LA Design System page in Figma (where you can see components and their 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 issue to the "Questions / In Review" column of the Project Board so that it can be addressed in the next development meeting
• You may also add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question
• Lastly, you can post your question in the hfla slack channel and link the issue you're working on, so other volunteers can see and respond

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

[Carlos-A-P]

How much time did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue?
12 hrs

[ExperimentsInHonesty]

• PRs that Carlos has reviewed
• Issues that Carlos has completed

[ExperimentsInHonesty]

@Carlos-A-P I see that you have gotten up to medium level issues. But when I look to see reviews by Carlos-A-P PR reviews for other developers, I don't see any. So you will need to rejoin the website team. Please reach out in the hfla-site Slack channel for instructions on how to do that.

Then please write back with what you have not yet done skill wise (see developer self test), and then add the ready for product label, and I will help you find issues and activities that will fulfil those requirements.

[ExperimentsInHonesty]

@Carlos-A-P I am going to close this issue since you seem to be off the team.