MVP: Setup

[0x4007]

• 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 (assigned to @ubiquity-bounties)
  • 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 a (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.
  • I created a new idea to be more competitive with pricing epic(setup): Base Payment Rate as Function of Ether Price #80