-
-
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
Skills Issue: Developer: Danielle Aras #6948
Comments
This comment has been minimized.
This comment has been minimized.
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? |
This comment has been minimized.
This comment has been minimized.
|
PrerequisiteWe 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. OverviewAs a developer on the Website team this issue will be your companion and a place to track your progress with the path we have set out for you. Special Notes
Action ItemsTable of ContentsSections 1 - JOINING THE WEBSITE TEAM.
2 - TEAM MEETINGS (OPTIONS AND REQUIREMENTS)
3 - DEVELOPMENT ENVIRONMENT SETUP
4 - FINDING AND ASSIGNING YOUR FIRST GITHUB ISSUE (GFI)
5 - GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES
6 - SUBMITTING YOUR FIRST PULL REQUEST
7 - ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES
8 - MOVE ON TO 2ND GOOD FIRST ISSUE (AKA, IT GETS EASIER AND DID YOU BRANCH CORRECTLY?)
9 - GOOD FIRST ISSUE (GFI) PULL REQUEST REVIEWSNow that you have two merged See How to review Pull Requests guide will teach you how to review pull requests. Please review 5
10 - UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING AND TEMPERATURE CHECKCongrats on making it this far. Issues get more complicated from here, either they include more changes, or have several files to change or you have to research something that we are unsure how to do, or there is complicated logic that needs writing or rewriting. Each issue size that you take on will guide you to a more complicated level in sequence, and you can see from the labels and overviews what they are about. Its important that you try to work on issues that fill in gaps in your knowledge (see the self tests for a reminder about what to look for). So keep going, the fun stuff is about to start. Having said that, we are also going to have you take on some issue making (surprise! There is no issue making fairy, only volunteers like you that created issues for the people that come after them). Pay attention to how the issues you have already worked on are constructed and how they change as they go up the ladder. That way when we start you on the issue making portion of the team work, you will know what you are shooting for when its your time to make issues. Also, we want you on the Merge team. This will ensure you are a competent developer and an awesome collaborative contributor to any team you join in the future.
[THIS WHOLE THING COULD BE MOVED TO A WIKI PAGE THAT EXPLAINS THE VALUE TO THEIR CAREER AND HAVE A TLDR HERE] 11 - MOVING ON TO A SMALL ISSUE
12 - PULL REQUEST REVIEWS - SMALLNow that you have your small PR merged, you are eligible to review small PRs, Review Required from other people who are following in the same journey path as you. Please review 3
13 - GET EXPERIENCE MAKING ISSUES - LEVEL 1 (GFI & Small)Creating issues from templates will give you experience on how issues
and like the good first and small issues you have already done, they are perscritive enough to do with no prior experience issue making.
14 - MOVING ON TO A MEDIUM ISSUE
14.1 MAKE A MEDIUM ISSUE FROM AN ER OR EPICOnly work on this section if you needed a medium issue and one is not available from the prioritized backlog
15 - PULL REQUEST REVIEWS - MediumNow that you have your medium PR merged, you are eligible to review medium PRs, Review Required from other people who are following in the same journey path as you. Please review 3
16 - ISSUE MAKING - LEVEL 2, GFI
17 - MERGE TEAM SKILLS REVIEWWe want everyone who joins this team to get onto the merge team so that you can get experience running meetings and office hours, mentoring, creating sufficent workflow for the team, escalations, and ultimately being responsible for final approval and merging of pull requests made by team members on lower sections. At this point we will check to see if you are ready to join the merge team, or what your next steps are to get you closer to ready.
FAQ sectionAre there exceptions to which size issues I work on?
What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?
If you need to take some time off from the teamCopy and customize this response, and leave it in a comment on this issue Resources/Instructions
Skills List - INTAKESkills List, self test on Intake, fill out when you join the team, don't update Front End
Back End
All Developers
Return to Skills List - ONGOINGSkills List, update as you do work on this team Front End
Back End
All Developers
|
1 - JOINING THE WEBSITE TEAM update
A: 6.5 (old Prework Checklist) |
2 - TEAM MEETINGS update
A: June |
3 - GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP update
A: Approximately 1 hour |
4 - FINDING AND ASSIGNING YOUR FIRST GITHUB ISSUE update
A: 15 minutes |
I have finished sections 1-16 and am ready to have my activity reviewed by the merge team |
This comment has been minimized.
This comment has been minimized.
Update 9/7/24:
|
This comment has been minimized.
This comment has been minimized.
Update:
|
This comment has been minimized.
This comment has been minimized.
Update:
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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 18, 2024 at 11:04 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 25, 2024 at 11:04 PM PST. |
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: