unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jai Flack <jflack@posteo.net>
To: Philip Kaludercic <philipk@posteo.net>
Cc: "Rudolf Adamkovič" <salutis@me.com>,
	"Stefan Monnier" <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: [NonGNU] New packages: avy-menu, flyspell-correct and friends
Date: Sun, 22 May 2022 03:46:59 +0000	[thread overview]
Message-ID: <87tu9iqle4.fsf@posteo.net> (raw)
In-Reply-To: <87ilq018kg.fsf@posteo.net> (Philip Kaludercic's message of "Fri,  20 May 2022 16:18:39 +0000")

Philip Kaludercic <philipk@posteo.net> writes:

> Rudolf Adamkovič <salutis@me.com> writes:
>
>> Jai Flack <jflack@posteo.net> writes:
>>
>>> The package does offer a completing-read interface in
>>> flyspell-correct.el as a default.
>>
>> As a long-time user of the package, I would like to see it become a part of
>> vanilla Emacs, now that the standard completing read API exists.
>
> This is part of the reason why I wanted to see if there was a reason
> against adding it to GNU ELPA first, and possibly the core later on.
>
>> Rudy

They've already had some discussion about getting the package in GNU ELPA,
it seems three of the contributors have yet to respond (it is noted that
two of them have previously contributed to Emacs) and one can't have the
copyright assignment. Only considering flyspell-correct.el there is ~19
lines of nontrivial changes by the contributor that can't get copyright
assignment.

Provided they would be happy with it, what are the requirements for
rewriting this by someone with copyright assignment? Then
flyspell-correct could be brought into GNU ELPA and the alternative
interfaces could go into NonGNU ELPA. I will use their bug tracker to
see if the copyright assignment situation has changed.

-- 
Thanks,
Jai



  reply	other threads:[~2022-05-22  3:46 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 [this message]
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

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=87tu9iqle4.fsf@posteo.net \
    --to=jflack@posteo.net \
    --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).