From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Stable releases
Date: Tue, 18 Aug 2015 15:40:09 -0500 [thread overview]
Message-ID: <20150818204009.GW25378@cardamom.adamsinfoserv.com> (raw)
In-Reply-To: <87fv3gv6rj.fsf@gnu.org>
On Tue, Aug 18, 2015 at 07:36:00PM +0200, Bastien wrote:
> Hi Scott,
>
> the main reason why 8.3 was not as "stable" as it should have been is
> that I've been releasing it too quickly, after having been inactive
> way too long.
>
> It's kind of a miracle that Org development could continue without an
> active "official" maintainer for so long, and we owe a lot to Nicolas
> and other contributors for this.
Bastien,
As a Org user since 2006 I've watched and appreciated how much time
and effort yourself and Carsten have put into maintainership. This
significant commitment brings about the following question:
Is Org large enough that it would benefit from being broken into more
pieces?
For instance a stable core that includes only the major mode itself,
which you continue to maintain. This defines the file syntax and
includes core features which require little to no external programs or
libraries.
Then could you break out the exporters, babel, and many of the other
sub-features into "plugins" that could be maintained separately by
others, and they depend back to the core version?
My impression has been that the core Org functionality has been stable
for quite a while, and the org ecosystem grows by leaps and bounds as
new users expand the incredibly flexible syntax to work for their use
case.
Could we reduce the amount of maintenance to the core if we separate
the rapidly changing plugins to separate projects?
Sorry if this has been hashed before, but I felt it appropriate to
ask.
Thanks.
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2015-08-18 20:40 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 17:18 Stable releases Scott Randby
2015-08-11 18:33 ` Ista Zahn
2015-08-11 19:34 ` Suvayu Ali
2015-08-11 20:56 ` Rasmus
2015-08-12 16:14 ` Scott Randby
2015-08-12 13:39 ` Nicolas Goaziou
2015-08-12 14:38 ` Peter Salazar
2015-08-12 15:57 ` Scott Randby
2015-08-12 22:56 ` Rasmus
2015-08-18 16:44 ` Bastien
2015-08-18 17:30 ` Bastien
2015-08-12 17:37 ` Achim Gratz
2015-08-12 19:06 ` Scott Randby
2015-08-13 9:32 ` Eric S Fraga
2015-08-13 13:28 ` Scott Randby
2015-08-18 17:36 ` Bastien
2015-08-18 17:52 ` Scott Randby
2015-08-18 20:40 ` Russell Adams [this message]
2015-08-18 22:26 ` Bastien
2015-08-19 20:00 ` Rasmus
2015-08-20 23:03 ` Bastien
2015-08-20 23:56 ` Thomas S. Dye
2015-08-21 7:21 ` Suvayu Ali
2015-08-22 17:32 ` Thomas S. Dye
2015-08-22 17:44 ` Achim Gratz
2015-08-22 17:55 ` Thomas S. Dye
2015-08-22 18:00 ` Achim Gratz
2015-08-22 18:23 ` Thomas S. Dye
2015-08-22 18:53 ` Thomas S. Dye
2015-08-22 18:57 ` Achim Gratz
2015-08-22 19:06 ` Thomas S. Dye
2015-08-21 18:37 ` Rasmus
2015-08-19 8:51 ` Nicolas Goaziou
2015-08-19 9:36 ` Bastien
2015-08-19 14:51 ` Nicolas Goaziou
2015-08-19 19:57 ` Rasmus
2016-01-17 10:12 ` Losing trust in Org: stable org-mode releases and unit tests for basic functionality Karl Voit
2016-01-17 10:30 ` Achim Gratz
2016-01-18 13:47 ` Karl Voit
2016-01-17 13:41 ` Marco Wahl
2016-01-18 14:06 ` Karl Voit
2016-01-19 9:00 ` Marco Wahl
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150818204009.GW25378@cardamom.adamsinfoserv.com \
--to=rladams@adamsinfoserv.com \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).