[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1051371: debian-policy: stop referring to legacy filesystem paths for script interpreters



>>>>> "Luca" == Luca Boccassi <bluca@debian.org> writes:
    Luca> Secondly, and less importantly, while I appreciate it's not
    Luca> how you handle policy changes, the way the rest of the
    Luca> distribution works is by 'building consensus' on mailing
    Luca> lists. Now I don't particularly like it, but it is what it
    Luca> is. And that means if somebody comes up with the most
    Luca> egregious nonsense like, to pick a completely fictional
    Luca> example, "hey folks, usr-merge broke docker, rsync and
    Luca> ansible, we need to revert it", and it is left unchallenged,
    Luca> then it becomes doxa.  So it has to be challenged. Every
    Luca> time. After half a decade, you don't think _that_ is
    Luca> exhausting?


Thanks for sharing this.
I understand what you've been doing a lot better now.  And if it is
actually true that you need to challenge these assertions every time,
your behavior makes more sense to me.

However, it's been my experience that challenging these assertions every
time is unnecessary.  It actually makes it harder to judge consensus and
keeps discussions alive longer than they need to.
I actually think that there are cases where if you had said less, a
consensus you would have liked just fine would have emerged faster  than
has happened.
Often when someone says something rediculous in a consensus discussion
it is best to let it fall into a void of silence.
Challenging it can sometimes just give it energy.

I would be very open to helping you (or anyone) explore how to work more
efficiently in a consensus environment and how to espace from a
consensus discussion when consensus is the wrong tool.
I realized that I focused a lot on consensus during my term as DPL.  A
lot of that was that I was hoping to help people explore how to approach
consensus discussions better (and because it was the right tool for some
of those discussions).
But there are a lot of discussions where consensus is the wrong tool.
And now that we've leveled up how we approach consensus discussions,
perhaps we should level up how not to have them:-)

Attachment: signature.asc
Description: PGP signature


Reply to: