Porters usually have to know the inside of the application they're porting for, and afaik none of the current dev team members uses e-xoops.
My suggestion is still: take a look at the bridge file stuff, how it is done. This will basically merge the user database of coppermine and e-xoops. The advantage is clear: you could always use new versions of coppermine and send all users who are looking for support to the coppermine forums. If you do a "real" port (like the phpNuke/postNuke people did), you'll have to maintain different code (the advantage of a real port is that coppermine would use the theme/skin that exists for e-xoops, so it would visually fit better into the design).
Right now, we're experiencing some kind of "forking", as the coppermine_for_nuke code has different features than the coppermine_standalone code. This can only be achieved if there are already some skilled coders working with e-xoops.
In other words: I doubt that the coppermine dev team will come up with a port for e-xoops, you'll have to build it on your own if you really need it, sorry.
GauGau
[edit GauGau]
merged the two postings dealing with e-xoops port into one
[/edit]