Is use-package unmaintained?

The last commit was over one year ago. Is there a fork that's actively developed?

It is a stable project and works well with latest versions of emacs (28,29) as well. That said, yes looks like no one is actively working on the issues or merging pull request. Not sure what’s happening there.

Lisp is a stable language. Use-package is just a macro, textual transformation. If the transformations are still correct, no changes are needed

I appreciate the response but this doesn't follow. Reliable macro expansion doesn't mean the resulting expression behaves as the user would expect.

The author is still very active, just not on that repo :( There are some good pull requests rotting in the queue Is it possible the code is frozen for the purpose of up streaming into emacs proper?

Maintainer here: Yes, it has not been actively maintained for over a year now. I am very much open to assistance from the community, so long we retain the objectives of stability and not breaking anyone's current configurations. The next major task to be done is packaging up use-package for inclusion in Emacs proper. If anyone is available to help with this effort, I would be more than happy to work alongside.

It's possible Why not ask the maintainer? > Is there a fork that's actively developed? Unless the fork maintainer was also acquiring copyright assignments for the purposes of upstreaming, this would be counter-productive. From what I understand, it's been a long, slow process to get to the point they're at now (having unfortunately not been taken into account from the outset). This is probably the status update you're looking for, in any case: https://github.com/jwiegley/use-package/issues/282#issuecomment-830852137 (itself 10 months old, but one suspects the situation is much the same.)

Thank you so much for your contributions! `use-package` is incredible. > The next major task to be done is packaging up use-package for inclusion in Emacs proper. If anyone is available to help with this effort, I would be more than happy to work alongside. That is truly great news. If any tasks could be performed by an elisp novice with no experience packaging anything for Emacs proper I'd happily offer some of my time.

I think it mainly needs two steps: Packaging up the code by moving it to the right places and integrating it with the Emacs build system; and reformatting the user documentation so that it shows up alongside the other packages that are included with Emacs. Neither of these should require much in the way of Lisp work... We've already done the work of getting copyright assignments from all contributors, so it's cleared to go in.

Thank you for the background info

Is there a contribution guide somewhere, so that I can get started? I'm an elisp novice with no experience but I'd also like to help out with this effort.

> Packaging up the code by moving it to the right places and integrating it with the Emacs build system How do you imagine use-package to be integrated? As its own subdirectory in lisp sources, similar to org, or as a one, maybe two-three, .el files directly in lisp dir? There are relatively few files making up use-package. What do you mean integration with the build system? Dumping use-package at build time or is it enough for users to just require it at init time? > reformatting the user documentation so that it shows up alongside the other packages that are included with Emacs You mean turning it into info pages for the manual? Sorry if there are too many questions, just curious about more practical side of what has to be done.

Wouldn't the first step be to add use-package to GNU ELPA? I added the necessary packages to my local ELPA checkout, and it seems to work (modulo the broken copyright headers). If this is the issue, the problem can be solved pretty easily. **Edit:** I have brought this up on [emacs-devel](https://mail.gnu.org/archive/html/emacs-devel/2022-03/msg00037.html).

I would like to see it in Emacs itself, so that it is always available in a new installation and does not itself need to be installed.

I think separate files in `lisp/` should be enough. It's OK to require it at init time. And yes to the info pages.

That's a really good question! I'm not sure if docs exist on how to add new Lisp code into Emacs itself.

Ok, thank you for the feedback.

Why not? It’s mostly user supplied code that needs to be wrapped in the standard emacs functions for hooks, bindings, etc. and putting some code before and after the package load. Unless emacs deprecates the way these things are done, use-package doesn’t need to change.