Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pre-work Checklist: Developer: Hiram Riddle #2701

Closed
19 tasks done
riddle015 opened this issue Jan 19, 2022 · 35 comments
Closed
19 tasks done

Pre-work Checklist: Developer: Hiram Riddle #2701

riddle015 opened this issue Jan 19, 2022 · 35 comments
Assignees
Labels
2 weeks inactive An issue that has not been updated by an assignee for two weeks Complexity: Prework prework Feature: Onboarding/Contributing.md role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours

Comments

@riddle015
Copy link
Member

riddle015 commented Jan 19, 2022

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
  • Read section 2.1 - 2.4 in Part 2: How the Website team works with GitHub issues within Contributing.md
  • Once you take a good first issue, you will providing estimates and progress reports.
    • 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:
    
    • 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
    
  • 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 "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

@github-actions
Copy link

Hi @riddle015.

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:

@riddle015 riddle015 self-assigned this Jan 19, 2022
@riddle015 riddle015 added role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers and removed role missing labels Jan 19, 2022
@github-actions
Copy link

@riddle015

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 github-actions bot added the To Update ! No update has been provided label Jan 28, 2022
@riddle015
Copy link
Member Author

Provide Update

  1. Progress: "Just starting"
  2. Blockers : "None"
  3. Availability: 5 hours this week
  4. ETA: 2/6

@riddle015 riddle015 added Status: Updated No blockers and update is ready for review and removed To Update ! No update has been provided labels Feb 2, 2022
@github-actions github-actions bot removed the Status: Updated No blockers and update is ready for review label Feb 11, 2022
@github-actions
Copy link

@riddle015

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 github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Feb 11, 2022
@JessicaLucindaCheng JessicaLucindaCheng added To Update ! No update has been provided and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Feb 12, 2022
@github-actions github-actions bot removed the To Update ! No update has been provided label Feb 18, 2022
@github-actions
Copy link

@riddle015

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.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Feb 18, 2022
@github-actions
Copy link

@riddle015

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
Copy link

@riddle015

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
Copy link

@riddle015

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
Copy link

@riddle015

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
Copy link
Member

@riddle015 How are you doing on this pre-work checklist? Did you have any questions?

@github-actions
Copy link

github-actions bot commented Mar 4, 2022

@riddle015

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

@github-actions
Copy link

@riddle015

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, March 22, 2022 at 12:19 AM PST.

@SAUMILDHANKAR
Copy link
Member

@riddle015 Hi Hiram, I see that you have already provided weekly progress reports in your good second issue, so you can check off that action item at top. Also, feel free to close this issue if all the remaining items are complete. Thank you.

@SAUMILDHANKAR SAUMILDHANKAR added To Update ! No update has been provided and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Mar 26, 2022
@github-actions github-actions bot removed the To Update ! No update has been provided label Apr 1, 2022
@github-actions
Copy link

github-actions bot commented Apr 1, 2022

@riddle015

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, March 29, 2022 at 12:20 AM PST.

@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Apr 1, 2022
@SAUMILDHANKAR
Copy link
Member

@riddle015 Hello Hiram, Hope you are doing well. Just wanted to follow up if you are planning to pick up your next issue. Please let us know if your availability has changed. I will leave a slack message about the same as well. Thanks.

@ExperimentsInHonesty ExperimentsInHonesty added prework and removed good first issue Good for newcomers labels Apr 3, 2022
@github-actions
Copy link

github-actions bot commented Apr 8, 2022

@riddle015

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, April 5, 2022 at 12:20 AM PST.

@SAUMILDHANKAR
Copy link
Member

@riddle015 Thanks for letting me know that you are planning to take up your next issue in the upcoming week. Also, wanted to check if the pending action items in this issue are complete. If yes, feel free to close this issue. Thanks.

@github-actions
Copy link

@riddle015

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, April 12, 2022 at 12:20 AM PST.

@SAUMILDHANKAR
Copy link
Member

@riddle015 Hope you are doing well. Please let me know if you are still planning to pick up your next issue or your availability has changed. Will leave a slack message as well. Thank you.

@github-actions
Copy link

@riddle015

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, April 19, 2022 at 12:20 AM PST.

@SAUMILDHANKAR
Copy link
Member

SAUMILDHANKAR commented Apr 23, 2022

@riddle015 Hi Hiram, I noticed that the small issue that you last picked wasn't ready to be worked upon. Please pick your next small issue from the Prioritized Backlog column. Based on the role filter that you want to go for, it should be the top small issue in the Prioritized Backlog column once you filter by small issues. I can demo this for you in our next team meeting as well. Please let me know when you are planning to attend one. Thank you.

@github-actions
Copy link

@riddle015

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, April 26, 2022 at 12:21 AM PST.

@github-actions
Copy link

github-actions bot commented May 6, 2022

@riddle015

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
Copy link
Member

@riddle015 Just a reminder to pick up your small issue next. Will leave a slack message as well. Thank you.

@github-actions
Copy link

@riddle015

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 10, 2022 at 12:23 AM PST.

@github-actions
Copy link

@riddle015

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
Copy link

@riddle015

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
Copy link
Member

@riddle015 Hi Hiram, jusr wanted to follow up on your pending action items above. You can check them off and close this issue if you are done with them. Also, please provide an update on #2952. Thank you.

@github-actions
Copy link

github-actions bot commented Jun 3, 2022

@riddle015

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 31, 2022 at 12:19 AM PST.

@github-actions
Copy link

@riddle015

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

@riddle015
Copy link
Member Author

Completed all the items in the checklist!

Best,
Hiram

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 weeks inactive An issue that has not been updated by an assignee for two weeks Complexity: Prework prework Feature: Onboarding/Contributing.md role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours
Projects
Development

No branches or pull requests

5 participants