-
-
Notifications
You must be signed in to change notification settings - Fork 777
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: Garrett Allen #4061
Comments
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.
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, March 6, 2023 at 11:17 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
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 14, 2023 at 12:16 AM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
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 21, 2023 at 12:15 AM PST. |
Hi @garrettallen0 It looks like you have not made any progress in about a month. Please let us know if you need some help by messaging in the hfla-site slack channel. If we don't hear back from you on this issue by the 2023-04-02 we will close the issue. Feel free to reopen it in the future if you want to come |
Hi @bonniewolfe, thank you. I am now making progress and looped in. I am going to keep chugging |
@garrettallen0 Thank you for the update. |
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? 7 hrs |
Hi @garrettallen0 congratulations on completing your good first issue. In case you were waiting for a 'good second issue', I wanted to let you know that you can simply take another 'good first issue'. In fact we are going to phase out the 'good second issue' label because those labels. I apologize if there was mixed messaging on the requirement for 'good second issue' issues. In any case, please leave an update in this issue. Issues that have been inactive for at least 2 weeks are automatically assigned the label '2 weeks inactive' to flag them for review by a dev lead. Please leave a comment outlining your progress and any blockers or problems that you are experiencing. Then please remove the '2 weeks inactive' label. Thank you! |
Hi @roslynwythe, right! I had heard that about the 'good second issues' getting phased out. I just started a swe bootcamp that is going to demand ALL my time for 3 months. Can I pause my progress through my issues and resume it when I get my life back in 3 months? |
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.
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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions. You are receiving this comment because your last comment was before Tuesday, May 16, 2023 at 12:16 AM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions. You are receiving this comment because your last comment was before Tuesday, May 23, 2023 at 12:17 AM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions. You are receiving this comment because your last comment was before Tuesday, May 30, 2023 at 12:15 AM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions. You are receiving this comment because your last comment was before Tuesday, June 6, 2023 at 12:16 AM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions. You are receiving this comment because your last comment was before Tuesday, June 13, 2023 at 12:16 AM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions. You are receiving this comment because your last comment was before Tuesday, June 27, 2023 at 12:17 AM PST. |
Hi @garrettallen0. Please create an update as described in the above comment. If you are not currently working on other issues, then we would like to see updates at least every two weeks, to inform us of your progress and any problems you might be experiencing, and to let us know that you are still interested in participating in Hack for LA. If we do not hear from you by 7/10/2023, we will assume that you are not interested in participating in Hack for LA at this time, and we will close this issue, but you can reopen it at a later date, and move it into the "In Progress" column. Thank you. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
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. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions. You are receiving this comment because your last comment was before Tuesday, July 4, 2023 at 12:18 AM PST. |
Hi @garrettallen0 as mentioned in #4061 (comment), we will be closing this issue, but if you should decide to return to Hack for LA, you are welcome to reopen it and move it into the "In Progress" column. |
@garrettallen0 I see that you did one good first issue and then did not pick up another. If you want to come back to the team and pick up where you left off, then please go ahead and self assign another good first issue from the prioritized backlog. If you find you have lost your rights to self assign an issue, please message us in the hfla-site Slack channel. |
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.
Special Notes
Action Items
website-write
andwebsite
teams on GitHubCheck 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. (Note: Please provide estimates on all the issues that you pick up, going forward.)
Progress through issues with increasing complexity in the following order:
What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?
Resources/Instructions
The text was updated successfully, but these errors were encountered: