From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: New Citation syntax on the master branch?
Date: Wed, 13 May 2015 13:02:28 +0200 [thread overview]
Message-ID: <87h9rgn3jv.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <554F0848.3030508@gmail.com> (Vaidheeswaran C.'s message of "Sun, 10 May 2015 12:57:04 +0530")
Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com> writes:
> On Sunday 10 May 2015 12:44 PM, Nicolas Goaziou wrote:
>
>> It will land in the trunk once a library using it for Org core is
>> implemented. I put it in a separate branch so that such a library can be
>> built, discussed and tested.
>
> 1. Do you, as a maintainer, have any specific plans for this library?
I'm not a maintainer. Anyway, I have no specific plan besides installing
it in core once involved parts (both developers and users in the ML)
agree on its quality and usefulness.
> 2. What conditions should such a library satisfy in order that it is
> considered a candidate.
I don't use a reference manager myself. However, we are lucky enough to
count on users of such things on the ML. Their opinion matters.
A candidate should be useful enough to make at least a part of them
willing to use it instead of their current set-up.
> 3. Are there any contenders for this library at this moment.
There was a discussion about it a couple of months ago. IIRC, there is
a library being developed there.
> For example, is ox-jabref.el a contender for this library. If "No", on
> what counts it fails to get through the gate.
There can be more than one library: one for Jabref, one for Zotero, one
for BibTex... Different users have different needs. The question is:
which one would be included in Org core?
Ideally, org-citation (oc.el for short) could implement the UI, and
libraries talking to reference managers (e.g oc-jabref, oc-zotero,
oc-bibtex...) could be used as back-ends feeding "oc.el". In this
situation, we could include more than one back-end in core.
From an external POV, I think "org-ref.el" pretty much defines what
features could be included in "oc.el" (though, some of them would be
back-end specific).
Regards,
next prev parent reply other threads:[~2015-05-13 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 7:00 New Citation syntax on the master branch? Vaidheeswaran C
2015-05-10 7:14 ` Nicolas Goaziou
2015-05-10 7:27 ` Vaidheeswaran C
2015-05-13 11:02 ` Nicolas Goaziou [this message]
2015-05-17 19:08 ` Vaidheeswaran C
2015-05-17 8:18 ` Nicolas Goaziou
2015-05-17 20:46 ` Vaidheeswaran C
2015-05-17 9:37 ` Rasmus
2015-05-20 6:23 ` Bastien
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=87h9rgn3jv.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=vaidheeswaran.chinnaraju@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).