-
-
Notifications
You must be signed in to change notification settings - Fork 766
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: Carlos Perez #2753
Comments
This comment has been minimized.
This comment has been minimized.
How much time did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue? |
@Carlos-A-P I see that you have gotten up to medium level issues. But when I look to see reviews by Carlos-A-P PR reviews for other developers, I don't see any. So you will need to rejoin the website team. Please reach out in the hfla-site Slack channel for instructions on how to do that. Then please write back with what you have not yet done skill wise (see developer self test), and then add the |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
@Carlos-A-P I am going to close this issue since you seem to be off the team. |
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
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.
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: