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 CBGhIqLj214QbQAA0tVLHw (envelope-from ) for ; Sat, 06 Jun 2020 18:42:42 +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 EOKPHqLj216cRQAAB5/wlQ (envelope-from ) for ; Sat, 06 Jun 2020 18:42:42 +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 E90FC94001C for ; Sat, 6 Jun 2020 18:42:41 +0000 (UTC) Received: from localhost ([::1]:51340 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jhdmB-0002C2-04 for larch@yhetil.org; Sat, 06 Jun 2020 14:42:39 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:33742) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jhdlq-0002Br-KS for emacs-orgmode@gnu.org; Sat, 06 Jun 2020 14:42:18 -0400 Received: from devianza.investici.org ([198.167.222.108]:26217) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jhdlo-0005dd-Uo; Sat, 06 Jun 2020 14:42:18 -0400 Received: from mx2.investici.org (unknown [127.0.0.1]) by devianza.investici.org (Postfix) with ESMTP id 1E2B6E05B6; Sat, 6 Jun 2020 16:15:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anche.no; s=stigmate; t=1591460148; bh=9qyhdsFBRsT53B3EvnmXCtm10cN03CnPnkeMU6QEm7M=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Ba6ss0ZFTLGShJmVZ94U0vIeIau7Lkc7Q8rhekxVgaRV27yiBby2N0a5c1RxdUN4b MN1hJ+fu1wRXkR9DRJOZJRxgMYPFB8A6QjGMbZeFqs1U3K2COYbW5t1KG3aoKjlMh8 kxJizrbU6hAW6qQ/WvWiTpTLF/86BRIuMUMmOyB8= Received: from [198.167.222.108] (mx2.investici.org [198.167.222.108]) (Authenticated sender: mariotomo@inventati.org) by localhost (Postfix) with ESMTPSA id CA355E05B2; Sat, 6 Jun 2020 16:15:46 +0000 (UTC) Subject: Re: issue tracker? To: Bastien References: <87ftbw3mvw.fsf@alphaville.usersys.redhat.com> <6ffc8465-fdeb-4981-8303-43f09e26e0c1@www.fastmail.com> <20200519073352.GC7874@tuxteam.de> <08ee796b-d541-69f3-518e-f577d9b29f0b@anche.no> <87imgau9ny.fsf@gnu.org> <71f5fa9a-8f55-6869-151a-209f53f86579@anche.no> <874kruzssr.fsf@gnu.org> <878sh5el37.fsf@gnu.org> <22b69acf-1b79-6257-9a97-6515f3841be4@anche.no> <871rms4oe8.fsf@gnu.org> From: Mario Frasca Message-ID: Date: Sat, 6 Jun 2020 11:15:28 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1 MIME-Version: 1.0 In-Reply-To: <871rms4oe8.fsf@gnu.org> Content-Type: multipart/alternative; boundary="------------CD60EA60283EC31394D5C66F" Content-Language: en-US Received-SPF: pass client-ip=198.167.222.108; envelope-from=mario@anche.no; helo=devianza.investici.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/06 14:42:10 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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@gnu.org 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=anche.no header.s=stigmate header.b=Ba6ss0ZF; 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.21 X-TUID: cSiS0KMoXg12 This is a multi-part message in MIME format. --------------CD60EA60283EC31394D5C66F Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi Bastien, > The tool is experimental: if it proves useful, let's try to keep it, > otherwise let's drop it: our main focus should be in recruiting new > developers to help with the codebase. very interesting approach. sounds like you don't want to manage the status changes a bit tighter.  I know, I can check the code, but it's more practical if we mention it here explicitly.  anybody can send status change emails?  I mean, this is an open list, anybody who just knows how to put a header to an email can confirm a bug?  on the other hand, I never tried to add extra headers using thunderbird. apart from the technical aspect, I would suggest: anybody can 'vote-for' a bug, and you keep a counter on voted-for.   but only a maintainer can 'confirm' (that fixing that bug is desirable). then we new contributors can choose which confirmed bug is easy enough for us to make an attempt.  or which fits our interests and skills.  or which has accumulated most votes, hasn't been rejected, so we can remind the maintainer. … if the "main focus" is recruiting, I would also suggest a category "good first issue". On 06/06/2020 02:57, Bastien wrote: > Hi Mario, > > Beware that this is not meant to be an issue tracker. I understand, not a bug "tracking" tool, but it sounds like it's able to shed some light in the dark. thank you and cheers, Mario --------------CD60EA60283EC31394D5C66F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hi Bastien,

The tool is experimental: if it proves useful, let's try to keep it,
otherwise let's drop it: our main focus should be in recruiting new
developers to help with the codebase.

very interesting approach. 

sounds like you don't want to manage the status changes a bit tighter.  I know, I can check the code, but it's more practical if we mention it here explicitly.  anybody can send status change emails?  I mean, this is an open list, anybody who just knows how to put a header to an email can confirm a bug?  on the other hand, I never tried to add extra headers using thunderbird.

apart from the technical aspect, I would suggest: anybody can 'vote-for' a bug, and you keep a counter on voted-for.   but only a maintainer can 'confirm' (that fixing that bug is desirable).  then we new contributors can choose which confirmed bug is easy enough for us to make an attempt.  or which fits our interests and skills.  or which has accumulated most votes, hasn't been rejected, so we can remind the maintainer.

… if the "main focus" is recruiting, I would also suggest a category "good first issue".

On 06/06/2020 02:57, Bastien wrote:
Hi Mario,

Beware that this is not meant to be an issue tracker.

I understand, not a bug "tracking" tool, but it sounds like it's able to shed some light in the dark.

thank you and cheers,

Mario

--------------CD60EA60283EC31394D5C66F--