From: Jim Porter <jporterbugs@gmail.com>
To: josh parson <jsparson1@gmail.com>, emacs-devel@gnu.org
Subject: Re: help
Date: Sun, 15 Jan 2023 21:20:15 -0800 [thread overview]
Message-ID: <0f4610ab-5fe7-86c7-df5c-264ab29b33e4@gmail.com> (raw)
In-Reply-To: <CADpebndgCBjWHtF7gaKQ6rdDj9KPiqO42xzpqc9z3ZMGYD2-Cg@mail.gmail.com>
On 1/12/2023 6:43 PM, josh parson wrote:
> Hi, I'm Josh. I'm relatively new to open source development and wanted
> to work on something I was passionate about (EMACs), I was wondering if
> there were any small fixes/features that needed work.
The way I got started was simply by finding some things in Emacs that I
wanted to do, but which didn't work right for me. I think it helps to
start small like this: if you use Emacs regularly, there are probably at
least a couple of times you've run into a situation like that. This has
the benefit that you're starting off by writing patches that you have a
personal stake in (because the patch will let you do something you want
to do), which can help keep you motivated as you run into roadblocks
learning a new codebase.
If you haven't found any issues like this, then the next thing I'd
suggest would be to look on the Emacs bug tracker
<https://debbugs.gnu.org/> for any open bugs related to features you use
a lot. Just put "emacs" in for the package name under "General search",
plus whatever other search terms you think make sense.
prev parent reply other threads:[~2023-01-16 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 2:43 help josh parson
2023-01-16 4:25 ` help Richard Stallman
2023-01-16 5:20 ` Jim Porter [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0f4610ab-5fe7-86c7-df5c-264ab29b33e4@gmail.com \
--to=jporterbugs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jsparson1@gmail.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.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).