From: Michael Alan Dorman <mdorman@ironicdesign.com>
To: Puneeth Chaganti <punchagan@gmail.com>
Cc: Rafael <rvf0068@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-blog 0.9 release
Date: Wed, 01 May 2013 06:48:58 -0400 [thread overview]
Message-ID: <8738u7ynz9.fsf@ironicdesign.com> (raw)
In-Reply-To: <CALnw1fS095RWtGzzY91VOWDf7v_WKh1r1YwnkpxxT3qNJ4O5bg@mail.gmail.com> (Puneeth Chaganti's message of "Wed, 1 May 2013 09:42:04 +0530")
Puneeth Chaganti <punchagan@gmail.com> writes:
> Or, if it seems reasonable, we could club the two projects into a
> single one to give the users something that's better than a sum of the
> parts!
Hi, Puneeth,
While I'm not sure the structure of the two tools is really amenable to
being joined---the code is very, very different, and I am, of course,
biased toward mine ;)---it seems to me *that* a common ox-blog (or
whatever) back-end could be a good point of collaboration: it would help
jump-start getting org2blog to where it work with 8.0, and it would get
org-blog the more sophisticated export capabilities that Rafael seeks.
What I'm imagining is an exporter derived from org-html (of which I've
already got the basics done) that adds on the additional features you've
implemented in org2blog.
If you don't mind, I will start looking at the org2blog code and seeing
how cleanly I can implement these additional capabilities as handlers or
filters for the exporter---and then maybe we could look for that
back-end to live in contrib, and both our codebases could take advantage
of it?
Cheers,
Mike.
next prev parent reply other threads:[~2013-05-01 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 18:46 org-blog 0.9 release Michael Alan Dorman
2013-05-01 3:05 ` Rafael
2013-05-01 4:12 ` Puneeth Chaganti
2013-05-01 10:48 ` Michael Alan Dorman [this message]
2013-05-01 11:04 ` Puneeth Chaganti
2013-05-23 23:48 ` Matt Price
2013-05-24 12:30 ` Michael Alan Dorman
2013-05-01 10:36 ` Michael Alan Dorman
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=8738u7ynz9.fsf@ironicdesign.com \
--to=mdorman@ironicdesign.com \
--cc=emacs-orgmode@gnu.org \
--cc=punchagan@gmail.com \
--cc=rvf0068@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).