From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id kCVoKKoui2J2xwAAbAwnHQ (envelope-from ) for ; Mon, 23 May 2022 08:50:18 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id sBVOKKoui2JNFgAAauVa8A (envelope-from ) for ; Mon, 23 May 2022 08:50:18 +0200 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 2ADB3500C for ; Mon, 23 May 2022 08:50:18 +0200 (CEST) Received: from localhost ([::1]:48204 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nt1tQ-0001Fb-Kp for larch@yhetil.org; Mon, 23 May 2022 02:50:16 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:36098) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nt1q2-0000Bb-Ee for emacs-orgmode@gnu.org; Mon, 23 May 2022 02:46:46 -0400 Received: from mail-pg1-x52a.google.com ([2607:f8b0:4864:20::52a]:44928) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nt1q0-0006UC-Lp for emacs-orgmode@gnu.org; Mon, 23 May 2022 02:46:46 -0400 Received: by mail-pg1-x52a.google.com with SMTP id v10so12848842pgl.11 for ; Sun, 22 May 2022 23:46:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=references:user-agent:from:to:subject:date:in-reply-to:message-id :mime-version; bh=W9w5GXEP3wu9ofuJXxDktl8UvIvQq7q/zxHDjhOq6Rs=; b=Ec48HussNnuJpnRpLel1XAAdJP0psMSHcNEbzUi63YiEqQNBD20lS/rVcguoeWc9VN JTzP1V/3BzKoX43VM8lWb1V++/HmMbv4/voVCPb7eySOvMDZ5bsNOn42z8wOXQnkilWL Fjv3tLrlaPYSTGTRz8WGuZh5uzDEqLlSwkW+cEuS83mpKt9pXnW1Ao2/4Q3v00cF1O6C +YFuLfO7YtDgyEtKmU+eIUo8NMbToqi5Th1cifapn4Pto2rkUDj3VhHnm55xV1clOb3X sd+GuH1eWeEczjg0LCivy3iw+DE+DcMqHB/bdojCZyhmqsrShiBx+SRQ9t1jK5bgD1Th 1zBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:references:user-agent:from:to:subject:date :in-reply-to:message-id:mime-version; bh=W9w5GXEP3wu9ofuJXxDktl8UvIvQq7q/zxHDjhOq6Rs=; b=VJEfFSUvTVnOl0ECAqo0ydSzg6oKcbQKzxbMjpD8JKXcDSAvvvIN6HVWYyFq7l2eIp OVDjgdPrqteD0ngTebp7qsZYEdJa+rMZRpaJS4tjULoHHSIagkJQaIILw/VWu6M/VEt7 0aJj+5hmx5fke87EgZ4cVpV2rU3Y/W/7O6q5K1pFA2bX6bCcSKv/XoluSaBwFnouZLRo p/Csol2KAQpxHhdGGBzd9tTC79tvEpd119/Vh8yMjzttuEPXja5Q59mAFqoUwpjcorNR UF99y63DW1t+wV2V5KGfGbFfIBuvpbqlZkC7pasFFqtChUDwSr8HU2RbWp53S6Iv9R4u QHgw== X-Gm-Message-State: AOAM5316Ii5fcedJQwS/i949ug1ia2RD18zhxOogwy6eRvkJCP9E3g9G NMQ2HBLeImOE0l7JoIR3XREC3CrAtXA= X-Google-Smtp-Source: ABdhPJzlKO3KRafAft+7dZEgReRc1N1ueEuAcueFT1N3DZMEFzE5gEnVeu4xmce3X9gFEngPwsGgWg== X-Received: by 2002:a65:6741:0:b0:3f6:2cca:765b with SMTP id c1-20020a656741000000b003f62cca765bmr19126466pgu.558.1653288402794; Sun, 22 May 2022 23:46:42 -0700 (PDT) Received: from dingbat (220-235-29-41.dyn.iinet.net.au. [220.235.29.41]) by smtp.gmail.com with ESMTPSA id x11-20020a17090a294b00b001df6f26c64esm6351400pjf.13.2022.05.22.23.46.41 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 22 May 2022 23:46:42 -0700 (PDT) References: User-agent: mu4e 1.7.23; emacs 28.1.50 From: Tim Cross To: emacs-orgmode@gnu.org Subject: Re: Question Regarding Easier Issues To Help With Date: Mon, 23 May 2022 16:36:43 +1000 In-reply-to: Message-ID: <87k0ac7nl6.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::52a; envelope-from=theophilusx@gmail.com; helo=mail-pg1-x52a.google.com 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 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" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1653288618; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to: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=W9w5GXEP3wu9ofuJXxDktl8UvIvQq7q/zxHDjhOq6Rs=; b=r5srBjI5eG3eR2nvZn2iXQo6B4mNtP5zvBYRea3+KJaYwIKkeerDzFu+W/7Rvgti/5Fmzn 1+2e+wJuPxAnt/0/zQNzlGQDiu6XliyrVQhjkhPsFlDSq+F+KVhJfhKQz9U5/D4y9uRoao AHbNzQhaBmcV9WE3HLYeoYOFcBdqF+ojHEILOrE7z6xwFpHNXmEA/OrDVLkxdmj4WTTMWk Bouq/g4p2aGcFE6itWyzbxWrQGWQGj1eknt0gbxabQlYKwqSZb9Zj8QnDY2+quXJVKVdao /6o4W7GDxlbfrKg2+/InN4/wB4Yktn3zi5qujvwbRbuwPOVEkoe/98pMOj7ZDg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1653288618; a=rsa-sha256; cv=none; b=LzKvZaL5ZaMlfHsC+djrmXpGzyyH1hDF+A3el9QolIuYdIAZ3zepVvCOxHos9XCWg1ylMc a/umaouKOGkt4kMkigWb32mCPZLGEjwkBSj+PT27PpUQFd/KJpk9qVeMD9tRGh7sQhStB8 WdXvcUc1KMt861BcS4Miozoa4MXjYCEwo6XA2og5FeKSUV91FbVwXrldY+l6VBaOuZonON D4OaQfUWhVVPi37p7SSudjM4RLcud6ffg1YzHT6gIHlgCK7ExGDoNSCwCCf2zx31WYdPOt wbVJLVza41tugnYBfSmmY92qJvYO+bv7d7PbF8MlBjSVi+PdqKaBEGnjEZy04A== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Ec48Huss; dmarc=pass (policy=none) header.from=gmail.com; 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" X-Migadu-Spam-Score: -9.35 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Ec48Huss; dmarc=pass (policy=none) header.from=gmail.com; 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" X-Migadu-Queue-Id: 2ADB3500C X-Spam-Score: -9.35 X-Migadu-Scanner: scn0.migadu.com X-TUID: LffKwNMPsDez "Samuel Banya" writes: > Hey there, > So I took a look at the following link recently as I finally have had time again over the past couple of months since I've been > dealing with a lot of personal family stuff, and got some time back again. > > Can anyone lead me in the right direction for some beginner tier issues to take a look at, as well as hand holding for any workflow > on how to actually work on the related issue / source code accordingly: > https://updates.orgmode.org/#help > > I ask because I'm a bit of an Elisp newbie. I'm assuming the first step is to try to reproduce the bug given the user's info, and then > attempt to look at the codebase to see what might be causing it? > Hi Sam, my recommendation would be to focus on the last part of what you outlined i.e. recipe to reproduce a bug. This is often the most time consuming part for the core maintainers. Given the size of org mode and the number of add on packages, as well as the flexible configuration of org, it can be very challenging and time consuming to get a minimal recipe which can reproduce an issue. Once an issue can be reliably reproduced, it typically takes little time for a fix to be identified. Focusing on how to define a minimal reproducible case is also a useful way to get familiar with org mode and the code structure. It can also help develop elisp skills. Therefore, my suggestion would be to select some reported issues which have not been confirmed or which don't have a clear, concise and minimal recipe to reproduce and try to both confirm the issue and provide a minimal recipe. I believe this would be a huge benefit for the core maintainers. I also suspect that in many cases, once you do have a minimal recipe to reproduce an issue, you will also see possible ways to resolve the issue. When you do, you can report both the recipe and your suggested solution/patch. The more experienced maintainers will quickly be able to assess your recipe and proposed solution and provide feedback for further improvements to your patch or perhaps guidance on how to narrow things down further.