I think this is a good idea, though not one to be taken lightly. Refactorings and cleanups are often double-edged swords, and while I am always supportive of investing time in such endeavors, I fear that we may introduce new bugs and/or remove code that was put there for a reason, even though it might not be at all apparent.
If the scope is more or less well defined upfront (i.e. if we determine that we will look into the screensaver code, or something more), I'm fine with that.
I'm not sure this needs to necessarily be a cross-coordinated effort, though - these efforts are always welcome as long as they're well tested, I believe.
There are a few things on my plate that I'd like to look into, ES-wise, that don't fall into the "new developments" area but rather in the "fixing/improvements" area, namely (in no particular order):
Document OMX and collections features, namely Predictive Profile (High 4:4:4) not working [EASY-ISH]
Address textures defaulting to white after returning from an emulator. [MEDIUM?]
Improve texture cache to reduce texture pop-in. [MEDIUM?]
Fix or mitigate VRAM handling, especially on out-of-memory scenarios. [MEDIUM?]
Try to get rid of the two video player options, but rather have a default hardware accelerated player for the Pi that works as intended (i.e. respects the actual layers, rather than being a separate process). [HARD]
I honestly have no idea how to go about several of these, but I secretly hope that with a proper Windows and VS debugging environment I'd be able to make some progress here.
Thanks for starting this.
