Pre-work Checklist: Developer: John Guan

[jqg123]

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
• 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 add the following in a comment

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

• Weekly, please also provide an update on the issue

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

• Once all tasks are completed, close this issue

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]

@jqg123

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, November 29, 2021 at 11:19 PM PST.}

[ExperimentsInHonesty]

Let's talk about what to do when no one responds to your updates on the issue in a timely manner.

[SAUMILDHANKAR]

@jqg123 Once you have given a progress report on an issue (other than your newly assigned status), then you can check off the box above and close this issue. See the following section above

• Weekly, please also provide an update on the issue

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

[github-actions]

@jqg123

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

[github-actions]

@jqg123

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, January 24, 2022 at 11:18 PM PST.}

[github-actions]

@jqg123

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, January 31, 2022 at 11:15 PM PST.}

[SAUMILDHANKAR]

@jqg123: Hi John, I am planning to close this issue, since haven't heard from you in a while. If you want, you can work on it later based on availability. I left a message for you on Slack stating the same. Thank you.

[SAUMILDHANKAR]

@jqg123 Thanks for getting back to me on Slack. Please update your progress on #2557 as well. Thank you.

[jqg123]

Done

[SAUMILDHANKAR]

@jqg123 Once you have given a progress report on an issue (other than this issue), then you can check off the box above and close this issue. I understand this might happen when you are working on another issue which takes long time to complete. Until that time this issue should remain open, so I am reopening this issue. See the following section above

• Weekly, please also provide an update on the issue

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

[JessicaLucindaCheng]

@jqg123 As Saumil commented, you still need to check off the box for a progress update, which should include the following:

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

You can provide that update in this issue you working on: #2528. After you provide that update, you can check off the checkbox for the "Weekly, please also provide an update on the issue" and close this issue.

[JessicaLucindaCheng]

Slack messaged John about #2523 (comment) on Fri, Feb 25, 2022.

Edit: John said he will work on it but has limited availability because of college.

[SAUMILDHANKAR]

Closing this issue due to change in availability, as John has an upcoming job. Marked inactive on roster.