Proposal: Add package to Nongnu Elpa (or Melpa)?
- Dominant language
- Emacs Lisp
- Stars
- 41
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure what's involved with adding a package to [Nongnu Elpa](https://elpa.nongnu.org/). But adding it either there or to [Melpa](https://melpa.org/#/) would make set-up easier and improve discoverability for Kmonad, since that would cause it to be listed with the other packages available from `list-packages`.
Nongnu Elpa is included in the default set-up for Emacs 28. So adding it there would be preferable since users wouldn't even have to add Melpa to `package-archives`. If the package were available on NonGnu Elpa, a user could add it to a fresh Emacs install simply by doing "M-x package-install RET kbd-mode RET", or by searching and clicking the install button after doing `M-x list-packages RET`.
But inclusion in Nongnu Elpa seems to be at the discretion of the Emacs maintainers. If for some reason that were a hindrance, adding the package to the Melpa repository would provide nearly the same benefit. The only difference being that Melpa has to be manually added to `package-archives` (but of course, that's something most Emacs users do already).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the Nongnu Elpa and Melpa submission guidance linked in the issue, then inspect how kbd-mode is currently packaged. Done means the package is accepted by one of those repositories and can be found and installed through Emacs's package interface. The issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- emacs-lisp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100