From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Cc: mark@ofosos.org
Subject: Re: ox-epub
Date: Fri, 17 Mar 2017 10:32:24 +0100 [thread overview]
Message-ID: <87zigks0yf.fsf@gmx.us> (raw)
In-Reply-To: 8760j9f0qy.fsf@nicolasgoaziou.fr
Hi,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Nowadays, moving a package to contrib/ only makes sense if it is meant
> to ultimately be included in core. Otherwise, GNU ELPA is just as fine.
An exporter is core is much more useful IMO, but I’m a big fan of
batteries included.
> As Rasmus pointed out, documentation is mandatory for inclusion in core.
>
> Also, you need write access on Org repository so as to be able to
> maintain "ox-epub.el" from there.
>>> Are there any technical barriers to continuing development on ox-epub to
>>> me? The legal stuff is not an issue to me.
>>
>> I think you wrote that you are already in the process of assigning
>> copyright for this work to FSF, right?
>>
>>> Do you find the addition worthwile?
>>
>> I do. Nicloas will probably chim in.
>
> I have not looked at the code, but the idea sounds nice.
At the moment, ox-epub.el still needs to mature a bit, as it behaves a bit
differently from other exporters. However, Mark seems to have a good
domain knowledge of what an epub is, so hopefully we could make it work.
I think Alan Tyree has agreed to help test it with "real-world" books
later, if necessary.
> However, IIRC, Bastien (Cc'ed) was reluctant to add more export
> back-ends, back when I wanted to move ox-koma-letter to core. He might
> want to have his word on the subject.
AFAIR there's also some issues with the copyright status of
ox-koma-letter. (I could ping Viktor to hear if anything happened re
this).
Rasmus
--
A page of history is worth a volume of logic
prev parent reply other threads:[~2017-03-17 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 17:58 ox-epub Mark Meyer
2017-03-13 19:02 ` ox-epub Mark Meyer
2017-03-14 9:24 ` ox-epub Rasmus
2017-03-16 20:03 ` ox-epub Nicolas Goaziou
2017-03-17 9:32 ` Rasmus [this message]
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=87zigks0yf.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
--cc=mark@ofosos.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).