Pre-work Checklist: Developer: Sarah S

[blulady]

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" label 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
• 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, please post the following as a comment in your new issue as well as in all the subsequent issues that you pick up or are assigned to:

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

• Weekly, please also provide an update on the issue

Provide Update
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."

• 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

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 @blulady.

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]

@blulady Hi Sarah, good progress on this issue. Please move this issue from new issue approval column to the in progress (actively working) column. Thank you.

[SAUMILDHANKAR]

@blulady Hi Sarah, good progress on this issue. Please move this issue from new issue approval column to the in progress (actively working) column. Thank you.

During the team meeting, we have decided that PM/Leadership team will move the Pre-work checklist issues from New Issue Approval column to In progress column. So, @blulady you can ignore my previous comment. Thanks.

[github-actions]

@blulady

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 Monday, February 7, 2022 at 11:17 PM PST.}