Pre-work Checklist: Developer: Johnnie Hicks

[Johnnie007]

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]

@Johnnie007

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

[Johnnie007]

Availability for this week 12/5 -12/11:
Tuesday & Thursday Evenings/Night EST
My estimated ETA for completing this issue:
15 mins

[ExperimentsInHonesty]

@Johnnie007

I noticed on your next issue #2267 that you did not post availability when you self assigned.

Then you did post a note when you had a question, and later followed up by at mentioning Matt (which was awesome)

When you didn't get a response, you did not bring it up at the team meeting today. Feel free to put things in the column labeled Development team meeting discussion items 🤔 https://github.com/hackforla/website/projects/7#column-14434559

[Johnnie007]

@ExperimentsInHonesty Thanks for reaching out. I noticed that my comment lacks detail. All in all, the issue was resolved when the Wins page was converted to use the Jekyll template( I believe in a previous issue). So no work needs to be done on the #2267 issue. The issue just needs to be closed. I'll be sure to leave a more detailed comment on the issue.

[SAUMILDHANKAR]

@Johnnie007 Once you have given an 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]

@Johnnie007

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]

@Johnnie007

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

[JessicaLucindaCheng]

@Johnnie007 I'm reopening your pre-work checklist because a weekly progress report still needs to be given on an issue you are working on (not including this pre-work issue). A weekly progress report should be given every week for an open issue that you are working on.

I see you are working on issue #1498 and you gave an initial ETA and availability. However, it has been over a week since you gave that initial ETA and availability, so please give a weekly progress report as a comment in issue #1498 that includes the following:

- Progress: "What is the current status of your project? What have you completed and what is left to do?"
- Blockers: "Difficulties or errors encountered."
- Availability: "How much time will you have this week to work on this issue?"
- ETA: "When do you expect this issue to be completed?"

Once you have added a weekly progress report to an issue, then you can check off the checkbox above for " Weekly, please also provide an update on the issue". Thank you.

[github-actions]

@Johnnie007

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

[github-actions]

@Johnnie007

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

[github-actions]

@Johnnie007

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

[SAUMILDHANKAR]

@Johnnie007 Please share your weekly progress report and then you can check off the item in the checklist above. Thanks.

[github-actions]

@Johnnie007

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 Wednesday, February 16, 2022 at 5:39 PM PST.}

[github-actions]

@Johnnie007

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 Wednesday, February 16, 2022 at 5:47 PM PST.}

[github-actions]

@Johnnie007

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 Thursday, February 17, 2022 at 2:43 AM PST.}

[github-actions]

@Johnnie007

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

[JessicaLucindaCheng]

@Johnnie007 For this pre-work checklist, a weekly progress report is still needed to be given on an issue you are working on (not including this pre-work issue). A weekly progress report should be given every week for an open issue that you are working on.

I see you are working on issue #1498 and you gave an initial ETA and availability. However, it has been over a week since you gave that initial ETA and availability, so please give a weekly progress report as a comment in issue #1498 that includes the following:

- Progress: "What is the current status of your project? What have you completed and what is left to do?"
- Blockers: "Difficulties or errors encountered."
- Availability: "How much time will you have this week to work on this issue?"
- ETA: "When do you expect this issue to be completed?"

Once you have added a weekly progress report to an issue, then you can check off the checkbox above for " Weekly, please also provide an update on the issue". Thank you.

[JessicaLucindaCheng]

Left a Slack message for Johnnie about #2524 (comment) on Fri, Feb 25, 2022.

[Johnnie007]

Completing a course, and I will be inactive for the next 5 weeks.