From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Choice of bug tracker Date: Thu, 31 Aug 2023 23:55:47 +0300 Message-ID: <78b3ce39-28da-8d07-8435-afa0ecb55ff5@gutov.dev> References: <87il9kksqz.fsf@dfreeman.email> <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> <831qfmhyx3.fsf@gnu.org> <87pm36kqlg.fsf@posteo.net> <87il8yuk6q.fsf@yahoo.com> <87ttsfts92.fsf@localhost> <87r0njtrdl.fsf@localhost> <87il8vtqwf.fsf@localhost> <835y4ve5sv.fsf@gnu.org> <87o7ins6r2.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22626"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Cc: Eli Zaretskii , brickviking@gmail.com, emacs-devel@gnu.org To: Stefan Kangas , Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 31 22:56:54 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 1qboii-0005dB-G8 for ged-emacs-devel@m.gmane-mx.org; Thu, 31 Aug 2023 22:56:53 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qbohq-0002FO-NR; Thu, 31 Aug 2023 16:55:58 -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 1qbohm-0002FA-GI for emacs-devel@gnu.org; Thu, 31 Aug 2023 16:55:54 -0400 Original-Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qbohj-0007d5-Q4; Thu, 31 Aug 2023 16:55:54 -0400 Original-Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id BF6215C00E3; Thu, 31 Aug 2023 16:55:50 -0400 (EDT) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 31 Aug 2023 16:55:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gutov.dev; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1693515350; x=1693601750; bh=cJttkNQ4PVCRhw5E0nR4+T8+M3RkqPhwYSS BHsD6Khg=; b=dFXTABH+2J6mX5KhCQ7pHQZ0u6KZCOpPMo4eRk+LKyHCzVEVf2F 1afVG1eR/CF3xtRc+r1tySyvYMrX5JEitTN18pD4XnQHAyIf4uXE7VvQMBZtBLaY DNXi4bTKKSV3HU0Zk9A7HJqlKCcOQwaBxASc8K4LdOukrcTpcpYP8RWRYfWNSXpz H4SLXFW5A6KQOrg5sbCCbjlAZ4rcRJ27oOLs0leuGhIbAG5D7/ovZWkhP3iHp4zN Dc35xanjfifLgLb1JqhfwqZpjzfWAhfboxNiF8zew3pMxIPlLdBr7pLKES6EMef/ rebtgCQwEo0yjb4yTuZAaMKRNE8re9fTsyw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1693515350; x=1693601750; bh=cJttkNQ4PVCRhw5E0nR4+T8+M3RkqPhwYSS BHsD6Khg=; b=O9PlWYF+3y8oqvWzS1wLoUc3CpF4CcGpKbhWttTdIWus4Tw1QmN 6BFIEvn13VApAXwKGLAq0WrkvgCEP6A/45np+uecXbGzfMPYkc5POW4HJqYwGTCA E5vuncomlSno4+IvEKFqtJ139LBWnXLqBDrjCZ4kyEJno43E3TtgJElXNyo50mM4 eolyau7Y3S04nls6Podvroyy9k9VM8IfDy0yw9QSwnkp7O5XGLiK9hkaQfaXT8EQ fqmHF8TzDwZ6k5mVr1PG1TLxofzaf4I/sazyyHshLAPAdeMnaqq09HUrp2IobH5W yBx28BioWSnMKYCuBHilOM/J0+xWKWNUUaQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudegtddgudehiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthejredttdefjeenucfhrhhomhepffhm ihhtrhihucfiuhhtohhvuceoughmihhtrhihsehguhhtohhvrdguvghvqeenucggtffrrg htthgvrhhnpeeigfetveehveevffehledtueekieeikeeufeegudfgfeeghfdulefgfeev ledvveenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe gumhhithhrhiesghhuthhovhdruggvvh X-ME-Proxy: Feedback-ID: i0e71465a:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 31 Aug 2023 16:55:49 -0400 (EDT) Content-Language: en-US In-Reply-To: Received-SPF: pass client-ip=66.111.4.28; envelope-from=dmitry@gutov.dev; helo=out4-smtp.messagingengine.com X-Spam_score_int: -62 X-Spam_score: -6.3 X-Spam_bar: ------ X-Spam_report: (-6.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-3.478, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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.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:309697 Archived-At: On 31/08/2023 23:44, Stefan Kangas wrote: > Ihor Radchenko writes: > >>> It isn't trivial when people respond to several threads in the same >>> message. You can see examples of this on this list, just look at the >>> recent large threads. >> I can see how that is a problem. So, is it a +1 for "modern trackers" >> and -1 for "mailing lists"? > Perhaps, yes. I'd definitely be much happier if we had a bug tracker > that made it possible to split threads after the fact. If that's > something you can do with a "modern tracker", then it would certainly > help. > > We are more disciplined these days, but I have seen many old, > sprawling bug threads with dozens upon dozens of replies, more than > half of which are about something else entirely. Coming back to such > threads after N years, as I've often done, it does take a long time to > find some signal in there: to figure out what is fixed, what is not, > what is a separate issue, and so on. That would be nice to be able to do, but is that feasible? If the main interface for interacting with discussions for many people remains their mail client, whatever we try to split after the fact (BTW, I know of such features in "forum software" similar to Discourse, but probably not in Gitlab's issues) wouldn't be reflected in everybody's existing mail archives. This would only work if we/they used an Emacs client that worked off Gitlab's programmatic API instead, showing the most recent views. But that would take a fair amount of work to create, and wouldn't support the existing mail rules/filters/etc, at the very least. A "modern tracker" could encourage us to use more structured threads going forward, though.