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 a7WsK++13F7dQQAA0tVLHw (envelope-from ) for ; Sun, 07 Jun 2020 09:39:59 +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 QMYJJ++13F47WAAAbx9fmQ (envelope-from ) for ; Sun, 07 Jun 2020 09:39:59 +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 2622694051C for ; Sun, 7 Jun 2020 09:39:58 +0000 (UTC) Received: from localhost ([::1]:36384 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jhrmV-0001mf-FH for larch@yhetil.org; Sun, 07 Jun 2020 05:39:55 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:37914) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jhrlH-0001Y6-4Y for emacs-orgmode@gnu.org; Sun, 07 Jun 2020 05:38:39 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:49783) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jhrlG-0006Nu-B6; Sun, 07 Jun 2020 05:38:38 -0400 Received: from [185.165.34.104] (port=23957 helo=guerry) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.82) (envelope-from ) id 1jhrlG-00088w-1D; Sun, 07 Jun 2020 05:38:38 -0400 Received: by guerry (Postfix, from userid 1000) id 711BA1A60829; Sun, 7 Jun 2020 11:38:31 +0200 (CEST) From: Bastien To: Mario Frasca Subject: Re: issue tracker? Organization: GNU 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> Date: Sun, 07 Jun 2020 11:38:31 +0200 In-Reply-To: (Mario Frasca's message of "Sat, 6 Jun 2020 11:15:28 -0500") Message-ID: <87v9k3nrl4.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.91 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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=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: 8hXQ3xUBR9Au Hi Mario, Mario Frasca writes: > very interesting approach.=C2=A0 Thanks for looking more closely into it. > sounds like you don't want to manage the status changes a bit > tighter.=C2=A0 I know, I can check the code, but it's more practical if we > mention it here explicitly.=C2=A0 anybody can send status change emails?= =C2=A0 Yes, anybody can confirm a bug and anybody can mark it as fixed. > I mean, this is an open list, anybody who just knows how to put a > header to an email can confirm a bug?=C2=A0 Yes. The pattern I've seen in the last 15 ten years is that someone sends a bug report and 50% of the time it is not really possible to reproduce the bug. And people who reproduce bugs are not always code contributors, they can be "power users", so I think it's safe to allow anyone to confirm a bug -- that's something that really helps. > on the other hand, I never tried to add extra headers using > thunderbird. Yes, you can: https://www.lifewire.com/arbitrary-custom-heading-email-thunderbird-1173089 > apart from the technical aspect, I would suggest: anybody can > 'vote-for' a bug, and you keep a counter on voted-for. It would require people to register on updates.orgmode.org. I'm not sure the expected benefit is really worth it for now. > but only a maintainer can 'confirm' (that fixing that bug is > desirable).=C2=A0 I think it is important that anyone can confirm a bug. > then > we new contributors can choose which confirmed bug is easy enough for > us to make an attempt.=C2=A0 or which fits our interests and skills.=C2= =A0 or > which has accumulated most votes, hasn't been rejected, so we can > remind the maintainer. > > =E2=80=A6 if the "main focus" is recruiting, I would also suggest a categ= ory > "good first issue". I have seen "good first issues" in many repositories and I don't think it is sufficient as a way to attract new contributors: those tags are useful when you also actively organize the contribution and the onboarding of new contributors. Also, "good first issues" are often those we can fix very easily and there is no good reason not to fix them. That said, I would love to organize a hackathon for Org-mode where people would gather online for one day, exchange ideas, break and fix things, propose new features, etc. That is, IMHO, the way to recruit new contributors, on top of simply formally asking "who would like to be in charge of X, Y and Z?" > I understand, not a bug "tracking" tool, but it sounds like it's able > to shed some light in the dark. Yes, I hope so! --=20 Bastien