Pre-work Checklist: Developer: Kaia

KBWells77 commented 2 years ago

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

[x] Add yourself to the #hfla-site and #hfla-site-pr Slack channels
[x] Share your Gmail address with the team lead so you can be added to the Google Drive
[x] Also, confirm with the team lead that they have added you to the Zoom meeting calendar invites
[x] (Once added to the Drive) Add yourself to the team roster
[x] 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
[x] Once added to the website-write team:
- [x] Self Assign this issue (gear in right side panel)
- [x] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label
- [x] Add this issue to the Project Board under the Projects section (gear in right side panel)
[x] Signup for a Figma account
[x] Attend weekly team meetings:
- [x] Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
- [x] (Optional) Office Hours, Thursdays 7-8pm PST
- [ ] All team meeting (UX, Development, Product), Sunday 10am-12pm PST
[x] 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.
[x] 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
- [ ] Follow the steps in section 2.3 Where can I find GitHub issues to work on? 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
- [ ] Read 2.6 What to do when you need to stop mid 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:
- [x] 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.
- [x] 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 SCSS 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

github-actions[bot] commented 2 years ago

Hi @KBWells77.

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:

SAUMILDHANKAR commented 2 years ago

@KBWells77 Hope you are doing well. Just wanted to check if you have been able to setup your dev environment yet. Please post a comment in our hfla-site slack channel if you have any questions or need help. Thank you.

KBWells77 commented 2 years ago

@KBWells77 Hope you are doing well. Just wanted to check if you have been able to setup your dev environment yet. Please post a comment in our hfla-site slack channel if you have any questions or need help. Thank you.

@SAUMILDHANKAR Hi thank you for your comment, I was having some issues just with looking into which download options were best for my computer and such but I've been working on it today and have been able to move further, thanks.

github-actions[bot] commented 2 years ago

@KBWells77

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.

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?"
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 7, 2022 at 12:21 AM PST.}

github-actions[bot] commented 2 years ago

@KBWells77

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.

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

Sparky-code commented 2 years ago

Hi @KBWells77 my name is Devin, a member of the merge team. I'm checking in to see if you were able to get everything sorted out with your environment and moving forward with your prework. Please let me know if you are running into issues or if your availability has changed.

github-actions[bot] commented 2 years ago

@KBWells77

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.

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?"
Pictures (optional): "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 21, 2022 at 12:20 AM PST.}

KBWells77 commented 2 years ago

Hello, I sorry for the delayed response, yes I do still plan to work on the team and finish getting my environment set up. I have been over seas the past two weeks and very busy since I got back. I will be back for the team meeting on July 5th if that it alright. I wasn’t completely sure how to announce my absence but I notified Tamara Snyder and she said it would be alright. Thank you

Sent from my iPhone

On Jun 23, 2022, at 4:33 PM, Devin Krizwold @.***> wrote:

Hi @KBWells77 my name is Devin, a member of the merge team. I'm checking in to see if you were able to get everything sorted out with your environment and moving forward with your prework. Please let me know if you are running into issues or if your availability has changed.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

Sparky-code commented 2 years ago

Hey @KBWells77 Thanks for the update! No worries, I must've missed that, I'll mention it to Tamara again and we'll look forward to seeing you on the 5th! Best practice is to post changes to your availability in the comments of the issue you're working on.

github-actions[bot] commented 2 years ago

@KBWells77

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.

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?"
Pictures (optional): "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, July 5, 2022 at 12:19 AM PST.}

github-actions[bot] commented 2 years ago

@KBWells77

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.

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?"
Pictures (optional): "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, July 12, 2022 at 12:20 AM PST.}

github-actions[bot] commented 2 years ago

@KBWells77

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.

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?"
Pictures (optional): "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, July 19, 2022 at 12:21 AM PST.}

Zak234 commented 2 years ago

@KBWells77 It doesn't look like there has been any activity on this issue since June, so we are closing it. If this is a mistake and you are still planning on working on the team, please reopen this issue and complete it.

hackforla / website