From: Ihor Radchenko <email@example.com>
To: Joost Kremers <firstname.lastname@example.org>
Cc: fatiparty--- <email@example.com>
Subject: Re: @string abbreviation in bib file not honored in (basic) org-cite
Date: Thu, 03 Nov 2022 07:25:37 +0000 [thread overview]
Message-ID: <87fsf07b4e.fsf@localhost> (raw)
Joost Kremers <firstname.lastname@example.org> writes:
> On Sun, Oct 30 2022, Ihor Radchenko wrote:
>> May I know if there is any update on the copyright assignment situation?
>> If you need any help, we can provide it.
> I have signed the form and sent it in, and I have received the counter-signed
> form back from the FSF.
> Parsebib's Github page mentions 6 contributors, however, and I have no idea if
> they all have copyright assignments, or if their contributions are small enough
> not to require one.
The rules are in https://www.gnu.org/prep/maintain/maintain.html#Legally-Significant
Shuguang Sun contributed TINYCHANGE (no need for copyright assignment;
though he contributed ~15LOC and it is on the edge)
Martin R. Albrecht also contributed TINYCHANGE
Alex Branham -- TINYCHANGE
aikrahguzar -- TINYCHANGE
András Simonyi has copyright assignment (see
And you have the copyright assignment
> I could dive into that and see if we need more copyright assignments, or I could
> ask for parsebib to be included in non-GNU Elpa, which would probably be faster.
> Don't know if you have a preference.
I see no obstacles to go for ELPA, unless you have strong reasons to
avoid asking copyright assignment for future contributors.
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-11-03 7:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 11:17 @string abbreviation in bib file not honored in (basic) org-cite Alain.Cochard
2022-07-08 12:05 ` Bruce D'Arcus
2022-07-09 3:55 ` Ihor Radchenko
2022-07-09 8:40 ` András Simonyi
2022-07-10 9:22 ` Can citeproc be installed without using MELPA? (was: @string abbreviation in bib file not honored in (basic) org-cite) Ihor Radchenko
2022-07-10 19:37 ` Joost Kremers
2022-07-11 2:06 ` Ihor Radchenko
2022-07-12 10:23 ` András Simonyi
2022-07-09 6:10 ` @string abbreviation in bib file not honored in (basic) org-cite [and a minimal working example with natbib] Alain.Cochard
2022-07-09 12:40 ` Bruce D'Arcus
2022-07-10 7:17 ` Ihor Radchenko
2022-07-12 11:14 ` András Simonyi
2022-07-12 11:36 ` John Kitchin
2022-07-12 11:48 ` András Simonyi
2022-07-13 4:52 ` Alain.Cochard
2022-08-07 14:08 ` Ihor Radchenko
2022-07-17 8:26 ` @string abbreviation in bib file not honored in (basic) org-cite Ihor Radchenko
2022-07-17 8:52 ` Alain.Cochard
2022-07-19 20:35 ` Joost Kremers
2022-07-19 20:40 ` Bruce D'Arcus
2022-07-20 10:46 ` Joost Kremers
2022-07-28 12:12 ` Ihor Radchenko
2022-07-29 8:02 ` Joost
2022-10-30 6:25 ` Ihor Radchenko
2022-11-02 21:54 ` Joost Kremers
2022-11-03 7:25 ` Ihor Radchenko [this message]
2022-11-04 14:26 ` Joost Kremers
2022-11-05 8:13 ` Ihor Radchenko
2022-11-07 18:41 ` Joost Kremers
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).