Before a new feature poll is started, it is probably worth it to compile a cleaned-up list of feature requests.
Currently, there are GitHub issues, a collection on the (not so frequently updated) Trello page, and then wishes/thoughts/opinions scattered here and there throughout the forums and Discord, where they eventually get burried under new stuff.
I think a pinned thread on this forum could be the best option: It stays up at the top, everyone can post new suggestions (but keep discussiosn to other threads or Discord), and the original author + mods can always edit the first post to keep the collected info up to date.
When the time comes, the thread is replaced with a feature poll.
After the poll is closed, a new thread can be opened that lists the previous poll picks (so people know what is already being worked on), carries over the unpicked options, and opens again for new suggestions.
This is just an idea of course. Dade and B.Y.O.B. should have the say on how they want to organise this (or not at the moment), since they will likely end up being the people who execute most of the work
Which brings me to another point: Involving new developers. I think a feature poll can be a good opportunity for this, as it provides a bit of a cut where you can assign features to people interested to have a go.
I have been interested since I joined here, just my lack of practical experience with C++ has not yet caught up to the tasks
Same with the specific algorithms used for ray tracing.
At the moment I have a lot of time and try a bit more in that direciton, specifically I've started some work on the lens-flare calculation that was recently posted also on GitHub.