e9aa1b9 · urbit.org · git.iko.soy

git.iko.soy/urbit.org

Merge pull request #1866 from urbit/thelifeandtimes-grants-updates

Thelifeandtimes grants updates

commite9aa1b9be5e295c7d427d5dcfaea28787aec3aee author~sarlev-sarsen <tlatfcp@protonmail.com> dateThu 3 Nov 2022, 15:09 (4 years ago) parent71de16d f680e27

3 files changed+41−26

compare with master

unifiedsplit

content/apprenticeships.md+16−10 content/bounties.md+15−7 content/proposals.md+10−9

content/apprenticeships.md+16−10

@@ -1,39 +1,45 @@

11+++

22title = "Become an Apprentice"

3−date = "2022-03-27"

3+date = "2022-10-26"

44weight = 1

55description = "Everything you need to know about applying for an apprenticeship"

66+++

88Apprenticeships are practical learning opportunities for new Urbit developers provided by experienced members of the Urbit development community. As an apprentice, you'll have the opportunity to:

10−- Learn from an expert Urbit engineer

11−- Make real contributions to the project, and

10+- Learn from an experienced Urbit contributor

11+- Make helpful contributions to an active project, and

1212- Earn address space for learning

1313

1414Becoming an apprentice is easily one of the best ways to level up your skills, and perhaps even land a job.

1515

1616## Get started

1717

18−Apprenticeships are for those that are new to Urbit development (or an area of it), but not new to programming. Nearly all apprenticeships involve some degree of Hoon work, so you should make sure that you've completed [Hoon School](/docs/hoon/hoon-school/intro) and the [Gall Guide](/docs/userspace/gall-guide/intro) prior to signing up.

18+Apprenticeships are for those that are new to Urbit development (or an area of it), and would like to find their grounding by working on a pre-existing codebase and problem set. Nearly all apprenticeships involve some degree of Hoon work, so you should make sure that you've completed [Hoon School](https://developers.urbit.org/guides/core/hoon-school) and [App School](https://developers.urbit.org/guides/core/app-school/intro) in either their asychronous or [cohort formats](https://developers.urbit.org/courses) prior to signing up.

1919

2020There are two ways to sign up for an apprenticeship:

2121

