on master help sign in
fix links
commit421869b85a2c6326e42b4b52f0da224a16887449 authorJosh Lehman <josh@urbit.org> dateTue 15 Feb 2022, 09:44 (5 years ago) parent136bef6
2 files changed+26−88
content/apprenticeships.md+10−30 content/bounties.md+16−58
content/apprenticeships.md+10−30
@@ -5,55 +5,35 @@ weight = 1
55description = "Everything you need to know about applying for an apprenticeship"
66+++
77
8−Apprenticeships are practical learning opportunities for new Urbit developers
9−provided by experienced members of the Urbit development community. As an
10−apprentice, you'll have the opportunity to:
8+Apprenticeships 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:
119
1210- Learn from an expert Urbit engineer
1311- Make real contributions to the project, and
1412- Earn address space for learning
1513
16−Becoming an apprentice is easily one of the best ways to level up your skills,
17−and perhaps even land a job.
14+Becoming an apprentice is easily one of the best ways to level up your skills, and perhaps even land a job.
1815
1916## Get started
2017
21−Apprenticeships are for those that are new to Urbit development (or an area of
22−it), but not new to programming. Nearly all apprenticeships involve some degree
23−of Hoon work, so you should make sure that you've completed [Hoon
24−School](/docs/hoon/hoon-school/intro) and the [Gall
25−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), 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.
2619
2720There are two ways to sign up for an apprenticeship:
2821
29−1. [Apply for an open
30− apprenticeship](/grants?program=apprenticeship&open=true&wip=false&completed=false)
22+1. [Apply for an open apprenticeship](/grants?program=apprenticeship&open=true&wip=false&completed=false#view-grants)
31232. [Sign up to be matched to a mentor](https://airtable.com/shrUZQpHqRtudHhAx)
3224
33−Apprenticeships are sometimes posted on the site to be claimed, but more often
34−than not they emerge out of a conversation between a mentor and an apprentice.
35−This is because mentors are generally busy engineering, and while they know many
36−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 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.
3726
38−When you [sign up to be matched](https://airtable.com/shrUZQpHqRtudHhAx), the
39−Urbit Foundation will review your application, pass it around to available
40−mentors, and more often than not a call will get scheduled and an apprenticeship
41−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 and an apprenticeship started.
4228
4329## How it works
4430
45−Once a mentor has written up an apprenticeship, approved an apprentice, and all
46−parties have signed a contract with the Urbit Foundation, work can proceed.
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.
4732
48−Mentors and apprentices work together by having weekly pairing sessions and
49−maintaining an open line of communication over Urbit. It's expected that mentors
50−put at least two hours per week into supporting their apprentice.
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.
5134
52−When a mentor has signed off on the apprentice's work, the mentor will notify
53−the Urbit Foundation of completion and the apprentice will invoice the UF for
54−payment.
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.
5536
5637## Funding
5738
58−Apprenticeships pay a flat $8,000 in WSTR to the apprentice, and $2,000 WSTR to
59−the mentor.
39+Apprenticeships pay a flat $8,000 in WSTR to the apprentice, and $2,000 WSTR to the mentor.
content/bounties.md+16−58
@@ -5,86 +5,44 @@ weight = 1
55description = "A guide to posting and claiming bounties"
66+++
77
8−Bounties are opportunities to do work on Urbit in exchange for address space or
9−other funding. Bounties can be provided by companies, DAOs or individuals
10−("benefactors") in the Urbit universe. To the extent that they benefit the rest
11−of the universe, the Urbit Foundation will [chip in on funding](#funding).
8+Bounties 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).
129
13−For **workers**, bounties offer substantial funding opportunities and,
14−like [apprenticeships](/grants/apprenticeships), are a good way to get hired by
15−other organizations. Learn how to [work on a bounty here](#work-on-a-bounty).
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).
1611
17−For **benefactors**, bounties allow you to scale your workforce through via the
18−Urbit community, get critical tools built, or just fund cool projects that you
19−want to see exist. Learn how to [post a bounty here](#post-a-bounty)
12+For **benefactors**, bounties allow you to scale your workforce through via 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)
2013
2114## Work on a Bounty
2215
23−You can see [open bounties
24−here](/grants?program=bounty&open=true&wip=false&completed=false), which can
25−claimed by filling out the form on each individual bounty.
16+You can see [open bounties here](/grants?program=bounty&open=true&wip=false&completed=false#view-grants), which can claimed by filling out the form on each individual bounty.
2617
2718### How it works
2819
29−After applying, the Urbit Foundation will circulate the details of your
30−application to the benefactor and schedule a follow-up interview should your
31−application be accepted &mdash; 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 should your application be accepted &mdash; think of it like a job application.
3221
33−The benefactor of the bounty is ultimately responsible for signing off on
34−completed work. They'll also be the primary point of contact while work is
35−underway, although the Urbit Foundation may assign personnel to assist on
36−bounties that it is particularly invested in.
22+The 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.
3723
38−Benefactors are vetted by the Urbit Foundation as trustworthy to ensure their
39−ability to fund the work that they post. The Urbit Foundation also collaborates
40−heavily with benefactors to ensure that the bounty is
41−[well-specified](#well-specified-bounties), which ensures that your project is
42−both properly scoped and technically viable.
24+Benefactors 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.
4325
4426## Post a Bounty
4527
46−To get started with a new bounty, [submit it via this
47−form](https://airtable.com/shr6ky4yshlhhqSm0).
28+To get started with a new bounty, [submit it via this form](https://airtable.com/shr6ky4yshlhhqSm0).
4829
49−We at the Urbit Foundation ensure that all bounties have [clear
50−specifications](#well-specified-bounties) &mdash; this ensures that they get
51−what you pay for. If your bounty submission is missing details or could be
52−otherwise improved, we'll provide that feedback and work with you to refine your
53−bounty.
30+We at the Urbit Foundation ensure that all bounties have [clear specifications](#well-specified-bounties) &mdash; 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.
5431
5532### Well-specified Bounties
5633
5734A well-specified bounty generally has these elements:
5835
59−- **Overview**: A clear description of what the worker will do to complete this
60− bounty. It's a good idea to include a problem statement or rationale for the
61− work.
62−- **Project Requirements**: An articulation of what constitutes complete work. User
63− stories, Figma designs, interface specifications, and other technical
64− constraints are all examples of requirements.
65−- **Worker Requirements**: A description of the skills and/or qualifications
66− required of a prospective worker. Technologies or skills known, years of
67− experience, work schedule (e.g. time availability), and demonstrable
68− accomplishments are all examples of this.
69−- **Milestones**: Logical segments of work that can be considered done on their
70− own. Breaking the project up into smaller pieces will help a new worker pick
71− up the work should that be necessary, keeps the worker motivated with
72− incremental achievement and remuneration, and is generally a sign of a clear
73− specification. Milestones don't always make sense; sometimes there's only one.
74−- **Timeline**: If you're trying hit a certain deadline, make sure to specify
75− absolute dates on the milestones. Otherwise, use relative dates (e.g. _two
76− months_) to give the worker an idea of how long each milestone will take. This
77− helps form an agreement between benefactor and worker on volume of work, and
78− grounds to seek other arrangements should schedules be missed.
36+- **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.
38+- **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.
39+- **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.
40+- **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.
7941
8042The more detail in the bounty's specification, the better the results.
8143
8244### Funding
8345
84−You're free to fund your bounty with as much of your own capital as you'd like.
85−You can also request funding from the Urbit Foundation.
46+You're free to fund your bounty with as much of your own capital as you'd like. You can also request funding from the Urbit Foundation.
8647
87−We fund projects based on their benefit to the whole network. If your bounty is
88−for contributions to Urbit itself, or other technical infrastructure, we might
89−fund all of it. If the bounty is to build or contribute to your company's
90−product, we'll be open to funding less of it.
48+We fund projects based on their benefit to the whole network. If your bounty is for contributions to Urbit itself, or other technical infrastructure, we might fund all of it. If the bounty is to build or contribute to your company's product, we'll be open to funding less of it.