-
-
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: Rajwinder Singh #7220
Comments
2 - TEAM MEETINGS update
A: |
@Rajwinder35 I assigned you to this issue you created (even though you had checked it off, you had not done it). Please add the role labels to this issue as described in section 1 |
Hi @Rajwinder35 I wanted to let you know that I have fixed the links to the Project Board in Contributing.md - Hack for LA Section 2.3 |
This comment has been minimized.
This comment has been minimized.
@Rajwinder35 I see that you didn't answer completely in this comment #7220 (comment) You also have not finished setting up your dev env. Please leave a comment on this issue about the challenges you are having and then post the link to the comment into slack so that someone can help you. |
*Progress:* I am actively working on the project, but I encountered some
technical issues with setting up the data on my local machine. These
challenges were related to my device, but I have since resolved them, and
my environment is now fully operational.
*Blockers:* There were initial technical difficulties with setting up the
local environment, which temporarily delayed progress. However, these
issues have been resolved, and I am back on track.
*Availability:* I will have over 20 hours available this week to work on
this issue and will prioritize it to ensure steady progress.
*ETA:* I expect to complete this issue by August 20th.
…On Sat, Aug 17, 2024 at 12:46 AM HackforLABot ***@***.***> wrote:
@Rajwinder35 <https://github.com/Rajwinder35>
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 (optional): "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 Questions/In
Review column of the Project Board 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
<#1619 (comment)>
and here
<#1908 (comment)>
are examples of well-formed questions.
You are receiving this comment because your last comment was before
Tuesday, August 13, 2024 at 12:14 PM PST.
—
Reply to this email directly, view it on GitHub
<#7220 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BKBYQPAZJNXHU7Q2GMOV34LZRZFXNAVCNFSM6AAAAABMBPCKUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUGAZTAOJYGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
3 - GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP update
A: "It took me approximately 45 minutes to complete the task, including reading the contribution.md file. The process took longer than expected due to technical difficulties I encountered while loading data from GitHub to my local device." |
4 - FINDING AND ASSIGNING YOUR FIRST GITHUB ISSUE update
A: It took me 2 hours to complete the task, including reading the contribution.md file and addressing a small priority issue labeled dev:GFI. |
7 - ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES update
A: "This step took 30 minutes, which included studying the Figma design."
|
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.
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 Tuesday, October 8, 2024 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 15, 2024 at 12:04 AM PST. |
@Rajwinder35 It looks like you have not been active since 2024-08-20. Which is over two months. I am close this issue. |
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 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 Items
Table of Contents
Sections
1 - Joining the website team
2 - Team Meetings (Options and Requirements)
3 - Development Environment Setup
4 - First GitHub Issue (GFI)
5 - Weekly Updates
6 - 1st Pull Request
7 - Additional reading 1
8 - 2nd good first issue
9 - Pull Request Reviews - GFI
10 - Additional reading 2
11 - Small Issue
12 - Pull Request Reviews - Small
13 - Issue Making - Level 1 (GFI & Small)
14 - Medium Issue
14.1 Issue Making - Level 2 (Medium)
15 - Pull Request Reviews - Medium
16 - Issue Making - Level 2 (GFI)
17 - Merge Team Skills Review
FAQ
Resources
1 - JOINING THE WEBSITE TEAM.
role: front end
orrole: back end/devOps
or both label(s) to this issue and remove therole missing
label (gear in right side panel)⇧ Table of Contents
2 - TEAM MEETINGS (OPTIONS AND REQUIREMENTS)
⇧ Table of Contents
3 - DEVELOPMENT ENVIRONMENT SETUP
⇧ Table of Contents
4 - FINDING AND ASSIGNING YOUR FIRST GITHUB ISSUE (GFI)
On assignment, you will be prompted to estimate Availability and ETA.
Once you have done that on your good first issue, check this box, above, on this issue to let us know you have completed that task and understand how to do it in future.
- If you have any questions about estimating the issue you choose, please add them to the issue, put the issue in the "Questions/ In Review" column, and add the labels
ready for dev lead
andStatus: Help Wanted
⇧ Table of Contents
5 - GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES
⇧ Table of Contents
6 - SUBMITTING YOUR FIRST PULL REQUEST
⇧ Table of Contents
7 - ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES
⇧ Table of Contents
8 - MOVE ON TO 2ND GOOD FIRST ISSUE (AKA, IT GETS EASIER AND DID YOU BRANCH CORRECTLY?)
⇧ Table of Contents
9 - GOOD FIRST ISSUE (GFI) PULL REQUEST REVIEWS
Now that you have two merged
good first issue
PRs, you are eligible to review good first issue PRs, Review Required from other people who are following in the same journey path as you.See How to review Pull Requests guide will teach you how to review pull requests.
Please review 5
good first issue
PRs. Each PR requires at least two reviews, so by reviewing 5 good first issue PRs you are repaying the effort that others did for you (provided 4 reviews for your 2 good first issues) plus 1 extra review to help us all make up the deficit for people who submit a PR but don't get this far.good first issue
prgood first issue
prgood first issue
prgood first issue
prgood first issue
prgood first issue
PR that your review, please paste the following text in a comment belowgood first issue
PRs to review right now, paste this comment instead and check back later. You can also go onto section 10.⇧ Table of Contents
10 - UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING AND TEMPERATURE CHECK
Congrats 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]
⇧ Table of Contents
11 - MOVING ON TO A SMALL ISSUE
⇧ Table of Contents
12 - PULL REQUEST REVIEWS - SMALL
Now 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
small
PRs. Each PR requires at least two reviews, so by reviewing 3 small PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 small issue PR) plus 1 extra review to help us all make up the deficit for people who submit small PRs and then drop off the team.small
prsmall
prsmall
prsmall
PR, please paste the following text in a comment belowsmall
PRs to review right now, paste this comment instead and check back later. You can also go onto section 13.⇧ Table of Contents
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.
ready for merge team
⇧ Table of Contents
14 - MOVING ON TO A MEDIUM ISSUE
⇧ Table of Contents
14.1 MAKE A MEDIUM ISSUE FROM AN ER OR EPIC
Only work on this section if you needed a medium issue and one is not available from the prioritized backlog
needs issue: medium
to this issue, so that we can notify you when new medium size issues are releasedready for merge team
ready for merge team
ready for prioritization
label is added. When the new issue(s) are approved, the issue making issue will be closed and you are welcome to move onto the next checkboxneeds issue: medium
⇧ Table of Contents
15 - PULL REQUEST REVIEWS - Medium
Now 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
medium
PRs. Each PR requires at least two reviews, so by reviewing 3 medium PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 medium issue PR) plus 1 extra review to help us all make up the deficit for people who submit medium PRs and then drop off the team.medium
prmedium
prmedium
prmedium
PR, please paste the following text in a comment belowmedium
PRs to review right now, paste this comment instead and check back later. You can also go onto section 16.⇧ Table of Contents
16 - ISSUE MAKING - LEVEL 2, GFI
ready for merge team
ready for merge team
⇧ Table of Contents
17 - MERGE TEAM SKILLS REVIEW
We 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.
⇧ Table of Contents
FAQ section
Are there exceptions to which size issues I work on?
you can work on one medium issue, but only one at a timeone per person, with some exceptions, see below)- The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
- We are trying to teach you the team methodology through the issues themselves.
- It ensures you understand what we expect and the quality of contributions.
What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?
Status: Help Wanted
so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that."Development team meeting discussion items""Questions/In Review" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.If you need to take some time off from the team
Copy and customize this response, and leave it in a comment on this issue
I need to take some time off from the team. I believe I will be back on [Replace with DATE YOU WILL BE BACK]
- If you have put work in, please make sure its well documented.
- Add the label
away on hold
- Move this issue to the questions column
- if you are assigned to an issue, if you have not yet made any progress on the issue, please unassign.
⇧ Table of Contents
Resources/Instructions
⇧ Table of Contents
Skills List - INTAKE
Skills List, self test on Intake, fill out when you join the team, don't update
Front End
Back End
All Developers
Return to
section 1
section 10
Skills List - ONGOING
Skills List, update as you do work on this team
Front End
Back End
All Developers
⇧ Table of Contents
The text was updated successfully, but these errors were encountered: