Replies: 2 comments 1 reply
-
|
In addition to the points we discussed in Discord, I was wondering how we might include some kind of "immutability provisions" in the Issues with bounties tied to them. If I'm midway through working on an issue and it undergoes feature creep, it could be harder for me to prove I've completed the work. Could we hash the issue at the time the bounty is put on it to ensure it doesn't change? Immutability provisions on contracts I've done in the past made my contractor's happy to know up front EXACTLY where the finish line is. Frequent complaint is moving target requirements. Would be good to make a "feature creep resistant platform" |
Beta Was this translation helpful? Give feedback.
-
|
GitHub actually keeps the history of an issue/discussion/comment.
Wait.... this is public, ins't it? Not just for the author... And I just noticed that you can also delete revisions: Putting the version at the time of bounty creation on IPFS could be worth investing some time for sure. |
Beta Was this translation helpful? Give feedback.
-
|
Related: #114 |
Beta Was this translation helpful? Give feedback.
-
Discussion all about how we prevent things from going wrong on the OctoBay platform, and what we do to make things right when they do go wrong.
Think like someone who's trying to scam the system. Penetration testing for business models.
Beta Was this translation helpful? Give feedback.
All reactions