Pre-work Checklist: Developer: Olanrewaju Akinola

[Olanrewaju-Ak]

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 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
• Also, confirm with the team lead that they have added you to the Zoom meeting calendar invites
• (Once added to the Drive) Add yourself to the team roster
• After you have finished adding yourself to the roster, let a team lead know you have added yourself to the roster and would like to be added to the website-write and website teams on GitHub
• Once added to the website-write team:
  • 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
  • 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 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
  • 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 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.

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

  • Time spent so far: Copy the question below into a new comment below 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. 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 with increasing complexity in the following order:
  • Good first issue (one per person)
  • Good second issue (one 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
• 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 "Development team meeting discussion items" 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 @Olanrewaju-Ak.

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

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

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]

@Olanrewaju-Ak I remember from our last meeting you were setting up your dev environment. Just wanted to follow up on that if it is going well. Please feel free to post on our hfla-site slack channel if you have any questions or need help. Thank you,

[Olanrewaju-Ak]

@Olanrewaju-Ak I remember from our last meeting you were setting up your dev environment. Just wanted to follow up on that if it is going well. Please feel free to post on our hfla-site slack channel if you have any questions or need help. Thank you,

Hello @SAUMILDHANKAR , i had issues installing the docker desktop because it does not run on Windows 10 Home. I had to download Docker Toolbox and VirtualBox. After installing and trying the docker compose-up code from the guideline, it does not seem to be working well. I will post pictures on the slack channel so you or anyone else could help

[ExperimentsInHonesty]

Please don't close the issue until we get you fully onboarded.

[github-actions]

@Olanrewaju-Ak

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: "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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, May 3, 2022 at 12:20 AM PST.}

[SAUMILDHANKAR]

@Olanrewaju-Ak Just wanted to follow up and check if you were able to set up your Docker based on the discussion on slack. Please let us know if you have more questions. If your blocker is resolved now. you can go ahead and pick up your good first issue. Thanks.

[Olanrewaju-Ak]

@SAUMILDHANKAR I have been able to resolve it. I will go ahead to work on my first issue. Thank you

[github-actions]

@Olanrewaju-Ak

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: "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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, May 17, 2022 at 12:21 AM PST.}

[github-actions]

@Olanrewaju-Ak

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: "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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, May 24, 2022 at 12:21 AM PST.}

[SAUMILDHANKAR]

@Olanrewaju-Ak I have unchecked your weekly progress report action item as you haven't posted an update using the format in any of your issues. Also, please pick up your good second issue next. Thank you.

[Olanrewaju-Ak]

1. Progress: Worked on Good second issue Remove unused alt-hero field from brigade-organizers-playbook.md project file #2922. pull request created
2. Blockers: none
   3.Availability:
3. ETA: 30/5
4. Pictures: None

[Olanrewaju-Ak]

1. Progress: Worked on a small issue: CONTRIBUTING.md: Additional Column Filtering Description in Section 2.2 CONTRIBUTING.md: Additional Column Filtering Description in Section 2.2 #3018, pull request created
2. Blockers: none
3. Availability:
4. ETA: 6/10
   5.Pictures:
   

[github-actions]

@Olanrewaju-Ak

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: "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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, June 14, 2022 at 12:19 AM PST.}

[Olanrewaju-Ak]

Progress: I have completed all the tasks in this issue
Blockers: none

[Sparky-code]

@Olanrewaju-Ak Looks like you're well and onboarded now, thank you for posting the issue updates.