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: Sat, 12 Dec 2020 05:40:18 +0000 Message-ID: References: <20201206092641.xv5gkqcwbpc5gau7@E15-2016.optimum.net> <87eejx532n.fsf@bzg.fr> <87h7osyjby.fsf@bzg.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17835"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Boruch Baum , Stefan Kangas , Emacs-Devel List To: emacs-devel@gnu.org, Bastien Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 12 06:41:41 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 1knxf2-0004Yd-Kr for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Dec 2020 06:41:40 +0100 Original-Received: from localhost ([::1]:59712 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1knxf1-0004uz-NR for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Dec 2020 00:41:39 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37476) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1knxdz-0004P9-8P for emacs-devel@gnu.org; Sat, 12 Dec 2020 00:40:35 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:40019) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1knxdw-00031G-Pn; Sat, 12 Dec 2020 00:40:34 -0500 Original-Received: from [192.168.43.201] ([::ffff:41.202.241.42]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_CHACHA20_POLY1305) by stw1.rcdrun.com with ESMTPSA id 00000000000442C7.000000005FD457CC.000011DF; Fri, 11 Dec 2020 22:40:28 -0700 In-Reply-To: <87h7osyjby.fsf@bzg.fr> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham 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:260708 Archived-At: Do you doubt it also when user reports straight from Org mode? Would it be = wrong for standard emacs bug function to detect org mode and ask user if it= is org related, and if it is, to route user to org report function? You do= n't need to ask if user does not begin bug report from Org mode Routing is to me logical and reasonable, I get surprised that it is not an= d was not obvious at inception of Org bug report function and that interfac= e within Emacs splitted into two directions of reporting bugs with later re= grets and efforts to make it again right=2E If not solved sooner, instead o= f 4 or 5 per month it may results amount to 40 or 50 in some time as Org an= d Emacs become popular=2E There are few other functions that want separate bug reporting such as TeX= etc=2E They add to confusions=2E It is more useful to have centralized bug database as that way there are b= etter responses to users=2E More skilled people not subscribed to org maili= ng list for answer and solve bugs=2E Imagine if that goes further to split = each package bug report to separate mailing lists, it does not branch reaso= nably=2E Then we get into silly discussions with users telling them from official m= aking lists how Org is not Emacs, etc=2E wronging and thus rejecting users= =2E Functions shall be united and they may remain at two places=2E I would eve= n place it as main menu after Help as number of reported bugs does not corr= espond appropriately to number of Emacs and Org users=2E The general Emacs bug function should be improved with references or butto= n to jump to Org mode report template if it is org mode related=2E One clic= k=2E Org more function should report to central database debbugs, use procmail = or equivalent to automatically route those bugs to org mailing list=2E If y= ou don't know how, ask me or somebody who knows=2E Things can be solved centrally without kicking users back and forth=2E Am December 11, 2020 5:58:57 AM UTC schrieb Bastien : >Jean Louis writes: > >> Something like: >> >> If user is in Org mode, then to be asked: >> >> - is this Org mode bug? >> >> then if no, to proceed to standard bug report=2E > >I see how this could be useful, but maybe Org is the only package in >this situation (i=2Ee=2E suffering from separate ways of reporting bugs), >so I doubt implementing a specific behavior for Org is correct=2E > >The stream of Org-related bugs reported with M-x report-emacs-bug is=20 >really not that big=2E