-
-
Notifications
You must be signed in to change notification settings - Fork 760
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: Ren Demeis-Ortiz #4719
Comments
Hi @LRenDO, thank you for taking up this issue! Hfla appreciates you :) Do let fellow developers know about your:- You're awesome! P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :) |
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? Approximately 8 hours of work including the onboarding meeting and the first Dev Team meeting I attended - 10 if you include the first time I attended the Sunday, Tuesday and Thursday meetings. |
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, July 4, 2023 at 12:18 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, July 11, 2023 at 12:18 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 You are receiving this comment because your last comment was before Tuesday, July 18, 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 You are receiving this comment because your last comment was before Tuesday, July 25, 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 You are receiving this comment because your last comment was before Tuesday, August 1, 2023 at 12:05 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 You are receiving this comment because your last comment was before Tuesday, August 8, 2023 at 12:06 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 You are receiving this comment because your last comment was before Tuesday, August 15, 2023 at 12:05 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 You are receiving this comment because your last comment was before Tuesday, August 22, 2023 at 12:06 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 You are receiving this comment because your last comment was before Tuesday, August 29, 2023 at 12:06 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 You are receiving this comment because your last comment was before Tuesday, September 5, 2023 at 12:05 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 You are receiving this comment because your last comment was before Tuesday, September 12, 2023 at 12:06 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 You are receiving this comment because your last comment was before Tuesday, September 19, 2023 at 12:06 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 You are receiving this comment because your last comment was before Tuesday, September 26, 2023 at 12:06 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 You are receiving this comment because your last comment was before Tuesday, October 3, 2023 at 12:06 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 You are receiving this comment because your last comment was before Tuesday, October 10, 2023 at 12:06 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 You are receiving this comment because your last comment was before Tuesday, October 17, 2023 at 12:06 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 You are receiving this comment because your last comment was before Tuesday, October 24, 2023 at 12:05 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 You are receiving this comment because your last comment was before Tuesday, October 31, 2023 at 12:06 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 You are receiving this comment because your last comment was before Monday, November 6, 2023 at 11:05 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 You are receiving this comment because your last comment was before Monday, November 13, 2023 at 11:06 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 You are receiving this comment because your last comment was before Monday, November 20, 2023 at 11:06 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 You are receiving this comment because your last comment was before Monday, November 27, 2023 at 11:06 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 You are receiving this comment because your last comment was before Monday, December 4, 2023 at 11:06 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 You are receiving this comment because your last comment was before Monday, December 11, 2023 at 11:06 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 You are receiving this comment because your last comment was before Monday, December 18, 2023 at 11:06 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 You are receiving this comment because your last comment was before Monday, December 25, 2023 at 11:06 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 You are receiving this comment because your last comment was before Monday, January 1, 2024 at 11:06 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 You are receiving this comment because your last comment was before Monday, January 8, 2024 at 11:05 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 You are receiving this comment because your last comment was before Monday, January 15, 2024 at 11:06 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 You are receiving this comment because your last comment was before Monday, January 22, 2024 at 11:05 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 You are receiving this comment because your last comment was before Monday, January 29, 2024 at 11:06 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 You are receiving this comment because your last comment was before Monday, February 5, 2024 at 11:06 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 You are receiving this comment because your last comment was before Monday, February 12, 2024 at 11:05 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 You are receiving this comment because your last comment was before Monday, February 19, 2024 at 11:06 PM PST. |
Hi @LRenDO, I see you got a large size issue completed on the website team last year. We have created new opportunities on the team, and if you are interested in coming back to get some different experience, please write back to us in the hfla-site channel so we can get you added to the resources again and then reach out to the merge team, to let them know that you ended with a large issue and are looking for the next steps and have them help you find whatever you still need experience with, from this list
Issue you could work on
|
Hi @ExperimentsInHonesty! I am still actively working on the merge team. I shared with Roslyn that I work nights and weekends and because of that it's difficult for me to attend the meetings regularly. I have been merging PRs, submitting code reviews, checking the 2 week inactives, and addressing issues in the questions / in review column though. Additionally, I'm not sure if there is a specific type of GitHub Action I need to work on for the Cron Job Scripting, but my large issue was for a GHA. Additionally, I have submitted thorough code reviews for GHAs as well. Please advise if there is something specific I would need to do to complete that task. Thanks! |
@LRenDO sorry about that, I did miss that you did the GHA issue. It looks like the next step would be for you to get some more experience making issues for other people to work on. (I see you did make an issue from an ER). Specifically, the different sizes of issue making. Then you will be able to coach other people in same as well as help us refine any instructions in the wiki. After that, we would of course love you to stick around, but you are also welcome to consider moving to another team for additional experience. We do have some that meet in the daytime and I am happy to chat about that without you after you have made some different levels of issues. p.s. Jessica is a master at this, feel free to reach out for help if you need it. |
Thanks for the clarification, @ExperimentsInHonesty! Very helpful. I'll spend more of my HFLA time creating different size issues. Since I have limited time to offer (and a somewhat inconvenient schedule), feel free to let me know anytime if I should be re-prioritizing a particular type of task over others. Happy to refocus wherever is need as long as my schedule allows! |
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 in the prioritized backlog only 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: