際際滷

際際滷Share a Scribd company logo

Open source-saturdays

Tejas Bubane
Tejas Bubane

This document discusses how to contribute to open source software by selecting a project, finding issues to work on, submitting pull requests, and engaging in discussions. It emphasizes the importance of open source software, notes benefits like learning and community, and provides tips for effective communication when contributing. The overall goal is to give back to open source communities and help make better software.

1 of 7
Download to read offline
CONTRIBUTING TO OPEN SOURCE SOFTWARE - TEJAS BUBANE FOR CYBRILLA OPENSOURCE SATURDAYS
WHY? We bene鍖t a lot from open source Imagine not having any of the open source software that we are using It is our moral responsibility to give back to the community and make better software For our bene鍖t - learning, getting better Community work culture Company reputation
HOW? Select a project Fork & Follow READ READ READ Find an issue Comment on issue that you are working on it Try to 鍖x it - ask for help if required github code search or `ag` command Send a Pull Request
HOW? - AFTER SENDING PR Discussions on code Follow coding and git standards Fixing Squashing Always push to the same branch
HOW? - OTHER WAYS Report Issues you come across Help Reproduce Issues Documentation
SOME THINGS TO KEEP IN MIND Be good while communicating Async communication No obligation Call people by their 鍖rst name Capital letters means shouting Do not use SMS language No dots
LETS MAKE THE WORLD A BETTER PLACE

More Related Content

Open source-saturdays

  • 1. CONTRIBUTING TO OPEN SOURCE SOFTWARE - TEJAS BUBANE FOR CYBRILLA OPENSOURCE SATURDAYS
  • 2. WHY? We bene鍖t a lot from open source Imagine not having any of the open source software that we are using It is our moral responsibility to give back to the community and make better software For our bene鍖t - learning, getting better Community work culture Company reputation
  • 3. HOW? Select a project Fork & Follow READ READ READ Find an issue Comment on issue that you are working on it Try to 鍖x it - ask for help if required github code search or `ag` command Send a Pull Request
  • 4. HOW? - AFTER SENDING PR Discussions on code Follow coding and git standards Fixing Squashing Always push to the same branch
  • 5. HOW? - OTHER WAYS Report Issues you come across Help Reproduce Issues Documentation
  • 6. SOME THINGS TO KEEP IN MIND Be good while communicating Async communication No obligation Call people by their 鍖rst name Capital letters means shouting Do not use SMS language No dots
  • 7. LETS MAKE THE WORLD A BETTER PLACE