My experience with it a few months ago had this exact issue - there is no standardisation of bounties whatsoever.
Initial work developing the API (10 hours of work, say) would be valued at 5000 credits but then after launch someone tweaking the color of a button might get set at 2000 credits.
Perhaps there needs to be a review process for tasks that go through a list of per-project moderators? Both for reducing cruft, keeping focus on the currently-important stuff, and to normalise bounties across the project's lifetime.
Alternatively, the bounties could be semi-invisible, instead with tasks assigned to various levels of difficulty and importance...
Comments
How will you prevent ownership from being diluted by intentional (or even unintentional) inflation of future bounties?
My experience with it a few months ago had this exact issue - there is no standardisation of bounties whatsoever.
Initial work developing the API (10 hours of work, say) would be valued at 5000 credits but then after launch someone tweaking the color of a button might get set at 2000 credits.
Perhaps there needs to be a review process for tasks that go through a list of per-project moderators? Both for reducing cruft, keeping focus on the currently-important stuff, and to normalise bounties across the project's lifetime.
Alternatively, the bounties could be semi-invisible, instead with tasks assigned to various levels of difficulty and importance...