@@ -1,6 +1,6 @@
11+++
22title = "Submit a Proposal"
3−date = "2022-10-26"
3+date = "2023-01-04"
44weight = 1
55description = "A comprehensive guide to creating a grant proposal"
66+++
@@ -11,9 +11,9 @@ We have a track record of funding many different kinds of different projects: ne
1111
1212Ready to get started? Here's how the process works:
1313
14−1. [Create your proposal](#create-your-proposal) as a group on Urbit
15−2. Submit your proposal using [this form](https://airtable.com/shrCi54rEDxgSZr3z)
16−3. Obtain [approval](#community-approval) from a member of our community and finalize your proposal
14+1. Submit your proposal using [this form](https://airtable.com/shrCi54rEDxgSZr3z)
15+2. Obtain [approval](#approval-by-the-foundation) from the Urbit Foundation and find a member of our community to champion your proposal
16+3. When your proposal is approved the Urbit Foundation and you will start looking for a suitable [champion](#looking-for-a-champion)
17174. Sign our [grant agreement](#paperwork)
18185. [Submit invoices](#getting-paid) after obtaining community signoff
1919
@@ -21,21 +21,6 @@ Ready to get started? Here's how the process works:
2121
2222Submitting a proposal starts by clearly articulating your idea and the value it will bring to the Urbit network. Getting the Urbit Foundation's signoff requires [approval from an established member of our community](#community-approval) and a compelling reason for receiving the requested amount of funding.
2323
24−### Create a group
25−
26−The first step is to create a group in Landscape's Groups app — this will be installed by default on your ship. If you don't have a ship running, check out our [Getting Started](https://urbit.org/getting-started) guide.
27−
28−Your group should:
29−
30−- Be **named** after your proposal
31−- Be **public** so our community can join
32−- Contain **a notebook** called `proposal`
33−- Contain **a chat channel** called `discussion`
34−
35−You'll write your proposal in markdown into the notebook, and engage with community members that would approve your proposal in the discussion channel.
36−
37−After writing up your proposal, [fill out this form](https://airtable.com/shrCi54rEDxgSZr3z), including the name of your group. The group name can be found in the URL of your browser. For example, in the URL `https://your.ship.domain/apps/landscape/~landscape/ship/~wolref-podlex/foundation` the group name is `~wolref-podlex/foundation`.
38−
3924### Elements of a proposal
4025
4126Good proposals all include the following:
@@ -55,6 +40,8 @@ Here are some examples of exceptional proposals for reference:
5540- [%pony](https://urbit.org/grants/pony-bounty) contains detailed thinking of current affordances of existing software if trying to build analogs to the traditional software stack
5641- [App Store](https://urbit.org/grants/app-store) blends the above with a nearly ideal balance of user stories mapped to milestones for clarity of completion, initial architectural thinking, and thinking around unique affordances and challenges of building on a distributed p2p system
5742
43+After writing up your proposal, [fill out this form](https://airtable.com/shrCi54rEDxgSZr3z) to submit your idea to the Foundation.
44+
5845### Funding
5946
6047The Urbit Foundation will provide funding of up to five stars for any one grant.
@@ -74,19 +61,11 @@ The intent of this policy is to:
7461
7562We try to use this rule in good faith. Reasonable delays due to unforseen life circumstances or project complexity will be tolerated, so long as the contributor is communicative with their champion and/or the Urbit Foundation. In these cases we'll encourage the contributor to modify the timelines and/or scope of their proposals to accommodate new information.
7663
77−## Community approval
78−
79−Your proposal will be considered approved when an established member of our community decides to _champion_ it. Only those that have made substantial past contributions to the project, generally through their own grants, are eligible to provide such a seal of approval.
80−
81−Approval from the community goes beyond simply clearing the project for funding. The community member that approves your project, called the _Champion_, will meet with you regularly to provide mentorship and support, help onboard you to the rest of the community, and ultimately be responsible for approving your work.
82−
83−### How it works
84−
85−After creating your group and [submitting it](https://airtable.com/shrCi54rEDxgSZr3z), the Urbit Foundation team will post your group to the community members that are approved for Championing proposals.
86−
87−The contents of your submission will be available to prospective champions, and if they're interested, they'll join your group and dive into the details with you (that's why that **discussion channel** is important).
64+### Approval by the Foundation
65+The Grants team of the Urbit Foundation looks at Grants on a bi-weekly basis. After they have decided on the grant they will inform you whether it is approved, rejected or needs some adjustments. In the latter case someone of the grants team will help you finetune your proposal so it can be reconsidered in the next round.
8866
89−When someone is sufficiently interested, they'll say so and ask to champion your project. If multiple people are interested in championing, you'll need to choose who to go with! This is, in our view, a good problem to have.
67+### Looking for a Champion
68+Finding a suitable champion is important for the success of your grant. Therefore we ask you to stay on the look-out for someone on the network who is capable to champion your proposal. The Foundation will assist you in finding a good champion.
9069
9170### Working with your Champion
9271
@@ -97,18 +76,18 @@ Here are some guidelines for how to engage with your champion:
9776- **Meet regularly:** Those that can champion projects are chosen for their past contributions. This means that they're able to provide hands-on support. This structure works best if you set up a regular check-in, either once a week or every other week. If nothing else, having an accountability buddy is really helpful.
9877- **Stay in touch:** Leverage the Urbit network for keeping in touch about your project. Don't hesitate to ask questions! The `[battery payload]` group (~dister-dozzod-lapdeg/battery-payload) is a great place to hang out with other developers, ask questions, and share your experiences.
9978- **Ask for connections:** Champions are well-connected throughout the network and know who's who. If you need support in a particular area that is beyond your Champion's expertise, they should be able to put you in touch with someone that can help.
100−- **Get your work reviewed:** Part of your Champion's job is to review your work and get others' eyes on it as well. Let them know when you need something reviewed by making a post in your proposal groups. Particularly, this is required for getting review and signoff that you have completed a milestone, but can be helpful for other complex asks as well.
79+- **Get your work reviewed:** Part of your Champion's job is to review your work and get others' eyes on it as well. Let them know when you need something reviewed. Particularly, this is required for getting review and signoff that you have completed a milestone, but can be helpful for other complex asks as well.
10180
10281If your Champion becomes unresponsive or is unhelpful, let someone at the Urbit Foundation know and we'll take care of it.
10382
10483## Paperwork
10584
106−After your proposal is Championed the Urbit Foundation will need to get a **signed contributor agreement** and **collect a small amount of personal information** from you as part of our KYC process.
85+After your proposal is approved and Championed, it will be added to this website, and the Urbit Foundation will need to get a **signed contributor agreement** and **collect a small amount of personal information** from you as part of our KYC process.
10786
10887The Urbit Foundation must comply with international law when distributing address space. We try to keep this process as minimal as we can, but there's no way to avoid it entirely without legally jeopardizing the Foundation's operations.
10988
11089## Getting Paid
11190
112−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 your proposal 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.
91+After you've finished your work on a given milestone, you will need to get signoff from your champion. To do this, you'll want to contact them to share the details of the milestone completed, any relevant instructions, github repos, or app download links, and solicit review from your champion. They can submit their approval by contacting `~marfun-pacpet`, at which point you are ready to [submit an invoice](https://airtable.com/shrXXCs1uaxtNSBcg). Once the Urbit Foundation receives approval from your champion and an invoice for the amount agreed upon in your grant or milestone, the Foundation will pay your star allocation to the Ethereum address you have provided.
11392
114−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.
93+We approve and issue payments within 30 days of invoice receipt and approval, although often payment is made more quickly. If you have any questions regarding getting paid or submitting an invoice, please contact `~marfun-pacpet` for assistance.