From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id kPvPA/odyV5hTgAA0tVLHw (envelope-from ) for ; Sat, 23 May 2020 12:58:34 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id CJkeO/kdyV5ICQAAbx9fmQ (envelope-from ) for ; Sat, 23 May 2020 12:58:33 +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 833729401AD for ; Sat, 23 May 2020 12:58:33 +0000 (UTC) Received: from localhost ([::1]:37012 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jcTjT-0004Ue-Ln for larch@yhetil.org; Sat, 23 May 2020 08:58:31 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:54708) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jcTj9-0004UQ-3q for emacs-orgmode@gnu.org; Sat, 23 May 2020 08:58:11 -0400 Received: from mail-vs1-xe32.google.com ([2607:f8b0:4864:20::e32]:40976) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jcTj8-0001eH-18 for emacs-orgmode@gnu.org; Sat, 23 May 2020 08:58:10 -0400 Received: by mail-vs1-xe32.google.com with SMTP id y13so7567654vsk.8 for ; Sat, 23 May 2020 05:58:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=o6rj6/UKpKLQptyckBwP/dzwjs2tvkkC0oMyjQG5VDE=; b=H1HKbkZgdA+UfPxy+AsRsmC2MwrHHfs3XVAR4K6aDh/9AtuTaLvhFjaJGe+z0U8Yqw mGOSFKjqZhZ8k1ihWKSkxUP2D7s+0DNTEdVr+Whxh2kUUuJbvrsu1hwfcFtaQFGf3ZIf JKuMCqAji3bXIlUqtTh72S+mQGuKzVb9lmbFtUF4425xVj+OY8dvdxZk6WkxKBDyn+XM YK5I6pzMSqbJbQhcmgCsby4Wkg5lmRHZeyz2R1ny+1zJCpfyvEwxji9JZ1CzksRJiTsc rM53nH8l1VyYvQ8W1QekpN+aa3kSq1SbMAYYI0zHRriyfV1pvDZplFr9fz0vt0zj8teH ipEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=o6rj6/UKpKLQptyckBwP/dzwjs2tvkkC0oMyjQG5VDE=; b=I5/uLJb73H38wl+2HI6ZzYNFpUkoPbzVrcF9thbwHe+0M4Io7FV0zbyfbQI7gzdBOG 8Jo9ui/wukyk5/dGa0cc0tj634fHdzOM2L6Af8Xno2zesRBaMvH7Mnjy3Q3IGHk61a0z T/pVY23Ac5QxUSknBtzWQHTYMTrWAH/m1PzuPx+I5W6FkYFYz0Cs4Pah5WY3Adi/Q2cA dyRDDedwTrvxBhU85zvWNf0eQtc+GkMad9xmp76067GRPYoN096eFbTWVlIX3WACl/D0 tYEtRstGqA/yvA2+b47v+kQBUFCXUhZeNVlRmVLIT6QLSWQJRXu5reZpfhnejrzK6LSR pu1Q== X-Gm-Message-State: AOAM530hzLIPgu+8wD8khNOorNJPMeQPVU1TUXjB5ilwrVNj1K/wvapD 06XZXn1M2aVgEzVZpqPq4kPY2qvQ8BRz6b7FdJ+4QA== X-Google-Smtp-Source: ABdhPJwl7C5Og2+BgsnvDjYXa+s3MC4XVYke8/Vr+V7HnB4e0zY1xT98+M1Rq9yrJUp0yMwwfn1/LIdpLzBMncIz4G0= X-Received: by 2002:a67:df02:: with SMTP id s2mr13222219vsk.210.1590238688533; Sat, 23 May 2020 05:58:08 -0700 (PDT) MIME-Version: 1.0 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> <1bc09da4-09e9-d895-6485-e60eae22c82a@memebeam.org> In-Reply-To: <1bc09da4-09e9-d895-6485-e60eae22c82a@memebeam.org> From: Roland Everaert Date: Sat, 23 May 2020 14:57:26 +0200 Message-ID: Subject: Re: issue tracker? To: Anthony Carrico Content-Type: multipart/alternative; boundary="0000000000002360a205a6504cbe" Received-SPF: pass client-ip=2607:f8b0:4864:20::e32; envelope-from=reveatwork@gmail.com; helo=mail-vs1-xe32.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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: , Cc: emacs-orgmode Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=H1HKbkZg; dmarc=pass (policy=none) header.from=gmail.com; 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.71 X-TUID: OkFCfCEYA8sN --0000000000002360a205a6504cbe Content-Type: text/plain; charset="UTF-8" I have to admit that I am kind of a state tracking freak, so, your proposal is welcomed to keep that tendency at bay. However, I would add a "category" for bugs/issues and feature requests, in the subject, else, the bot, the readers and the maintainer will have still to dig deep into threads to know which one was a feature and which one was actually a bug report. There must be also some kind of "protocol" to transition between the various discussions, like - from bug to a normal question - normal question to a feature request We must avoid that to much bugs ends up as simple discussion, without a proper sanitation of the thread subject. * I am not sure this is clear even for me :/* On Fri, May 22, 2020 at 4:54 PM Anthony Carrico wrote: > 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 > > --0000000000002360a205a6504cbe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I have to admit that I am kind of a state tracking fr= eak, so, your proposal is welcomed to keep that tendency at bay.
=
However, I would add a "category" for bugs/issues = and feature requests, in the subject, else, the bot, the readers and the ma= intainer will have still to dig deep into threads to know which one was a f= eature and which one was actually a bug report.

Th= ere must be also some kind of "protocol" to transition between th= e various discussions, like
- from bug to a normal question
=
- normal question to a feature request

We mus= t avoid that to much bugs ends up as simple discussion, without a proper sa= nitation of the thread subject. * I am not sure this is clear even for me := /*


On Fri, May 22, 2020 at 4:54 PM Anthony Carrico <= acarrico@memebeam.org> wrot= e:
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&= #39;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 h= ard
for someone to write an elisp script to scan a mailbox/maildir to gather a list of subject lines--is this true?

--
Anthony Carrico

--0000000000002360a205a6504cbe--