emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Alan Schmitt <alan.schmitt@polytechnique.org>,
	Org Mode List <emacs-orgmode@gnu.org>,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: [RFC] Move ox-koma-letter into core?
Date: Sat, 08 Feb 2014 14:17:09 +0100	[thread overview]
Message-ID: <87a9e1vj56.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87wqh6zw8t.fsf@gmail.com> (Nicolas Goaziou's message of "Fri, 07	Feb 2014 18:08:18 +0100")

Hi Nicolas,

Nicolas Goaziou <n.goaziou@gmail.com> writes:

>> If you're fine with this, I'll raise the topic on both emacs-devel
>> and this list.
>
> I suggested this idea because I thought it was a good one. The very fact
> that we're still discussing it proves that it isn't as obvious as
> I initially thought. That's fine with me.

Let me state it clearly: I'm not against including ox-koma-letter.el
in Org's core (then in Emacs), I actually think it is a good addition
(once documented, that is.)

My suggestion is to ask Emacs maintainers about the general policy
regarding new Org/Emacs exporters.  Chances are that they will blindly
trust us, which I'm fine with.  If they have a different opinion, it's
better to hear it now than when we do the merge.

Also remember I *removed* some exporters and other files from Org's
core when releasing 8.0, because I wanted to draw a clearer line: the
current rule is "If an Org feature relies on something that is not
part of Emacs or not part of a standard GNU system, don't include it
into core."  That's why ox-freemind.el and org-mew.el new lives in
contrib/, for example.

For those features, GNU ELPA or some other packages archive (I'm not
insisting on Org ELPA) is a the way to go IMO.  But let's not revisit
this, it's a separate issue.

-- 
 Bastien

  parent reply	other threads:[~2014-02-08 13:17 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 23:08 [RFC] Move ox-koma-letter into core? Nicolas Goaziou
2014-01-18 11:55 ` Rasmus
2014-01-18 18:10 ` Carsten Dominik
2014-01-19 13:19   ` Bastien
2014-01-19 14:03     ` Achim Gratz
2014-01-19 14:20       ` Bastien
2014-01-20 17:38         ` Achim Gratz
2014-01-20 18:12           ` Bastien
2014-01-20 19:10             ` Achim Gratz
2014-01-20 20:05               ` Bastien
2014-01-21  1:12                 ` Rasmus
2014-01-21  2:50                 ` Eric Schulte
2014-01-21 10:52                   ` Bastien
2014-01-21 15:50                     ` Nick Dokos
2014-01-21 15:57                       ` Bastien
2014-01-21 18:31                     ` Achim Gratz
2014-01-21 19:10                       ` Bastien
2014-01-21  8:22                 ` Detlef Steuer
2014-01-21 18:19                 ` Achim Gratz
2014-01-21 19:08                   ` Bastien
2014-01-27 14:36     ` Bastien
2014-01-29 13:53       ` Nicolas Goaziou
2014-01-29 14:02         ` Bastien
2014-02-07 10:35           ` Nicolas Goaziou
2014-02-07 10:47             ` Bastien
2014-02-07 17:08               ` Nicolas Goaziou
2014-02-07 17:28                 ` Rasmus
2014-02-07 17:37                 ` Thomas S. Dye
2014-02-08 13:17                 ` Bastien [this message]
2014-02-17 19:10   ` Viktor Rosenfeld
2014-02-17 21:56     ` Thomas S. Dye
2014-02-19 20:33       ` Viktor Rosenfeld
2014-02-20 13:29         ` Rasmus
2014-02-20 22:32           ` Alan L Tyree
2014-03-04  9:35         ` Bastien
2014-02-17 22:25     ` Rasmus
2014-03-10 18:12     ` Greg Troxel
2014-01-18 21:15 ` Alan Schmitt

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=87a9e1vj56.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=alan.schmitt@polytechnique.org \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@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 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).