From: Jai Flack <jflack@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
philipk@posteo.net, salutis@me.com, emacs-devel@gnu.org
Subject: Re: [NonGNU] New packages: avy-menu, flyspell-correct and friends
Date: Mon, 23 May 2022 12:26:39 +0000 [thread overview]
Message-ID: <87r14kxwn4.fsf@posteo.net> (raw)
In-Reply-To: <83k0ad7m77.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 22 May 2022 16:04:28 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Cc: Philip Kaludercic <philipk@posteo.net>, Rudolf Adamkovič <salutis@me.com>, emacs-devel@gnu.org
>> Date: Sun, 22 May 2022 08:53:51 -0400
>>
>> Jai Flack [2022-05-22 03:57:36] wrote:
>> > One more thing: do we have a clear definition for "non-trivial
>> > contributions"?
>>
>> We define it as "equivalent to about 15 lines worth of code", where
>> equivalence should be understood in a kind of kolmogorov-complexity sense.
>
> It's not just a line count: the nature of the "code" in those 15 lines
> also matters. They must express some real creative activity. For
> example, 15 lines of data that can be gleaned from some source don't
> count.
Right. In that case copyright assignment for them shouldn't be a
problem, what can go in GNU ELPA vs. NonGNU ELPA is only dictated by the
dependencies.
The maintainer is working on submitting their copyright assignment
papers at the moment.
--
Thanks,
Jai
prev parent reply other threads:[~2022-05-23 12:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 3:51 [NonGNU] New packages: avy-menu, flyspell-correct and friends Jai Flack
2022-05-16 17:30 ` Philip Kaludercic
2022-05-17 8:59 ` Jai Flack
2022-05-17 18:32 ` Stefan Monnier
2022-05-18 12:55 ` Jai Flack
2022-05-20 13:19 ` Rudolf Adamkovič
2022-05-20 16:18 ` Philip Kaludercic
2022-05-22 3:46 ` Jai Flack
2022-05-22 3:57 ` Jai Flack
2022-05-22 12:53 ` Stefan Monnier
2022-05-22 13:04 ` Eli Zaretskii
2022-05-23 12:26 ` Jai Flack [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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r14kxwn4.fsf@posteo.net \
--to=jflack@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=salutis@me.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.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).