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: Confused by y-or-n-p Date: Mon, 04 Jan 2021 18:10:22 +0200 Message-ID: <83mtxobs41.fsf@gnu.org> References: <834kkcr1eo.fsf@gnu.org> <56435592-d2d0-5fb6-977f-01e1931da835@gmx.at> <87k0t38g1z.fsf@mail.linkov.net> <83czyvkts6.fsf@gnu.org> <87bleetirr.fsf@mail.linkov.net> <87y2hhri3n.fsf@mail.linkov.net> <83pn2tkfg8.fsf@gnu.org> <871rf7ippu.fsf@mail.linkov.net> <83a6trg6mc.fsf@gnu.org> <87im8f951f.fsf@gnus.org> <83lfdacapo.fsf@gnu.org> <83wnwsbuwp.fsf@gnu.org> <87mtxo4tph.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26339"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, juri@linkov.net, rudalics@gmx.at, stefankangas@gmail.com, emacs-devel@gnu.org, drew.adams@oracle.com, monnier@iro.umontreal.ca To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 04 17:11:46 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 1kwSSP-0006jy-5R for ged-emacs-devel@m.gmane-mx.org; Mon, 04 Jan 2021 17:11:45 +0100 Original-Received: from localhost ([::1]:43902 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kwSSO-0001lk-8S for ged-emacs-devel@m.gmane-mx.org; Mon, 04 Jan 2021 11:11:44 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40776) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kwSRe-0001JS-VI for emacs-devel@gnu.org; Mon, 04 Jan 2021 11:10:58 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:37557) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kwSRd-0000tT-VH; Mon, 04 Jan 2021 11:10:57 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:2667 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kwSRD-00026E-6p; Mon, 04 Jan 2021 11:10:32 -0500 In-Reply-To: <87mtxo4tph.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 04 Jan 2021 16:17:46 +0100) 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:262439 Archived-At: > From: Lars Ingebrigtsen > Cc: Stefan Kangas , monnier@iro.umontreal.ca, > rms@gnu.org, juri@linkov.net, rudalics@gmx.at, emacs-devel@gnu.org, > drew.adams@oracle.com > Date: Mon, 04 Jan 2021 16:17:46 +0100 > > > provided that someone volunteers to manage it: identify and announce > > the relevant changes, keep track of the time-box of each one of them, > > initiate a discussion when the time is up, etc. It's a non-trivial > > amount of work. > > I think the most natural person to manage the process would be the > person that's proposing the change. That is, we don't really need much > formalism around this. I don't mind that, either, but what about people who submit changes, but don't intend to stick around long enough to see this process through? Someone will have to step in and do it for them.