I am investigating if we could add this package to NonGNU ELPA (see link), a new Emacs Lisp package archive that will be enabled by default in Emacs 28. This means that users of that version or later will be able to install this package without any configuration: they can just run M-x list-packages and install it out of the box. We hope that this will improve Emacs and help bring new users to this package and others.
However, NonGNU ELPA has a requirement that all files must have a clear statement of its license and copyright status. I believe the first patch here would be sufficient to fulfill this requirement.
The main difference between NonGNU ELPA and MELPA is that only stable versions of packages are released. A new release will be made automatically when you bump the ";; Version: NNN" commentary header in this repository, as I do in the second patch. NonGNU ELPA does not look at any "git tag". In the future, you can bump the package version (thereby releasing a new version) when you think it makes sense and at your convenience.
Please let me know if you have any questions about NonGNU ELPA.
skangas
commented
1 year ago
Hi!
I am investigating if we could add this package to NonGNU ELPA (see link), a new Emacs Lisp package archive that will be enabled by default in Emacs 28. This means that users of that version or later will be able to install this package without any configuration: they can just run
M-x list-packagesand install it out of the box. We hope that this will improve Emacs and help bring new users to this package and others.However, NonGNU ELPA has a requirement that all files must have a clear statement of its license and copyright status. I believe the first patch here would be sufficient to fulfill this requirement.
The rules for accepting a package into NonGNU ELPA are here, for your reference: https://git.savannah.gnu.org/cgit/emacs/nongnu.git/tree/README.org#n133
The main difference between NonGNU ELPA and MELPA is that only stable versions of packages are released. A new release will be made automatically when you bump the ";; Version: NNN" commentary header in this repository, as I do in the second patch. NonGNU ELPA does not look at any "git tag". In the future, you can bump the package version (thereby releasing a new version) when you think it makes sense and at your convenience.
Please let me know if you have any questions about NonGNU ELPA.
Thanks!