[Python-Dev] project culture: take responsibility for your commits

Nick Coghlan ncoghlan at gmail.com
Thu Oct 3 01:21:23 CEST 2013


On 3 Oct 2013 09:00, "Nick Coghlan" <ncoghlan at gmail.com> wrote:
>
> Stefan,
>
> You blew up a minor design disagreement over the new async parsing API
for XML into a huge impending disaster that would destroy the XML library
APIs forever. In truth, even if we had left the original commit alone it
would, at worst, have resulted in a slightly inconsistent API design.
>
> I get that you're passionate about the relevant API since you need to
replicate it in lxml. I even agree that the API we ended up with after I
got involved as a mediator to separate out the legitimate complaints from
the hyperbole is better than the one that was originally committed.
>
> But when your opening gambit is to accuse people of complete incompetence
(and you repeat similar accusations multiple times over the course of the
disagreement), developers are entirely within their rights to stop
listening to the abuse.
>
> It's important to remember that this is a project staffed by volunteers,
and some basic civility and appreciation for those efforts goes a long way
in obtaining a more constructive response. In the absence of that, don't be
surprised if the reaction is "There may be a valid complaint somewhere in
there, but I'm not wading through the vitriol to look for it".

I'll also note that the affected developers *didn't* completely ignore the
concerns you raised (which would have been an entirely reasonable
response), but instead asked me to help out as a neutral mediator. That's
an entirely responsible thing for them to do, and one that resulted in the
underlying technical concerns being resolved *despite* the unwarranted
abuse.

Regards,
Nick.

>
> Regards,
> Nick.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20131003/77a1757c/attachment.html>


More information about the Python-Dev mailing list