22221. [Apply for an open apprenticeship](/grants?program=apprenticeship&open=true&wip=false&completed=false#view-grants)

23232. [Sign up to be matched to a mentor](https://airtable.com/shrUZQpHqRtudHhAx)

2424

25−Apprenticeships are sometimes posted on the site to be claimed, but more often than not they emerge out of a conversation between a mentor and an apprentice. This is because mentors are generally busy engineering, and while they know many things that need to be done, getting those ideas into writing is difficult.

25+Apprenticeships are sometimes posted on the site to be claimed, but more often than not they emerge out of a conversation between a mentor and an enthusiastic potential apprentice. This is because mentors are generally busy engineering, and while they know many things that need to be done, getting those ideas into writing is difficult.

2626

27−When you [sign up to be matched](https://airtable.com/shrUZQpHqRtudHhAx), the Urbit Foundation will review your application, pass it around to available mentors, and more often than not a call will get scheduled and an apprenticeship started.

27+When you [sign up to be matched](https://airtable.com/shrUZQpHqRtudHhAx), the Urbit Foundation will review your application, pass it around to available mentors, and more often than not a call will get scheduled with the lead for a project that may be a good fit.

2828

2929## How it works

3030

31−Once a mentor has written up an apprenticeship, approved an apprentice, and all parties have signed a contract with the Urbit Foundation, work can proceed.

31+Once a mentor has written up an apprenticeship, and approved an apprentice, The Urbit Foundation will perform a quick KYC step and send contracts to all parties for signing. Once those contracts are executed, work can proceed.

3232

33−Mentors and apprentices work together by having weekly pairing sessions and maintaining an open line of communication over Urbit. It's expected that mentors put at least two hours per week into supporting their apprentice.

33+The mentor will host a group with a chat and notebook where ongoing asychronous discussions can occur, and long-form content can be shared.

3434

35−When a mentor has signed off on the apprentice's work, the mentor will notify the Urbit Foundation of completion and the apprentice will invoice the UF for payment.

35+Mentors and apprentices work together by having weekly pairing sessions and maintaining an open line of communication over Urbit. It's expected that mentors put at least two hours per week into supporting their apprentice.

3636

3737## Funding

3838

39−Apprenticeships pay 1 star upon the sucessful completion of the apprenticeship, for an apprenticeship of a duration of up to three months. Upon completion of your apprenticeship, please [submit an invoice here](https://airtable.com/shrXXCs1uaxtNSBcg).

39+Apprenticeships pay 1 star upon the sucessful completion of the apprenticeship, for an apprenticeship of a duration of up to three months.

40+

41+## Getting Paid

42+

43+When an apprentice has completed the scope of their grant, they will create a detailed writeup of the work completed and their learnings, post it in the Apprenticeship notebook, and get the approval of their mentor. After recieving this approval from your mentor, please [submit an invoice here](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.

44+

45+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.

content/bounties.md+15−7

@@ -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+++

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).

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

content/proposals.md+10−9

@@ -1,6 +1,6 @@

11+++

22title = "Submit a Proposal"

3−date = "2022-01-03"

3+date = "2022-10-26"

44weight = 1

55description = "A comprehensive guide to creating a grant proposal"

66+++

@@ -50,9 +50,10 @@ It's recommended to break your project into _milestones_, each of which must hav

5050

5151Here are some examples of exceptional proposals for reference:

5252

53−- [Azimuth CLI](https://urbit.org/grants/azimuth-cli)

54−- [Pokur: Texas Holdem on Urbit](https://urbit.org/grants/pokur)

55−- [Urbit Speech Recognition](https://urbit.org/grants/speech-recognition)

53+- [Urbit Forms](https://urbit.org/grants/urbit-forms) has great demonstration of thinking around technical architecture

54+- [Bitcoin Lightning Development](https://urbit.org/grants/lightning-development) shows well defined user stories and future development opportunities that can inspire potential collaborators

55+- [%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

56+- [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

5657

5758### Funding

5859

@@ -60,11 +61,11 @@ The Urbit Foundation will provide funding of up to five stars for any one grant.

6061

6162Our formula for determining how much to value a particular grant is a function of time spent on the project, value to the Urbit universe, and track record of the contributor (either via past work within the grants program, or a relevant external background).

6263

63−If you're looking for more funding for a project that you're planning on devoting 100% of your full-time work to, you might instead consider [The Combine](https://the-combine.org).

64+Further funding may be available for continued development pending the successful completion of your grant. Additionally, contributors of exceptionally well completed grant proposals become eligible to mentor apprentices which can support continued development of their application for maintenence and feature additions.

6465

6566### Abandonment

6667

67−A proposal is considered abandoned when a milestone is more than a month behind schedule. When a proposal is considered abandoned, the Urbit Foundation may choose to compensate the work differently upon completion, or not at all.

68+A proposal is considered abandoned when a milestone is more than a month behind schedule and preemptive action is not taken to inform The Urbit Foundation of an adjusted timeline that has been approved by your Champion. When a proposal is considered abandoned, the Urbit Foundation may choose to compensate the work differently upon completion, or not at all.

6869

6970The intent of this policy is to:

7071

@@ -94,9 +95,9 @@ Your champion is invested in the success of your project — if they success

9495Here are some guidelines for how to engage with your champion:

9596

9697- **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.

97−- **Stay in touch:** Leverage the Urbit network for keeping in touch about your project. Don't hesitate to ask questions!

98+- **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.

9899- **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.

99−- **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.

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.

100101

101102If your Champion becomes unresponsive or is unhelpful, let someone at the Urbit Foundation know and we'll take care of it.

102103

@@ -108,6 +109,6 @@ The Urbit Foundation must comply with international law when distributing addres

108109

109110## Getting Paid

110111

111−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 recievd for the amount agreed upon in your grant or milestone, the Foundation will pay your star allocation to the Ethereum address you have provided.

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.

112113

113114We 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.