This sort of defensiveness doesn’t help.
Let me give a concrete example.
The project started supporting ARM boards in September and then two months later you write in your post that the workload is too great for the current team.
You also wrote that you are adding a pre-configured
i3 BSPWM as an installer option. It is one step from that to make another offline installer (and I’m pretty sure I’ve seen that request here on the forum).
Someone on the forum said EnOS does not provide (or aim to provide) driver tooling, and yet there is
What I’m trying to point out is that you are in the process of “project scope creep” - you are doing more than you initially set out to, and then wondering why it is taking more work.
I’d recommend you spend some time as a team discussing a road map for the project for exactly what your goals are over the next three, six, and 12 months. Then, identify where effort is being spent and how the goals can be supported.
Once you know what you are aiming to do, and what help you need, then you can effectively ask (or “advertise”) for help - along with the roadmap.
If you don’t want EnOS to be another Antergos, or Manjaro, or Garuda, then don’t be one - but then also make sure that you are happy with EnOS being an “enhanced” graphical Arch installer.