Re: [PATCH] Documentation/CommunityGuidelines

From: Theodore Ts'o <tytso@mit.edu>
Date: Jun 12, 2013, 12:27 UTC
Message-ID: <20130612122723.GA26281@thunk.org>
In-Reply-To: <CAMP44s10TVF9-uT5OtCLXBKrrXAspYnHM+go1zvu6ocMZwN14A@mail.gmail.com>

On Tue, Jun 11, 2013 at 06:19:23PM -0500, Felipe Contreras wrote:

Show 5 quoted lines

> Fair? Fairness requires to judge each action without biases, nor
> double standards. In the case of an open source community it requires
> you to listen to the arguments before dismissing them, and consider
> the patches before dropping them on the floor. Fairness requires no
> favoritism.

At least in development communities that *I* run, if someone were as rude to me as you have been in some previous exchanges to Junio, I would have set the bozo bit a long time ago and reviewed your submissions with a very jaudiced eye, and treated your non-technical arguments with same amount of attention as I give madmen and drunkards in the street. Junio has given you *far* more latitude than I would have.

Keep in mind, the demands for respect go in both directions, and in non-technical matters about style and "good taste", at the end of the day the maintainer does get to have the final say, because he or she is the one who applies the patches or accepts the pull request. So if the maintainer says something like, "maintaining ABI backwards compatibility for libext2fs (or for kernel syscalls) is critically important", that's not up to you. Sending me abusive e-mails about how I'm not listening to your arguments isn't going to help. You can try to change my mind with reasoned arguments, but for questions like that, or what functions do or don't belong in a library, the maintainer is the benevolent dictator.

Things a very different for things like "this change causes a 30% performance regression in a particular workload". For those sorts of technical questions, a much more collaborative discussion style is important. But for questions of what is and isn't "good taste", it's not a good idea to reply to a maintainer's e-mail with "that's your opinion" over and over again. For things like that it *IS* his (or her) opinion, and if you can't live with it, you'll save a lot of bandwidth on the mailing list by moving on to some other project.

Regards,

					- Ted