[haiku-development] Re: Dario
- From: waddlesplash <waddlesplash@xxxxxxxxx>
- To: Haiku Development ML <haiku-development@xxxxxxxxxxxxx>
- Date: Sun, 28 Oct 2018 17:10:07 -0400
On Sun, Oct 28, 2018 at 3:54 PM Adrien Destugues
<pulkomandy@xxxxxxxxxxxxx> wrote:
On Sun, Oct 28, 2018 at 02:58:07PM -0400, chase rayfield wrote:
How about not going down that path. We don't need any more burned
bridges and that is the only thing tha can come from flames.
The media kit has been a target of several developers desire to fix
over the years and we *finally* have someone working on it now and you
want to shoot them down... this seems couterproductive in the extreme.
You underestimate how much energy it drains from other developers
(myself included) to handle aggressive and inappropriate behavior. And
even the time spent writing and replying to these emails. All of this
has a huge cost, and is very dangerous in the long term. Given the
choice between one aggressive but productive developer and the rest of
the team, the decision for me is definitely on the side of the rest of
the team.
+10.
Dario is often correct, but the fact is that it often takes a *lot* of
emotional labor on the part of others to get him to explain himself in
a way that we can understand, and there is often name-calling
(sometimes by both sides...) before that happens.
I have an email from Stephan (stippi) from a few years back, on an
email chain that was getting rather heated, in which he defuses an
argument between axeld and jscipione and ends by talking about how "in
a community project like ours, it's not only about the code quality."
That sentiment really struck me then, and now that I understand the
project dynamic more, it just seems so obvious -- but it wasn't so
obvious then.
Haiku has survived for so long partially because we value quality over
quantity. Not just in code (though this is certainly the case, as
anyone who reads our code vs. Linux's code can attest to), but also in
people and in community, because if the people and the community start
rotting, the code will follow, eventually.
It is not a problem with the code. It is a problem of aggressive
behavior, difficulties cooperating with other developers, and draining a
lot of motivation from everyone as a result. This is harmful and
dangerous for the project as a whole, and more than I'm willing to pay
for a new Media Kit.
Yes, indeed.
-waddlesplash
Other related posts:
