4. Have a way for the original bounty creator to edit the title/description of the project. Allow anyone to view previous versions of the title/desc.
The problem is - why bounty creator only? Why not the rest of the users as well? How'd we decide which description is right? Voting?
Make it editable by all members, like a wiki. Everyone can see the edit history.
5. Have a comment thread for each bounty for others to ask questions, clarify, make suggestions to improve the bounty, propose/discuss solutions/implementations.
That'd be a huge piece of code unless I'd use some external toys. I thought of allowing to add a bitcointalk thread.
A linked bitcoin talk thread (or more than one) would be better than nothing.
9. Have weighted voting on who wins the bounty after a solution(s) is submitted. Have weighted voting where the bounty starter and people who contributed more BTC to the bounty have most of the say, but let other users of the site also have a small vote. Have a comment thread for each proposed solution to discuss it / clarify problems. Allow the person who submitted the solution to revise/re-submit, etc.
Kind of already implemented/discussed, just without the small votes and the last sentence.
Bounty hunters still need a way to revise/improve/resubmit their solution IMO.
10. Have a way to close bounties that are no longer wanted.
Again, who and how would decide that?
A voting system, along with some discretion by a site administrator/moderators, would take care of that.
What language is the site written in? I'd be happy to do a code review for you if you want to post/send a zip file with your code.
BTW, did you have a look at my messed up code?
I did. For the time being I mostly looked for possible security vulnerabilities, of which I didn't find anything obvious. As for stylistic/philosophical comments, I don't see a lot of need for that. I would have done a lot of things differently (OOP, class design, MVC design, separation of concerns), but since this was a learning project for you, that's ok.