First of all, thanks for everyone's responses to the new site. This is a second proposal based on your ideas. Please respond with what you think as well as please answer with your opinion on the possibilities section in its entirety. Please keep all related posts inside this thread. Thanks for your time.

If I missed anything or you got any new ideas, feel free to mention those too!

MorphBounties Proposal #2

Almost definitely:

1. There will be two ways (atleast at this point in time) to start up a bounty. #1: People suggest a program or concept they'd like to see and donate money towards it. #2: People suggest a specific program that they would like a specific author to port and donate money towards it.
2. A trusted community individual (maybe more than one person..) will serve as the treasurer. See the possibilities section for information regarding forms of money, although PayPal is preferred.
3. Donations will be allowed even after a bounty is fulfilled (these go straight to the author). Donations will not be stopped at any time. See the possibilities section for information regarding forms of money, although PayPal is preferred.
4. There will be an administration team to oversee all site operations and manage all bounties.
5. Anyone can donate to a bounty or a bounty's author.
6. There will be a designated public testing period (two weeks?) before donations are forwarded to the author.
7. All programs that result from bounties will be free for all of the public.

Possibilities:

1. Should we allow developers to suggest their own bounties? as well as required donation amount?
2. Should rules be fully defined? or should they be on a program by program basis?
3. Somewhat related to the previous question..should programs submitted be required to be open-source licenses (GPL/LGPL)? or should it be like the prior and possibly require this on a program by program basis?
4. Should projects be assigned to a single author (or group)? or should it be an open competition?
5. If projects are assigned should a person from the adminstration team be assigned to oversee the development?
6. Should there be deadlines? (There will definitely be deadlines if projects are assigned.)
7. Should we accept all forms of donations? not just PayPal, but also checks and money orders? Note that as these projects are international, checks and money orders may be difficult and might only be useful for donations and not for sending to the authors. Note that not requiring PayPal might force the treasurer to spend quite a bit of time managing the money.
8. Should we limit the number of concurrent bounties? possibly somewhere around five or six? This will also cause the creation of bounties to go through a "review" process before they are accepted.
9. For further donations after a bounty has been fulfilled, forwarding would be PayPal only; any other types of donations would be required to have the donator contact the author directly.

my responses to the possibilities:

1. I think this would lead to too much greed and would take the spirit out of the site.
2. I think the suggested program by program basis works the best, this way certain programs might require to be opensource while others might not be.
3. See #2.
4. Open competition promotes new authors, but might require some authors to do alot of work with little or no financial payoff. Assigned vs open has its positives and negatives, this could possibly be on a program by program basis as well.
5. If a project is assigned, this should be overseen on administration on open bounties only, not ones that target a specific author's specific program.
6. There should be deadlines on assigned bounties but not on open ones.
7. If we have a treasurer willing to spend the time, all donations should be accepted, however, PayPal is preferred.
8. This is another great idea mentioned on the forums, I think the limit should be at least five, perhaps six. Maybe a max of eight?
9. I think this is fine, PayPal is easy to forward, but forwarding money orders and checks that could easily go straight to the author is a waste of time.

1. There will be three ways - but only 2 was there It'd be nice if developers could offer to port something over for a fixed prize.
2. All right with me.
3. Where the extra money will go in case of already finished projects?
4. All right with me.
5. All right with me.
6. Very fine idea.
7. Excellent idea.

Possibilities:

1. Definitely yes.
2. I vote for being fully defined and uniform, with small exceptions maybe in complex cases.
3. GPL is a difficult question. A work which required money should be available for everyone? If yes, then GPL is fine, but we should consider something like the AROS license. (Ab)using GPL is just the hot topic of ANN.
4. Very good question. I suggest, that using the AROS approach (assign to single developer/group) is satisfactory. Open challenges should be exceptions only.
5. Why not? But it'd be better if just inquiries could be made whether the project stopped or is ongoing, instead of day to day monitoring, which can be frustrating for any developer.
6. Yes. But deadlines are always missed, so extending deadlines must be a possibility.
7. As it is best. I have little experience in that.
8. Definitely, concurrent bounties shouldn't be more than 2 IMHO, except for open challenges, where no limit is needed.