From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: bug archiving policy Date: Sun, 6 Dec 2020 13:24:09 +0300 Message-ID: References: <20201206092641.xv5gkqcwbpc5gau7@E15-2016.optimum.net> <20201206101445.qvlefrucfbgi7ods@E15-2016.optimum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24796"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Cc: Bastien , Stefan Kangas , Emacs-Devel List To: Boruch Baum Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 06 11:29:35 2020 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 1klrIM-0006Lq-RK for ged-emacs-devel@m.gmane-mx.org; Sun, 06 Dec 2020 11:29:34 +0100 Original-Received: from localhost ([::1]:35832 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1klrIL-0003eK-I7 for ged-emacs-devel@m.gmane-mx.org; Sun, 06 Dec 2020 05:29:33 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51982) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1klrH2-000317-5E for emacs-devel@gnu.org; Sun, 06 Dec 2020 05:28:12 -0500 Original-Received: from static.rcdrun.com ([95.85.24.50]:58099) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1klrH0-0005c0-Lt; Sun, 06 Dec 2020 05:28:11 -0500 Original-Received: from localhost ([::ffff:197.157.0.57]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by static.rcdrun.com with ESMTPSA id 00000000002C0010.000000005FCCB238.00006E57; Sun, 06 Dec 2020 10:28:07 +0000 Content-Disposition: inline In-Reply-To: <20201206101445.qvlefrucfbgi7ods@E15-2016.optimum.net> Received-SPF: pass client-ip=95.85.24.50; envelope-from=bugs@gnu.support; helo=static.rcdrun.com X-Spam_score_int: 14 X-Spam_score: 1.4 X-Spam_bar: + X-Spam_report: (1.4 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action 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:260415 Archived-At: * Boruch Baum [2020-12-06 13:16]: > On 2020-12-06 03:52, Stefan Kangas wrote: > > (Cc to Bastien.) > > > > Although the org-mode maintainers do read emacs-devel and bug-gnu-emacs > > with some frequency, most subscribers are not org-mode experts. > > > > I would therefore recommend sending org-mode patches directly to the > > org-mode mailing list: emacs-orgmode@gnu.org. This makes sure it is > > seen by the competent and helpful org-mode hackers. In most cases, I > > don't think there is any need to also open a bug against Emacs. > > Your comments were points of discussion in the org-mode thread that I > referenced. See there, but in part, that list requires one to first > subscribe and become a member in order to post to the list, which is a > barrier to entry for bug reporters not committed to be developers or > insiders, and the method is inconsistent with other parts of emacs-core > and thus unexpected for users. The thread also addressed issues of > maintainabilty, bug-tracking, and other useful and constructive > comments. Do see there. I can fully relate to that problem and in last months we have seen few users having similar issue. Issue related to specific bug should be, in my opinion, be handled automatically by the mailing list software. I think it is handled so, but I am not sure. Bug submitter should always get the update to the bug regardless if other people put such in the message Cc: carbon copy field (where is the carbon?) I am not sure if Org mailing list is setup that way. But you may try with {M-x org-submit-bug-report RET} which also has its menu item under Org menu. You may also open up this issue straight in that mailing list. Question is if such bug would be reported back to you if users do not conduct Group-Reply option in ther email software. That would not be useful to rely on many people with many email software to be explicit how to answer the bug. If they miss it one time, you miss the update.