emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Samuel Banya <sbanya@fastmail.com>
Cc: Charles Berry <emacs-orgmode@gnu.org>
Subject: Re: Question Regarding Easier Issues To Help With
Date: Wed, 25 May 2022 09:26:02 +0800	[thread overview]
Message-ID: <87mtf6s8r9.fsf@localhost> (raw)
In-Reply-To: <68f842de-d208-44bf-9320-6bc21ef93f7f@www.fastmail.com>

"Samuel Banya" <sbanya@fastmail.com> writes:

> Its kind of funny since all I do at work doing tech support is reproducing stuff for Devs, but I guess that works in this context too. I just didn't want to have to do more tech support, and wanted to get into the nitty gritty of Elisp to be honest. More so, to get Dev experience so that I can finally move away from tech support and into a Dev job later (after I finish my web dev bootcamp first though).

If you prefer to do something programming-related, some of the provided
links also offer such possibility. Or you can reproduce a bug and then
also fix it ;)

Further, you can contribute to Org testing suite. Just look at testing/
folder and look at the existing tests. You can add some new edge cases
to the tests or create new tests for interactive Org functions not yet
covered by the tests (there are plenty). Also, See
https://orgmode.org/list/874k81bsvz.fsf@localhost

Finally, I may host another meetup this Saturday where we can discuss
Org development/bug fixes live, possibly with screen sharing.

Best,
Ihor


  reply	other threads:[~2022-05-25  1:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23  4:53 Question Regarding Easier Issues To Help With Samuel Banya
2022-05-23  6:36 ` Tim Cross
2022-05-23  9:03 ` Ihor Radchenko
2022-05-25  0:58   ` Samuel Banya
2022-05-25  1:26     ` Ihor Radchenko [this message]
2022-05-25 14:04       ` Samuel Banya
2022-05-25 14:46         ` Ihor Radchenko

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=87mtf6s8r9.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sbanya@fastmail.com \
    /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).