From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id SLNsAc3nx15DTQAA0tVLHw (envelope-from ) for ; Fri, 22 May 2020 14:55:09 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id c6rhOMznx14CEQAA1q6Kng (envelope-from ) for ; Fri, 22 May 2020 14:55:08 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 6A6C09403ED for ; Fri, 22 May 2020 14:55:08 +0000 (UTC) Received: from localhost ([::1]:40182 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jc94l-0000rg-2n for larch@yhetil.org; Fri, 22 May 2020 10:55:07 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59800) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jc94Q-0000rN-Pc for emacs-orgmode@gnu.org; Fri, 22 May 2020 10:54:46 -0400 Received: from memebeam.org ([80.68.89.71]:52661 helo=jvb.vm.bytemark.co.uk) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jc94P-0005z7-M1 for emacs-orgmode@gnu.org; Fri, 22 May 2020 10:54:46 -0400 Received: from [192.168.1.27] (dhcp-68-142-47-225.greenmountainaccess.net [::ffff:68.142.47.225]) (AUTH: LOGIN acarrico@memebeam.org, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by jvb.vm.bytemark.co.uk with ESMTPSA id 0000000000180077.5EC7E788.000036DD; Fri, 22 May 2020 10:54:00 -0400 Subject: Re: issue tracker? To: emacs-orgmode@gnu.org References: <87ftbw3mvw.fsf@alphaville.usersys.redhat.com> <6ffc8465-fdeb-4981-8303-43f09e26e0c1@www.fastmail.com> <20200519073352.GC7874@tuxteam.de> <20200519165720.GQ30250@volibear> <87d06z9czz.fsf@ucl.ac.uk> <20200520114026.034c24c2@linux-h0yu.plc.hootoo.com> <87r1vdg12u.fsf@nicolasgoaziou.fr> <87zha1s5vh.fsf@gmail.com> <87lfll45ck.fsf@ericabrahamsen.net> From: Anthony Carrico Message-ID: <1bc09da4-09e9-d895-6485-e60eae22c82a@memebeam.org> Date: Fri, 22 May 2020 10:53:59 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=80.68.89.71; envelope-from=acarrico@memebeam.org; helo=jvb.vm.bytemark.co.uk X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/22 10:54:01 X-ACL-Warn: Detected OS = Linux 3.1-3.10 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 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -0.01 X-TUID: YowIJFT200S/ On 5/22/20 4:17 AM, Roland Everaert wrote: > Example of message states: > [QUESTION] -> [ANSWER] > [BUG] -> ( [CONFIRMED] | [WONTFIX] | [SOLVED] ) > [CONFIRMED] -> ( [SOLVED] | [PLANNED] ) > [FEATURE] -> ( [WONTDO] | [PLANNED] | [IMPLEMENTED] ) > [PLANNED] -> ( [IMPLEMENTED] | [SOLVED] ) I love your enthusiasm. A mailing list has no means to type check messages, so I think it does call for a more simplified mechanism, especially as a first pass (note that the machine is necessarily nondeterministic, since different people can cause it to transition at the same time by sending a message). I'd argue that questions and answers are just normal threads, that don't need a state, and issues just need an open state, and a closed state. /The details of the of those states are in the threads for anyone who cares to look/. So, OPEN/CLOSED and let the threads speak for themselves. In this way, there are just two kinds of discussions: tracked, and untracked. Newbies can quickly pick up the OPEN/CLOSED grammar. People can meander threads between the richer states in their discussion, hopefully with good subject lines, and 'bots just need to look for one pair of keywords, ignoring threads without those keywords. I don't actually use emacs for email, but I'm guessing it wouldn't be too hard for someone to write an elisp script to scan a mailbox/maildir to gather a list of subject lines--is this true? -- Anthony Carrico