emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Re Org 9.4 is out. Can you help? // breaking apart Org Mode
Date: Tue, 15 Sep 2020 15:49:44 +0200	[thread overview]
Message-ID: <20200915134944.GR20869@maokai> (raw)
In-Reply-To: <ed251152-da62-4ef7-83a9-d1424a56b37e@www.fastmail.com>

On Tue, Sep 15, 2020 at 09:00:39AM -0400, Nicholas Savage wrote:
> I'm new to the development scene (contributed my first patch to
> Emacs last week or so) and a new developer in general who has been
> looking to get involved. I saw Bastien's post on Hacker News
> yesterday and thought that if Org Mode is looking for contributors
> it would be a good place for me, since I use Org Mode frequently. I
> have a rudimentary understanding of elisp, but I'm looking to
> improve by actually contributing.


I'm in much the same position. I've offered to help and trying to
participate. My elisp is ok, but I have little practical experience.

From the code standpoint my concern for several years has been that
Org is so powerful, too powerful, that every edge case asks attention
to be added into core. There are so many things Org has been expanded
to do that were outside of the original scope. That growth can't be
sustained with volunteer time forever.

Rather than a huge refactoring or pushing code back into other Emacs
modes, my thought was that Org should be trimmed into the "core" of
Org functions and that other things should be implemented as modules
available in MELPA outside of the official Org core. That way the
limited maintainer time can be focused on the core of Org and
maintaining strong interfaces for components made and maintained by

I understand that there may be some effort already underway to push
items into external packages.

Perhaps this is a better place to start than a huge refactoring
effort? Also note that I feel like the constant deluge of additions
prohibits refactoring and code improvement in the core. That's my
outside perspective though.

Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

  reply	other threads:[~2020-09-15 13:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 10:05 Re Org 9.4 is out. Can you help? // breaking apart Org Mode William Rankin via General discussions about Org-mode.
2020-09-15 13:00 ` Nicholas Savage
2020-09-15 13:49   ` Russell Adams [this message]
2020-09-23  8:28     ` Bastien
2020-09-23 14:44       ` Dr. Arne Babenhauserheide
2020-09-23  8:25   ` Bastien
2020-09-23  8:21 ` Bastien
2020-09-23 13:03   ` arthur miller
2020-09-23 13:27     ` 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:

  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=20200915134944.GR20869@maokai \
    --to=rladams@adamsinfoserv.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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