Kissaki
Enabling the editor and then visiting an article in the administrator site, PHP will fatal-quit because it requires(!) a php-file within the editor switcher directory named like the installed editors.
A quick peek at the code shows it iterating over all installed editor-plugins and require_once()-ing a plg-local file.
Thus, the downloadable package seems 1.) incomplete, 2.) untested.
I also question the concept being used here in general. It means the editor-switcher would require a PHP file for each editor you install. And it will not be able to provide these for custom installed editors or custom editors.
I want you for me to help for a GPL license.
Of course, although I am testing, it cannot test in the environment which I do not know.
Then, please tell me the editor which you have installed, and environment.
In addition, it is only the selected editor that is requiring.
As Passwords are not complying the synching is not enough to use flyspray stand-alone but being able to assign a menu item with a specific theme one can make it, at least visually, clean very easily.
In fact it sends an email to the first super adminsitrator, and that's all. Not to all admins, not only to those who want an email and not an activation mail to the signer.
The code has a lot of commented out code, wrong comments…
As an example above issue: In the fn for sending the mail, the code for sending to email-reveive-allowed super admins is commented out. In a block titled with the comment "// Send email to user" the mail is sent to one super admin.
This is non-usable.

