@Fabio:
AROS is Open Source, this means that anyone can take its sources and do whatever he wants with it, even port it to the Efika. On the same fashion, anyone is free to offer as much money as he wants in order to incentive the port: there's an offer waiting for demand, a demand which might not be there at all in the first place.
I understand that. However, not all open source projects are bounty driven, and the ones that progress best* are the ones which follow a development roadmap and at least a loose schedule.
The ones that tend to drift wherever the wind (or bounties) take them are the ones which tend to get bogged down and stagnate.
In fact, if you haven't noticed it, no one has taken up on the bounty yet.
It would be damaging to AROS if and only if
1) someone had taken up on the bounty
True.
and
2) by accepting the bounty, that person would subtract valuable time to other kind of AROS development.
Considering that (1) hasn't happened yet and (2) is quite unlikely to be the case, there's simply no damage being done.
Well, we can't say much about (2) until the bounty is taken. Even then it may be impossible to know if the person who accepts it would otherwise have chosen to work on something more advantageous for AROS as a whole.
I remain of the opinion that a port to Efika is primarily meaningless at best and will use up resources best used elsewhere at worst. People who want to run things like Hollywood on Efika would do so on MorphOS - as that OS is considerably ahead of AROS in development and will probably remain so for the foreseeable future. Any suggestion that 68k emulation would be easier to do on PPC is pointless as well because in that case it won't be portable and thus of no use to AROS in general. The only benefit to AROS would be if it helped port more of MorphOS into AROS thus feeding back into the general code base, but as there seems to be very little enthusiasm for convergence from either MOS or AOS4 I don't see much mileage in that either.
* by this I refer to relatively complex team projects. Single developer OSS projects tend to follow a different pattern.