From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [ANNOUNCE] Emacs 25.3 released Date: Fri, 15 Sep 2017 11:01:24 +0300 Message-ID: <83fubomluz.fsf@gnu.org> References: <87wp55t0un.fsf@petton.fr> <5defcc74-e4d2-57c9-3307-fe5f7ac66fb7@cs.ucla.edu> <83r2vbq2ph.fsf@gnu.org> <87efrbixj1.fsf@zigzag> <87377pixhf.fsf@zigzag> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1505462500 31649 195.159.176.226 (15 Sep 2017 08:01:40 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 15 Sep 2017 08:01:40 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 15 10:01:29 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dslZ2-0007ks-CI for ged-emacs-devel@m.gmane.org; Fri, 15 Sep 2017 10:01:28 +0200 Original-Received: from localhost ([::1]:51824 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dslZ4-0007CX-QM for ged-emacs-devel@m.gmane.org; Fri, 15 Sep 2017 04:01:30 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54250) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dslYy-0007CE-Hq for emacs-devel@gnu.org; Fri, 15 Sep 2017 04:01:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dslYt-0008Uo-1c for emacs-devel@gnu.org; Fri, 15 Sep 2017 04:01:24 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:42668) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dslYs-0008Uk-Ur for emacs-devel@gnu.org; Fri, 15 Sep 2017 04:01:18 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2729 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dslYs-0004Xp-Dp for emacs-devel@gnu.org; Fri, 15 Sep 2017 04:01:18 -0400 In-reply-to: <87377pixhf.fsf@zigzag> (message from Thien-Thi Nguyen on Thu, 14 Sep 2017 08:51:40 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:218313 Archived-At: > From: Thien-Thi Nguyen > Date: Thu, 14 Sep 2017 08:51:40 +0200 > > The primary reason to maximize process transparency is to reduce > potential misunderstanding. That's the advantage, yes. The (not insignificant) disadvantage is that every revealed detail of the process tends to trigger a non-trivial amount of discussions, objections, counter-proposals, etc. When there's no urgency, this disadvantage is negligible, and should be generally disregarded. But when the action should be urgent, the optimal balance between transparency and just getting the job done shifts. I think in this case the balance was about right. Ultimately, in such extremal situations, the community should trust those who do the job. If they are not trusted, they shouldn't be asked to do the job in the first place.