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: Thu, 10 Dec 2020 14:57:16 +0300 Message-ID: References: <20201206092641.xv5gkqcwbpc5gau7@E15-2016.optimum.net> <87eejx532n.fsf@bzg.fr> 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="14472"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Cc: Emacs-Devel List , Stefan Kangas , Boruch Baum To: Bastien Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 10 13:19:06 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 1knKuX-0003fn-SP for ged-emacs-devel@m.gmane-mx.org; Thu, 10 Dec 2020 13:19:05 +0100 Original-Received: from localhost ([::1]:56194 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1knKuW-00019w-Eu for ged-emacs-devel@m.gmane-mx.org; Thu, 10 Dec 2020 07:19:04 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53464) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1knKa5-0002zJ-Cy for emacs-devel@gnu.org; Thu, 10 Dec 2020 06:57:57 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:34951) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1knKZy-0001iI-Re; Thu, 10 Dec 2020 06:57:57 -0500 Original-Received: from localhost ([::ffff:41.202.241.31]) (AUTH: PLAIN securesender, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000001E52F.000000005FD20D3B.000025A9; Thu, 10 Dec 2020 04:57:47 -0700 Content-Disposition: inline In-Reply-To: <87eejx532n.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_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01 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:260648 Archived-At: * Bastien [2020-12-10 14:11]: > Jean Louis writes: > > > There is main Emacs bug tracking system and such shall accept > > logically bugs that also relate to Org mode. To avoid > > misunderstandings for people reading advises, it is maybe more useful > > to say "while Org mode is part of Emacs there is also separate Org bug > > tracking mailing list" and then to advise users there in gentle > > manner. This is because not everybody can find that information > > easily and maintainers will say that maybe Org is not part of Emacs > > while it is part of Emacs thus confusing mostly new users. > > I would like to introduce M-x report-org-bug as an alias to > M-x org-submit-bug-report > > I think it would help enforce the policy of submitting Org bugs to > emacs-orgmode@gnu.org first. Good idea. It will work only for those who know how to use M-x. Many people do not know, and many will use menu and skip Org and use Help to report bug. So better idea would be that you harmonize both org and Emacs and just have one function to report bug as by its meaning Org is part of Emacs. You can keep 2 menues as usual, but one function which would determine if the bug is related to Org mode, or not, and forward bugs to Org mode to different mailing list with a different template. 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. If user is not in Org mode, then: - Is this general Emacs bug? Yes If user answers No: - Is this Org mode bug? The message can be prepared depending of the bug and email address can be changed appropriately. Org menu reporting option would work as usual. Help report emacs bug menu option could work by asking user those questions. Think about harmonizing user interface and not splitting users over development of one software between its modes.