3
Let me look at it this way... How many forks have been forked out of the all forks in the open source environment?. If you look back in history, quite a few including most or all the major content management systems.
Why? Because an excellent developer cannot be a manager and vice versus. A plumber cannot be a marketing Guru, there are exceptions but there are few abouts. There is a difference in 'wannabee' leaders and true leaders who understand the market and can back it up.
I am not saying XOOPS is full of crap people trying to manage each other, I am saying the above is designed by history and XOOPS is likely to lose more developers and clients by acting slow.
Compare that with commercial versions where forks are almost none-exsistent compared to the GPL/Open Source software (in general, don't pick). Why? They are organised better and their diciplin is working.
Predator and Catz were 2 of if not the best module developers, producing modules that were actually useful for the community. Needless to say their coding practise where great too. Mambo have no idea how lucky they are having them now onboard.
Xoops: Get this sorted out quick before you start to lose more people. There have been forks before and this 2nd batch of jumpers should tell you that your management cannot be trusted to do the job that were assigned. The way you 'employ' new developers/managers will have to be changed too. You should get more senior people joining into your team as none-developers. A developer is afterall a developer, same can be said for a senior manager. You need to balance those two, having too much of one will divide your team - hence the jumps.
Besides, where is the loyalty? From what I can see, you have had some people in the past jumping grounds due to 'internal' conflicts. This can be avoided by taking in the right people for the right job.
Good luck with your re-structure.