all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: jamesaorson@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: Looking to become a new regular contributor
Date: Tue, 05 Dec 2023 05:31:44 +0200	[thread overview]
Message-ID: <83cyvl5nq7.fsf@gnu.org> (raw)
In-Reply-To: <393A7BF7-A20B-4914-A249-27FD356B3071@gmail.com> (jamesaorson@gmail.com)

> 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.



  parent reply	other threads:[~2023-12-05  3:31 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 [this message]
2023-12-05  4:05   ` James Orson

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=83cyvl5nq7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jamesaorson@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 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.