Pre-work Checklist: Developer: [Adolf Schmuck]

[answebdev]

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
  • Read 2.6 What to do when you need to stop mid issue
  • 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

[github-actions]

Hi @answebdev.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Role

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[SAUMILDHANKAR]

@answebdev Just wanted to follow up if you got an opportunity to provide your weekly progress report on any of the issues that you worked on. Please feel free to check off the pending items and close this issue once done. Thank you.

[answebdev]

@SAUMILDHANKAR Thank you for pointing that out. I didn't realize that I had to provide my weekly progress report for this checklist here. Maybe I misunderstood and have been doing the progress reports on the actual issues I work on. Also, I have been checking off the items, but my understanding is that I need to complete all my other issues, like good first issue, good second issue, etc. Is that correct? I just need to do a "large issue". After I complete my "large issue" is when I can finally close this issue, right? Or should I already have closed this issue?

[SAUMILDHANKAR]

@answebdev Sorry if I was not clear enough, the progress report needs to be provided on the actual issues not here. I just wanted to say that since you worked on issue #2401 for more than a week, you could have used it to provide a weekly progress report in the format as mentioned in this pre-work checklist and checked off your only pending item here. I understand you would be working on a large issue next and if it takes more than a week, you would have an opportunity to provide a weekly progress report again (which should be a comment on that issue) and then you can check off your pending items in this pre work issue and close it. Please let me know if you have any questions on this. Thank you.

[answebdev]

@SAUMILDHANKAR Okay, I understand now. I guess I just understood it in a different way. But thanks for the clarification. So, yes, I will be working on a large issue next, and I will provide a weekly progress report here if it takes more than a week. And now I wonder...I haven't started my large issue yet, but what if it does not take more than a week? Should I still provide a weekly report here so that I can check off my pending item, since this will be the last issue for this pre-work issue?

Also, after I finally check off all my items in this pre-work issue, do I need to tag you and/or Jessica first before I close this issue, or do I just go ahead and close this issue on my own once I get everything checked off?

Thank you.

[SAUMILDHANKAR]

@answebdev You can still work on issues after you finish your large issue. I would suggest to keep this per-work checklist open until you find an opportunity to provide a progress report.

After you check off all the items, you can close this issue. No need to tag me or Jessica. Thank you for your great work.

[answebdev]

@SAUMILDHANKAR Okay, I got it. Thank you for letting me know. And I'll be sure to close this issue after I check off all the items. Thanks again.

[answebdev]

Progress Report for current Large Issue #2455

• Progress: Have redesigned the navbar according to the figma design (i.e., navbar items Our Work, Join Us, Get in Touch, etc. with dropdown items) and got most of the basic styling done
• Blockers: I got the redesigned navbar dropdown working, but all of the dropdown items are in one separate .yml. file, and they should be in separate files. I am currently stuck on getting this to work (i.e., they are in now in separate files but my blocker is getting everything to work)
• Availability: 6 hours
• ETA: 3/30/2022

[answebdev]

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? 6 hours