From: Pankaj Jangid <firstname.lastname@example.org>
To: Bastien <email@example.com>
Subject: Re: Release Org 9.4.2
Date: Wed, 16 Dec 2020 09:29:09 +0530 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Bastien's message of "Tue, 15 Dec 2020 15:24:57 +0100")
Bastien <firstname.lastname@example.org> writes:
>> My question is/are: (1) Why Org is developed outside Emacs, given that
>> it is a core/built-in package.
> When Org's development switched to Git (13 years ago, from memory),
> the release cycle was very short. Way shorter than the release cycle
> of Emacs. Also, the process for accepting new code contributors was
> lighter, even when we asked them to sign the FSF copyright assignment.
> In this context, having a separate Git repo was a huge plus, and Org
> was not yet included of Emacs.
> Then Org became part of Emacs, which was a very important move.
> But still, using a separate repo and a separate mailing list was key
> in being free to progress at our own pace, which was still quite fast.
> Today, the release cycle of Org is longer and that of Emacs shorter.
> So yes, it could make sense to envision a destiny similar to Gnus:
> Gnus is now developed in Emacs and Org could also be developed in
Thanks for writing this. This explains everything.
> But (1) it is not only *our* decision, it's also in the hands of the
> Emacs maintainers, which may think otherwise; (2) all the consequences
> need to be considered, as it is a sensible move; (3) I am on the verge
> of stepping down as a maintainer, so it is not a good time for me to
> push into a direction or another.
I sensed (3) when I saw an email (last month I guess) about assimilating
parts of Org into Emacs. While that is a good idea. But I don’t have a
very good feeling about you leaving. You have contributed so much. You
have maintained it so well.
I can understand how it feels when people complain about features. And
sometimes they blame the maintainers for some specific product
directions. But it is bound to happen when they are also attached to the
product. I hope these things have not shaped up your decision. It
happens in a closely knit family.
> Anyway, I don't think now is the right time to consider this move, as
> there are many more things to achieve. I suggest we discuss this again
> later next year.
Yes. This is endless. We’ll continue this...
next prev parent reply other threads:[~2020-12-16 4:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 7:04 Release Org 9.4.2 Bastien
2020-12-14 14:10 ` Pankaj Jangid
2020-12-14 14:18 ` Bastien
2020-12-14 15:19 ` Pankaj Jangid
2020-12-15 11:38 ` Eric S Fraga
2020-12-15 13:58 ` Pankaj Jangid
2020-12-15 14:24 ` Bastien
2020-12-16 3:59 ` Pankaj Jangid [this message]
2020-12-16 6:19 ` Bastien
2020-12-16 7:00 ` Pankaj Jangid
2020-12-16 7:14 ` TEC
2020-12-16 13:04 ` Gustav Wikström
2020-12-16 13:49 ` Eric S Fraga
2020-12-16 14:11 ` Gustav Wikström
2020-12-16 14:50 ` Eric S Fraga
2020-12-16 15:05 ` Gustav Wikström
2020-12-29 9:42 ` TEC
2020-12-29 12:14 ` Gustav Wikström
2020-12-16 15:13 ` Loris Bennett
2020-12-16 19:01 ` Tim Cross
2020-12-17 13:27 ` Eric S Fraga
2020-12-17 15:32 ` Greg Minshall
2020-12-17 23:19 ` Samuel Wales
2020-12-16 14:56 ` Pankaj Jangid
2020-12-16 18:41 ` Tim Cross
2020-12-22 14:27 ` Lennart C. Karssen
2020-12-22 15:07 ` TEC
2020-12-22 16:18 ` Bastien
2020-12-22 19:46 ` Jean Louis
2020-12-15 21:12 ` Daniele Nicolodi
2020-12-16 5:19 ` Pankaj Jangid
2020-12-18 21:49 Asa Zeren
2020-12-21 12:25 ` Eric S Fraga
2021-01-02 22:45 ` TRS-80
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 \
* 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).