golgoj4 and coley,
you two are the ones mainly working on qOrbiter and as such are setting the rules. However, I really like to point out, that MOST of the stuff in qOrbiter will be library independent. By creating two different codebases you will introduce a lot of overhead, where bugfixes and feature enhancements which deal with DCE communication and LinuxMCE-specific object creation will need to be done in two places. I doubt, that you will like that very much.
Please reconsider your decision to split trees.
Puh, now I have at least written something down, so IF you find out in two month time, that things do not work out with two codebases, I am able to say: 'I told you so'. IF things DO work out, in our next argument, YOU are able to say: 'Just look at Qt4 vs Qt5 in July 2012, and how it did work out'.
I'd say: win-win situation