Yeah. I think the main issue is the lack of a transition plan - at least in my case, I would not want to see a formal fork if it can be avoided. However the lack of communication from @Morgan_Hardwood is problematic in this regard - I think there are enough people like @Thanatomanic and @heckflosse who could take over the release process for one release, but ideally they get permission to do so (even if temporarily) from the project’s owner.
One of the sticking issues appears to be a review of the default language as @Morgan_Hardwood says he’s concerned about wasting translator’s time on obsolete strings - Roadmap for v5.9 · Issue #5632 · Beep6581/RawTherapee · GitHub - now the question is:
How many obsolete strings might there actually be? Perhaps if some obsolete strings are missed, the amount of time spent by translators might be negligible?
Perhaps this is an opportunity for automation? What’s the review/revise process that @Morgan_Hardwood has in mind? Could this be something where a tool is run on the code to determine which strings no longer have anything referencing them and thus can be garbage collected?
Perhaps another improvement opportunity would be to use something like crowdin? https://crowdin.com/ - I’ve been involved with other projects that used it seemingly successfully. I could try contacting Ethan and Max from Omni - OmniROM translations in Crowdin - for tips on integrating it.