Download to read offline
Uploaded byMiguel Ignacio Balparda
Maintaining an Open Source Project
An open source project allows anyone to modify and access source code, providing transparency into technical decisions and better understanding of features. The document discusses maintaining the Nexcess_Turpentine open source project, noting its 170 forks, 370 stars, 28 releases, 700 closed issues, 90 closed pull requests, and 17 contributors. It defines issues as a way to report problems or suggestions, and pull requests as proposed solutions created by forking the repository, making changes, and submitting a pull request for review.
More Related Content
Similar to Maintaining an Open Source Project
Maintaining an Open Source Project
- 1. Nexcess_Turpentine Maintaining an OpenSource Project
- 2. What is anopen source project, and why is better than proprietary code? Can be modified by anyone. Access to source code. Better grasp on its features and functionality. Transparency in technical decisions.
- 3. Open source projectswe use everyday:
- 4. Even a smalldeveloper can find a way to help millions of others.
- 6.
- 7.
- 8. Nexcess_Turpentine 170 forks 370 stars 28releases 700 closed issues 90 closed pull requests 17 contributors
- 9. Practical definition ofIssues: Best way to tell core developers about a problem, an improvement or a feature. Anyone can answer an issue. Not a place to scream at developers. Open source project equivalent to a ticket.
- 10. “The needs ofthe many outweigh the needs of the few.”
- 15. Pull requests andhow to create them: Fork the repository in your account. Do changes and push them to GitHub. Open a PR and point it to devel. Check if tests are passing. Core developers revise it and merge it. Congrats, you are a contributor!
- 16. Issues are problemsand suggestions. Pull requests are solutions.
- 21.
- 22. Thank you forcoming! Maintaining an Open Source Project