Moving core packages to ELPA [Was: Re: Why not include all ELPA packages in an Emacs release?]

[Jeremy Bryant <jb@jeremybryant.net>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Stefan Kangas <stefankangas@gmail.com>
>> Date: Wed, 29 May 2024 13:44:37 -0700
>> Cc: jb@jeremybryant.net, emacs-devel@gnu.org, monnier@iro.umontreal.ca, 
>> 	philipk@posteo.net
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > What we discussed was the desire to move packages out of core in a way
>> > that a release tarball would include those package.  That is what we
>> > have a consensus about (but not a complete and satisfactory solution
>> > yet).
>> 
>> It's possible that we have interpreted the previous discussions a bit
>> differently, or that I'm filling in too many blanks.
>> 
>> My understanding was that this was always going to be something like
>> 1) make it possible to ship ELPA packages with core Emacs and then
>> 2) decide which packages should be included.
>> 
>> To my mind, step 2 could either be restricted to only include packages
>> that used to be in core, or it could not be.  The difference is not very
>> big, at least not in principle, since before we bundle even two
>> packages, we still have to solve the issue of how to bundle even one.
>
> Sure, but we never meant that step 2 will include all of ELPA, I
> think.  And at least my understanding of step 2 was indeed that it
> should allow to have more core packages on ELPA than to add packages
> to the Emacs release tarballs.

What is a good core package to start working on migrating to ELPA?

(In searching previous discussions, it wasn't obvious, apart from IDLWAVE)