Yes, a good idea indeed, but Qora dev left so long ago now that chances are he isn't coming back, so whoever starts 'doing things' will probably get community support very quickly, it's not like the problem here is rival dev camps squabbling over what to do, the problem is if people are really doing things behind the scenes, it's not obvious to the community what those things are, and if they're getting results.
The advantage of a "Community Edition" lies in communication ... a community edition is simply another client version (with possibly additional bug fixes) for the same protocol. A new client can be done by anyone, anywhere, in any moment and would need not even planning a "takeover" because it needs no authorization nor planning. As long as it does not change consensus rules (hard or soft forks) it will be compatible with any code the old dev delivers (if he does).
A full "takeover", instead, normally does involve a lot of planning and discussions and thus is a move that requires more time.
So my advice would be: just fork the repo and someone (or a group) that is online every day or two (it's not necessary for him/her to be a software developer!) should manage it so any developer that wants to fix the bug can simply do it by providing a pull request.