Do You Know Open Source Contribution Etiquette? ( a.k.a. don't re-order my house when you fix my tap)
30/03/2016 6:07 AM by
If you get a tradesman in to fix your tap, and on the way to the kitchen he sees your bookcase is messy and re-orders it for you.... you probably wouldn't be very happy.
When you contribute to open source projects it is great to fix bugs and contribute features, but it is essential to be respectful of the people that came before you, and possibly have invested lots of time in putting everything where it currently is.
- Figure: Bad Example - bad open source contribution etiquette involves gratuitous refactoring, re-organisation of files and classes, changing of formatting beyond those used throughout the rest of the project
- Figure: Good Example - good open source contributors review the CONTRIBUTING.md for the project and work within the guidelines provided, they follow existing coding styles and architecture and if large refactoring or changes are required communicate with the community and the core contributors
This issue is described beautifully here http://tirania.org/blog/archive/2010/Dec-31.html
Do you feel this rule needs an update?