I have to admit that in concept this is an excellent idea.
From the site:
"Keep in mind programmers this effort should work on @ least Amiga OS 3.9, WinUAE, Amithlon, MorphOS, AROS, Amiga OS 4.0, etc. so everyone can benefit from the effort."
However, I do not think that it will be practical to get it working on all these variations of AmigaOS (or compatible - whatever).
3.9 and 4.0 for example - I'm not sure how you would manage this - would you maintain a 68k version and two ppc versions? I could perhaps see gettin one version to run on 4.0 and MorphOS - but even that would be an interesting trick.
Lets not forget the Amiga500 users that will want to run it on 512k of fast. ;-)
My suggestion? Drop all classic ports for now and focus on 4.0 - it would be nice to have a full-featured web browser available with the new OS. I would probably also drop the requirement for Flash as well as it is not a standard.
How would the money be doled out? All at once, once the project was "finished" - or is "bug-free"?
I would suggest laying out a list of goals to meet, perhaps with a suggested timeline, and then paying out as the project meets the goals.
To be honest, I'd be just as happy to see Ibrowse getting brought up to standards, and it probably would be easier to get a complete version done (but I'm not sure).
Perhaps someone should let the folks at Opera know about this as well - its a nice browser as well, and they at one point had interest in an Amiga version.
