QA Pre-flight Checklist

[Draeieg]

These items should all be checked regularly to confirm everything is working as intended

Assigning Bounties

• /assign is the command that anybody can write to be assigned by the bot.
• If a new contributor writes a comment, the bot should give a small tutorial as a response. For example:

  • Please comment "/assign" to be assigned the bounty.

Unassigning Bounties

• When disqualified for the bounty, the bounty should be released back into the DevPool
• The bot should also leave a comment notifying the Bounty Hunter that they have been disqualified so that they know it is intentional.
• The unassign should measure the amount of time elapsed without any activity on the bounty (no comments or commits.) If activity stops for over one week, the bounty attempt is probably finished. In this case, regardless if its a Time: <1 Day bounty or a Time: <1 Month bounty, the bot should follow up every 4 days (configurable) asking for an update, particularly when there are no commit/comment updates from the assignee. The bot should unassign after 7 days (configurable.)
• If the assignee delegated the bounty to another hunter, they technically should be reporting to us so the rules are still valid. If they want to remove themselves as a bottle neck then we can manually change the assignee

Setting Prices for Bounties

• The script currently has a small table in it that essentially multiplies

  (base rate $) * (priority score) * (time estimate score.)
  

• If a Bounty Master sets any labels (profitability and/or time) then the bot is able to determine a price for the bounty.

Registering wallet addresses and associating it to each GitHub username

• The Bounty Hunter should be able to set their wallet address with the following command:

  • /wallet pavlovcik.eth

• If a user is assigned to an issue, the bot should immediately check if the author has a registered address. If they do not, then it should comment with instructions; something like

  • @user your payment wallet address is not currently registered. Please register your payment wallet address by commenting your address in the following format "/wallet ubq.eth" or "/wallet 0xefC0e701A824943b469a694aC564Aa1efF7Ab7dd" this wallet address will be used to receive payment upon the successful completion of this bounty.

    • If the bounty hunter registers their payment address as ubq.eth or 0xefC0e701A824943b469a694aC564Aa1efF7Ab7dd (they misunderstand the example) throw an error as a comment and say something like:

    • Failed to register your wallet address. You must include the address to your wallet, not ubq.eth or 0xefC0e701A824943b469a694aC564Aa1efF7Ab7dd

• If the user successfully registers their wallet address, the bot should provide a confirmation:

  • @user's payment wallet address is now set to pavlovcik.eth.

Paying Bounties

• Please see the code here to learn how we generate payment permits.
• The bot will need to know the bounty hunter's address to generate a permit.
• When 1. the bounty is complete and 2. the bot has the user's wallet address, then it will generate the permit and post a link.
• Bot posts a link to our "DevPool Claims" (view and claim PERMIT) interface.

• [ CLAIM 1 DAI ]

Commands

All commands not mentioned should also be tested