Some thoughts since then:
1) With devcoin.org and a forum coming, they do perhaps already offer a venue where basic bounties could be hosted/linked?
2) Actually starting the process with integral vetting requires people and skillsets - perhaps quite a few - certainly in providing any meaningful appraisal of code/tech prior to end product. Without it there could be a simple skew towards ideas rather than doable ideas because average users (like me) might not appreciate what's involved in fulfilling the bounty?
3) A means of automating that system (paying dvc) is an interesting idea. Would that be added to the recipients final bounty payment, or are you referring to different systems?
4) Tying that in to having a devtome account is another thing I hadn't even considered, not sure yet about relative pros/cons of that, because there's a potential risk that the people voting will be the least attuned to to the bounty skillset?
5) Less complicated is better, at least to begin with?
dalamar96: Bounties are paid out from generation devcoin like all other direct devcoin earnings.
Alright, I guess my thoughts count now since I am needed
(I'm just messing with ya!)1) Yes start simple, add functionality (that is what I am working towards right now)
2) The automated DVC I was talking about was how to add a receiver line automatically once an admin approves a bounty payout.
3) The input will be simple for proposing, I figured the vetting and voting will take care of itself through comments and the voting I am putting into place
4) I am not sure about the pros/cons yet for having to have a devtome account, I am just doing that because I don't want to have to make people sign up for the site I am creating, I am just using usernames that are in the account files.
5) The system I am creating could be moved to any site that is running on a LAMP server. It can be edited to work on IIS or WAMP if need be. But, it is hard coded at this time for my server and database layout. It is a prototype after all!
I wasn't looking to get a bounty for what I was working on and I don't want to take away from anyone else that is working on things like I have on the site. Everyone is welcome to use what is there and make suggestions and what not, but I can't warranty any of it! At least not yet!
Chad