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: My resignation from Emacs development Date: Tue, 03 Dec 2024 15:33:28 +0200 Message-ID: <8634j43n87.fsf@gnu.org> References: <169c6564-4722-4338-a049-5f8f3ce69394@alphapapa.net> <86zflh9myy.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14501"; mail-complaints-to="usenet@ciao.gmane.io" Cc: adam@alphapapa.net, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 03 14:34:09 2024 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 1tIT2W-0003cE-JK for ged-emacs-devel@m.gmane-mx.org; Tue, 03 Dec 2024 14:34:08 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tIT2F-0006jq-HO; Tue, 03 Dec 2024 08:33:51 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tIT2C-0006j8-9R for emacs-devel@gnu.org; Tue, 03 Dec 2024 08:33:48 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tIT2B-0000s4-TS; Tue, 03 Dec 2024 08:33:47 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=dwvnh/MBF19E+5aJryxtgGdr+TfVmpJLGV+6tO8KIi0=; b=SrxTXllxW/uM 6dKGiDHb3hPDNiq76qGyNcr2iDGA92qVsx8keJDiym7rdhWTNLOTrBxq0iXoOc13PKJf2EnJQ9JlR EtmGlAYbnj8ZTA3I/IHFlpjWdEmYR7TX5ioFHUDq6D7UQbesWLajKa8/0tRexfLLFA8HucNvMC5t/ Fbteizan+S2U6S/N+YDfeY5FwlXZbCh+4nGnibju71ovRTqF/XV8JLY7oJWA3spTsRrB3/v30+KXX o7hxgJQOJQz5YyYhCkKWRIMWA5uuYjk4RFjd+AWlthIYR5ZLRyQNRfaIcZCS0MouQcY0YNW990JRW Tqe4336xI3pbhDWt40EBpA==; In-Reply-To: (message from Richard Stallman on Tue, 03 Dec 2024 02:26:13 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:325988 Archived-At: > From: Richard Stallman > Cc: adam@alphapapa.net, emacs-devel@gnu.org > Date: Tue, 03 Dec 2024 02:26:13 -0500 > > I suggested > > > > I have complained before that the practice of discussing a feature > > > change on the bug list caused feature change ideas not to be > > > recognized as such. People should help notify all of us > > > that we are discussing a feature change. > > You replied, pointing out some details of how things tend to work > currently: > > > When such discussions happen on the bug list, we generally try to add > > to the discussion people who might be relevant or whose opinions we > > want to hear. > > Adding specific pertinent people is a helpful think to do, I agree. > > In other cases, someone insists to move the discussion > > to emacs-devel. > > I'm simply suggesting that we make a point of thinking of this > in certain sitations. I definitely agree, as a general rule. > > Of course, mistakes can and do happen. But the understanding that > > some issues need broader discussions does exist, and there's no > > intentional avoidance of that for some covert reasons. > > None of us is perfect, and I don't think anyone had a ban intention > in handling that bug report thread. > > By thinking consciously of the importance of bringing a feature > discussion to emacs-devel, we'll learn to remember hat more often. > > > Please also keep in mind that a person interested in some subject > > could be off-line for some reason, not reading any of the Emacs lists, > > when the discussion happens. So even making sure all such discussions > > happen on emacs-devel is not a guarantee that everyone who should be > > involved will be. > > I know. It won't be guaranteed to happen. But with all of us aware > that moving such discussions to emacs-devel, we will start noticing > oppprtunities to do that. > > (I do agree that emacs-devel is a better place for > > discussing important changes, I'm just saying it is not a panacea.) > > I agree. There are bo panaceas in this field. Full agreement.