unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Payas Relekar <relekarpayas@gmail.com>
Cc: emacs-devel@gnu.org,  jwiegley@gmail.com
Subject: Re: Progress on merging use-package?
Date: Sat, 24 Sep 2022 14:08:48 +0000	[thread overview]
Message-ID: <8735cgooen.fsf@posteo.net> (raw)
In-Reply-To: <8735chq62g.fsf@gmail.com> (Payas Relekar's message of "Sat, 24 Sep 2022 18:26:29 +0530")

Payas Relekar <relekarpayas@gmail.com> writes:

> Hello!
>
> Recent progress with eglot has kindled my hopes, so here goes another
> shot.
>
> I understand John Wiegley(Author and maintainer of use-package, cc'd)
> always intended to submit use-package[0] to
> emacs core, and would like to ask what the remaining blockers are, and
> what could be done to improve the status quo.
>
> The Github issue[1] tracking copyright assignments appear to be nearly
> at completion, with last contributor remaining having difficulties
> getting the confirmation (or something).
>
> I understand John has been very occupied with $LIFE, but if it is
> possible to take this further with any outside help, I'm sure there are
> volunteers here :)

FYI there was a thread on exactly this topic earlier this year
(https://yhetil.org/emacs-devel/87y21ri7px.fsf@posteo.net/), that
slightly diverged towards the end.  John mentioned the following:

        I would definitely like to see it move to core, and would be
        happy to work with others to make this happen. I feel it still
        needs enough effort -- mostly in terms of documentation -- that
        this is why it hasn't happened yet.

I still argue that adding it to GNU ELPA would be a good fist step, just
like how Eglot was part of GNU ELPA for a while before the merge started.

> Thanks,
> Payas
>
> [0]: https://github.com/jwiegley/use-package
> [1]: https://github.com/jwiegley/use-package/issues/282
>
> --



  reply	other threads:[~2022-09-24 14:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 12:56 Progress on merging use-package? Payas Relekar
2022-09-24 14:08 ` Philip Kaludercic [this message]
2022-09-24 14:22   ` Payas Relekar
2022-09-24 14:35     ` Philip Kaludercic
2022-09-24 14:36       ` Payas Relekar
2022-09-24 15:51         ` Philip Kaludercic
2022-09-24 20:24         ` John Wiegley
2022-09-25  2:34           ` Payas Relekar
2022-09-25  2:45             ` Payas Relekar
2022-09-25  8:09               ` Philip Kaludercic
2022-09-25  8:39             ` Philip Kaludercic
2022-09-28 22:57               ` chad
2022-09-29  8:20                 ` Eli Zaretskii
2022-09-29  8:36                   ` Philip Kaludercic
2022-10-07 22:47                     ` What does use-package do? Richard Stallman
2022-10-08  4:50                       ` John Wiegley
2022-09-24 15:42   ` Progress on merging use-package? Stefan Monnier

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=8735cgooen.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=relekarpayas@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.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).