Open question: should be make the bounty submitter the author of the posted article? This would then give you the possibility of being able to add, change and alter the bounty in any way that you would like. This possibility would also given to earlier bounties as long that we can locate and connect the submitter to an user profile within the system.
It's then really important that there are some few code lines including the PayPal code and some joomla mostags un-edited by all means.
I don't think this is a good idea. If a developer starts work on one of these they need to know that the criteria for receiving the bounty isn't going to change. Many of the projects listed would take a lot of time and effort. It would be a real deterrent if they knew someone could come in change the version requirement etc and make much of their current effort a waste of time.
Hi all,
oops!
I have to admit that I didn't think of what Gregg said. He's absolutely right.
If there's a suggestion on how to combine these two aspects without making it too tedious as a workflow, that would be great. If asked for a quick decision NOW, I would say... "Gregg's right - don't change it".
Regards,
Thomas
...and I don't think I'd like to see a bounty change for the worse (from my point of view) when I have put my money on it.
Bye
Cris
The reason for suggesting the possibility of being able to update the bounty is only to be able to clearify the content of the bounty and of course this shouldn't be used to change or alter the bounties original purpose. But, then again, all bounties has a supporting thread here in the forum and might be better to suggest updates there than updating the original bounty text.