From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id KK6ENhCLWGduVgEAe85BDQ:P1 (envelope-from ) for ; Tue, 10 Dec 2024 18:40:17 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id KK6ENhCLWGduVgEAe85BDQ (envelope-from ) for ; Tue, 10 Dec 2024 19:40:17 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="h+Nd/meN"; dmarc=pass (policy=none) header.from=posteo.net; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1733856016; a=rsa-sha256; cv=none; b=vA0HOtd24kr8LOwuVTUCtpLV3gfkT7RNUkT93YgbKSPIXEQdej7MnBfQjCVLqFkrHhu4YJ ld1fwuH/l+CckhlFZbAJzNzHAqfOrCrubHgSnLu9GBqQ0wtUtbjMmH//33N0Tg6ccZt9kL cs7zvvzvSSe5A1GFarPzhbNY1wsQwPJfL/uqm/gDrhLcB6c6+D9J08U1W4N8E2S68YV9M+ qgmFHoJQ5z08GxVWnY3pR9K5cQ5wlxkrZ9J4eJoRIBn3icSvUwPKeYCDVmz7AbOfoMrTmw xWtNWUAQlFfYnTC9bkdGPKOe94aMZYqAgcLoRdI1UWYbJciOzZyk8NwrV6NqPQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="h+Nd/meN"; dmarc=pass (policy=none) header.from=posteo.net; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1733856016; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=dOJ5Fy/rbU87Al3/1aGypxQcRVXkW3VUcpCODVBPzX4=; b=llrzQHv511+GyUae3hC18Q8qgw6puD4dJOp31lw5bkfXpm+0PbQqs+r0hDdo2dm23u0UxW N+cN4H1gHsepnZ5H7evtln8+c+Qr4X9abaRQsz3jWsmcNoejZ8EGYoQcDoQ/KBcJWga3pG osOiePxku9Ubtp4ybf32kQ+RphIM28C6w3vGOQR0VjiNNazSmT50nDCg8YowFOJ85VUe+3 EBRUvJfzHOQE2TVamsdXsRzmSjNuKl85OE/6XyDzqScs9ukrKhhNYw2RyteTysn5belhlq ZejjPcM3jM4NDa1eL4bHcQO/a09WYuVpd6mSfNN2IOT6Gmxf+hOm9j4jeX/KVQ== 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 7BF3378A4D for ; Tue, 10 Dec 2024 19:40:15 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tL4Tk-0007hT-AO; Tue, 10 Dec 2024 12:57:00 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tL4Ti-0007hE-Qv for Emacs-orgmode@gnu.org; Tue, 10 Dec 2024 12:56:58 -0500 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tL4Tg-0000P5-Pu for Emacs-orgmode@gnu.org; Tue, 10 Dec 2024 12:56:58 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 4327D240029 for ; Tue, 10 Dec 2024 18:56:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1733853414; bh=q9bsVnlus4PG/Cu9FTKFG6EoDLS4bLY8vEjs0FaZtp0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=h+Nd/meN3fKVbAUzzQaPyycFz4YE73Vlk+d0rwYpqmT63W1OmvYqqlas5GrGrNFsf HJ9mjAkFPevmAIUYKZxm0ep1CTOVB/3lwgohakmLQ1A0/ZFLESZtRaDMCzX062soHm H2V+KrTotOHNy3Da2Lo67MeMxfjAWbcn4iVbmIKJ4C4EP2vGpRtG7zM/NMIKVtP7Z1 9oMbz60b9/lY42Ag34ShTlBCZP8ODv1uqUERl1gy7cS07FM8jOqa5XC+kFP7/DtPJc V4vFFxbJd4JBiqhi2FacQkd1a8G1TJw63R0pWrTwx0Dc1l8R6Vz+lWqPKfrVi7+x3a OEWTiQHNHLuNg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Y75yr0Rlvz9rxD; Tue, 10 Dec 2024 18:56:51 +0100 (CET) From: Ihor Radchenko To: Derek Chen-Becker Cc: Emacs-orgmode , bzg@gnu.org Subject: Re: Contributing (looking for good first issues to tackle) In-Reply-To: References: Date: Tue, 10 Dec 2024 17:58:19 +0000 Message-ID: <87y10nwhc4.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 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-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Queue-Id: 7BF3378A4D X-Migadu-Scanner: mx13.migadu.com X-Migadu-Spam-Score: -8.88 X-Spam-Score: -8.88 X-TUID: ujT05CGWjU6x Derek Chen-Becker writes: > ... I took a look at https://orgmode.org/worg/org-contribute.html and > https://tracker.orgmode.org/bugs but it's not clear to me if this is the > actual way we track issues or if this is just fancy indexing of the > mailing list (both?). Thanks for your interest! Woof! is the way to track issues, at least eventually. It works by indexing the mailing list, so using Woof! simply saves you from the noise of non-bug messages we get here. You may also follow the whole mailing list if that's ok for you. > ... Some of the bugs reported in the list already have a > message stating that the issue is fixed, so I'm also a little confused > about the consistency of the Woof index vs reality. Woof! is still in early development, and we have an annoying bug there causing some issues to remain open even after marking them closed. Bastien, can we do something about it? This problem keeps confusing potential contributors. AFAIK, the new bug reports will consistently appear in the list. So, you can take a look at the latest reports. They are likely to be unfixed. You can also subscribe to see new bug reports via RSS: https://tracker.orgmode.org/bugs.rss > ... As a first task, maybe > is there a way I could help triage things and mark completed > requests/bugfixes in Woof? Or do we have a different way of tracking things? As you can see, marking things completed is just a bug in Woof that we should eventually solve. Woof! is written in Clojure and developed in https://sr.ht/~bzg/woof/. Probably it is not what you want. (Or, if you do, I am sure that Bastien will welcome contributions there.) For triaging the bugs, you can look at the bugs without any response and the bugs without _my_ response. These are the bugs I did not triage yet. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at , or support my work at