From the perspective of the EEF/working group, it makes sense to first ask for a owner who will then find people to take on the specific tasks, ie to fill the spots in an as yet empty shell.
What you ask for is somebody to manage an unscheduled promise. But if the other people around here are remotely like me, I guess you won’t find a match easily. I am a freelancer. I can pick the tasks I take, but if I take a task it implies a strong promise to deliver something tangible, within a deadline.
So… i think what the EEF working group needs to decide on is…
- For what OSes should packages be provided;
that doesn’t have to be all at once and fixed forever, more like a priorities-and-wishes list;
as people were asking mostly about packages for Ubuntu jammy, that should rank high
- What range of OTP releases should packages be made available;
ESL provides packages down to R13 for some OSes, that isn IMO overkill;
the latest versions of the latest minor releases of the actively supported releases are IMO enough;
the latest versions of the latest major releases of the actively supported releases are probably enough
This, in turn, determines what kind of people you are looking for, like “Hey, I know how to do packaging for this OS (but not for that other OS)” (and if you dear reader are one of those people, raise your hand please!!!) Preferably, you can find several of each, bus factor and all.
Apart from that, you will need somebody to automate all this, mabye via GitHub Actions other something.
Lastly, you will need some place to host it all. This again I see in the hands of the EEF/working group, since it requires a long-term commitment from some company or other. the requirements, for space mostly, is determined by how many OSes (now, and later) and OTP releases (now and later) are to be supported.
Put differenty, you are asking for an engineer to asemble a clock. Among us are the gears that can be assembled into a clockwork, but looking for an engineer.