Exactly, it seems that every video on youtube now is 10 minutes long and has like 2 minutes of relevant content. This one, though, is good and short. Subscribed :D
I agree, if I could start my journey over I would jump straight into Open source and treat that as my ‘projects’ vs building things on your own. Because not only are you contributing but you’re also working with others as a team. Most definitely will look good on your resume and you will for sure meet mentors and high name tech contributors and even get paid through open source. Would encourage anyone starting out to prioritize open source over building things or a portfolio for a job
Yes exactly! The type of experience you can get by working on projects that are already established and somewhat unfamiliar to you is so valuable. Starting a job working on a new codebase will be way easier because you’ve exercised that muscle working on open source projects
@@thewillderness7852 wrote, _"Open source isn't going to make you rich. Creating something on your own might."_ You may find this video more relevant than it first appears: ruclips.net/video/u6XAPnuFjJc/видео.html
@@thewillderness7852 1. Literally no software you produce on your own will make you rich unless it's some shitty mobile app. 2. Some of us prefer volunteering our time towards projects that are useful for everyone and guarenteed to not have any shitty monitoring, DRM, etc., large projects always need help. 3. Due to #2, it's significantly more fun than coming up with stuff on your own, besides, all of the heavy lifting has been done for you.
@@colbyboucher6391 1. It's the marketing that largely decides that. 2. Personal preference 3. Personal preference. Some of us enjoy innovating a little more from scratch.
You're not wrong. Open source is more valuable compared to building things when it comes to resumes and looking for jobs. But it's so much more fun to do stuff on your own, where you have 100% creative freedom and no BS politics, red tape, legacy etc. Sure people in Corpo world will be more impressed if I can manage these issues in open source rather than just build stuff on my own stuff, but hey why would I fight with that in my free time, when I have to do it anyways at work.
@@EverRusting agreed, some even accept stupid prs and reject the useful one. There's a pr in a particular project which spammed time.sleep(), which got accepted, but the pr that refactored the codebase and made significant improves, gets ignored. This is really outrageous.
@@EverRusting I didn't make that experience and I would highly doubt bad experiences like you sadly made are the norm. For me, I only contributed once, as I rather like to work on some personal projects in my free time. However, directly writing to the main dev of a huge utility I love on discord and figuring out some stuff, then creating a PR and see your changes solve an issue other people have is amazing. Most people are pretty chill and glad that you want to help.
I think you forgot step 0 when contributing code: Leave a comment on any issue you want to fix, state clearly that you would like to contribute a solution, and ASK(!) if a maintainer is there and willing to review/accept your work. It usually doesn't take long to get a response, gives you a general sense of the pace at which the repo operates, and saves you from contributing to dormant projects. For the first PR it will take a couple of days to set up a dev environment, get familiar with the tooling, understand the test-suite, etc. Nothing takes the wind out of your sails faster than putting in those days of work just to see the PR sitting there for months with no feedback and no merge. So before you start, make sure you have talked to maintainers (like me) before you airdrop a PR. We don't want your work to sit around and collect dust, but unfortunately, most of us have to split our time between the project and a regular job. Having clear communication on this from the start goes a long way in having fun with open source :)
Hi, I'm just getting into coding myself, been doing some work on my own to prepare for some classes I have coming up in the fall (preparing for these community college classes by watching cs50 from Harvard lol, kinda feels like overkill but I don't like surprises and I want to excel at this.) So I understand the basics, but have only a little actual on hand experience (I've done all the programs provided in cs50, have bought a couple books on making games in Python and have coded some simple games, as well as currently working on building my own chess game just as a fun starter project and as an exercise in problem solving with code.) As someone who seems well versed in this area, do you have any tips for getting into this, like places I should start or where my minimal skills could be best put to use? I'm very good with the English language so I feel myself naturally drawn to documentation and editing, which was brought up in the video, and I think that would be an excellent place to start. Any advice, including any projects you yourself could use such help on, will be greatly appreciated!
This. I was taken back when he said to just go ahead with contributing to a project without contacting the people that maintain it. I would never go ahead without first contacting the person that maintain a project because they may not want or need help.
@@fisharepeopletoo9653just keep it up. stop looking online for answers. if you're going to college and you're doing things, it won't take much to find a job. do your first web page, that'll help you have "something to show", even if it's a real simple thing. really don't think big. the simpler the better.
Honestly, I think the more feedback you get on your PRs, the better. That means people doing code reviews care enough about you as a contributor that they’re willing to spend time going over your authored PR. It gives that much more meaning to your PR when it’s eventually approved and merged. And you can say, “I’ve contributed something meaningful to this project!”
It can be a shock the first time your ideas/contributions are beaten up on, but you end up with the contribution being all the stronger for it, and you start to look forward to finding the groups who will really put your work on trial
@@stevecarter8810so true, i work with someone on my team that is very strict, when i first joined i thought he was being overly nitpicky and hated adding him to reviewers list because he always had something to say, but now i gottten to know him more and got used to it . I can proudly say that thanks to his guidance, sometimes toxic but with good intentions, I have gotten a lot better with thanks to his advice and he became my favorite person on the team, it feels really good when he gives you good feedback and actually cares about what you put on
Also, just remember to check whether the project is still active or not by checking the latest pull request date and also ask the owner before solving an issue, the issue might already be assigned to someone or for any reason they may not accept your PR so prepare for that as well just in case.
I started my journey with open source in 2019. Gradually I made my career in open source and now working for an Open Source company. The best part is ypu get to contribute to projects freely. There are lot of talented developers and almost every open source developer is passionate about their work. ❤️
@@pedrotorres2747 It was awesome. The interviewers were the engineers working on the project that I was going to join. They asked me very basic DSA questions and then some computer science concepts. They talked a lot about my projects, GSoC experience. Most of the interview was a open discussion on general programming topics.
@@deepspaceship I'm glad to hear that your interview went well, and I hope to have a similar experience in my future job interviews. I have experience in JavaScript and PHP, but sometimes it's difficult to access job opportunities because they require years of experience or even a bachelor's degree in my country. That's why I'm focusing on improving my English skills so I can work in another country that offers more opportunities. Do you have any recommendations for me?
Timestamps for those interested: 0:00 - Why contribute? 0:44 - Finding a project and an issue 1:33 - Read the rules 1:46 - Form the project, make a branch 2:03 - Feeding the RUclips algorithm 2:08 - Make your changes 2:23 - Push your changes 2:28 - Open a PR that resolves the issue 2:47 - Monitor and receive feedback gracefully 3:05 - Signing off
@@PossumMedic still cool to see chapters with the youtube chapter feature + in this day and age everything longer than a tik tok is already very long ;)
Let's be honest. It's easy to submit contributions. It's not always easy to contribute. As he said in the video, be prepared for the worst and do not attach too much feelings to your contributions.
I can't agree with this enough. The sense of achievement for adding anything of value to something YOU value is amazing. I've even had my own fork become more popular than the original project, and made it the reference implementation for an IETF RFC. Aim high, and have fun. Oh, and read "The Cathedral and the Bazaar" for a primer on how open source rewards contributors, and how contributors reward open source.
I've acquired my knowledge from the open-source community, and I actively seize every chance to contribute. Numerous individuals and companies have approached me for projects tied to one or more of my pull requests, opening up a plethora of opportunities for me. I am sincerely grateful for the enriching experiences this has brought into my professional journey.
@@LearnFastMakeThings .. or at least not negative. Most PRs I've made (and I've done a lot in the past) have pretty dry responses, but they are on the point.
I've always been really intimidated to contributing to an open-source project, but i think I just need to give it a go. Just looking through other people's code will be helpful, and making some changes can help me practice more all the things that I've learned. Will have to give this a try soon!
My first contribution was not too long ago to inquirer js library. I was fixing uncaught errors throw in in some case of menu scrolling. After tracking down all the calls I found just one line where the problem was. My change was accepted and pushed to npm. As a result I felt myself a hero of some meme who crashes people's prod servers with just one line change, because that's what I did by using es2020 operator "??"😅 Bunch of ppl with node 12 and lower were complaining, even dependencies freeze quick patch was rolled. 😵💫 Luckily I managed to replace it with polyfil before too much damage been made. 😊 This kind of experience was new to me, scared and excited at the same time 🙃
I try to make bug reports instead of providing the actual solution, to keep the (minor) contributor count low so that license-wise there are no problem if someone decides to change it (I seriously had people hit me up if changing the license was ok, because I added one DLL the repository). And I seriously had one dude complaining about my bug report, that I wasn't fixing it myself and that I suck for being a security researcher who just posts bug reports on open-source projects so that they can use the unfixed bugs in their reports to say open-source sucks (of which none is true). I legitimately just had a wrong free bug when running the code "casually". I provided reproducible steps, test files, everything. In the end I fixed it in the same manner as the rest of the code has been fixed at a similar line of code, created a pull request and it still hasn't been merged. (~6 hours wasted, plus a giant "f u" in my face) Another time, I added a feature I wanted, created a pull request and basically got a "won't merge", because it simply doesn't fit the idea of the maintainer of what the project should look like. (Neither would there have been any grounds to make this feature fit, because it's nature was just not fitting) Other times I create a pull request with the message: "Please test before merging" and it gets merged so fast that it can't possibly have run through any tests. Other times it takes 2 years before my pull request gets accepted, despite it literally being just a fix where someone accidentally had swapped x and y (or rather u and v). And now to the worst offender, which is my professor at uni, wants me to rebase my 60+ commits (among which are also commits of colleagues) into 4 big commits that are actually features that rely on each other, rewrite history that way and screw up authorship of files and cause me a bunch of headaches and increased testing efforts when I'm already 1 year due to submission. Not just that but it eliminates the detailed description of each commit and thereby I need to change a bunch of files again and reconsider which stuff I put into the documentation and which not, while before it was very clear that certain bugs that have been fixed did not need inclusion in the documentation, but had a detailed explanation in source control. THAT'S my experience with open-source.
Im sorry to hear that you've had a poor experience. Sometimes contributing is harder than it really should be. I know there are some toxic environments out there and some projects that just dont appreciate contributors. but... There are also some great open source communities that openly welcome contributions of any type, especially security research.
Is your prof high or something? If your commits are atomic with good messages, don't rewrite history (which is already bad practice in 99% of all cases) eliminating that beautiful, self-describing and maintainable git log.
I was so happy to contribute to Mantine React UI library. It feels amazing to see my profile on the contributor list and know that it will impact thousands of people :)
Helping more people become comfortable with open source and contributing in such a clear concise video is fantastic, well done. Telling people "github is the new resume" is utter nonsense!
thanks for the comment. Its too late now, but i think if i could do it again i would soften that statement. github is like a portfolio, not necessarily the new resume.
Yes I mean I pushed for certain interface features during development on Blender's Grease Pencil. And I saw it through. I insisted that they should sync up the toggle options for onion skins and layer visibility in the timeline section and the tool section. And whaddya know, they decided to include that. 🙌😄 If you ever have an idea that can help make an open source project better, it's best to speak up about it and keep pushing for it to happen.
You could also maybe in the future talk about issue tags and good first issues. You can actually use advance search to filter these and then I feel contributing becomes much easier. Good stuff tho!
Submitting tickets, well written, researched and with reproduction steps, can also be really helpful to maintainers or to yourself. I have first hand experience at finding bugs or missing features in a framework I use at work, write professional tickets (what's the issue, severity, why it's an issue, expected behavior, tracing the origin of the issue in the source code if possible, providing code/pseudo code when a PR isn't an option) and get notification of a patch within a week on totally open source projects. That's also a good skill to have and you can use it at interviews if you can show multiple tickets and their resolution time compared to other tickets or average closing time in a project.
*Thank you* so much for this. GitHub has always been really confusing for me to use and navigate, so having clear, to-the-point instructions or standards here have been really helpful.
What's most wild to me is how often people run into an issue or hurdle when installing some software then don't just go in and add their steps to resolve into the projects documentation. If I ever have an issue with documentation and I find the answer and it isn't in the documentation already, I open a PR with those changes added.
You are the best creator❤, this video shows how genuinely you wanted to share your knowledge, but not just make a content that makes you so special and you are amazing❤
This is really great and something I didn't know you could do. I will have to look into this a lot more as I think the experience and feedback is something you are unlikely to get elsewhere.
Thanks for this video! I've been using Git Hub for a few years now to manage personal projects, but I've never understood how to work on other, open source projects. I've heard about forks and pull requests, but never understood exactly how they worked. So much info in a ~3 min video!
This sounds romantic but the truth of the matter is: It's extremely difficult to find a repository to commit to. The explore page shows you repos across all languages, if you nail down a single language the most starred repos are usually pretty quick to fix trivial bugs while the much more complex ones are left open. The less stars a repo has the worse, when you find a repo with an issue you could tackle you already see an open pull request from 4 months ago. As a new developer this can be a really frustrating experience.
love the video. I'm just confused on one thing. What's the point of forking the project? Isn't it possible to clone the project and then create a branch for what you're tryign to resolve?
that was a straight to the point, very informative and cool to watch video. Great stuff man. I just started on the computer science carreer and this was 3min of solid help in my path
I tried. And here's the thing. I submit the pull requests, the other developers copy the change, generate their own pull request and approve their own pull request rather than approving mine. It's kind of fool's gold.
Is it really worth the time investment? Doesnt seem like that to me tbh, its a great time sink to get to know a project enough to contribute, and then what is the reward? A cool looking github profile? I think there are a lot better ways to improve your skills or/and increase income than this
I’d say it’s worth it. Most hiring managers including myself will check someone’s GitHub profile before an interview. It’s not really about the quantity of commits. It’s more about the types of contributions and the quality of the code.
@@szilagyimiklos4757 I guess I look at it a different way. If someone contributes to a somewhat large repository, it most likely means they are capable of reading source code of other people(AKA has experience and won't need much time to adapt), and when their PRs are merged, it means they wrote code that's good enough to be useful. But doing all of your projects on your own kind of makes you live in your own bubble and does not expose you to how others code. It potentially means you're inexperienced when it comes to writing code that is manageable by a team.
You missed the point....it's about collaboration skills and the ability to not only write code but read others people's coding style and add to it.... To keep it short: I'm also a business owner that need programmers and I write my own code....even if a guy with a degree for some reason didn't do what he said in this video I wouldn't hire him even with a degree....it's about team work and adapting to get the job done. Not how good one programmers is...you can't do it all sooooo team work... Ask anyone that programs for big tech.
Thank you! I know the video is slightly old, but I’m job hunting for full-stack junior dev roles right now and this video succinctly explains to me how I can improve my job hunt by showing how to easily contribute to open-source projects. Now I just have to find something to work on and hopefully not break anything 😂😂
I also want to suggest a change: remove the red arrow in the thumbnail. It points to nothing meaningful and the colour is ugly, especially in the context of navy and green colours. The text, ‘This One’, can go too. I feel like forking your video is bad practice, so I won’t do it myself.
@@LearnFastMakeThings Tbf I think similarly. The thumbnail is actually pretty, but the red doesn't really fit on the color scheme. Without the arrow and the text it would be a more sharp and clean thumbnail. Ofc that's only my opinion though.
This is simple yet best explanation! I also made my first contribution few weeks ago by adding background color to a navbar of a frontend site and it got merged 😀
Amazing. I have created a meetup "Together, we OpenSource". My goal is to help underprivileged and underrerpresented groups of people to find their path in IT world. I hope you do not mind if I share your video? BTW, the group is fully remote and free to join.
@@LearnFastMakeThings thank you. My meetup grew from 1 person to 114 since the 5 th of June. I cannot mentor 1:1 all of them, so I'm trying to save the answers to my own YT channel. Please subscribe, if you have some time.
Superb video. But, let me share this here knowing it can uplift someone that comes across it. Effective financial management made me rich and it is all you need if you want to build a strong financial future tomorrow. I started with 1000USD, 3 years ago I invested in a diversified stock market and fast forward to now I am worth 500000USD and am currently finishing my 8 unit apartments. I'm only 35 years old. Diversified stock investments have always proven to be very profitable, especially with the help of experts.
I'm really impressed. At 35, i was worth a little over $200,000 from * in the stock market. But what you've done with your *finances* and numbers you worth, is pure genius.
You have done well. It's people like you who set the benchmark for people like us to know that achieving financial stability and transition of status from being comfortable to wealthy is possible with the right *investment* plan.
@@minoritymindset4823 Experience plays a key role when *investing* in diversified *stock markets*, which is why I have Rachel Hilda, whose experience has greatly helped me persevere in the diversified *stock market*. For three years she helped me grow my portfolio using her diversified knowledge of the financial *market*.
@@charitytoke6461 Thank you very much for the response, I don't know if you can share a medium that I could use to communicate with Rachel. It's really a tough time for me due to inflations and an additional source of *income* would be exactly what I need for me in these unprecedented times and does she accept a minimum amount for startup?
I rarely sub to channels specially on the first video I wach, but you sir are the exception Why did I sub?: 1 Useful free content with great advice 2 Less than 5 minute video 3 Next video was less than 10 minute and I loved the thumb and tittle 4 I feel like getting notifications from this channel will help me get my brain into code mode easier than watching anyother content and help me with procrastrination loop youtube tends to do to me
Sometimes you don't even need to fork or code a single line to contribute! I have opened several issues that has been resolved, by code, by other people. Sometimes just raising awareness helps!
Thank you so much . I'm a totally beginner and I was thinking about writing some personal project in order to level up my resume and github . but this is a good idea . I found my new place to play . Thanks
You left out one of the most important steps -- discussing the change you'd like to commit before working on it. I've had plenty of pull requests go ignored because maintainers just didn't care about the feature
First step is the harderst, totally true. To me the hard point is find a project where collaborate. I have the feeling most of them are very big to me right now.
I joined an open source project for I think a custom tuning software for speakers or something. Don't even know. Have zero experience with any sort of coding. They use me as the "guy who's never once touched audio software" tester. Boy let me tell you is it fun to watch someone who's just spent the ladder half of a week fixing bugs and doing programmer stuff only to be told that the UI that they thought was simple enough was in fact not simple enough. I am both critical and completely useless to the project at all times, but boy do I enjoy it.
Love how short yet detailed this is, not a 10-20 minute to an hour video, not a whole lecture/series, just straight to the point
time is precious. Glad you liked it.
Exactly this. Thanks for pointing it out. And to ya my man for the video
Ngl
@@LearnFastMakeThings This video is very good, could you make one on how to use git, and explain the fork and so on? please
Exactly, it seems that every video on youtube now is 10 minutes long and has like 2 minutes of relevant content. This one, though, is good and short. Subscribed :D
I agree, if I could start my journey over I would jump straight into Open source and treat that as my ‘projects’ vs building things on your own. Because not only are you contributing but you’re also working with others as a team. Most definitely will look good on your resume and you will for sure meet mentors and high name tech contributors and even get paid through open source. Would encourage anyone starting out to prioritize open source over building things or a portfolio for a job
Yes exactly! The type of experience you can get by working on projects that are already established and somewhat unfamiliar to you is so valuable. Starting a job working on a new codebase will be way easier because you’ve exercised that muscle working on open source projects
@@thewillderness7852 wrote, _"Open source isn't going to make you rich. Creating something on your own might."_
You may find this video more relevant than it first appears: ruclips.net/video/u6XAPnuFjJc/видео.html
@@thewillderness7852 1. Literally no software you produce on your own will make you rich unless it's some shitty mobile app.
2. Some of us prefer volunteering our time towards projects that are useful for everyone and guarenteed to not have any shitty monitoring, DRM, etc., large projects always need help.
3. Due to #2, it's significantly more fun than coming up with stuff on your own, besides, all of the heavy lifting has been done for you.
@@colbyboucher6391 1. It's the marketing that largely decides that.
2. Personal preference
3. Personal preference. Some of us enjoy innovating a little more from scratch.
You're not wrong. Open source is more valuable compared to building things when it comes to resumes and looking for jobs. But it's so much more fun to do stuff on your own, where you have 100% creative freedom and no BS politics, red tape, legacy etc. Sure people in Corpo world will be more impressed if I can manage these issues in open source rather than just build stuff on my own stuff, but hey why would I fight with that in my free time, when I have to do it anyways at work.
Contributing is fun, it's nice to be part of a project used by thousands of people
Totally agree!
@@EverRusting must be js developer 😬
@@EverRusting agreed, some even accept stupid prs and reject the useful one. There's a pr in a particular project which spammed time.sleep(), which got accepted, but the pr that refactored the codebase and made significant improves, gets ignored. This is really outrageous.
Really it is !
@@EverRusting I didn't make that experience and I would highly doubt bad experiences like you sadly made are the norm.
For me, I only contributed once, as I rather like to work on some personal projects in my free time. However, directly writing to the main dev of a huge utility I love on discord and figuring out some stuff, then creating a PR and see your changes solve an issue other people have is amazing. Most people are pretty chill and glad that you want to help.
It’s a wonderful feeling to find a bug in a piece of software you use and to submit a pr resolving that bug!
absolutely!
I wonder when AI will be able to fix the issues automatically, later this year?
@@Danuxsy soon but not that soon
@@Danuxsy I already ue ChatGPT to debug code. It not only fixes it, but more importantly it explains the fix.
I think you forgot step 0 when contributing code: Leave a comment on any issue you want to fix, state clearly that you would like to contribute a solution, and ASK(!) if a maintainer is there and willing to review/accept your work. It usually doesn't take long to get a response, gives you a general sense of the pace at which the repo operates, and saves you from contributing to dormant projects.
For the first PR it will take a couple of days to set up a dev environment, get familiar with the tooling, understand the test-suite, etc. Nothing takes the wind out of your sails faster than putting in those days of work just to see the PR sitting there for months with no feedback and no merge. So before you start, make sure you have talked to maintainers (like me) before you airdrop a PR. We don't want your work to sit around and collect dust, but unfortunately, most of us have to split our time between the project and a regular job. Having clear communication on this from the start goes a long way in having fun with open source :)
Hi, I'm just getting into coding myself, been doing some work on my own to prepare for some classes I have coming up in the fall (preparing for these community college classes by watching cs50 from Harvard lol, kinda feels like overkill but I don't like surprises and I want to excel at this.) So I understand the basics, but have only a little actual on hand experience (I've done all the programs provided in cs50, have bought a couple books on making games in Python and have coded some simple games, as well as currently working on building my own chess game just as a fun starter project and as an exercise in problem solving with code.) As someone who seems well versed in this area, do you have any tips for getting into this, like places I should start or where my minimal skills could be best put to use? I'm very good with the English language so I feel myself naturally drawn to documentation and editing, which was brought up in the video, and I think that would be an excellent place to start. Any advice, including any projects you yourself could use such help on, will be greatly appreciated!
yes. All good advice. thanks!
@@firefoxmetzger9063 A very good advice. Thank you. I would like to make my first open source contribution
This. I was taken back when he said to just go ahead with contributing to a project without contacting the people that maintain it. I would never go ahead without first contacting the person that maintain a project because they may not want or need help.
@@fisharepeopletoo9653just keep it up. stop looking online for answers. if you're going to college and you're doing things, it won't take much to find a job. do your first web page, that'll help you have "something to show", even if it's a real simple thing. really don't think big. the simpler the better.
Honestly, I think the more feedback you get on your PRs, the better. That means people doing code reviews care enough about you as a contributor that they’re willing to spend time going over your authored PR. It gives that much more meaning to your PR when it’s eventually approved and merged. And you can say, “I’ve contributed something meaningful to this project!”
Yes. every project varies, but as long as its constructive feedback and not toxic opinions it's all good.
It can be a shock the first time your ideas/contributions are beaten up on, but you end up with the contribution being all the stronger for it, and you start to look forward to finding the groups who will really put your work on trial
@@stevecarter8810so true, i work with someone on my team that is very strict, when i first joined i thought he was being overly nitpicky and hated adding him to reviewers list because he always had something to say, but now i gottten to know him more and got used to it . I can proudly say that thanks to his guidance, sometimes toxic but with good intentions, I have gotten a lot better with thanks to his advice and he became my favorite person on the team, it feels really good when he gives you good feedback and actually cares about what you put on
the problem is that I'm not smart enough to contribute anything meaningful to any project..
@@Danuxsy nah youre good u just gotta startt
Also, just remember to check whether the project is still active or not by checking the latest pull request date and also ask the owner before solving an issue, the issue might already be assigned to someone or for any reason they may not accept your PR so prepare for that as well just in case.
Oh yeah, getting into Linux and fixing small bugs and annoyances in the programs I used, or even just reporting them, that's how I got started.
It’s a great way to learn!
I started my journey with open source in 2019. Gradually I made my career in open source and now working for an Open Source company. The best part is ypu get to contribute to projects freely. There are lot of talented developers and almost every open source developer is passionate about their work. ❤️
P.S - I never worked on closed source projects 😂
very cool.
How was your interview?
@@pedrotorres2747 It was awesome. The interviewers were the engineers working on the project that I was going to join. They asked me very basic DSA questions and then some computer science concepts. They talked a lot about my projects, GSoC experience. Most of the interview was a open discussion on general programming topics.
@@deepspaceship I'm glad to hear that your interview went well, and I hope to have a similar experience in my future job interviews. I have experience in JavaScript and PHP, but sometimes it's difficult to access job opportunities because they require years of experience or even a bachelor's degree in my country. That's why I'm focusing on improving my English skills so I can work in another country that offers more opportunities. Do you have any recommendations for me?
Timestamps for those interested:
0:00 - Why contribute?
0:44 - Finding a project and an issue
1:33 - Read the rules
1:46 - Form the project, make a branch
2:03 - Feeding the RUclips algorithm
2:08 - Make your changes
2:23 - Push your changes
2:28 - Open a PR that resolves the issue
2:47 - Monitor and receive feedback gracefully
3:05 - Signing off
Thanks!
My guy went the open source way on RUclips lol
it's only 3min long 😂
@@PossumMedic still cool to see chapters with the youtube chapter feature + in this day and age everything longer than a tik tok is already very long ;)
@@LearnFastMakeThings Add it in the description so youtube can section the video :)
love this video because
1. On point
2. Time saver
3. Insightful
thank you!
this video changed my mind about open source projects, i never knew that it was so easy to contribute, thanks dude!
Glad I could help!
Let's be honest.
It's easy to submit contributions.
It's not always easy to contribute. As he said in the video, be prepared for the worst and do not attach too much feelings to your contributions.
I think the recommendation is to have at least a basic understanding of your chosen programming language
I can't agree with this enough. The sense of achievement for adding anything of value to something YOU value is amazing. I've even had my own fork become more popular than the original project, and made it the reference implementation for an IETF RFC. Aim high, and have fun.
Oh, and read "The Cathedral and the Bazaar" for a primer on how open source rewards contributors, and how contributors reward open source.
I've acquired my knowledge from the open-source community, and I actively seize every chance to contribute. Numerous individuals and companies have approached me for projects tied to one or more of my pull requests, opening up a plethora of opportunities for me. I am sincerely grateful for the enriching experiences this has brought into my professional journey.
what kinda projects? Web dev?
Probably the best, most straightforward video out here on contributing to open source projects. Thank you so much sir.
Thanks!
Great advice! Can’t believe I never thought to look at the dependencies of a project to find other projects to contribute to. Love that suggestion!
Glad it was helpful!
Like 1:20? I still don’t understand how you find other projects by only looking at dependency of one project
Note that contribution guidelines are sometimes not in the README file (called CONTRIBUTIONS, contrib, or something similar)
good point! thanks!
The best part of making PRs is in fact the feedback because you learn so much from it.
true. as long as everyone remains positive, its a good way to learn
@@LearnFastMakeThings .. or at least not negative. Most PRs I've made (and I've done a lot in the past) have pretty dry responses, but they are on the point.
I've always been really intimidated to contributing to an open-source project, but i think I just need to give it a go. Just looking through other people's code will be helpful, and making some changes can help me practice more all the things that I've learned. Will have to give this a try soon!
Love this straight to the point clean without water
My first contribution was not too long ago to inquirer js library. I was fixing uncaught errors throw in in some case of menu scrolling.
After tracking down all the calls I found just one line where the problem was.
My change was accepted and pushed to npm.
As a result I felt myself a hero of some meme who crashes people's prod servers with just one line change, because that's what I did by using es2020 operator "??"😅
Bunch of ppl with node 12 and lower were complaining, even dependencies freeze quick patch was rolled. 😵💫
Luckily I managed to replace it with polyfil before too much damage been made. 😊
This kind of experience was new to me, scared and excited at the same time 🙃
it can be difficult to put yourself out there but its also rewarding to see your stuff get merged.
This video alone shows that this dude knows how to do useful contributions in general.
Wow, finally a simple explanation for how to contribute to open source
Appreciate the comment!
I would've never clicked if it wasnt that short. Great Video!!
Glad you liked it!
I try to make bug reports instead of providing the actual solution, to keep the (minor) contributor count low
so that license-wise there are no problem if someone decides to change it (I seriously had people hit me up if changing the license was ok, because I added one DLL the repository).
And I seriously had one dude complaining about my bug report, that I wasn't fixing it myself
and that I suck for being a security researcher who just posts bug reports on open-source projects so that they can use the unfixed bugs in their reports to say open-source sucks (of which none is true).
I legitimately just had a wrong free bug when running the code "casually". I provided reproducible steps, test files, everything.
In the end I fixed it in the same manner as the rest of the code has been fixed at a similar line of code, created a pull request and it still hasn't been merged. (~6 hours wasted, plus a giant "f u" in my face)
Another time, I added a feature I wanted, created a pull request and basically got a "won't merge",
because it simply doesn't fit the idea of the maintainer of what the project should look like.
(Neither would there have been any grounds to make this feature fit, because it's nature was just not fitting)
Other times I create a pull request with the message: "Please test before merging" and it gets merged so fast that it can't possibly have run through any tests.
Other times it takes 2 years before my pull request gets accepted, despite it literally being just a fix where someone accidentally had swapped x and y (or rather u and v).
And now to the worst offender, which is my professor at uni,
wants me to rebase my 60+ commits (among which are also commits of colleagues) into 4 big commits that are actually features that rely on each other,
rewrite history that way and screw up authorship of files and cause me a bunch of headaches and increased testing efforts when I'm already 1 year due to submission.
Not just that but it eliminates the detailed description of each commit and thereby I need to change a bunch of files again and reconsider which stuff I put into the documentation and which not, while before it was very clear that certain bugs that have been fixed did not need inclusion in the documentation, but had a detailed explanation in source control.
THAT'S my experience with open-source.
Im sorry to hear that you've had a poor experience. Sometimes contributing is harder than it really should be. I know there are some toxic environments out there and some projects that just dont appreciate contributors. but... There are also some great open source communities that openly welcome contributions of any type, especially security research.
This is why I have a hard time taking the plunge into contributing, I've heard some many negative things about the open source community
Is your prof high or something? If your commits are atomic with good messages, don't rewrite history (which is already bad practice in 99% of all cases) eliminating that beautiful, self-describing and maintainable git log.
That was really a wonderful video which consisted pure content and no bullshit....Keep Going, mate...Thanks again!
I was so happy to contribute to Mantine React UI library. It feels amazing to see my profile on the contributor list and know that it will impact thousands of people :)
It is a good feeling. especially for larger projects that are used by many.
Helping more people become comfortable with open source and contributing in such a clear concise video is fantastic, well done. Telling people "github is the new resume" is utter nonsense!
thanks for the comment. Its too late now, but i think if i could do it again i would soften that statement. github is like a portfolio, not necessarily the new resume.
I believe your channel will be big in the future! nice work! keep it up man!
Thank you!
Quick and straightforward. I didn't have to waste 10 minutes of my life
Yes I mean I pushed for certain interface features during development on Blender's Grease Pencil. And I saw it through. I insisted that they should sync up the toggle options for onion skins and layer visibility in the timeline section and the tool section. And whaddya know, they decided to include that. 🙌😄
If you ever have an idea that can help make an open source project better, it's best to speak up about it and keep pushing for it to happen.
Did you code it? Or just demand repeatedly that someone else do it?
Forking, pull requests, and other things to pull, change, and send changes to the base project might be more explanatory. Thanks, I like this content.
Thanks a lot for the video, very simple yet very well explained.
Glad you liked it!
As an open-source project that relies on help from everyone, thank you for this video :)
This is great, I’ve always wanted to contribute to an open-source project but it always seemed so intimidating.
thanks! no need to feel intimidated. find something you like with some like-minded individuals and it will be fun.
Thanks for the quick and short video. Really helps out and doesn’t overwhelm newcomers!
You could also maybe in the future talk about issue tags and good first issues. You can actually use advance search to filter these and then I feel contributing becomes much easier.
Good stuff tho!
Great idea! Appreciate it.
Love how you went straight to the point. Short and informative.
I'm a hobby programmer and I'm really interested in contributing to open source, but I'm very intimidated.
This was super encouraging. Thank you!
I mean, I literally had no clue how this works. This video is everything that I needed. Thanks 1 million you are a lifesaver❤
So glad I was able to help!
Submitting tickets, well written, researched and with reproduction steps, can also be really helpful to maintainers or to yourself.
I have first hand experience at finding bugs or missing features in a framework I use at work, write professional tickets (what's the issue, severity, why it's an issue, expected behavior, tracing the origin of the issue in the source code if possible, providing code/pseudo code when a PR isn't an option) and get notification of a patch within a week on totally open source projects.
That's also a good skill to have and you can use it at interviews if you can show multiple tickets and their resolution time compared to other tickets or average closing time in a project.
very true. A well written, detailed issue report goes a long way. There's nothing worse than "this thing doesn't work" with no additional details!
*Thank you* so much for this.
GitHub has always been really confusing for me to use and navigate, so having clear, to-the-point instructions or standards here have been really helpful.
An amazing video. So much information condensed into such a small sized video. Absolutely love it!
Thank you!
AMAZING video. Loved it. But I have a request: please create a longer version of this video explaining each step of the process in a bit more detail.
Great suggestion!
Wow...this was both concise yet extremely informative. Thank you!
What's most wild to me is how often people run into an issue or hurdle when installing some software then don't just go in and add their steps to resolve into the projects documentation. If I ever have an issue with documentation and I find the answer and it isn't in the documentation already, I open a PR with those changes added.
Great video! Perfectly short and digestible. As somebody who's been wanting to get into contributing to open source, this video was extremely helpful!
Glad you liked it!
You are the best creator❤, this video shows how genuinely you wanted to share your knowledge, but not just make a content that makes you so special and you are amazing❤
I appreciate that!
This is really great and something I didn't know you could do.
I will have to look into this a lot more as I think the experience and feedback is something you are unlikely to get elsewhere.
Glad it was helpful!
Dude taught us all THAT in 3 minutes.
Thank you so much.
Thanks for this video! I've been using Git Hub for a few years now to manage personal projects, but I've never understood how to work on other, open source projects. I've heard about forks and pull requests, but never understood exactly how they worked. So much info in a ~3 min video!
Glad it was helpful!
I’ve searched and watched many video which only let to lots of confusion, but this was gold❤
This sounds romantic but the truth of the matter is: It's extremely difficult to find a repository to commit to. The explore page shows you repos across all languages, if you nail down a single language the most starred repos are usually pretty quick to fix trivial bugs while the much more complex ones are left open.
The less stars a repo has the worse, when you find a repo with an issue you could tackle you already see an open pull request from 4 months ago.
As a new developer this can be a really frustrating experience.
love the video. I'm just confused on one thing. What's the point of forking the project? Isn't it possible to clone the project and then create a branch for what you're tryign to resolve?
The issue with cloning is permissions. You probably won’t have permission to push your branch to the project. Thanks for the question.
that was a straight to the point, very informative and cool to watch video. Great stuff man. I just started on the computer science carreer and this was 3min of solid help in my path
I tried. And here's the thing. I submit the pull requests, the other developers copy the change, generate their own pull request and approve their own pull request rather than approving mine. It's kind of fool's gold.
Man, that's a bummer. I've personally not encountered this.
Short, instructive, engaging, and straight to the point. Nice!
Is it really worth the time investment? Doesnt seem like that to me tbh, its a great time sink to get to know a project enough to contribute, and then what is the reward? A cool looking github profile? I think there are a lot better ways to improve your skills or/and increase income than this
I’d say it’s worth it. Most hiring managers including myself will check someone’s GitHub profile before an interview. It’s not really about the quantity of commits. It’s more about the types of contributions and the quality of the code.
@@LearnFastMakeThings Creating own projects and publishing them on your github would be just as or more benefical no?
Yeah, if that’s your preferred approach.
@@szilagyimiklos4757 I guess I look at it a different way.
If someone contributes to a somewhat large repository, it most likely means they are capable of reading source code of other people(AKA has experience and won't need much time to adapt), and when their PRs are merged, it means they wrote code that's good enough to be useful. But doing all of your projects on your own kind of makes you live in your own bubble and does not expose you to how others code. It potentially means you're inexperienced when it comes to writing code that is manageable by a team.
You missed the point....it's about collaboration skills and the ability to not only write code but read others people's coding style and add to it....
To keep it short: I'm also a business owner that need programmers and I write my own code....even if a guy with a degree for some reason didn't do what he said in this video I wouldn't hire him even with a degree....it's about team work and adapting to get the job done. Not how good one programmers is...you can't do it all sooooo team work...
Ask anyone that programs for big tech.
Thank you! I know the video is slightly old, but I’m job hunting for full-stack junior dev roles right now and this video succinctly explains to me how I can improve my job hunt by showing how to easily contribute to open-source projects. Now I just have to find something to work on and hopefully not break anything 😂😂
Lol. That second part is always the challenge
I also want to suggest a change: remove the red arrow in the thumbnail. It points to nothing meaningful and the colour is ugly, especially in the context of navy and green colours. The text, ‘This One’, can go too.
I feel like forking your video is bad practice, so I won’t do it myself.
Thanks for the feedback
@@LearnFastMakeThings Tbf I think similarly. The thumbnail is actually pretty, but the red doesn't really fit on the color scheme. Without the arrow and the text it would be a more sharp and clean thumbnail. Ofc that's only my opinion though.
Short and straight to the point. I like that
thanks!
And what's the benefit? a reward from god?
72 virgins maybe, who knows
no, probably not. benefits can be experience, or just getting a feature you need in a project you use frequently.
This is simple yet best explanation!
I also made my first contribution few weeks ago by adding background color to a navbar of a frontend site and it got merged 😀
Nice! Thanks!
"Github is the new resume". No it's not. Hardly anyone looks at github projects when hiring.
thanks for the comment
time
Will
Tell
Yes it's totally luck. Many don't care of github
@@chineseRATFACEdon't they have remote position?
So they look at what
Best dev piece of knowledge I've got in 3 mins ever
Amazing. I have created a meetup "Together, we OpenSource". My goal is to help underprivileged and underrerpresented groups of people to find their path in IT world.
I hope you do not mind if I share your video?
BTW, the group is fully remote and free to join.
Love this!
@@LearnFastMakeThings thank you. My meetup grew from 1 person to 114 since the 5 th of June. I cannot mentor 1:1 all of them, so I'm trying to save the answers to my own YT channel. Please subscribe, if you have some time.
One of my favorite videos on the internet. So short yet so valuable.
:)
Thanks man. That's exactly what I needed. Short and to the point.
Superb video. But, let me share this here knowing it can uplift someone that comes across it. Effective financial management made me rich and it is all you need if you want to build a strong financial future tomorrow. I started with 1000USD, 3 years ago I invested in a diversified stock market and fast forward to now I am worth 500000USD and am currently finishing my 8 unit apartments. I'm only 35 years old. Diversified stock investments have always proven to be very profitable, especially with the help of experts.
I'm really impressed. At 35, i was worth a little over $200,000 from * in the stock market. But what you've done with your *finances* and numbers you worth, is pure genius.
You have done well. It's people like you who set the benchmark for people like us to know that achieving financial stability and transition of status from being comfortable to wealthy is possible with the right *investment* plan.
I'm curious, is *investing* in a diversified stock *market* a pretty lucrative venture? Can you share how you achieved these figures?
@@minoritymindset4823 Experience plays a key role when *investing* in diversified *stock markets*, which is why I have Rachel Hilda, whose experience has greatly helped me persevere in the diversified *stock market*. For three years she helped me grow my portfolio using her diversified knowledge of the financial *market*.
@@charitytoke6461 Thank you very much for the response, I don't know if you can share a medium that I could use to communicate with Rachel. It's really a tough time for me due to inflations and an additional source of *income* would be exactly what I need for me in these unprecedented times and does she accept a minimum amount for startup?
Thank you so much for this. I have never seen the complete process being explained so clearly like this.
Glad it was helpful!
I rarely sub to channels specially on the first video I wach, but you sir are the exception
Why did I sub?:
1 Useful free content with great advice
2 Less than 5 minute video
3 Next video was less than 10 minute and I loved the thumb and tittle
4 I feel like getting notifications from this channel will help me get my brain into code mode easier than watching anyother content and help me with procrastrination loop youtube tends to do to me
thanks for the feedback. really appreciate it!
To the point, short, well explained. Thanks!
I love the short format of the video. Thank you.
Didnt even start the video and already hit subscribe since you are wearing a woodford reserve distillery shirt. My actual favorite.
coffee now, bourbon later.
Thanks! as someone trying to land a programming gig, I appreciate this idea-
You bet!
Sometimes you don't even need to fork or code a single line to contribute!
I have opened several issues that has been resolved, by code, by other people. Sometimes just raising awareness helps!
absolutely
I've been looking for someone to follow in their Cloud Developer journey. Thank you for taking time to make this, liked and sub'ed!
Awesome, thank you!
This is fantastic. I always thought forks were there for you to take over a project if it died or needed to change hands. So glad this isn't the case!
They can be used for that as well, but yeah it’s good that it’s not the original intended purpose
Thank you so much . I'm a totally beginner and I was thinking about writing some personal project in order to level up my resume and github . but this is a good idea .
I found my new place to play .
Thanks
Glad it was helpful!
Great content! I am currently looking for a job so it might be the right time to give this a go.
best guide I've found on this topic, thanks! All thriller, no filler!
Wow, thanks!
This is so far the most clear-cut explanation and also has motivated me to contribute more!
Thank you so much for the video !!
Glad it was helpful!
Leaving the good content of this video aside, I like the intention behind this video - we need more people (or may I say leaders) like him
Prepare for the worst and hope for the best, nice one bruh, thanks, the video is amazing!
Very good ! I found the suggested steps extremely practical to start right away. thank you !
Thank you so much for this post! I’ve always wondered how to contribute, I love how concise and straight to the point it is!
you're welcome!
good enough to get a kick start and that's all we need.
You left out one of the most important steps -- discussing the change you'd like to commit before working on it. I've had plenty of pull requests go ignored because maintainers just didn't care about the feature
True. Thanks for the contribution!
As a 3 month in dev I appreciate a lot this tip. Thx
glad you like it!
First step is the harderst, totally true. To me the hard point is find a project where collaborate. I have the feeling most of them are very big to me right now.
if you have your own projects, its a good place to start. look at all the stuff you use and see if any of them would be better with new features.
Wow amazing! thank you for providing these detail explanations within 3 minutes.
Thank you so much! youtube algo is working overtime to give me exactly what i needed
Glad I could help!
videos like this would have helped me so much 6 5 years ago and it is greatly appreciated
if only i had a time machine. Getting views on youtube was also easier 6 years ago, lol
I thought this would be something actually life-changing, but it's just a resume. If I needed a job, I'd have one by now.
You don’t need a job? Nice. How do you make money?
I love how you went straight to point!
thanks! time is precious!
straight to point + crystal clear explanation...
Thanks!😊
I love this video. Thank you. I've been contributing for a while, when I can, or I find a bug.
Straightforward. Thank you for making my first contribution painless.
I just subscribed based on how effective this video was, keep up the good work.
Welcome aboard!
I joined an open source project for I think a custom tuning software for speakers or something. Don't even know.
Have zero experience with any sort of coding. They use me as the "guy who's never once touched audio software" tester. Boy let me tell you is it fun to watch someone who's just spent the ladder half of a week fixing bugs and doing programmer stuff only to be told that the UI that they thought was simple enough was in fact not simple enough. I am both critical and completely useless to the project at all times, but boy do I enjoy it.
This is gold! I love that you jumped in, and the community sees the value of your contributions!