[WFC Draft] Bounty Standards

@repighost I totally agree with you and I was hoping that OGTracker and OpenGov.Watch could try to connect and combine their efforts into one (along with @Saxemberg) - they have very well documented and identified the checklist items needed for projects to report post-funding. They also have the examples and lists of successful proposals that had a high chance of approval and funding.

If those items can be included HERE with this initiative led by Tommi, it will potentially provide the required items that can be required and defined in this proposal when applying for funding and the minimum requirements for post funding follow-ups that OGTracker has been providing as a service.

We can even create and base a point reputation system that will make it easier to identify teams or people that are strong contributors and consistently add value through their proposals - streamlining the overall process.

Thanks
Peter

thx for all the comments everyone. We got 48 comments on the HackMD! Crazy!

We are integrating them today and tomorrow. We will post the WFC on-chain on Monday.

Please submit your feedbacks by the end of Sunday.

3 Likes

The “Bounty Compliance Standards 1.0” have been submitted on the Wish-For-Change-Track: Bounty Compliance Standards 1.0

Thank you all for your feedback. We either integrated it or tried to comment and reflect on it in the “Appendix” section.

The general direction of the feedback led us to simplify many parts and give bounties more choice in how to implement the requirements, while still focusing on audibility and raising the bar.

The proposal is now up for vote and we tagged it “1.0” to communicate that it can be superseded by better versions in the future.