I am sure that such a bounty would be posted if people would help with a detailed description.

If you can write it and send it to Targhan it will be posted as a new bounty. If there is enough interest for it (and I am sure there will be enough to match the minimum amount that will be fixed to open a new bounty) then you can decide at what point you want to take it.

People have to consider that Targhan is swamped with work and that he asked several times for help with very few results

Yes feel free to write up an idea for your bountie. you can make it from scratch if you feel your up to it.

Once again the bounties that are up are only for a start. They are by no means the only ones that will stay. We are working hard at getting this up and going and wanted something to show a start.

Okay, I guess I need to re-express my vision, or scope again to keep things on track.

Initial Bounties: They are a starting point, to hopefully make describing bounties an easier process. Yes, some are very important. Some are there to be placeholders until we get other efforts co-ordinated.

In essence the initial set of bounties are a framework to be modelled for upcoming bounties. The TCP bounty is OPEN with the basic rules and donation button on it's own page.

3 words: morphos team bounties!

What we need in Bounties?

Hummm...


1) TCP/IP Stack


2) GTK porting

(without GTK we couldn't port any GUI based *NIX program, and Firefox is included in the number of GUI based programs)


3) A decent browser (see also my point nr. 2)

---- These first three are most important ----

Then,


4) Working Gigaethernet (hope it will be in 1.5)


5) Working Firewire


6) New Video Drivers supporting TV output and double monitor also


7) Videotoaster II PCI-Card Drivers

Honey? We need it disperately!


6) I agree with Targhan. VirtualDub is a beautiful piece of program.

It is not certainly a program which is strictly necessary but it will improve respect in MOS of users from other OSes.

Be careful, GTK porting is in the AROS bounty section, so we don't need to put it here as It has already begin.

For the web browser project, they are three ways:
- we want to port FireFox and first we need to improve the posix compatibility and a GTK wrapper. We will have a very fat and slow browser. This way, we may port many other applications.
- we want a khtml solution, and then we match the AWeb team project goals, so we may boost it a little. We can use webcore/khtml (there is a gtk port too like firefox).
- we want a from scratch solution like Paihia and we must pay for it and wait for a complete development. It can take months and a year to reach ibrowse or aweb current specifications...

But be aware that from my point of vue, the choice must not be a user choice but a coder choice.
People know firefox because they use it on their windows or linux, great. But konqueror or safari are really good too (faster and lighter). And the must important is the amount of work for each solution.
A firefox port is possible if we make wrappers and porting tools but It'll never be an amiga application. It's a problem because the browser should be a part of ambient like in windows.
The khtml solution within aweb is easier to release and It's a great web engine. To a coder point of view It's far more realistic... The code is well structured and under oriented object paradigm. Amizilla code is hum a big mess according to me and all that have seen this ugly code.

Amizilla has already 10000$ and no results. Put 10000$ on khtml for AWeb and you will see soon a good browser. But the precondition must be that the team should count at least 10 members to get the money. Everybody wants the money for themself and It's why this bounty may have an opposite effect that the one expected...

[ Edited by tetuzo on 2005/6/23 2:11 ]