bkubicek/Marlin — comment on commit 4589ab3f860cfc4c22060412e86434b49f9ff533
File:  line 0
By lampmaker:

Hi guys,

I agree with most of both of your comments, I can see both sides of the issue.

However, I do think it's good to agree on some collaboration rules. It's not always as simple as making sure your code doesn't break any other. There are situations where some discussion beforehand would prevent things like this getting out of hand.

Changes that are simple bug fixes, corrections, minor improvements etc can be committed without any discussions. However, there are many features that could be implemented in different ways, and different people will hold different opinions on what is the best way to implement it. In such cases, it's probably better to discuss and agree upon an approach beforehand, or work on separate branches and merge them into the main branch after everyone has agreed it's a good thing to do.

Going back and forth because one likes approach A better, and the other likes approach B better creates a lot of frustration with everyone and is a waste of time.