Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Collaborating on Open Source Software

Collaborating on Open Source Software

There are several reasons you might want to contribute to open source software. For me, it was that I wanted to learn in a more useful way than doing programming challenges. So I looked into how I could contribute to open source projects that I use myself.
After contributing for almost two years, I notice that I have learned a lot from my contributions (which has been useful at work), as well as have made friends and have become part of a community.

In this talk I will share my experience with contributing to Cucumber, including an early mistake (merging something that wasn’t ready yet) and fixing it with the support of core maintainers, and still feeling welcome!
You’ll learn how how to find your project and contributions to start with, how to connect with the community to make sure your contributions are useful and the many different types of contributions you can make.

Contributing to open source is a way of giving back to the community. In addition, it is a way for you to learn, collaborate and become part of a community. Getting (constructive) feedback on a pull request and collaborating to make things even better is a great feeling!

Marit van Dijk

October 06, 2022
Tweet

More Decks by Marit van Dijk

Other Decks in Programming

Transcript

  1. Collaborating on 
 Open Source Software 
 
 Voxxed Days

    Cluj-Napoca – Oct 6th, 2022 @MaritvanDijk77 
 github.com/mlvandijk 
 https://maritvandijk.com/
  2. Report Issues •Ask if not sure •Check for duplicates •Provide

    relevant information: use template (or add one!) @MaritvanDijk77
  3. Report Issues •Ask if not sure •Check for duplicates •Provide

    relevant information: use template (or add one!) •Create an MCVE (https://stackoverflow.com/ help/mcve) @MaritvanDijk77
  4. @MaritvanDijk77 Find a project • Awesome for Beginners • Up

    For Grabs • Issuehub.io • First Timers Only • Good First Issues
  5. Check how to contribute • README • CONTRIBUTING (a.k.a. HACKING)

    • LICENSE (a.k.a. COPYING) @MaritvanDijk77
  6. Check how to contribute • README • CONTRIBUTING (a.k.a. HACKING)

    • LICENSE (a.k.a. COPYING) • Code of Conduct @MaritvanDijk77
  7. Check how to contribute • README • CONTRIBUTING (a.k.a. HACKING)

    • LICENSE (a.k.a. COPYING) • Code of Conduct • Style guides @MaritvanDijk77
  8. Check how to contribute • README • CONTRIBUTING (a.k.a. HACKING)

    • LICENSE (a.k.a. COPYING) • Code of Conduct • Style guides • Contributor License Agreement (CLA) @MaritvanDijk77
  9. Check how to contribute • README • CONTRIBUTING (a.k.a. HACKING)

    • LICENSE (a.k.a. COPYING) • Code of Conduct • Style guides • Contributor License Agreement (CLA) • Ask! @MaritvanDijk77
  10. Get the project •For to your profile •Clone to your

    machine •Manage remotes @MaritvanDijk77
  11. TL;DR •Contributing to open source doesn’t have to take a

    lot of time or programming skill •If you want to contribute, but don’t know how – ask the community! •Please go and collaborate! @MaritvanDijk77
  12. TL;DR •Contributing to open source doesn’t have to take a

    lot of time or programming skill •If you want to contribute, but don’t know how – ask the community! •Please go and collaborate! @MaritvanDijk77
  13. TL;DR •Contributing to open source doesn’t have to take a

    lot of time or programming skill •If you want to contribute, but don’t know how – ask the community! •Please go and collaborate! @MaritvanDijk77
  14. Collaborating on 
 Open Source Software 
 @MaritvanDijk77 
 github.com/mlvandijk

    
 https://maritvandijk.com/ https://maritvandijk.com/presentations/collaborating-on-open-source-software/