Dework Docs

Bountied Issues with Github + Dework

A common use case in Dework is to use Github + Dework in tandem to work with engineering contributors. A core engineering team operates in Github and some issues are automatically synced to Dework. Then, these issues are "bountied" in Dework and engineering contributors can more easily work on them.
Let's see how this works!

1. Use the Dework integration to sync issues with a specific label

In Dework, you can easily sync a Space with one or more Github repos. Issues created in these repos will automatically create tasks in your Dework Space. To have more control over what tasks are synced, you can add labels to your issues and choose to only sync issues with these specific labels.
You can create a "bounty" label in Github and sync that label to Dework. Then, after adding that label to any Github issue, a task representing that issue will be automatically created in Dework!
More than just syncing the task metadata, we also sync assignees and PRs. Read more.

2. Create Bountied Issues in Dework

After setting up your workflow to sync relevant issues, tasks will be created in Dework. Then, like any normal task, you can take advantage of Dework’s contributors focused features to open these tasks to contributors:
  1. 1.
    🏰 Granularly control permissions to only allow certain contributors to work on these tasks.
  2. 2.
    💰 Add a bounty and the bountied issue will appear on Dework’s global bounty board.
  3. 3.
    💬 Use our Discord integration to automatically create threads to discuss these tasks in Discord.
  4. 4.
    💳 Pay all bounties through Dework, including batch paying with Gnosis Safe.
When a task is assigned in Dework, it will automatically be assigned to the same person in Github.

🦊 Case study: ShapeshiftDAO

Let’s take a quick look at how ShapeshiftDAO are leveraging these features to work with engineering contributors.

1. Syncing issues from 6 repos

Shapeshift have one Dework Space called Shapeshift Bounties that is synced to 6 different Github repos. From these repos, they decided to only sync issues with the following labels: bounty, needs bounty and low priority.

2. Adding bounties on Dework & opening tasks to certain roles

The first step in their workflow is to process all “needs bounty” tasks.
Step 1: 💰 Add a bounty in FOX token, pegged to USD.
Step 2: 🏰 Set permissions to determine what type of contributors should be able to work on these issues
Shapeshift are using two types of permissions:
  1. 1.
    Open to Applications: Anyone can apply to work on the bountied issues. Task reviewer decides who gets assigned.
  2. 2.
    Directly claimable by contributors with the trustedevcom role in Discord: Contributors with this role can assign themselves to bounties, without asking for permission. Shapeshift already trust them and hence are happy with letting them permissionlessly claim bounties.

3. Discussion in Discord

Once a contributor has been assigned to a task, details are discussed in Discord in the thread that was automatically created by our Discord integration.

4. Payment in Dework

After the work is done, only clicking one button is needed to pay out contributors. Bounties are paid through Dework directly, using our Gnosis Safe integration.