From: James Orson <jamesaorson@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Looking to become a new regular contributor
Date: Mon, 4 Dec 2023 20:05:28 -0800 [thread overview]
Message-ID: <CAAo17pWFr3j2i1hsRMTgavEY_=G401g9Ddr5ZsBjViYxKNcJsQ@mail.gmail.com> (raw)
In-Reply-To: <83cyvl5nq7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
Thanks Eli
I will look at those lists a bit later
On Mon, Dec 4, 2023 at 19:31 Eli Zaretskii <eliz@gnu.org> wrote:
> > From: jamesaorson@gmail.com
> > Date: Mon, 4 Dec 2023 16:06:05 -0800
> >
> > I have, for a long time, been looking for a meaningfully project to
> create, but I’ve come to realize that this is seemingly what everyone is
> doing, and instead I have decided it would be more helpful to others to
> work on an existing and well respected tool (like emacs).
> >
> > On top of that, it will work to humble me as I read the code of RMS and
> others before me who made and are still making emacs what it is today.
> >
> > I intend to devote the great majority of my leisure programming time to
> emacs development, and see how that goes after a few years. I have a stable
> job and don’t see this as just some resume fodder, but just want to
> continue to improve and start to also contribute.
>
> Thank you.
>
> > Before I pursue those things myself, what are the best ways to get
> involved in emacs at the current moment? I know I can look at the open
> TODOs and bugs for emacs today and I will definitely do so, but what is
> most likely to actually provide some benefit right now? Say there was some
> large effort being worked on that EVERYTHING else is sort of being tabled
> for. I would not want to run off and do something contradictory to that
> work, etc.
>
> I suggest to subscribe to the bug-gnu-emacs mailing list and see if
> any bugs reported there are something you could investigate and try
> fixing.
>
> There's also etc/TODO, which lists some ideas for improving Emacs.
>
[-- Attachment #2: Type: text/html, Size: 2108 bytes --]
prev parent reply other threads:[~2023-12-05 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 0:06 Looking to become a new regular contributor jamesaorson
2023-12-05 1:56 ` [External] : " Drew Adams
2023-12-05 3:31 ` Eli Zaretskii
2023-12-05 4:05 ` James Orson [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAo17pWFr3j2i1hsRMTgavEY_=G401g9Ddr5ZsBjViYxKNcJsQ@mail.gmail.com' \
--to=jamesaorson@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.