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

Why, Where and How to contribute to Open Source

Isabel Costa
December 07, 2019

Why, Where and How to contribute to Open Source

In this talk I will provide my insights over why it can be helpful to your career to contribute to Open Source, where you can get started with it (OS communities, initiatives, projects, etc) and how you can actually contribute in multiple ways to Open Source, whether you're a developer, designer, tester... or just a curious person who wants to contribute to a project you care about.

Isabel Costa

December 07, 2019
Tweet

More Decks by Isabel Costa

Other Decks in Technology

Transcript

  1. Why

  2. Where • Which platform to use? • Which projects to

    contribute to? • What about communities?
  3. Be aware of ... • Is the project active or

    inactive/archived? • How responsive and welcoming are the maintainers? • Are there beginner issues or any other available? • Does the project have a License? • Does the project have Code of Conduct? • Is the project well Documented? • Contribution guidelines?
  4. Be aware of ... • Is the community beginner friendly?

    ◦ Do they have Code of Conduct & Reporting Guidelines • Is the community transparent? • Is the community inclusive? • Do they promote open communication? • Is it open for every type of contributions?
  5. Where to find these ... • Projects you use or

    care about • Communities “well” established or organized ◦ GSoC has a list of communities • Through initiatives: Hacktoberfest, 24 Pull Requests … • Other: Up for grabs, Code Triage
  6. How

  7. What can you contribute with? • Implement new features or

    fix bugs • UI/UX Designs and Wireframes • Solution Architecture • Outreach / Research • Documentation • Testing and reporting issues • Help others contribute • Review work from others • Give feedback • Mentor for Open Source initiatives • ...
  8. You can contribute as a ... developer QA tester technical

    writer designer project manager interested person
  9. My personal examples • My LICENCE link change of Elastic

    UI framework • Reported an issue and ended up solving (systers.io) • Open Data Kit PR (I continued someone else work) • Code Review I did to fix typos • Added a portuguese open source project