emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Derek Chen-Becker <derek@chen-becker.org>
To: Emacs-orgmode <Emacs-orgmode@gnu.org>
Subject: Contributing (looking for good first issues to tackle)
Date: Mon, 9 Dec 2024 23:41:38 -0700	[thread overview]
Message-ID: <CAMbmz5mLirm80zfrz_pqy_R3FhAVVxbhKKbYjvpqE7T=1NL1Zw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]

Hi,

I've been a long-time user of org mode and while I already make monetary
donations, I would also like to help out in terms of code and
documentation. I've been writing software for a long time but only in the
last couple of years have I really started to dig into elisp, mostly to
write my own helper functions and customizations. Based on Ihor's recent
talk, 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?). 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. 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?

Thanks,

Derek


-- 
+---------------------------------------------------------------+
| Derek Chen-Becker                                             |
| GPG Key available at https://keybase.io/dchenbecker and       |
| https://pgp.mit.edu/pks/lookup?search=derek%40chen-becker.org |
| Fngrprnt: EB8A 6480 F0A3 C8EB C1E7  7F42 AFC5 AFEE 96E4 6ACC  |
+---------------------------------------------------------------+

[-- Attachment #2: Type: text/html, Size: 3008 bytes --]

             reply	other threads:[~2024-12-10  6:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10  6:41 Derek Chen-Becker [this message]
2024-12-10 10:02 ` Contributing (looking for good first issues to tackle) Dilip
2024-12-10 17:03   ` Derek Chen-Becker
2024-12-10 18:07     ` Ihor Radchenko
2024-12-10 19:14       ` Derek Chen-Becker
2024-12-13 17:30         ` Ihor Radchenko
2024-12-10 13:39 ` Russell Adams
2024-12-10 17:58 ` Ihor Radchenko
2024-12-15 10:10   ` Bastien Guerry
2024-12-15 10:33     ` Ihor Radchenko
2024-12-15 12:04       ` Bastien Guerry
2024-12-16 17:50         ` Ihor Radchenko
2024-12-16 18:41           ` Bastien Guerry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMbmz5mLirm80zfrz_pqy_R3FhAVVxbhKKbYjvpqE7T=1NL1Zw@mail.gmail.com' \
    --to=derek@chen-becker.org \
    --cc=Emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).