From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Recentish C-s M-y change Date: Sun, 03 Jan 2021 17:05:47 +0200 Message-ID: <83pn2mcb78.fsf@gnu.org> References: <<87r1na4tyu.fsf@gnus.org>> <<87tus6tj7s.fsf@mail.linkov.net>> <<87a6txigm1.fsf@gnus.org>> <<874kk5lzew.fsf@mail.linkov.net>> <> <<87eej8ifll.fsf@mail.linkov.net>> <> <<87h7o3k5b5.fsf@mail.linkov.net>> <> <> <83wnwwg8iu.fsf@gnu.org> <837dovg687.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33725"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ams@gnu.org, emacs-devel@gnu.org, larsi@gnus.org, drew.adams@oracle.com, juri@linkov.net To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jan 03 16:07:27 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kw4yd-0008gi-KO for ged-emacs-devel@m.gmane-mx.org; Sun, 03 Jan 2021 16:07:27 +0100 Original-Received: from localhost ([::1]:51164 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kw4yc-0002Cf-MR for ged-emacs-devel@m.gmane-mx.org; Sun, 03 Jan 2021 10:07:26 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52872) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kw4xr-0001nK-FM for emacs-devel@gnu.org; Sun, 03 Jan 2021 10:06:39 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:43392) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kw4xq-0000lO-61; Sun, 03 Jan 2021 10:06:38 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1852 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kw4xD-00018F-Ah; Sun, 03 Jan 2021 10:06:15 -0500 In-Reply-To: (message from Richard Stallman on Sun, 03 Jan 2021 01:01:45 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:262359 Archived-At: > From: Richard Stallman > Cc: ams@gnu.org, juri@linkov.net, larsi@gnus.org, > drew.adams@oracle.com, emacs-devel@gnu.org > Date: Sun, 03 Jan 2021 01:01:45 -0500 > > > > Thus I propose a rule, which I hope people will remember to apply, > > > that if a change in features has been discussed inside a thread > > > about a specific bug, always to raise the issue on emacs-devel > > > afterward. > > > As a guideline, I could agree. But as an enforced rule, I don't think > > this will fly, and I don't think we should waste our limited resources > > to try enforcing it. > > What is the sort of "enforcement" that seems so bad to you? > Maybe I have no intention of doing that anyway. A "rule" that is enforced is something that people are required to abide by, and if they don't, they should expect to be reprimanded. It also means that changes should be rejected and/or reverted if they weren't discussed up front on emacs-devel. I'm opposed to this kind of enforcement. A "guideline" means we encourage people to start discussions about changes they think might be controversial. This is OK IMO, and is already being done, actually, but maybe we should encourage more.