@@ -1,13 +1,13 @@
11+++
22title = "Guide to Bounties"
3−date = "2022-02-16"
3+date = "2022-10-26"
44weight = 1
55description = "A guide to posting and claiming bounties"
66+++
77
88Bounties are opportunities to do work on Urbit in exchange for address space or other funding. Bounties can be provided by companies, DAOs or individuals ("benefactors") in the Urbit universe. To the extent that they benefit the rest of the universe, the Urbit Foundation will [chip in on funding](#funding).
99
10−For **workers**, bounties offer substantial funding opportunities and, like [apprenticeships](/grants/apprenticeships), are a good way to get hired by other organizations. Learn how to [work on a bounty here](#work-on-a-bounty).
10+For **workers**, bounties offer substantial funding opportunities and, compared to [apprenticeships](/grants/apprenticeships), are a way to take on larger challenges in a more autonomous manner. Learn how to [work on a bounty here](#work-on-a-bounty).
1111
1212For **benefactors**, bounties allow you to scale your workforce through the Urbit community, get critical tools built, or just fund cool projects that you want to see exist. Learn how to [post a bounty here](#post-a-bounty).
1313
@@ -17,29 +17,37 @@ You can see [open bounties here](/grants?program=bounty&open=true&wip=false&comp
1717
1818### How it works
1919
20−After applying, the Urbit Foundation will circulate the details of your application to the benefactor and schedule a follow-up interview should your application be accepted — think of it like a job application.
20+After applying, the Urbit Foundation will circulate the details of your application to the benefactor and schedule a follow-up interview to see if you would be a good fit for the project. Should your application be accepted, you will undergo a quick KYC process and recieve a contract for signature. Some bounties may also entail additional direct compensation from the benefactor for which the Urbit Foundation is not responsible for managing; please discuss these parameters directly with your Champion.
2121
2222The benefactor of the bounty is ultimately responsible for signing off on completed work. They'll also be the primary point of contact while work is underway, although the Urbit Foundation may assign personnel to assist on bounties that it is particularly invested in.
2323
2424Benefactors are vetted by the Urbit Foundation as trustworthy to ensure their ability to fund the work that they post. The Urbit Foundation also collaborates heavily with benefactors to ensure that the bounty is [well-specified](#well-specified-bounties), which ensures that your project is both properly scoped and technically viable.
2525
26+### Getting Paid
27+
28+After you've finished your work on a given milestone, you will need to get signoff from your Champion. To do this, make a notebook post in the Champion's designated group with the details of the milestone completed, any relevant instructions, github repos, or app download links, and solicit review from your champion. Their reply of `approved` in the notebook post comments will constitute signoff and you'll need a link to that milestone post when you [submit an invoice](https://airtable.com/shrXXCs1uaxtNSBcg). Upon successful review of this notebook post by the Urbit Foundation and an invoice recieved for the amount agreed upon in your grant or milestone, the Foundation will pay your star allocation to the Ethereum address you have provided.
29+
30+We approve and issue payments within 30 days of invoice receipt and approval, although often payment is made more quickly as transactions are batched with other grantees who have recently completed milestones. If you are having any issues accepting stars through [Bridge](https://bridge.urbit.org) please contact `~taller-ravnut` for assistance.
31+
2632## Post a Bounty
2733
28−To get started with a new bounty, [submit it via this form](https://airtable.com/shr6ky4yshlhhqSm0).
34+To get started posting a new bounty, [submit it via this form](https://airtable.com/shr6ky4yshlhhqSm0).
35+
36+We at the Urbit Foundation will work with you to ensure that all bounties have [clear specifications](#well-specified-bounties) — this ensures that they get what you pay for. If your bounty submission is missing details or could be otherwise improved, we'll provide that feedback and work with you to refine your bounty.
2937
30−We at the Urbit Foundation ensure that all bounties have [clear specifications](#well-specified-bounties) — this ensures that they get what you pay for. If your bounty submission is missing details or could be otherwise improved, we'll provide that feedback and work with you to refine your bounty.
38+You will also be required to host an Urbit group within which there is a chat channel for discussion around the scoping and execution of the bounty, and a notebook for the final specification as well as contributor reports of milestone completion.
3139
3240### Well-specified Bounties
3341
3442A well-specified bounty generally has these elements:
3543
3644- **Overview**: A clear description of what the worker will do to complete this bounty. It's a good idea to include a problem statement or rationale for the work.
37−- **Project Requirements**: An articulation of what constitutes complete work. User stories, Figma designs, interface specifications, and other technical constraints are all examples of requirements.
45+- **Project Requirements**: An articulation of what constitutes complete work. User stories, Figma designs, interface specifications, and other technical constraints are all examples of requirements. It is recommended to reference any specific requirements — such as key user stories — on a milestone level to ensure clarity in which requirements need to be met at each stage of the project.
3846- **Worker Requirements**: A description of the skills and/or qualifications required of a prospective worker. Technologies or skills known, years of experience, work schedule (e.g. time availability), and demonstrable accomplishments are all examples of this.
3947- **Milestones**: Logical segments of work that can be considered done on their own. Breaking the project up into smaller pieces will help a new worker pick up the work should that be necessary, keeps the worker motivated with incremental achievement and remuneration, and is generally a sign of a clear specification. Milestones don't always make sense; sometimes there's only one.
4048- **Timeline**: If you're trying hit a certain deadline, make sure to specify absolute dates on the milestones. Otherwise, use relative dates (e.g. _two months_) to give the worker an idea of how long each milestone will take. This helps form an agreement between benefactor and worker on volume of work, and grounds to seek other arrangements should schedules be missed.
4149
42−The more detail in the bounty's specification, the better the results.
50+The more detail in the bounty's specification, the better the results and the smoother your working relationship will be with a contributor. Once a contributor has been selected, parameters such as absolute dates or other open ended questions will be updated prior to contract to ensure there are clear expectations for all parties involved
4351
4452### Funding
4553