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 yCBUMS8Y1V7YYQAA0tVLHw (envelope-from ) for ; Mon, 01 Jun 2020 15:01:03 +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 eNZCLS8Y1V4OdwAAB5/wlQ (envelope-from ) for ; Mon, 01 Jun 2020 15:01:03 +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 047549404CF for ; Mon, 1 Jun 2020 15:01:03 +0000 (UTC) Received: from localhost ([::1]:60254 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jflvw-00081c-Nw for larch@yhetil.org; Mon, 01 Jun 2020 11:01:00 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:42340) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jflv0-00081O-Ui for emacs-orgmode@gnu.org; Mon, 01 Jun 2020 11:00:02 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:50432) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jflv0-0001tS-Eh; Mon, 01 Jun 2020 11:00:02 -0400 Received: from [2a01:e35:2fe1:f780:a886:3d11:7807:868b] (port=38606 helo=guerry) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.82) (envelope-from ) id 1jfluv-0003HD-K7; Mon, 01 Jun 2020 10:59:59 -0400 Received: by guerry (Postfix, from userid 1000) id 935981A603C1; Mon, 1 Jun 2020 16:59:55 +0200 (CEST) From: Bastien To: Anthony Carrico Subject: Re: issue tracker? Organization: GNU References: Date: Mon, 01 Jun 2020 16:59:55 +0200 Message-ID: <87y2p6ltlg.fsf@bzg.fr> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.91 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 7ptkgFo91zVY Hi Anthony, Anthony Carrico writes: > Does org-mode have an issue tracker, to keep track of which issues > are active, or is it just this mailing list? thanks for asking. I've skimmed through https://orgmode.org/worg/org-faq.html and the question "Does org-mode have an issue tracker?" is not there, while it's probably the most frequently asked question :) As Nicolas pointed out, the main issue is the lack of maintainers, not the absence of a bug tracker -- otherwise Org would have died years ago! One thing we can do is to recruit developers: I will discuss it with Kyle and Nicolas and see if it sounds useful to them, and for what area of the code. (For example, I would love to have someone responsible for Org Babel, someone for Worg, someone for important export backends, etc.) While I think a bug tracker is no magical solution (and can even add more to the current problem of our lack of resources), I agree there is still something we can do better: not losing reports of confirmed bugs. I have setup this page on orgmode.org which now tracks confirmed bugs: https://updates.orgmode.org Org developers can subscribe to this RSS feed: https://updates.orgmode.org/feed/bugs And bugs are also available as json data: https://updates.orgmode.org/data/bugs Anyone on the list can "confirm" a bug by adding this header: X-Woof-Bug: confirmed I hope this will help us move in the right direction while still using the list for *every* kind of input*. Best, -- Bastien