From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id aLwbBsOKx14AQwAA0tVLHw (envelope-from ) for ; Fri, 22 May 2020 08:18:11 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id 2JMUAsOKx15KBgAAB5/wlQ (envelope-from ) for ; Fri, 22 May 2020 08:18:11 +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 9225F9403EA for ; Fri, 22 May 2020 08:18:10 +0000 (UTC) Received: from localhost ([::1]:41978 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jc2sb-0005lZ-In for larch@yhetil.org; Fri, 22 May 2020 04:18:09 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:46164) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jc2sG-0005lF-9u for emacs-orgmode@gnu.org; Fri, 22 May 2020 04:17:48 -0400 Received: from mail-vs1-xe33.google.com ([2607:f8b0:4864:20::e33]:39616) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jc2sF-0008OD-7B for emacs-orgmode@gnu.org; Fri, 22 May 2020 04:17:47 -0400 Received: by mail-vs1-xe33.google.com with SMTP id e7so5600104vsm.6 for ; Fri, 22 May 2020 01:17:46 -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; bh=56ePmzaqTZwva182A5dWpa7x1EWu29rloSoG/K0r56U=; b=R46LJ5bs52Up99DFY6Bc6R66zSIurIGLG3nUmbeV0ZAcPRc6o5a4zX+pVej0lvssG+ g7Q0XK0aOTjjaP7oPfCyYqkG8CasKOqj7oR5KbDkNXMf77QmSuEyAjIQkYyf1+LQLGh2 U6pAKT82Y1EfaQ0MWYOV3EJthBn8aMEeUKY2znbqhj2B+AERsOH6AKZ3s160r+vqC/cj dG4l0KgMcvfHBBEcTGLUsCUCXKn9GcKV7LS1qO99h651mpIabnTCteGF2EB6SHnA1/xK rww8fV/BKLbIhr2+sY2auH6NQlJCMGkfhKoAax3Uii/GuEi5iy2GtHIAuNld9URx6XpL Qd2w== 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; bh=56ePmzaqTZwva182A5dWpa7x1EWu29rloSoG/K0r56U=; b=fhJ/Y4ukWM0b/OYdkRHbe87G4qFDFu508Z7vQkrSHXz5HGOovJI9G/FqwPstSJWd6a a7fyJ/k0KM796/ymwT7vwRmM0+4x2McmIqYrnuEtGqd0GgHSb5KQsMu3kfg14IN4wBua e8cJIzqEbdF4kZ1KRHKo/vQumLoycIOMTRSLG0qNs2UPhQruHuResDFIjVS6C54e5fHi 0BkVrZkzosjQEbaH2pcYUuyHJ7CwSNYWouzbpCWPcpdkzKky0102G5/Pp5LYwOgwwWX3 etqRl3nJx2S2R9VaoWkdMIYfZiTqQtFg9Y4/ieMl7TwKlToeIrOG9qeQ/gEZAySbRO0v 5pAA== X-Gm-Message-State: AOAM531OeeBGHqq3URz1Mqzg43ARCNX6Tq8v6A4l8HE7GkS9rjZXzymy 5RyoEyrfvhVjvWdlTSITX07eCUf+jjjf938SF0bkP1hf X-Google-Smtp-Source: ABdhPJyNG3I/nkyMIEQsCKaOXG5cnwVXs0sesoMG6F1AbviW9RkxveubtyH3apCSgM6XJdPqwhnMr9UHJfiiNb6WJsM= X-Received: by 2002:a05:6102:242b:: with SMTP id l11mr9037405vsi.14.1590135465789; Fri, 22 May 2020 01:17:45 -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> In-Reply-To: <87lfll45ck.fsf@ericabrahamsen.net> From: Roland Everaert Date: Fri, 22 May 2020 10:17:33 +0200 Message-ID: Subject: Re: issue tracker? To: emacs-orgmode Content-Type: multipart/alternative; boundary="000000000000954cd905a6384389" Received-SPF: pass client-ip=2607:f8b0:4864:20::e33; envelope-from=reveatwork@gmail.com; helo=mail-vs1-xe33.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: , 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=R46LJ5bs; 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.29 X-TUID: djmSvY4YRfjQ --000000000000954cd905a6384389 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I will surely state the obvious, but the output of this discussion is that ther4e is a need for everybody, what ever our relationship to org-mode or emacs, needs a way to filter the various conversation about org-mode on the various communication channel used by the project. This mainly imply this ML and if there is a way to pre-format messages we want to send to the ML it will make filtering easier. In fact, a good approach would be the same as for todo state. Example of message states: [QUESTION] -> [ANSWER] [BUG] -> ( [CONFIRMED] | [WONTFIX] | [SOLVED] ) [CONFIRMED] -> ( [SOLVED] | [PLANNED] ) [FEATURE] -> ( [WONTDO] | [PLANNED] | [IMPLEMENTED] ) [PLANNED] -> ( [IMPLEMENTED] | [SOLVED] ) Of Course, nothing should prevent moving a message from [BUG] to [QUESTION] for example. Hope this will help go on with a solution and an actual implementation, I suppose mainly documentation on the org website and configuration for all of us. Regards, Roland. On Thu, May 21, 2020 at 6:32 PM Eric Abrahamsen wrote: > K=C3=A9vin Le Gouguec writes: > > > Nicolas Goaziou writes: > > > >> - As pointed out, Org has a bug tracker : Emacs' Debbugs. See > >> . Org users do not send bugs > >> through it much. > > > > (In the event that they do, should whoever follows bug-gnu-emacs refer > > these users to emacs-orgmode?) > > Maybe a first step would be changing `org-submit-bug-report' to submit > the bug to debbugs, not to this mailing list? > > I know I'd be happy to help with bug triage, but I don't go wading > through this mailing list like I used to. I do use debbugs for other > stuff, though, and it would be easy to add an extra filter that I check > regularly. > > 2=C2=A2... > > --000000000000954cd905a6384389 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I will surely state the obvious, but the output of th= is discussion is that ther4e is a need for everybody, what ever our relatio= nship to org-mode or emacs, needs a way to filter the various conversation = about org-mode on the various communication channel used by the project.

