Okay, I guess we should start a new thread for defining the first set of bounties together.

To start with the three (IMHO) easier ones:

To those who brought these bounty ideas up: Are there any specific objectives regarding AmiTCP and SFSSalv - or "just" a 1:1 port?

How could we define a proof for SFSSalv to work correctly?

Regarding AmiTCP: Would you consider it sufficient as an objective that it works with Voyager, Microdot2 and e.g. AmiTradeCenter?

And how about a web browser - what do you consider the minimum (realistic) objectives: javascript, css, ...?

I don't get what is involved with the amitcp one.

Why a AmiTCP 3 port as AmitTCP4 native + integrated in MorphOS (GUI, prefs, ...) is planned for MorphOS 1.5 ?

Instead, the goalcould be to provide an automatic installer + gui / prefs for Amitcp 3 on the Pegasos (Genesis alike) ?


[ Edited by cdfr on 2005/6/16 12:14 ]

Basic: Create a SFS Salv like utility for MorphOS with a simple GUI.

Long: Application should be PPC, easy for users to setup and use. The application should be able to use another drive or partition to recover deleted files and salvaged files from partitions with read errors, mistakenly quick formated drives ect. Application is not expected to work miracles but should have the basic functions of the Amiga application SFS_Salv.
Licensing: LGPL. BSD-styled, to allow others to add to this work.

Donations: [Soon Accepting]

Okay, I have clarified some for the tcp/ip thing. It is native ppc tcp/ip stack with some kind of gui that will work out of the box. it must have dhcp support. I have changed it from a port to _whatever_ a programmer thinks he or she can do to get a native stack running, and am tentivly calling it ezTCP.

I've moved $30 from the general fund to this fund, and have opened up the donation button for it on it's page. Am adding some details now. I'll leave it up to you guys to "publicize it" either via news or regular forums.

Targhan

P.S.: The money for the other bounty, Senex, does not appear in my account. Check with the person who sent the 150 to me. If they don't have it, we'll contact PayPal to find out what happened. (I didn't accept because it would have charged money to that 150.00 at 1.9% and that wouldn't be fair).

Something like this http://pingu.ii.uj.edu.pl/~armo/morphos/SfsRecoverTool ??? :)
But use at your own risk ...

I'll let the others look at it, but I do want to say that I love your TDolphin MPlayer GUI!

I could still use some help on the others that are still missing a guide line. PM myself or Targhan if you want to help out!

If this SFS Recover-Tool works without killing your HD, then this bounty is done. Or what do you think guys?

This is just my personal opinion, but to me the #1 bounty over all else is to get a decent web browser on morphos...whatever it takes. I'd make a big contribution to that and my own view is that all money should be concentrated on that as a primary goal above all else.

@ThePlayer

It works and it doesnt kill your hd but its GUI is unfinished... Other than that it is very promising. Only if the author could polish it.

Quote:

Is it MOS native?

Yes, it is native.

Quote:

Thanks
.... and wait for new version ... soon

@armo

How about a radio button, drop box, or some other gadget for window size when not using fullscreen, giving the arguements of "-xy 99" where 99 is a number. ( "-xy 1.5" for one and a half times the normal video size )

Nice to see the Bounties are open - great work, guys, thanks!

Seems the only description still open for now is the browser one. So what do those of you suggesting this bounty expect from it, feature-wise - could you please help to define this bounty?

Personally I just hope on the AmiZilla project, so I can't really be of help here - but what do you expect from such an alternative, yet modern browser as minimum requirements?

HTML 4
XML 1
XHTML 1.1
CSS 2
JavaScript 1.5 ...?

Hi Senex,

Well, before we open the browser bounty, I would very much like to co-ordinate something with the current amizilla effort. Amizilla currently, as a fund-raiser, lacks from not having enough outward activity. If we are to support that project, we *will* require regular project updates or reports, it's too large to just put a deadline on like other projects.

I'm also considering to open a second bounty for WWW later, an open ended one that can be ANY browser that supports modern specifications. (HTML 4, etc) That bounty will go to the first native project, and will also have it's OWN rules for donating.