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: Choice of bug tracker Date: Thu, 31 Aug 2023 10:02:19 +0300 Message-ID: <83v8cveltw.fsf@gnu.org> References: <87il9kksqz.fsf@dfreeman.email> <87a5uw9ivs.fsf@posteo.net> <87ttt42gna.fsf@dfreeman.email> <87wmy080kn.fsf@posteo.net> <83v8djcydl.fsf@gnu.org> <87350ndquw.fsf@dfreeman.email> <83350ncbns.fsf@gnu.org> <87cyzrjbd8.fsf@dfreeman.email> <83zg2vav46.fsf@gnu.org> <87o7j99304.fsf@dfreeman.email> <87wmxj27fn.fsf@dfreeman.email> <831qfrptiq.fsf@gnu.org> <57429221-d9be-5791-e975-b3539905e2f6@gutov.dev> <83a5udlj47.fsf@gnu.org> <87a5udk1co.fsf@posteo.net> <835y51kslv.fsf@gnu.org> <7a82c524-1aa1-e755-e377-673ebb107a44@gutov.dev> <83r0nok8s4.fsf@gnu.org> <83ledwk4xi.fsf@gnu.org> <76ecf629-a41a-f6e4-f661-2ef926326d6c@gutov.dev> <83zg2cias7.fsf@gnu.org> <83pm37ie54.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4681"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dmitry@gutov.dev, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 31 09:03:08 2023 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 1qbbhr-0000z3-KM for ged-emacs-devel@m.gmane-mx.org; Thu, 31 Aug 2023 09:03:07 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qbbhW-0002E9-2G; Thu, 31 Aug 2023 03:02:46 -0400 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 1qbbhU-0002Dx-TE for emacs-devel@gnu.org; Thu, 31 Aug 2023 03:02:44 -0400 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 1qbbhU-0007oB-Gg; Thu, 31 Aug 2023 03:02:44 -0400 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=LJn6rtkhk93esvZXYU62ltnFeFCLs7WKToV1n8UK9iE=; b=kZMx027fitXq n1RYLNHg6/WsbO4qoDVMIkkiqKK8uAqEjxav8Vl0cDtVr0pgWHnefP81Pt+ED6jYATldU/0ouT2O3 JvOUXBU3KZLDxyjHRZBrCq4o3EGCbbXt3gkLWb+WAbNdOoxWs3EAYeLKZLzkx/2oSyp7fe1ud/bWA 9xZZjU4b7klIBExhNpnu6x2xtvFNkpUHT8PZyPLfvTjyN2fUY6ENwaS0c35Vzwer1GA+QEo8nexIo H1vEEH2DdPElZ54NUPUZJKSILSbISwf00o6nXXmgvOHggkJj4NA62Rf4H7R4yh5CYp0fDgAcxhZ8i LNxMoLN1ar7mhy38/npxkw==; In-Reply-To: (message from Richard Stallman on Wed, 30 Aug 2023 22:07:05 -0400) 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:309600 Archived-At: > From: Richard Stallman > Cc: eliz@gnu.org, emacs-devel@gnu.org > Date: Wed, 30 Aug 2023 22:07:05 -0400 > > However, adopting a bug tracker is a decision we hope not to have to > change again for years. That calls for using a server run by people > we can trust; which means, people who share our values. It is hard for > a company to merit that much trust. To clarify: what we currently discuss is NOT a move to a different bug tracker; that is a very serious decision, and we are not even close to be able to make it. What is being discussed here is how to try using another tracker, for now using it in parallel with debbugs, until we have enough experience and data points to make that decision about switching away from debbugs. Also, which alternative tracker(s) to try and how to evaluate their merits and demerits. Until now such discussions were purely theoretical: we didn't try to actually use any of the alternatives for real work. My hope is that we could now conduct a more practical experiment and gain some real-life experience and conclusions. > I have a possible workaround for all of that. Could we use one single > account GNU-EMAIL to file all email submissions, and record who really > sent each submission (obtained from the From field) in another data > field in the submission? This needs to be set up, since the users who report problems must have an easy way of receiving the discussions about their issues via email and sending responses to questions. Any significant inconvenience in these aspects will simply kill the email-based workflow of working on patches and discussing issues and bugs.