This mainly imply this ML and if there is a way to p= re-format messages we want to send to the ML it will make filtering easier.=

In fact, a good approach would be the same as for= todo state.

Example of message states:
= [QUESTION] -> [ANSWER]
[BUG] -> ( [CONFIRMED] | [WONTFIX] |= [SOLVED] )
[CONFIRMED] -> ( [SOLVED] | [PLANNED] )
<= div>[FEATURE] -> ( [WONTDO] | [PLANNED] | [IMPLEMENTED] )
[PLA= NNED] -> ( [IMPLEMENTED] | [SOLVED] )

Of Course= , nothing should prevent moving a message from [BUG] to [QUESTION] for exam= ple.

Hope this will help go on with a solution and= an actual implementation, I suppose mainly documentation on the org websit= e and configuration for all of us.

Regards,

Roland.


On Thu, May 21, 2020= at 6:32 PM Eric Abrahamsen <= eric@ericabrahamsen.net> wrote:
K=C3=A9vin Le Gouguec <kevin.legouguec@gmail.com> writ= es:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> - As pointed out, Org has a bug tracker : Emacs' Debbugs. See<= br> >>=C2=A0 =C2=A0<https://debbugs.gnu.org/Emacs.html>= ;. Org users do not send bugs
>>=C2=A0 =C2=A0through it much.
>
> (In the event that they do, should whoever follows bug-gnu-emacs refer=
> these users to emacs-orgmode?)

Maybe a first step would be changing `org-submit-bug-report' to submit<= br> the bug to debbugs, not to this mailing list?

I know I'd be happy to help with bug triage, but I don't go wading<= br> through this mailing list like I used to. I do use debbugs for other
stuff, though, and it would be easy to add an extra filter that I check
regularly.

2=C2=A2...

--000000000000954cd905a6384389--