git.iko.soy/urbit.org
on master help sign in
Added milestones
66777e8Tyler Brown Cifu Shuster
content/community/grants-and-bounties/-smol-future-sustained-knowledge-sharing-and-marketing.md+54−1
compare with master
unifiedsplit
@@ -2,7 +2,7 @@
2title = "-=[smol future]=- Sustained Knowledge Sharing and Marketing"
2title = "-=[smol future]=- Sustained Knowledge Sharing and Marketing"
3date = 2021-01-15
3date = 2021-01-15
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Community"]
6grant_category = ["Community"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -45,4 +45,57 @@ Let's do this and change the world.
45
45
46
46
47
47
48+
49+## Milestones
50+
51+
52+### Initial Documentation: Beginner's Guide
53+1 stars
54+Publish a comprehensive guide on urbit.org wiki explaining how to run Urbit on a Raspberry Pi using recommended and tested hardware configurations. Walk the user through every step of of the process.
55+
56+
57+### Initial Marketing: Outreach + Messaging
58+1 stars
59+Research and outreach to engage existing Raspberry Pi users and key hardware manufacturers. Introduce the Urbit narrative into new communities, including memes/vibes.
60+
61+
62+### Sustained Documentation + Marketing: MAR
63+1 stars
64+A fire-and-forget approach will fail. To succeed and continually gain traction, both documentation (updated content) and marketing (new outreach/engagement/materials) must be sustained efforts.
65+
66+
67+### Sustained Documentation + Marketing: APR
68+1 stars
69+A fire-and-forget approach will fail. To succeed and continually gain traction, both documentation (updated content) and marketing (new outreach/engagement/materials) must be sustained efforts.
70+
71+
72+### Sustained Documentation+Marketing: MAY
73+1 stars
74+A fire-and-forget approach will fail. To succeed and continually gain traction, both documentation (updated content) and marketing (new outreach/engagement/materials) must be sustained efforts.
75+
76+
77+### Sustained Documentation + Marketing: JUN
78+1 stars
79+A fire-and-forget approach will fail. To succeed and continually gain traction, both documentation (updated content) and marketing (new outreach/engagement/materials) must be sustained efforts.
80+
81+
82+### Sustained Documentation + Marketing: JUL
83+1 stars
84+A fire-and-forget approach will fail. To succeed and continually gain traction, both documentation (updated content) and marketing (new outreach/engagement/materials) must be sustained efforts.
85+
86+
87+### Sustained Documentation + Marketing: AUG
88+1 stars
89+A fire-and-forget approach will fail. To succeed and continually gain traction, both documentation (updated content) and marketing (new outreach/engagement/materials) must be sustained efforts.
90+
91+
92+### Sustained Documentation + Marketing: SEP
93+1 stars
94+A fire-and-forget approach will fail. To succeed and continually gain traction, both documentation (updated content) and marketing (new outreach/engagement/materials) must be sustained efforts.
95+
96+
97+### Sustained Documentation + Marketing: OCT
98+1 stars
99+A fire-and-forget approach will fail. To succeed and continually gain traction, both documentation (updated content) and marketing (new outreach/engagement/materials) must be sustained efforts.
100+
48
101
content/community/grants-and-bounties/a-book-about-urbit.md+54−1
@@ -2,7 +2,7 @@
2title = "A book about Urbit"
2title = "A book about Urbit"
3date = 2020-07-23
3date = 2020-07-23
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Community"]
6grant_category = ["Community"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -29,4 +29,57 @@ I'm writing a book-length history of Urbit. I'll also write, in an Urbit-centric
29
29
30I'm a novelist and essayist who has written about tech, politics, and literature. My plan, so far, for any received stars, is to spawn planets for interesting individuals and communities who might like Urbit, and to research what might go into creating a hosted star-based community.
30I'm a novelist and essayist who has written about tech, politics, and literature. My plan, so far, for any received stars, is to spawn planets for interesting individuals and communities who might like Urbit, and to research what might go into creating a hosted star-based community.
31
31
32+
33+## Milestones
34+
35+
36+### First Chapter
37+1 stars
38+Ch1. Actually completed 10/21, not 10/29
39+
40+
41+### Second Chapter
42+1 stars
43+Ch2
44+
45+
46+### Third Chapter
47+1 stars
48+Ch3
49+
50+
51+### Fourth Chapter
52+1 stars
53+Ch4
54+
55+
56+### Fifth Chapter
57+1 stars
58+Ch5
59+
60+
61+### Sixth Chapter
62+1 stars
63+Ch6
64+
65+
66+### Seventh Chapter
67+1 stars
68+Ch7
69+
70+
71+### Eighth Chapter
72+1 stars
73+Ch8
74+
75+
76+### Ninth Chapter
77+1 stars
78+Ch9
79+
80+
81+### Tenth Chapter
82+3 stars
83+Ch10. Contract is for disbursal of 12 stars at 1 star per chapter until completion; if projected is completed in fewer than 12 chapters, then remaining stars (12 - x) are to be disbursed at completion
84+
32
85
content/community/grants-and-bounties/a-collaborative-web-mapping-system-for-urbit.md+14−1
@@ -2,7 +2,7 @@
2title = "A Collaborative Web Mapping System for Urbit"
2title = "A Collaborative Web Mapping System for Urbit"
3date = 2020-09-03
3date = 2020-09-03
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Other"]
6grant_category = ["App Dev: Other"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -83,4 +83,17 @@ I am a beef farmer and software engineer (geospatial web applications). I work
83
83
84~lomped-firser
84~lomped-firser
85
85
86+
87+## Milestones
88+
89+
90+### Stage 1
91+2 stars
92+A spatial store, spatial types, simple demo landscape app
93+
94+
95+### Stage 2
96+2 stars
97+A Portal Store and Collaboration System
98+
86
99
content/community/grants-and-bounties/analytics-script.md+8
@@ -43,4 +43,12 @@ The generator should accept a few parameters:
43- The Urbit Foundation will connect you with Tlon engineers for 1:1 support, should you need it
43- The Urbit Foundation will connect you with Tlon engineers for 1:1 support, should you need it
44- Code should be submitted as a pull request against https://github.com/urbit/urbit
44- Code should be submitted as a pull request against https://github.com/urbit/urbit
45- The generator shall be called `crunch` (we're open to better ideas)
45- The generator shall be called `crunch` (we're open to better ideas)
46+
47+## Milestones
48+
49+
50+### Work is complete
51+1 stars
52+The generator is submitted as a pull request to the Urbit repository, reviewed, and merged.
53+
46
54
content/community/grants-and-bounties/antechamber.md+13
@@ -87,4 +87,17 @@ Your solution to this bounty should include pull requests against these reposito
87You will work closely with the director of urbit.org on this project. This means that regular check-in calls will be held to discuss the project's progress. Additionally, the you are expected to provide regular status updates on the project to the Urbit community via twice-monthly updates on this bounty.
87You will work closely with the director of urbit.org on this project. This means that regular check-in calls will be held to discuss the project's progress. Additionally, the you are expected to provide regular status updates on the project to the Urbit community via twice-monthly updates on this bounty.
88
88
89The director will ensure that you have access to the necessary resources to complete this project. All prior work done on this project will be explained and made available to you, and should questions arise that require the expertise of engineers at Tlon, time will be made (schedules permitting) for your questions to be answered either in writing or over a call.
89The director will ensure that you have access to the necessary resources to complete this project. All prior work done on this project will be explained and made available to you, and should questions arise that require the expertise of engineers at Tlon, time will be made (schedules permitting) for your questions to be answered either in writing or over a call.
90+
91+## Milestones
92+
93+
94+### Part 1: Extend Bridge to Support Claims
95+2 stars
96+Pull requests to azimuth-js and bridge, as specified above, have been merged.
97+
98+
99+### Part 2: Create the senate-group-hook
100+2 stars
101+Pull requests against the antechamber repo mentioned above have been merged.
102+
90
103
content/community/grants-and-bounties/art-by-urbit.md+9−1
@@ -2,7 +2,7 @@
2title = "Art by Urbit"
2title = "Art by Urbit"
3date = 2020-08-27
3date = 2020-08-27
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Community"]
6grant_category = ["Community"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -21,4 +21,12 @@ For those already homesteading Urbit, part of the regular digest will be a pair
21I'm qualified to carry out this proposal as I have built a portfolio of prior Urbit-related art (available [here](https://twitter.com/nartesfasrum) ) and have prior experience building & deploying websites & social media promotional campaigns.
21I'm qualified to carry out this proposal as I have built a portfolio of prior Urbit-related art (available [here](https://twitter.com/nartesfasrum) ) and have prior experience building & deploying websites & social media promotional campaigns.
22
22
23
23
24+
25+## Milestones
26+
27+
28+### Six months of regular digests
29+1 stars
30+As described - six months of regular monthly Art by Urbit digests, posted to the Art by Urbit website & promoted on social media.
31+
24
32
content/community/grants-and-bounties/bart-train-tracker-landscape-tile.md+8
@@ -38,4 +38,12 @@ Resources:
38- You have 90 days from the time of approval to complete this bounty.
38- You have 90 days from the time of approval to complete this bounty.
39- Successful completion of this bounty may result in an invitation to complete other API integration bounties.
39- Successful completion of this bounty may result in an invitation to complete other API integration bounties.
40
40
41+
42+## Milestones
43+
44+
45+### Your PR is merged
46+3 stars
47+Your code is accepted and merged.
48+
41
49
content/community/grants-and-bounties/bitcoin-full-node-provider-and-wallet.md+13
@@ -76,4 +76,17 @@ The director will ensure that you have access to the necessary resources to comp
76
76
77The worker should have a background that either demonstrates experience building Gall agents, or developing on Bitcoin (or similar crypto systems)--both would be even better.
77The worker should have a background that either demonstrates experience building Gall agents, or developing on Bitcoin (or similar crypto systems)--both would be even better.
78
78
79+
80+## Milestones
81+
82+
83+### Implement the full node bridge/provider
84+3 stars
85+Create a set of gall agents to interface with a Bitcoin full node, access to which can be provided to other ships.
86+
87+
88+### Implement the wallet
89+3 stars
90+Create a set of gall agents to handle extended public keys, address derivation, and facilitate payments between ships.
91+
79
92
content/community/grants-and-bounties/bitcoin-key-derivation.md+8
@@ -50,4 +50,12 @@ The worker should have a background that demonstrates proficiency with building
50
50
51* [Urbit HD Wallet design](https://github.com/urbit/fora-posts/blob/master/proposals/posts/~2018.11.8..19.31.59..ba77~.md)
51* [Urbit HD Wallet design](https://github.com/urbit/fora-posts/blob/master/proposals/posts/~2018.11.8..19.31.59..ba77~.md)
52* [BIP-32 re: extended public keys](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#Extended_keys)
52* [BIP-32 re: extended public keys](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#Extended_keys)
53+
54+## Milestones
55+
56+
57+### Work is Complete
58+2 stars
59+Pull requests to each repository have been submitted, reviewed and merged.
60+
53
61
content/community/grants-and-bounties/bitcoin-node-json-rpc-api-part-1.md+8
@@ -37,4 +37,12 @@ This bounty is to create a portion of the Gall app library for Remote Procedure
37* Base your work off of the [btc-node-grant branch](https://github.com/urbit/urbit/tree/btc-node-grant). Follow Boilerplate. Look for `TODO`s.
37* Base your work off of the [btc-node-grant branch](https://github.com/urbit/urbit/tree/btc-node-grant). Follow Boilerplate. Look for `TODO`s.
38* Submit your code as a PR to the [btc-node-grant](https://github.com/urbit/urbit/tree/btc-node-grant) branch of the `urbit` repo in form of a `.hoon` file.
38* Submit your code as a PR to the [btc-node-grant](https://github.com/urbit/urbit/tree/btc-node-grant) branch of the `urbit` repo in form of a `.hoon` file.
39* You have 45 days from the time of approval to complete this bounty.
39* You have 45 days from the time of approval to complete this bounty.
40+
41+## Milestones
42+
43+
44+### Your PR is merged
45+1 stars
46+Your PR containing all the relevant code updates is accepted and merged.
47+
40
48
content/community/grants-and-bounties/bitcoin-node-json-rpc-api-part-2.md+8
@@ -37,4 +37,12 @@ This bounty is to create a portion of the Gall app library for Remote Procedure
37* Base your work off of the [btc-node-grant branch](https://github.com/urbit/urbit/tree/btc-node-grant). Follow Boilerplate. Look for `TODO`s.
37* Base your work off of the [btc-node-grant branch](https://github.com/urbit/urbit/tree/btc-node-grant). Follow Boilerplate. Look for `TODO`s.
38* Submit your code as a PR to the [btc-node-grant](https://github.com/urbit/urbit/tree/btc-node-grant) branch of the `urbit` repo in form of a `.hoon` file.
38* Submit your code as a PR to the [btc-node-grant](https://github.com/urbit/urbit/tree/btc-node-grant) branch of the `urbit` repo in form of a `.hoon` file.
39* You have 45 days from the time of approval to complete this bounty.
39* You have 45 days from the time of approval to complete this bounty.
40+
41+## Milestones
42+
43+
44+### Your PR is merged
45+1 stars
46+Your PR containing all the relevant code updates is accepted and merged.
47+
40
48
content/community/grants-and-bounties/bitcoin-node-json-rpc-api-part-3.md+8
@@ -38,4 +38,12 @@ This bounty is to create a portion of the Gall app library for Remote Procedure
38* Submit your code as a PR to the [btc-node-grant](https://github.com/urbit/urbit/tree/btc-node-grant) branch of the `urbit` repo in form of a `.hoon` file.
38* Submit your code as a PR to the [btc-node-grant](https://github.com/urbit/urbit/tree/btc-node-grant) branch of the `urbit` repo in form of a `.hoon` file.
39* You have 45 days from the time of approval to complete this bounty.
39* You have 45 days from the time of approval to complete this bounty.
40
40
41+
42+## Milestones
43+
44+
45+### Your PR is merged
46+1 stars
47+Your PR containing all the relevant code updates is accepted and merged.
48+
41
49
content/community/grants-and-bounties/bitcoin-node-json-rpc-api-part-4.md+8
@@ -37,4 +37,12 @@ This bounty is to create a portion of the Gall app library for Remote Procedure
37* Base your work off of the [btc-node-grant branch](https://github.com/urbit/urbit/tree/btc-node-grant). Follow Boilerplate. Look for `TODO`s.
37* Base your work off of the [btc-node-grant branch](https://github.com/urbit/urbit/tree/btc-node-grant). Follow Boilerplate. Look for `TODO`s.
38* Submit your code as a PR to the [btc-node-grant](https://github.com/urbit/urbit/tree/btc-node-grant) branch of the `urbit` repo in form of a `.hoon` file.
38* Submit your code as a PR to the [btc-node-grant](https://github.com/urbit/urbit/tree/btc-node-grant) branch of the `urbit` repo in form of a `.hoon` file.
39* You have 90 days from the time of approval to complete this bounty.
39* You have 90 days from the time of approval to complete this bounty.
40+
41+## Milestones
42+
43+
44+### Your PR is merged
45+2 stars
46+Your PR containing all the relevant code updates is accepted and merged.
47+
40
48
content/community/grants-and-bounties/bitcoin-wallet-on-bridge.md+8
@@ -47,4 +47,12 @@ A completed wallet should:
47- Bounty claimant should have a good working knowledge of React and Bitcoin transactions.
47- Bounty claimant should have a good working knowledge of React and Bitcoin transactions.
48- Submit your code as a PR to the [Bridge](https://github.com/urbit/bridge) repository.
48- Submit your code as a PR to the [Bridge](https://github.com/urbit/bridge) repository.
49- You have 45 days from the time of approval to complete this bounty.
49- You have 45 days from the time of approval to complete this bounty.
50+
51+## Milestones
52+
53+
54+### Pull request is accepted
55+1 stars
56+Your pull request containing all of the relevant code has been merged.
57+
50
58
content/community/grants-and-bounties/boston-t-train-tracker-landscape-tile.md+8
@@ -43,4 +43,12 @@ We would like to create a T Train information Landscape tile. The backend should
43- Successful completion of this bounty may result in an invitation to complete other API integration bounties.
43- Successful completion of this bounty may result in an invitation to complete other API integration bounties.
44
44
45
45
46+
47+## Milestones
48+
49+
50+### Your PR is merged
51+3 stars
52+Your code is accepted and merged.
53+
46
54
content/community/grants-and-bounties/calendar-ui.md+14−1
@@ -2,7 +2,7 @@
2title = "Calendar UI"
2title = "Calendar UI"
3date = 2020-07-16
3date = 2020-07-16
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Arvo"]
6grant_category = ["App Dev: Arvo"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -37,4 +37,17 @@ The second stage is to integrate the screens with the Gall agent implemented as
37# Basis for future integration
37# Basis for future integration
38
38
39These pages can provide the basis for UX experiments and integrations with other parts of Landscape. One possibility is to integrate notebook posts with the timeline of a calendar, allowing a temporal exploration of the notebook posts a ship has seen.
39These pages can provide the basis for UX experiments and integrations with other parts of Landscape. One possibility is to integrate notebook posts with the timeline of a calendar, allowing a temporal exploration of the notebook posts a ship has seen.
40+
41+## Milestones
42+
43+
44+### Functional pages
45+1 stars
46+Build the necessary pages that will allow Landscape to interact with a Calendar Gall app
47+
48+
49+### Working integration with Gall app
50+1 stars
51+Fully capable of importing an .ics calendar, creating new events, looking through existing events in the calendar of a ship.
52+
40
53
content/community/grants-and-bounties/calendar.md+24−1
@@ -2,7 +2,7 @@
2title = "Calendar"
2title = "Calendar"
3date = 2020-05-19
3date = 2020-05-19
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Arvo"]
6grant_category = ["App Dev: Arvo"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -89,4 +89,27 @@ END:VCALENDAR
89```
89```
90
90
91If time permits, we'd also want to support parsing VALARM components, which correspond to alarms/reminders about events. These components can be nested within VEVENTs, and have three flavors - audio, display, and email (each representing the kind of reminder the component can give you). We aim to support parsing display alarms (displaying some text) initially, as audio is only useful once a UI is built and we don't have email on mars. While handling the alarms is outside the scope of this proposal, by parsing them we hope to make it easy for future proposals to build on them.
91If time permits, we'd also want to support parsing VALARM components, which correspond to alarms/reminders about events. These components can be nested within VEVENTs, and have three flavors - audio, display, and email (each representing the kind of reminder the component can give you). We aim to support parsing display alarms (displaying some text) initially, as audio is only useful once a UI is built and we don't have email on mars. While handling the alarms is outside the scope of this proposal, by parsing them we hope to make it easy for future proposals to build on them.
92+
93+## Milestones
94+
95+
96+### VEVENT Parser
97+1 stars
98+A generator that can parse `.ics` files from the dojo containing VEVENTs into hoon data structures. This milestone will NOT support top-level calendar properties.
99+
100+
101+### Calendar Gall Agent
102+1 stars
103+Creation of a gall agent that can be used to persist and read events from `.ics` files into a "calendar" on the running ship.
104+
105+
106+### Gall Agent Enrichment
107+1 stars
108+Extend the gall agent to support queries (e.g. within a range), updates and deletes of events, and a generator to create events without use of `.ics` files.
109+
110+
111+### Pubsub/Channel Support
112+2 stars
113+Extend the gall agent to allow pubsub with other ships and integration with Groups to ultimately allow calendars to exist as an additional channel.
114+
92
115
content/community/grants-and-bounties/comprehensive-local-server-and-mum-explanation-video.md+10−2
@@ -2,11 +2,11 @@
2title = "Comprehensive local, server and mum explanation video"
2title = "Comprehensive local, server and mum explanation video"
3date = 2021-01-31
3date = 2021-01-31
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Community"]
6grant_category = ["Community"]
7[extra]
7[extra]
8image = ""
8image = ""
9−description = "Series of three videos"
9+description = "Series of three videos:1) Purchase planet, install and run on a local machine2) nginx setup3) Explaining Urbit to my tech illiterate mum "
10reward = 1
10reward = 1
11assignee = "mislyr-midnyt"
11assignee = "mislyr-midnyt"
12id = "2020133197"
12id = "2020133197"
@@ -30,4 +30,12 @@ Explain Urbit in a simple way to my sister and technologically illiterate mum. I
30Videos will be entertaining and engaging, not entirely dissimilar to voice messages posted on urbit-community. Reckon this will be a good way to allow people to very easily onboard onto the network.
30Videos will be entertaining and engaging, not entirely dissimilar to voice messages posted on urbit-community. Reckon this will be a good way to allow people to very easily onboard onto the network.
31
31
32Granted star would be used to onboard friends, family and people from the easypeasymethod.org community (currently Discord server).
32Granted star would be used to onboard friends, family and people from the easypeasymethod.org community (currently Discord server).
33+
34+## Milestones
35+
36+
37+### Record, edit and upload all videos
38+1 stars
39+Upload all three videos to Youtube, post links in proposal updates.
40+
33
41
content/community/grants-and-bounties/content-saver.md+8
@@ -33,4 +33,12 @@ The file should strip the content out of HTML and save it into the Markdown form
33- Submit your code as a PR to the [urbit](github.com/urbit/urbit] repository.
33- Submit your code as a PR to the [urbit](github.com/urbit/urbit] repository.
34- You have 90 days from the time of approval to complete this bounty.
34- You have 90 days from the time of approval to complete this bounty.
35
35
36+
37+## Milestones
38+
39+
40+### PR is merged
41+2 stars
42+Your code is accepted and merged.
43+
36
44
content/community/grants-and-bounties/cross-platform-desktop-urbit-app.md+24−1
@@ -2,7 +2,7 @@
2title = "Cross-Platform Desktop Urbit App"
2title = "Cross-Platform Desktop Urbit App"
3date = 2021-02-23
3date = 2021-02-23
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Other"]
6grant_category = ["App Dev: Other"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -59,4 +59,27 @@ People like to jump in and experiment with things first. I think this app provid
59My name is Hunter Miller, and I've been building on the web for 7 years. I currently work as a Senior Software Engineer for This Dot building websites and web apps for our clients. I'm focused on delivering the best user experience, which takes delicate coordination between back-end and front-end architecture to really achieve near-perfection. Throughout my time as a developer I've gained a variety of experience starting at an advertising and design agency, moving to a half a billion dollar e-commerce website, and then on to a high-level contracting and consulting firm.
59My name is Hunter Miller, and I've been building on the web for 7 years. I currently work as a Senior Software Engineer for This Dot building websites and web apps for our clients. I'm focused on delivering the best user experience, which takes delicate coordination between back-end and front-end architecture to really achieve near-perfection. Throughout my time as a developer I've gained a variety of experience starting at an advertising and design agency, moving to a half a billion dollar e-commerce website, and then on to a high-level contracting and consulting firm.
60
60
61You can checkout [my website](https://hmiller.dev/), [LinkedIn](https://www.linkedin.com/in/hunter-miller-dev/), and [Twitter](https://twitter.com/hmillerdev) to see more about me.
61You can checkout [my website](https://hmiller.dev/), [LinkedIn](https://www.linkedin.com/in/hunter-miller-dev/), and [Twitter](https://twitter.com/hmillerdev) to see more about me.
62+
63+## Milestones
64+
65+
66+### Ability to run basic ship features
67+1 stars
68+Includes start/stop/restart ship, show status, eject ship for hosting, boot new planets, moons, and comets, boot existing planets and comets, act as browser for hosted ships, and ship removal.
69+
70+
71+### (Timeboxed) Proof of Concept for Windows
72+1 stars
73+To include the Windows' user base, the PoC should enable running on Windows either through WSL or some other means. Two week timebox to make sure we don't spend too much time here.
74+
75+
76+### Urbit Client Beta Release
77+4 stars
78+Significant testing during this time. Cross-platform, include all basic ship features, with no major bugs. Renamed to Urbit Client and added to urbit.org as an easy download.
79+
80+
81+### Azimuth Integration and Official Release
82+4 stars
83+Integrating Urbit key generation for easy booting of new planets. Adding further refinements to UI, all moderate issues resolved, and documentation for users and contributors.
84+
62
85
content/community/grants-and-bounties/cta-train-tracker-landscape-tile.md+8
@@ -38,4 +38,12 @@ The tile interface should encompass:
38- Please note that this bounty is for the CTA Train API and not for the CTA Bus API.
38- Please note that this bounty is for the CTA Train API and not for the CTA Bus API.
39- Do not use copyrighted images, including the CTA logo or the official route map. Instead, always refer to CTA in plaintext, and use the provided train image which is detailed in the above Developer License Agreement link. You should include an external link to the CTA L Train route map; do not host this map locally (we are open to an open-source, good quality route map which does not include the CTA logo or other trademarks, however).
39- Do not use copyrighted images, including the CTA logo or the official route map. Instead, always refer to CTA in plaintext, and use the provided train image which is detailed in the above Developer License Agreement link. You should include an external link to the CTA L Train route map; do not host this map locally (we are open to an open-source, good quality route map which does not include the CTA logo or other trademarks, however).
40- Please read the Developer License Agreement and Branding Guide carefully and obey their guidelines for application naming and presentation of API data.
40- Please read the Developer License Agreement and Branding Guide carefully and obey their guidelines for application naming and presentation of API data.
41+
42+## Milestones
43+
44+
45+### Your PR is merged
46+3 stars
47+Your code is accepted and merged.
48+
41
49
content/community/grants-and-bounties/display-eth-data.md+8
@@ -45,4 +45,12 @@ Create a gall application, and a user interface for that application, that are u
45- When applying to work on the bounty, tell us a little about yourself and some projects you’ve worked on in the past.
45- When applying to work on the bounty, tell us a little about yourself and some projects you’ve worked on in the past.
46- You have 90 days from the time of approval to complete this bounty.
46- You have 90 days from the time of approval to complete this bounty.
47
47
48+
49+## Milestones
50+
51+
52+### Work is finished
53+1 stars
54+Your work has been finished and accepted.
55+
48
56
content/community/grants-and-bounties/docker-image-for-cloud-container-orchestration.md+12−1
@@ -2,7 +2,7 @@
2title = "Docker image for cloud container orchestration"
2title = "Docker image for cloud container orchestration"
3date = 2020-12-21
3date = 2020-12-21
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Dev Tool"]
6grant_category = ["Dev Tool"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -32,4 +32,15 @@ Many cloud providers offer container orchestration services that abstract away f
32
32
33# Team
33# Team
34Edward Amsden ~ritpub-sipsyl is a veteran developer with several years experience using Nix to manage production builds and deployments. He is the principal of Black River Software LLC
34Edward Amsden ~ritpub-sipsyl is a veteran developer with several years experience using Nix to manage production builds and deployments. He is the principal of Black River Software LLC
35+
36+## Milestones
37+
38+
39+### Merged PR: Nix docker integration
40+1 stars
41+- Nix code to generate an Urbit docker image
42+- CI integration to release docker images on GitHub
43+- CI integration to publish docker images on Docker Hub
44+- Documentation
45+
35
46
content/community/grants-and-bounties/educational-guide-todomvc-urbit-edition.md+28
@@ -300,4 +300,32 @@ Your solution to this bounty should include:
300You will work closely with the director of urbit.org on this project. This means that regular check-in calls will be held to discuss the project's progress. Additionally, the you are expected to provide regular status updates on the project to the Urbit community via twice-monthly updates on this bounty.
300You will work closely with the director of urbit.org on this project. This means that regular check-in calls will be held to discuss the project's progress. Additionally, the you are expected to provide regular status updates on the project to the Urbit community via twice-monthly updates on this bounty.
301
301
302The director will ensure that you have access to the necessary resources to complete this project. All prior work done on this project will be explained and made available to you, and should questions arise that require the expertise of engineers at Tlon, time will be made (schedules permitting) for your questions to be answered either in writing or over a call.
302The director will ensure that you have access to the necessary resources to complete this project. All prior work done on this project will be explained and made available to you, and should questions arise that require the expertise of engineers at Tlon, time will be made (schedules permitting) for your questions to be answered either in writing or over a call.
303+
304+## Milestones
305+
306+
307+### Part 1: Serving Static Content
308+2 stars
309+Sample code and guide are completed and ready for merge against urbit/docs.
310+
311+
312+### Part 2: Data Modeling
313+1 stars
314+Sample code and guide are completed and ready for merge against urbit/docs.
315+
316+
317+### Part 3: Taking Action
318+1 stars
319+Sample code and guide are completed and ready for merge against urbit/docs.
320+
321+
322+### Part 4: Client Integration
323+3 stars
324+Sample code and guide are completed and ready for merge against urbit/docs.
325+
326+
327+### Part 5: Collaboration
328+3 stars
329+Sample code and guide are completed and ready for merge against urbit/docs.
330+
303
331
content/community/grants-and-bounties/escape.md+14−1
@@ -2,7 +2,7 @@
2title = "Escape"
2title = "Escape"
3date = 2019-12-04
3date = 2019-12-04
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Arvo"]
6grant_category = ["App Dev: Arvo"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -29,4 +29,17 @@ The aim of this proposal is not to create a perfect reputation system but rather
29The Beta Reputation is a system that is very easy to understand to non-technical users but has a statistical background behind it. Nevertheless this is just one of the many reputation systems that are out there like [Regret](https://dl.acm.org/doi/pdf/10.1145/375735.376110), [Fire](https://eprints.soton.ac.uk/259559/1/dong-ecai2004.pdf) or [Travos](https://idp.springer.com/authorize/casa?redirect_uri=https://link.springer.com/content/pdf/10.1007/s10458-006-5952-x.pdf&casa_token=M38itGxqsu0AAAAA:lAUgQUvbc4dZFhrNs4SSPWrQ9PzUj05pzmU5zkvPkytDOfgFOIxVP0a8Tzk_VkRi37J1bRHPJ2IhTD8C). I envision this work as a starting point for introducing reputation systems in Urbit as libraries that can be used by the community for experimentation.
29The Beta Reputation is a system that is very easy to understand to non-technical users but has a statistical background behind it. Nevertheless this is just one of the many reputation systems that are out there like [Regret](https://dl.acm.org/doi/pdf/10.1145/375735.376110), [Fire](https://eprints.soton.ac.uk/259559/1/dong-ecai2004.pdf) or [Travos](https://idp.springer.com/authorize/casa?redirect_uri=https://link.springer.com/content/pdf/10.1007/s10458-006-5952-x.pdf&casa_token=M38itGxqsu0AAAAA:lAUgQUvbc4dZFhrNs4SSPWrQ9PzUj05pzmU5zkvPkytDOfgFOIxVP0a8Tzk_VkRi37J1bRHPJ2IhTD8C). I envision this work as a starting point for introducing reputation systems in Urbit as libraries that can be used by the community for experimentation.
30
30
31With this is mind the Beta library (`/lib/beta.hoon`) can be used with any app that has a well defined data structure that comprises a list of timestamped events with a certain score, weighted, if desired, for a specific dimension. The ability to tag each event with a weighted dimension allows for complex reputations where different data points can be aggregated together.
31With this is mind the Beta library (`/lib/beta.hoon`) can be used with any app that has a well defined data structure that comprises a list of timestamped events with a certain score, weighted, if desired, for a specific dimension. The ability to tag each event with a weighted dimension allows for complex reputations where different data points can be aggregated together.
32+
33+## Milestones
34+
35+
36+### Gall Agent and Beta Reputation Library
37+2 stars
38+Delivery of the agent and library for the Beta reputation that's able to poke Azimuth for the Blockchain data, calculate the reputation score, and store it on the agent.
39+
40+
41+### Escape UI
42+2 stars
43+Delivery of the UI interface that will show the Reputation Score to the user, with the ability to search for specific sponsors and filter the results accordingly.
44+
32
45
content/community/grants-and-bounties/ethereum-abi-parser.md+8
@@ -44,4 +44,12 @@ Create a Gall app that can output the byte code for a contract ABI.
44- When applying to work on the bounty, tell us a little about yourself and some projects you’ve worked on in the past.
44- When applying to work on the bounty, tell us a little about yourself and some projects you’ve worked on in the past.
45- You have 90 days from the time of approval to complete this bounty.
45- You have 90 days from the time of approval to complete this bounty.
46
46
47+
48+## Milestones
49+
50+
51+### PR is merged
52+2 stars
53+Your code is accepted and merged.
54+
47
55
content/community/grants-and-bounties/gall-api-documentation.md+13
@@ -38,4 +38,17 @@ Developers should be able to use this document as a template for writing their G
38* Submit your document in the form of a pull-request to the [Docs repo](https://github.com/urbit/docs). This file should live under the reference directory.
38* Submit your document in the form of a pull-request to the [Docs repo](https://github.com/urbit/docs). This file should live under the reference directory.
39* Expect to receive requests for changes to your document.
39* Expect to receive requests for changes to your document.
40
40
41+
42+## Milestones
43+
44+
45+### First draft is submitted
46+0 stars
47+Your first draft is submitted as a pull request to the Docs repository.
48+
49+
50+### Final draft is merged
51+1 stars
52+Your edits are satisfactory, and your PR is merged to master.
53+
41
54
content/community/grants-and-bounties/go-airlock-library.md+8
@@ -34,4 +34,12 @@ Additionally, write a one-page explanation for the design choices for this libra
34- You have 90 days from the time of approval to complete this bounty.
34- You have 90 days from the time of approval to complete this bounty.
35- Successful completion of this bounty may result in an invitation to complete other Airlock library bounties. If you are interested in creating an Airlock library for a language other than the ones currently presented, please contact us at grants@urbit.org ; it’s likely we’ll approve this as a proposal.
35- Successful completion of this bounty may result in an invitation to complete other Airlock library bounties. If you are interested in creating an Airlock library for a language other than the ones currently presented, please contact us at grants@urbit.org ; it’s likely we’ll approve this as a proposal.
36
36
37+
38+## Milestones
39+
40+
41+### Work is finished
42+3 stars
43+You have completed your work and pushed it to a Github repo.
44+
37
45
content/community/grants-and-bounties/graph-store-documenation-guide.md+19−1
@@ -2,7 +2,7 @@
2title = "Graph Store Documenation Guide"
2title = "Graph Store Documenation Guide"
3date = 2021-02-13
3date = 2021-02-13
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Documentation"]
6grant_category = ["Documentation"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -79,4 +79,22 @@ As a developer who already understands `graph-store` I can:
79* look up API information
79* look up API information
80* maintain existing `graph-store` applications on the backend
80* maintain existing `graph-store` applications on the backend
81* maintain existing `graph-store` applications on the frontend in the frontend stack of my choice
81* maintain existing `graph-store` applications on the frontend in the frontend stack of my choice
82+
83+## Milestones
84+
85+
86+### Explainer
87+1 stars
88+Full written explainer posted online
89+
90+
91+### Tutorial
92+1 stars
93+Full written tutorial with tested code samples
94+
95+
96+### Cookbooks & Reference, Finalization
97+2 stars
98+Full written cookbook document, updated reference, and finalization of the content
99+
82
100
content/community/grants-and-bounties/haskell-airlock-library.md+8
@@ -34,4 +34,12 @@ Additionally, write a one-page explanation for the design choices for this libra
34- You have 90 days from the time of approval to complete this bounty.
34- You have 90 days from the time of approval to complete this bounty.
35- Successful completion of this bounty may result in an invitation to complete other Airlock library bounties. If you are interested in creating an Airlock library for a language other than the ones currently presented, please contact us at grants@urbit.org ; it’s likely we’ll approve this as a proposal.
35- Successful completion of this bounty may result in an invitation to complete other Airlock library bounties. If you are interested in creating an Airlock library for a language other than the ones currently presented, please contact us at grants@urbit.org ; it’s likely we’ll approve this as a proposal.
36
36
37+
38+## Milestones
39+
40+
41+### Your work is finished
42+3 stars
43+You have completed your work and pushed it to a Github repo.
44+
37
45
content/community/grants-and-bounties/hoon-001-learner-efficiency-and-early-learner-resources.md+9−1
@@ -2,7 +2,7 @@
2title = "Hoon 001: Learner efficiency and early-learner resources"
2title = "Hoon 001: Learner efficiency and early-learner resources"
3date = 2020-02-10
3date = 2020-02-10
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Documentation"]
6grant_category = ["Documentation"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -70,4 +70,12 @@ Let’s create! Five generators, from fairly trivial (1-2) to stretching the lea
70
70
71Expected hours: 125
71Expected hours: 125
72
72
73+
74+## Milestones
75+
76+
77+### Full Project
78+3 stars
79+Full project delivery, including content, learning materials, generators, walkthroughs, video walkthroughs
80+
73
81
content/community/grants-and-bounties/host-three-college-university-urbit-meetups-1.md+8
@@ -49,4 +49,12 @@ Check out our [guide](https://urbit.org/community/hosting-a-meetup/) to best pra
49- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
49- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
50- You have 100 days from the time of approval to complete this bounty.
50- You have 100 days from the time of approval to complete this bounty.
51
51
52+
53+## Milestones
54+
55+
56+### Three meetups are held
57+1 stars
58+Your three meetups are held, and links to the presentations have been posted and sent to grants@urbit.org.
59+
52
60
content/community/grants-and-bounties/host-three-college-university-urbit-meetups-2.md+8
@@ -49,4 +49,12 @@ Check out our [guide](https://urbit.org/community/hosting-a-meetup/) to best pra
49- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
49- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
50- You have 100 days from the time of approval to complete this bounty.
50- You have 100 days from the time of approval to complete this bounty.
51
51
52+
53+## Milestones
54+
55+
56+### Three meetups are held
57+1 stars
58+Your three meetups are held, and links to the presentations have been posted and sent to grants@urbit.org.
59+
52
60
content/community/grants-and-bounties/host-three-college-university-urbit-meetups-3.md+8
@@ -48,4 +48,12 @@ Check out our [guide](https://urbit.org/community/hosting-a-meetup/) to best pra
48- When applying to work on the bounty, tell us a little about yourself and mention which university and location you'd be hosting the meetups in.
48- When applying to work on the bounty, tell us a little about yourself and mention which university and location you'd be hosting the meetups in.
49- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
49- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
50- You have 100 days from the time of approval to complete this bounty.
50- You have 100 days from the time of approval to complete this bounty.
51+
52+## Milestones
53+
54+
55+### Three meetups are held
56+1 stars
57+Your three meetups are held, and links to the presentations have been posted and sent to grants@urbit.org.
58+
51
59
content/community/grants-and-bounties/host-three-virtual-urbit-meetups.md+8
@@ -40,4 +40,12 @@ Check out our [guide](https://urbit.org/community/hosting-a-meetup/) to best pra
40- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
41- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
41- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
42- You have 100 days from the time of approval to complete this bounty.
42- You have 100 days from the time of approval to complete this bounty.
43+
44+## Milestones
45+
46+
47+### The third meetup is help
48+1 stars
49+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
50+
43
51
content/community/grants-and-bounties/host-two-urbit-meetups-1.md+13
@@ -39,4 +39,17 @@ Check it out our [guide](https://urbit.org/community/hosting-a-meetup/) to best
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
41- You have 100 days from the time of approval to complete this bounty.
41- You have 100 days from the time of approval to complete this bounty.
42+
43+## Milestones
44+
45+
46+### The first meetup is held
47+0 stars
48+The first meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
49+
50+
51+### The second meetup is held
52+1 stars
53+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
54+
42
55
content/community/grants-and-bounties/host-two-urbit-meetups-10.md+13
@@ -39,4 +39,17 @@ Check out our [guide](https://urbit.org/community/hosting-a-meetup/) to best pra
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
41- You have 100 days from the time of approval to complete this bounty.
41- You have 100 days from the time of approval to complete this bounty.
42+
43+## Milestones
44+
45+
46+### The first meetup is help
47+0 stars
48+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
49+
50+
51+### The second meetup is help
52+1 stars
53+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
54+
42
55
content/community/grants-and-bounties/host-two-urbit-meetups-11.md+13
@@ -39,4 +39,17 @@ Check out our [guide](https://urbit.org/community/hosting-a-meetup/) to best pra
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
41- You have 100 days from the time of approval to complete this bounty.
41- You have 100 days from the time of approval to complete this bounty.
42+
43+## Milestones
44+
45+
46+### The first meetup is held
47+0 stars
48+The first meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
49+
50+
51+### The second meetup is held
52+1 stars
53+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
54+
42
55
content/community/grants-and-bounties/host-two-urbit-meetups-2.md+13
@@ -39,4 +39,17 @@ Check it out our [guide](https://urbit.org/community/hosting-a-meetup/) to best
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
41- You have 100 days from the time of approval to complete this bounty.
41- You have 100 days from the time of approval to complete this bounty.
42+
43+## Milestones
44+
45+
46+### The first meetup is held
47+0 stars
48+The first meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
49+
50+
51+### The second meetup is held
52+1 stars
53+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
54+
42
55
content/community/grants-and-bounties/host-two-urbit-meetups-3.md+13
@@ -39,4 +39,17 @@ Check it out our [guide](https://urbit.org/community/hosting-a-meetup/) to best
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
41- You have 100 days from the time of approval to complete this bounty.
41- You have 100 days from the time of approval to complete this bounty.
42+
43+## Milestones
44+
45+
46+### The first meetup is held
47+0 stars
48+The first meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
49+
50+
51+### The first meetup is held
52+1 stars
53+The first meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
54+
42
55
content/community/grants-and-bounties/host-two-urbit-meetups-4.md+13
@@ -39,4 +39,17 @@ Check it out our [guide](https://urbit.org/community/hosting-a-meetup/) to best
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
41- You have 100 days from the time of approval to complete this bounty.
41- You have 100 days from the time of approval to complete this bounty.
42+
43+## Milestones
44+
45+
46+### The first meetup is held
47+0 stars
48+The first meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
49+
50+
51+### The second meetup is held
52+1 stars
53+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
54+
42
55
content/community/grants-and-bounties/host-two-urbit-meetups-5.md+13
@@ -39,4 +39,17 @@ Check it out our [guide](https://urbit.org/community/hosting-a-meetup/) to best
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
41- You have 100 days from the time of approval to complete this bounty.
41- You have 100 days from the time of approval to complete this bounty.
42+
43+## Milestones
44+
45+
46+### The first meetup is held
47+0 stars
48+The first meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
49+
50+
51+### The second meetup is held
52+1 stars
53+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
54+
42
55
content/community/grants-and-bounties/host-two-urbit-meetups-6.md+13
@@ -39,4 +39,17 @@ Check it out our [guide](https://urbit.org/community/hosting-a-meetup/) to best
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
41- You have 100 days from the time of approval to complete this bounty.
41- You have 100 days from the time of approval to complete this bounty.
42+
43+## Milestones
44+
45+
46+### The first meetup is held
47+0 stars
48+The first meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
49+
50+
51+### The second meetup is held
52+1 stars
53+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
54+
42
55
content/community/grants-and-bounties/host-two-urbit-meetups-7.md+13
@@ -39,4 +39,17 @@ Check out our [guide](https://urbit.org/community/hosting-a-meetup/) to best pra
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
41- You have 100 days from the time of approval to complete this bounty.
41- You have 100 days from the time of approval to complete this bounty.
42+
43+## Milestones
44+
45+
46+### The first meetup is held
47+0 stars
48+The first meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
49+
50+
51+### The second meetup is held
52+1 stars
53+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
54+
42
55
content/community/grants-and-bounties/host-two-urbit-meetups-8.md+13
@@ -39,4 +39,17 @@ Check out our [guide](https://urbit.org/community/hosting-a-meetup/) to best pra
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@urbit.org.
41- You have 100 days from the time of approval to complete this bounty.
41- You have 100 days from the time of approval to complete this bounty.
42+
43+## Milestones
44+
45+
46+### The first meetup is held
47+0 stars
48+The first meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
49+
50+
51+### The second meetup is held
52+1 stars
53+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
54+
42
55
content/community/grants-and-bounties/host-two-urbit-meetups-9.md+13
@@ -39,4 +39,17 @@ Check out our [guide](https://urbit.org/community/hosting-a-meetup/) to best pra
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
39- When applying to work on the bounty, tell us a little about yourself and mention which city you'd be hosting the meetups in.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
40- Proof of the meetups happening will be determined by the recordings of the presentations. Email links to these recordings to grants@tlon.io.
41- You have 100 days from the time of approval to complete this bounty.
41- You have 100 days from the time of approval to complete this bounty.
42+
43+## Milestones
44+
45+
46+### The first meetup is help
47+0 stars
48+The first meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
49+
50+
51+### The second meetup is help
52+1 stars
53+The second meetup is held, and a recording of that meetup's talk or presentation is sent to grants@urbit.org.
54+
42
55
content/community/grants-and-bounties/links-in-urbit-reference-docs.md+9−1
@@ -2,7 +2,7 @@
2title = "Links in Urbit Reference Docs"
2title = "Links in Urbit Reference Docs"
3date = 2020-06-16
3date = 2020-06-16
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Documentation"]
6grant_category = ["Documentation"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -19,4 +19,12 @@ The goal of this proposal is to add links to the Urbit Reference docs (that is,
19Suppose you're browsing [section 2a](https://urbit.org/docs/reference/library/2a/) of the Hoon standard library. You see the word "unit" a bunch of times, but you're not actually sure what it means. You try to click on one of the instances, hoping it'll take you to a page with more information, but nothing happens! That's because the library (and a fair amount of Urbit documentation) lacks links between pages.
19Suppose you're browsing [section 2a](https://urbit.org/docs/reference/library/2a/) of the Hoon standard library. You see the word "unit" a bunch of times, but you're not actually sure what it means. You try to click on one of the instances, hoping it'll take you to a page with more information, but nothing happens! That's because the library (and a fair amount of Urbit documentation) lacks links between pages.
20
20
21Consider, for contrast, a [random Python doc page](https://docs.python.org/3/library/os.html). Every concept that has documentation has a link to said documentation. By adding links to the Urbit docs, we'll make the documentation easier to use, and from there make Hoon and Urbit easier to learn.
21Consider, for contrast, a [random Python doc page](https://docs.python.org/3/library/os.html). Every concept that has documentation has a link to said documentation. By adding links to the Urbit docs, we'll make the documentation easier to use, and from there make Hoon and Urbit easier to learn.
22+
23+## Milestones
24+
25+
26+### Links added to Reference documentation
27+1 stars
28+Concepts that refer to pages with documentation have links to said documentation.
29+
22
30
content/community/grants-and-bounties/llelogram.md+29−1
@@ -2,7 +2,7 @@
2title = "Llelogram"
2title = "Llelogram"
3date = 2020-07-29
3date = 2020-07-29
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Arvo"]
6grant_category = ["App Dev: Arvo"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -24,4 +24,32 @@ Technically, Llelogram is a set of tables to run contravariant to legislation. T
24
24
252020 has been a scary year, but for all the sound and fury I can see light in our eyes. If we can create what I have been conceptualizing since 2015, Llelogram will be a tool for people to see how well legislation written in their names reflects the light in their eyes. Thank you so much for reading, I hope I can be part of utilizing Urbit and bringing it into the real world with you folks!
252020 has been a scary year, but for all the sound and fury I can see light in our eyes. If we can create what I have been conceptualizing since 2015, Llelogram will be a tool for people to see how well legislation written in their names reflects the light in their eyes. Thank you so much for reading, I hope I can be part of utilizing Urbit and bringing it into the real world with you folks!
26
26
27+
28+## Milestones
29+
30+
31+### Build the CLI
32+1 stars
33+At this point we should have a basic CLI that imports actionable* federal legislation, and provides a basic way for us to flag language/numbers and score it according to how generally displaced is.
34+
35+
36+### Compiling the tables
37+1 stars
38+Having worked in parallel with the engineers as they put together the CLI, I'll be compiling a basic list of tax liabilities issued by tax code; also a literary collage of seminal sociology
39+
40+
41+### Interpret the stimulus package
42+1 stars
43+Given the gravity of the stimulus package congress is working on, we should apply our project to it as a way of testing how well our agent illustrates the content and resonates with our control
44+
45+
46+### Write a paper
47+1 stars
48+The paper should stand as a kind of thesis which would be tested as the election happens and we can see how these developments were interpreted through the constituents.
49+
50+
51+### Create a kind of graphic rendition
52+1 stars
53+Given that the ultimate goal of Llelogram is to be something like a stock ticker, I want to create a coherent design language that would reflect the State we are managing.
54+
27
55
content/community/grants-and-bounties/matrices-in-hoon.md+8
@@ -46,4 +46,12 @@ Any paradigm is acceptable as long as it results in code whose performance is at
46- Submit your code as a PR to the [urbit Github repo](https://github.com/urbit/urbit)
46- Submit your code as a PR to the [urbit Github repo](https://github.com/urbit/urbit)
47- You have 180 days from the time of approval to complete this bounty.
47- You have 180 days from the time of approval to complete this bounty.
48
48
49+
50+## Milestones
51+
52+
53+### Your PR is merged
54+5 stars
55+Your PR is accepted and merged.
56+
49
57
content/community/grants-and-bounties/matrixriotim-bridge-bot.md+14−1
@@ -2,7 +2,7 @@
2title = "Matrix(Riot.im) bridge/bot"
2title = "Matrix(Riot.im) bridge/bot"
3date = 2020-11-05
3date = 2020-11-05
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Community"]
6grant_category = ["Community"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -22,4 +22,17 @@ I'm currently apart of a group split between the two platforms, us Martians push
22I'm a close friend of ~nartes-fasrum, a prominent member of the community. They've gotten me addicted to this new age internet and gave me the idea for this project. I'm seeking a single star to cement my place in the galaxy, helping grow the community. I've actively recruited people in the real world under ~sorwet on behalf of ~nart but would like to start sponsoring them myself. I'm an AWS certified engineer with a burning passion for bleeding edge tech, this is my newest and most burning passion. The second milestone is more of a stretch goal of mine, I'm not sure I'm able to complete that alone, but I think it would be a really nice addition to lower the entry bar for fellow martians.
22I'm a close friend of ~nartes-fasrum, a prominent member of the community. They've gotten me addicted to this new age internet and gave me the idea for this project. I'm seeking a single star to cement my place in the galaxy, helping grow the community. I've actively recruited people in the real world under ~sorwet on behalf of ~nart but would like to start sponsoring them myself. I'm an AWS certified engineer with a burning passion for bleeding edge tech, this is my newest and most burning passion. The second milestone is more of a stretch goal of mine, I'm not sure I'm able to complete that alone, but I think it would be a really nice addition to lower the entry bar for fellow martians.
23
23
24
24
25+
26+## Milestones
27+
28+
29+### Working base client
30+1 stars
31+At this point I'd like to have the base client working, subscribing and emitting messages between systems. I'd plan on this running via a separate cli-based client.
32+
33+
34+### Web Client
35+1 stars
36+A self hosted administration portal for the bot, able to add matrix channels/ships seamlessly. This is something that I'd like to complete but not sure on an ETA.
37+
25
38
content/community/grants-and-bounties/minimal-urbit-os.md+24−1
@@ -2,7 +2,7 @@
2title = "Minimal Urbit OS"
2title = "Minimal Urbit OS"
3date = 2021-01-20
3date = 2021-01-20
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Core Dev"]
6grant_category = ["Core Dev"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -30,4 +30,27 @@ Possible environments:
30All management functionality that will be essential regardless of environment will be included and exposed through a basic API. This API will most likely be a command line program, and it will simplify tasks like breaching by combining multiple steps into a single, reliable command. While there are most likely existing scripts to handle some of these tasks, it will be necessary to adapt those processes to this new OS since some things will be missing or work differently.
30All management functionality that will be essential regardless of environment will be included and exposed through a basic API. This API will most likely be a command line program, and it will simplify tasks like breaching by combining multiple steps into a single, reliable command. While there are most likely existing scripts to handle some of these tasks, it will be necessary to adapt those processes to this new OS since some things will be missing or work differently.
31
31
32Qualifications: I recently installed Gentoo on a 20 year old ThinkPad for fun.
32Qualifications: I recently installed Gentoo on a 20 year old ThinkPad for fun.
33+
34+## Milestones
35+
36+
37+### Proof of concept
38+1 stars
39+A minimal VM that supports booting and running a comet for several hours with a small amount of manual setup
40+
41+
42+### System architecture plan
43+1 stars
44+A diagram and written overview of all components and their dependencies, explaining how the system works and why those components were chosen. I will seek input from Tlon.
45+
46+
47+### Usable OS image
48+2 stars
49+A reasonably stable and complete OS image that testers can use for hosting their planets
50+
51+
52+### Documentation and fixes
53+2 stars
54+Documentation for the entire system and build process, including specs for each component and ideas for replacements within Urbit. The OS will be updated to address known problems.
55+
33
56
content/community/grants-and-bounties/network-explorer-data-pipeline-http-api.md+26
@@ -200,4 +200,30 @@ implementer.
200 worker.
200 worker.
201- The director of urbit.org will ensure access to other resources or personnel
201- The director of urbit.org will ensure access to other resources or personnel
202 as needed.
202 as needed.
203+
204+## Milestones
205+
206+
207+### Data ETL
208+2 stars
209+The database has been designed and data from both sources is ingested
210+(extracted, transformed and loaded) on a regular schedule. Analysis can be
211+performed at the database layer.
212+
213+
214+
215+### HTTP API
216+2 stars
217+An HTTP API is written per the above specification and deployed to
218+`https://api.network.urbit.org`.
219+
220+
221+
222+### UI Integration
223+1 stars
224+The Network Explorer UI will be a separate proposal, but integration with an
225+interface inevitably surfaces oversights in the original design. An additional
226+star will be awarded for providing ongoing maintenance as-needed during
227+front-end integration.
228+
203
229
content/community/grants-and-bounties/open-street-maps-data-importation.md+8
@@ -41,4 +41,12 @@ Additionally, write a one-page explanation for your design choices in the readme
41- You have 90 days from the time of approval to complete this bounty.
41- You have 90 days from the time of approval to complete this bounty.
42- Successful completion of this bounty may result in an invitation to complete other API bounties.
42- Successful completion of this bounty may result in an invitation to complete other API bounties.
43
43
44+
45+## Milestones
46+
47+
48+### You are finished
49+2 stars
50+Your work has been approved.
51+
44
52
content/community/grants-and-bounties/overhaul-the-urbitorg-website.md+13
@@ -57,4 +57,17 @@ The path to implementation is necessarily dependent on the outcomes of the desig
57
57
58- A vision document from the Urbit Foundation will be made available.
58- A vision document from the Urbit Foundation will be made available.
59- The Urbit Foundation and Tlon design team will be available for assistance and will provide feedback and design review throughout the process.
59- The Urbit Foundation and Tlon design team will be available for assistance and will provide feedback and design review throughout the process.
60+
61+## Milestones
62+
63+
64+### Designs are complete
65+2 stars
66+Completion of the contents of the Design section above.
67+
68+
69+### Implementation is complete
70+4 stars
71+Completion of the contents of the Implementation section above.
72+
60
73
content/community/grants-and-bounties/ragnarok-online-on-urbit.md+19−1
@@ -2,7 +2,7 @@
2title = "Ragnarok Online on Urbit"
2title = "Ragnarok Online on Urbit"
3date = 2019-08-30
3date = 2019-08-30
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Other"]
6grant_category = ["App Dev: Other"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -32,4 +32,22 @@ Other potential outcomes:
32- In game chat channels can be mapped to urbit chats, or to urbit itself, meaning you can get in-game code evaluation. Ad-hoc addons for boss fights, guild events, and market trading maybe?
32- In game chat channels can be mapped to urbit chats, or to urbit itself, meaning you can get in-game code evaluation. Ad-hoc addons for boss fights, guild events, and market trading maybe?
33- An emergent reputation system - players won't want to join servers that have corrupt GMs or excessive botting, since those servers will likely be blacklisted and your character won't be transferable. Servers might also identify stars that sell planets to gold sellers and ban planets under them.
33- An emergent reputation system - players won't want to join servers that have corrupt GMs or excessive botting, since those servers will likely be blacklisted and your character won't be transferable. Servers might also identify stars that sell planets to gold sellers and ban planets under them.
34- Patreon-esque donation system when we get bitcoin wallet support.
34- Patreon-esque donation system when we get bitcoin wallet support.
35+
36+## Milestones
37+
38+
39+### Gall app
40+1 stars
41+A gall app that handles updates to all linked character states and relevant game state. The data model should be constructed with an eye towards supporting multiple games and permissioning
42+
43+
44+### Frontend UI
45+1 stars
46+Character and game state display. Should be able to view various server and character stats as well as read chat channels. Character creation and account deletion as well.
47+
48+
49+### Working connection to RO server
50+1 stars
51+A customized urbit RO server that only accepts @p logins and a documented communication pattern with the gall app.
52+
35
53
content/community/grants-and-bounties/search-in-groups.md+14−1
@@ -2,7 +2,7 @@
2title = "Search in groups"
2title = "Search in groups"
3date = 2021-02-25
3date = 2021-02-25
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Other"]
6grant_category = ["App Dev: Other"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -25,4 +25,17 @@ The user-facing interface would be a shoe app where you enter your search word i
25This basic version of search only searches for exact word from post, when limited between whitespace and contains English characters. Later iterations will bring more improvements.
25This basic version of search only searches for exact word from post, when limited between whitespace and contains English characters. Later iterations will bring more improvements.
26
26
27There will also be a generator with nearly same functionality but it's stateless so could only search specified fixed nr. of posts.
27There will also be a generator with nearly same functionality but it's stateless so could only search specified fixed nr. of posts.
28+
29+## Milestones
30+
31+
32+### search generator done
33+1 stars
34+↑
35+
36+
37+### shoe app done
38+1 stars
39+↑
40+
28
41
content/community/grants-and-bounties/staff-the-urbit-help-desk-1.md+8
@@ -50,4 +50,12 @@ Repos to file issues:
50- It may be requested that staffers modify their hours to improve coverage of issues.
50- It may be requested that staffers modify their hours to improve coverage of issues.
51- Estimated work: 2 - 4 hours per day
51- Estimated work: 2 - 4 hours per day
52
52
53+
54+## Milestones
55+
56+
57+### You have been staffing a help desk for 30 days
58+1 stars
59+You have been responsive daily for 30 days.
60+
53
61
content/community/grants-and-bounties/staff-the-urbit-help-desk-2.md+8
@@ -50,4 +50,12 @@ Repos to file issues:
50- It may be requested that staffers modify their hours to improve coverage of issues.
50- It may be requested that staffers modify their hours to improve coverage of issues.
51- Estimated work: 2 - 4 hours per day
51- Estimated work: 2 - 4 hours per day
52
52
53+
54+## Milestones
55+
56+
57+### You have been staffing a help desk for 30 days
58+1 stars
59+You have been responsive daily for 30 days.
60+
53
61
content/community/grants-and-bounties/staff-the-urbit-helpdesk-east.md+11−3
@@ -1,6 +1,6 @@
1+++
1+++
2title = "Staff the Urbit Helpdesk, East"
2title = "Staff the Urbit Helpdesk, East"
3−date = 2020-12-03
3+date = 2021-01-25
4[taxonomies]
4[taxonomies]
5grant_type = ["bounty"]
5grant_type = ["bounty"]
6grant_category = ["Community"]
6grant_category = ["Community"]
@@ -8,8 +8,8 @@ grant_category = ["Community"]
8image = ""
8image = ""
9description = "Help guide newcomers onto the network."
9description = "Help guide newcomers onto the network."
10reward = 1
10reward = 1
11−assignee = "~ritfed-tabryg"
11+assignee = "~libmud-bonted"
12−id = "1282409899"
12+id = "1140084926"
13completed = false
13completed = false
14link = ""
14link = ""
15+++
15+++
@@ -49,4 +49,12 @@ It will help if you identify yourself periodically as a support resource so that
49
49
50
50
51
51
52+
53+## Milestones
54+
55+
56+### Work Complete
57+1 stars
58+You've spent the last month helping out newcomers.
59+
52
60
content/community/grants-and-bounties/staff-the-urbit-helpdesk-west.md+8
@@ -46,4 +46,12 @@ It will help if you identify yourself periodically as a support resource so that
46- Claimant will be online and responsive, 4 hours daily, for 30 days
46- Claimant will be online and responsive, 4 hours daily, for 30 days
47- It may be requested that staffers modify their hours to improve coverage of issues.
47- It may be requested that staffers modify their hours to improve coverage of issues.
48- Estimated work: 2 - 4 hours per day
48- Estimated work: 2 - 4 hours per day
49+
50+## Milestones
51+
52+
53+### Work Complete
54+1 stars
55+You've spent the last month helping out newcomers.
56+
49
57
content/community/grants-and-bounties/the-complete-guide-to-gall-and-landscape.md+15−1
@@ -2,7 +2,7 @@
2title = "The Complete Guide to Gall and Landscape"
2title = "The Complete Guide to Gall and Landscape"
3date = 2020-06-22
3date = 2020-06-22
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Documentation"]
6grant_category = ["Documentation"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -60,4 +60,18 @@ The student who completes this course will not only be able to author their own
60
60
61## Video Materials
61## Video Materials
62* 5 Lessons of 2-3 hours in length each, taught on a weekly basis to help students through the material who are more interactive learners.
62* 5 Lessons of 2-3 hours in length each, taught on a weekly basis to help students through the material who are more interactive learners.
63+
64+## Milestones
65+
66+
67+### Written Guide
68+1 stars
69+Full written guide (table of contents in proposal) posted online.
70+
71+
72+### Videos Courses & Full Sample Application
73+1 stars
74+* Videos made for the course
75+* Full sample application finished and polished with extensive commenting, integrated into the lessons
76+
63
77
content/community/grants-and-bounties/thread-documentation.md+8
@@ -64,4 +64,12 @@ This can be thin for now, because most necessary thread functions are in `lib/st
64
64
65## resources available
65## resources available
66`~timluc-miptev` will be available to whomever does the bounty to explain things, work through any tough spots, and connect to useful people if necessary.
66`~timluc-miptev` will be available to whomever does the bounty to explain things, work through any tough spots, and connect to useful people if necessary.
67+
68+## Milestones
69+
70+
71+### Complete the bounty
72+1 stars
73+Everything in "sections" is done.
74+
67
75
content/community/grants-and-bounties/tor-nodes-relay-search-tile.md+8
@@ -35,4 +35,12 @@ We would like to create an Urbit-native Tor node relay search tool which replica
35- Successful completion of this bounty may result in an invitation to complete other API integration bounties.
35- Successful completion of this bounty may result in an invitation to complete other API integration bounties.
36
36
37
37
38+
39+## Milestones
40+
41+
42+### Your PR is merged
43+3 stars
44+Your code is accepted and merged.
45+
38
46
content/community/grants-and-bounties/translate-key-parts-of-urbitorg-into-german.md+9−1
@@ -2,7 +2,7 @@
2title = "Translate key parts of Urbit.org into German"
2title = "Translate key parts of Urbit.org into German"
3date = 2021-01-19
3date = 2021-01-19
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Documentation"]
6grant_category = ["Documentation"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -19,4 +19,12 @@ Analog to https://grants.urbit.org/proposals/1921641407-translate-key-parts-of-u
19Files could be sent in Markdown as PR to the urbit/docs repository or be transmitted via Email.
19Files could be sent in Markdown as PR to the urbit/docs repository or be transmitted via Email.
20
20
21I am a native German speaker with a long history of speaking and writing English and currently assisting in the translation team of a worldwide operating education and development enterprise, doing both written translation as well as live interpretation.
21I am a native German speaker with a long history of speaking and writing English and currently assisting in the translation team of a worldwide operating education and development enterprise, doing both written translation as well as live interpretation.
22+
23+## Milestones
24+
25+
26+### Translation of Key Website Content
27+1 stars
28+Introduction, Urbit OS, Urbit ID, Interface, Roadmap: OS1-> OS N, People + History, and Install + Setup
29+
22
30
content/community/grants-and-bounties/translate-key-parts-of-urbitorg-into-korean.md+9−1
@@ -2,7 +2,7 @@
2title = "Translate key parts of Urbit.org into Korean"
2title = "Translate key parts of Urbit.org into Korean"
3date = 2021-01-30
3date = 2021-01-30
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Documentation"]
6grant_category = ["Documentation"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -20,4 +20,12 @@ I am a native English speaker with a high level of competence in written Korean.
20
20
21At the current pace we are translating a little under 1000 words per week. The total amount to be translated is a little over 9000 words.
21At the current pace we are translating a little under 1000 words per week. The total amount to be translated is a little over 9000 words.
22
22
23+
24+## Milestones
25+
26+
27+### Translation of Key Website Content
28+1 stars
29+Introduction, Urbit OS, Urbit ID, Interface, Roadmap: OS1-> OS N, People + History, and Install + Setup
30+
23
31
content/community/grants-and-bounties/translate-key-parts-of-urbitorg-into-norwegian.mdnew file+31
@@ -0,0 +1,31 @@
1++++
2+title = "Translate key parts of Urbit.org into Norwegian"
3+date = 2021-04-07
4+[taxonomies]
5+grant_type = ["grant"]
6+grant_category = ["Community"]
7+[extra]
8+image = ""
9+description = "Help the Urbit community grow internationally by translating key resources, guides, and documentation to Norwegian."
10+reward = 1
11+assignee = "Andreas Atakan"
12+id = "1227012285"
13+completed = false
14+link = ""
15++++
16+
17+Similar to other translation proposals for German, Korean and Spanish, I would provide the core parts of the Documentation in Norwegian, in order to improve accessibility of the Urbit project.
18+Translations can for example be provided as pull requests to the urbit.org repo.
19+
20+I am a native speaker of Norwegian and have lived in Norway my whole life. I also speak English fluently.
21+I have extensive technical experience working as a full-stack web-developer, and specialized experience from several years working as a GIS consultant in the off-shore sector in Norway. I also have experience working with blockchain technologies, and I'm currently hosting a bitcoin- and lightning-node on a hobby basis.
22+In addition to contributing with my translation work, I can also contribute to the Urbit community with my experience of integrating dynamic web-maps into web-applications (like for example React-based apps).
23+
24+## Milestones
25+
26+
27+### Translation of key site content
28+1 stars
29+Introduction, Urbit OS, Urbit ID, Interface, Roadmap: OS1-> OS N, People + History, and Install + Setup
30+
31+
content/community/grants-and-bounties/translate-key-parts-of-urbitorg-into-spanish.md+9−1
@@ -2,7 +2,7 @@
2title = "Translate key parts of Urbit.org into Spanish"
2title = "Translate key parts of Urbit.org into Spanish"
3date = 2021-03-20
3date = 2021-03-20
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Documentation"]
6grant_category = ["Documentation"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -19,4 +19,12 @@ Similar to other translation proposals for German and Korean, this would provide
19Translations can be provided as pull requests to the urbit.org repo, or whatever is convenient for the team managing the resource.
19Translations can be provided as pull requests to the urbit.org repo, or whatever is convenient for the team managing the resource.
20
20
21I am a fluent speaker with 20+ years of experience with the language and have lived in a handful of Spanish-speaking locales for several years. With professional experience as a programmer and teacher, I am skilled at breaking down complex technical concepts to new learners.
21I am a fluent speaker with 20+ years of experience with the language and have lived in a handful of Spanish-speaking locales for several years. With professional experience as a programmer and teacher, I am skilled at breaking down complex technical concepts to new learners.
22+
23+## Milestones
24+
25+
26+### Translation of key site content
27+1 stars
28+Introduction, Urbit OS, Urbit ID, Interface, Roadmap: OS1-> OS N, People + History, and Install + Setup
29+
22
30
content/community/grants-and-bounties/try-urbit-website.md+9−1
@@ -2,7 +2,7 @@
2title = "Try Urbit Website"
2title = "Try Urbit Website"
3date = 2021-02-14
3date = 2021-02-14
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Other"]
6grant_category = ["App Dev: Other"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -21,4 +21,12 @@ The server will run a script that "pre-mines" comets to create a pool of IDs and
21The server will also maintain a database of users, status, comet ID, process ID and timestamp when assigned to user. After a predetermined time (1 day?), the server will send an email asking if the user still wants to keep their comet, then stops the process if they reply no or don't reply after some time.
21The server will also maintain a database of users, status, comet ID, process ID and timestamp when assigned to user. After a predetermined time (1 day?), the server will send an email asking if the user still wants to keep their comet, then stops the process if they reply no or don't reply after some time.
22
22
23The website will have an admin interface with performance stats. It will also allow admins to set up email alerts on usage, processes, comet pool, etc.
23The website will have an admin interface with performance stats. It will also allow admins to set up email alerts on usage, processes, comet pool, etc.
24+
25+## Milestones
26+
27+
28+### Project complete
29+2 stars
30+Website and sever side scripts complete and deployed.
31+
24
32
content/community/grants-and-bounties/typescript-airlock-library.md+8
@@ -33,4 +33,12 @@ Additionally, write a one-page explanation for the design choices for this libra
33- When applying to work on the bounty, tell us a little about yourself and some projects you’ve worked on in the past.
33- When applying to work on the bounty, tell us a little about yourself and some projects you’ve worked on in the past.
34- You have 90 days from the time of approval to complete this bounty.
34- You have 90 days from the time of approval to complete this bounty.
35- Successful completion of this bounty may result in an invitation to complete other Airlock library bounties. If you are interested in creating an Airlock library for a language other than the ones currently presented, please contact us at grants@urbit.org; it’s likely we’ll approve this as a proposal.
35- Successful completion of this bounty may result in an invitation to complete other Airlock library bounties. If you are interested in creating an Airlock library for a language other than the ones currently presented, please contact us at grants@urbit.org; it’s likely we’ll approve this as a proposal.
36+
37+## Milestones
38+
39+
40+### Your work is finished
41+3 stars
42+You have completed your work and pushed it to a Github repo.
43+
36
44
content/community/grants-and-bounties/udon-syntax-highlighter.md+8
@@ -31,4 +31,12 @@ Write a CodeMirror language-mode file that results in correct syntax highlightin
31#### Contribution Guidelines
31#### Contribution Guidelines
32
32
33* Your submission should come in the form of a single JavaScript file. Email the submission to grants@urbit.org
33* Your submission should come in the form of a single JavaScript file. Email the submission to grants@urbit.org
34+
35+## Milestones
36+
37+
38+### The highlighter is complete
39+1 stars
40+The highlighter has been finished and tested, and the language-mode file is finished.
41+
34
42
content/community/grants-and-bounties/unit-tests-for-json-parsing.md+8
@@ -38,4 +38,12 @@ Save the test files in the `/tests/sys/hoon` directory in Arvo. Use the same fra
38* Your tests should be written as two files: one file for `+format` functions and one file for `+html` functions.
38* Your tests should be written as two files: one file for `+format` functions and one file for `+html` functions.
39* Write the appropriate number of unit tests per function. Some arms will only need one test, but some arms may or may not require more. An insufficient number of tests for arms may result in your submission being rejected.
39* Write the appropriate number of unit tests per function. Some arms will only need one test, but some arms may or may not require more. An insufficient number of tests for arms may result in your submission being rejected.
40* Submit your tests as a PR to the [“urbit” repository](https://github.com/urbit/urbit). Your test file should be under `pkg/arvo/tests/sys/hoon` within the repository. Link this bounty in the PR’s description.
40* Submit your tests as a PR to the [“urbit” repository](https://github.com/urbit/urbit). Your test file should be under `pkg/arvo/tests/sys/hoon` within the repository. Link this bounty in the PR’s description.
41+
42+## Milestones
43+
44+
45+### Test files are merged
46+2 stars
47+Your test files are accepted and merged on GitHub.
48+
41
49
content/community/grants-and-bounties/unit-tests-for-pure-algorithms.md+8
@@ -50,4 +50,12 @@ Save the test files in the `/tests/sys/hoon` directory in Arvo. Use the same fra
50* Submit your tests as a PR to the [“urbit” repository](https://github.com/urbit/urbit). Your test file should be under `pkg/arvo/tests/sys/hoon` within the repository. Link this bounty in the PR’s description.
50* Submit your tests as a PR to the [“urbit” repository](https://github.com/urbit/urbit). Your test file should be under `pkg/arvo/tests/sys/hoon` within the repository. Link this bounty in the PR’s description.
51* You have 30 days from the time of approval to complete this bounty.
51* You have 30 days from the time of approval to complete this bounty.
52
52
53+
54+## Milestones
55+
56+
57+### Test files are merged
58+1 stars
59+Your test files are accepted and merged on GitHub.
60+
53
61
content/community/grants-and-bounties/unit-tests-for-sha-functions.md+8
@@ -39,4 +39,12 @@ Save the test file in the `/tests/sys/hoon` directory in Arvo. Use the same fram
39* Your tests should be written as one file.
39* Your tests should be written as one file.
40* Write the appropriate number of unit tests per function. Some arms will only need one test, but some arms may or may not require more. An insufficient number of tests for arms may result in your submission being rejected.
40* Write the appropriate number of unit tests per function. Some arms will only need one test, but some arms may or may not require more. An insufficient number of tests for arms may result in your submission being rejected.
41* Submit your tests as a PR to the [“urbit” repository](https://github.com/urbit/urbit). Your test file should be under `pkg/arvo/tests/sys/hoon` within the repository. Link this bounty in the PR’s description.
41* Submit your tests as a PR to the [“urbit” repository](https://github.com/urbit/urbit). Your test file should be under `pkg/arvo/tests/sys/hoon` within the repository. Link this bounty in the PR’s description.
42+
43+## Milestones
44+
45+
46+### Your test file is merged
47+1 stars
48+Your test file for all the relevant functions is accepted and merged.
49+
42
50
content/community/grants-and-bounties/unit-tests-for-zuse-cryptographic-functions.md+8
@@ -41,4 +41,12 @@ Save the test files in the `tests/sys/zuse/crypto` directory in Arvo. Use the sa
41* You have 60 days from acceptance to complete this bounty.
41* You have 60 days from acceptance to complete this bounty.
42* Write the appropriate number of unit tests per function. Some arms will only need one test, but some arms may or may not require more. An insufficient number of tests for arms may result in your submission being rejected.
42* Write the appropriate number of unit tests per function. Some arms will only need one test, but some arms may or may not require more. An insufficient number of tests for arms may result in your submission being rejected.
43* Submit your tests as a PR to the [“urbit” repository](https://github.com/urbit/urbit). Your test file should be under `pkg/arvo/tests/sys/hoon` within the repository. Link this bounty in the PR’s description.
43* Submit your tests as a PR to the [“urbit” repository](https://github.com/urbit/urbit). Your test file should be under `pkg/arvo/tests/sys/hoon` within the repository. Link this bounty in the PR’s description.
44+
45+## Milestones
46+
47+
48+### Your test file is merged
49+1 stars
50+Your test file for all the relevant functions is accepted and merged.
51+
44
52
content/community/grants-and-bounties/up-to-date-hoon-reference-card.md+10−2
@@ -2,11 +2,11 @@
2title = "Up-to-date Hoon reference card"
2title = "Up-to-date Hoon reference card"
3date = 2020-03-15
3date = 2020-03-15
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Documentation"]
6grant_category = ["Documentation"]
7[extra]
7[extra]
8image = ""
8image = ""
9−description = "I have made an up-to-date version of the Urbit Hoon reference card and will maintain it."
9+description = "I have made an up-to-date version of the Urbit Hoon reference card and will maintain it.https://github.com/natareo/hooncard"
10reward = 1
10reward = 1
11assignee = "N E Davis"
11assignee = "N E Davis"
12id = "607772785"
12id = "607772785"
@@ -19,4 +19,12 @@ I have made and will maintain an up-to-date Urbit Hoon reference card. (I am se
19You can see the current version here: https://github.com/natareo/hooncard/blob/master/hooncard.pdf
19You can see the current version here: https://github.com/natareo/hooncard/blob/master/hooncard.pdf
20
20
21I put 1 star, but, whatever, I don't really think this is worth a whole star—I was encouraged to put this up as a proposal, which has the added benefit of making Tlon aware that this now exists. But if not, a Nock shirt or the like would be nice.
21I put 1 star, but, whatever, I don't really think this is worth a whole star—I was encouraged to put this up as a proposal, which has the added benefit of making Tlon aware that this now exists. But if not, a Nock shirt or the like would be nice.
22+
23+## Milestones
24+
25+
26+### Make card public
27+1 stars
28+Make an accurate, up-to-date Hoon reference card available.
29+
22
30
content/community/grants-and-bounties/urbian-a-customized-linux-distribution-for-urbit-appliances.md+14−1
@@ -2,7 +2,7 @@
2title = "Urbian: a customized Linux distribution for Urbit appliances"
2title = "Urbian: a customized Linux distribution for Urbit appliances"
3date = 2020-10-06
3date = 2020-10-06
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Dev Tool"]
6grant_category = ["Dev Tool"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -70,4 +70,17 @@ It has the potential to evolve into a system that makes it easier for users to s
70
70
71The development of this backend will support UX experiments with a frontend meant to create a user friendly, turnkey-style Urbit device.
71The development of this backend will support UX experiments with a frontend meant to create a user friendly, turnkey-style Urbit device.
72
72
73+
74+## Milestones
75+
76+
77+### An Armbian userpatches overlay for Urbit
78+1 stars
79+Overlay with scripts and services integrated, used to create an image for installation to a device, which will setup Urbit upon being booted.
80+
81+
82+### Demo of image generation and boot
83+1 stars
84+Blog style write-up of how to create an image with the Armbian build tool, flashing it to a device, and how it might work with a simple frontend to communicate with the user.
85+
73
86
content/community/grants-and-bounties/urbit-api-for-elixir.md+19−1
@@ -2,7 +2,7 @@
2title = "Urbit API for Elixir"
2title = "Urbit API for Elixir"
3date = 2021-02-11
3date = 2021-02-11
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Other"]
6grant_category = ["App Dev: Other"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -17,4 +17,22 @@ link = ""
17Elixir is an increasingly popular language with state of the art concurrency, based on the Erlang BEAM VM, and it's also a functional language with one of the most attractive syntaxes out there.
17Elixir is an increasingly popular language with state of the art concurrency, based on the Erlang BEAM VM, and it's also a functional language with one of the most attractive syntaxes out there.
18
18
19I am a web developer fluent in Ruby, JS, and working mainly with elixir for the last 5 years. I am also an Urbit user since 2019, and have already built small apps using the Urbit HTTP API to automate some tasks on my groups. I am very excited to build a full API and bring the whole functionality of the BEAM to the Urbit community.
19I am a web developer fluent in Ruby, JS, and working mainly with elixir for the last 5 years. I am also an Urbit user since 2019, and have already built small apps using the Urbit HTTP API to automate some tasks on my groups. I am very excited to build a full API and bring the whole functionality of the BEAM to the Urbit community.
20+
21+## Milestones
22+
23+
24+### Basic HTTP Interface
25+1 stars
26+Enabling a basic interface to send/receive json to a running Urbit ship.
27+
28+
29+### Graph Store
30+1 stars
31+Enabling full interactivity with the graph-store HTTP endpoints.
32+
33+
34+### Other Gall Apps
35+1 stars
36+Reach all available endpoints for other Gall apps such as hark-store, metadata-store, etc.
37+
20
38
content/community/grants-and-bounties/urbit-community-concierge-east-coast-2q2021.mdnew file+35
@@ -0,0 +1,35 @@
1++++
2+title = "Urbit Community Concierge - East Coast - 2Q2021"
3+date = 2021-04-27
4+[taxonomies]
5+grant_type = ["bounty"]
6+grant_category = ["Community"]
7+[extra]
8+image = ""
9+description = "Provide concierge service assisting new users in the Urbit Community Group"
10+reward = 1
11+assignee = "tocrex"
12+id = "427340266"
13+completed = false
14+link = ""
15++++
16+
17+Provide concierge service assisting new users in the Urbit Community Group, particularly the General, Watercooler, Help, and Community Formation channels. Identify yourself periodically as a support resource on these channels so that users know they can ask questions of you. Using a nickname could be helpful here.
18+
19+Applicants should:
20+
21+- know the "big picture" of Urbit well.
22+- be able to answer general questions about the structure and purpose of Urbit and Landscape.
23+- keep up with community and be able to recommend public groups, events, people to connect with, etc.
24+- have general information available (FAQ, Eth/gas prices, Urbit documentation, etc.)
25+- encourage and help new members to start a new group and publicize it in the Directory
26+- send a weekly digest email to mike@urbit.org, with a report of key events, most frequently asked questions, and hours worked
27+
28+## Milestones
29+
30+
31+### Complete 240 hours of concierge service
32+1 stars
33+Complete 12 weeks, 5 days/week, 4 hours/day of concierge service in the UC group
34+
35+
content/community/grants-and-bounties/urbit-community-concierge-east-coast.md+8
@@ -23,4 +23,12 @@ Applicants should:
23- have general information available (FAQ, Eth/gas prices, Urbit documentation, etc.)
23- have general information available (FAQ, Eth/gas prices, Urbit documentation, etc.)
24- encourage and help new members to start a new group and publicize it in the Directory
24- encourage and help new members to start a new group and publicize it in the Directory
25- send a weekly digest email to support@urbit.org, with a report of key events, most frequently asked questions, and hours worked
25- send a weekly digest email to support@urbit.org, with a report of key events, most frequently asked questions, and hours worked
26+
27+## Milestones
28+
29+
30+### 80 hours of concierge service
31+1 stars
32+Provide concierge service for 4 hours/day, 5 days/week, for 4 weeks during prime East Coast hours
33+
26
34
content/community/grants-and-bounties/urbit-community-concierge-west-coast-2q2021.mdnew file+35
@@ -0,0 +1,35 @@
1++++
2+title = "Urbit Community Concierge - West Coast - 2Q2021"
3+date = 2021-04-27
4+[taxonomies]
5+grant_type = ["bounty"]
6+grant_category = ["Community"]
7+[extra]
8+image = ""
9+description = "Provide concierge service assisting new users in the Urbit Community Group"
10+reward = 1
11+assignee = "~sibhul-soctul"
12+id = "1693084001"
13+completed = false
14+link = ""
15++++
16+
17+Provide concierge service assisting new users in the Urbit Community Group, particularly the General, Watercooler, Help, and Community Formation channels. Identify yourself periodically as a support resource on these channels so that users know they can ask questions of you. Using a nickname could be helpful here.
18+
19+Applicants should:
20+
21+- know the "big picture" of Urbit well.
22+- be able to answer general questions about the structure and purpose of Urbit and Landscape.
23+- keep up with community and be able to recommend public groups, events, people to connect with, etc.
24+- have general information available (FAQ, Eth/gas prices, Urbit documentation, etc.)
25+- encourage and help new members to start a new group and publicize it in the Directory
26+- send a weekly digest email to mike@urbit.org, with a report of key events, most frequently asked questions, and hours worked
27+
28+## Milestones
29+
30+
31+### Complete 240 hours concierge service
32+1 stars
33+Complete 12 weeks, 5 days/week, 4 hours/day concierge service during west coast hours
34+
35+
content/community/grants-and-bounties/urbit-community-concierge-west-coast.md+8
@@ -23,4 +23,12 @@ Applicants should:
23- have general information available (FAQ, Eth/gas prices, Urbit documentation, etc.)
23- have general information available (FAQ, Eth/gas prices, Urbit documentation, etc.)
24- encourage and help new members to start a new group and publicize it in the Directory
24- encourage and help new members to start a new group and publicize it in the Directory
25- send a weekly digest email to support@urbit.org, with a report of key events, most frequently asked questions, and hours worked
25- send a weekly digest email to support@urbit.org, with a report of key events, most frequently asked questions, and hours worked
26+
27+## Milestones
28+
29+
30+### 80 hours of concierge service
31+1 stars
32+Provide concierge service for 4 hours/day, 5 days/week, for 4 weeks during prime West Coast hours
33+
26
34
content/community/grants-and-bounties/urbit-event-series.md+19−1
@@ -2,7 +2,7 @@
2title = "Urbit Event Series"
2title = "Urbit Event Series"
3date = 2020-10-11
3date = 2020-10-11
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Community"]
6grant_category = ["Community"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -69,4 +69,22 @@ Deliverable: A one day virtual summit, this will be the first public Urbit confe
69Scope of work: Act as project manager for the event. Consult with Tlon, community members, event staff/volunteers, and speakers to finalize event schedule and budget, and plan event logistics. Review applications for speaking slots and develop process to allocate speaking slots. Recruit guest speakers. Work with speakers to review and prepare talks and decks. Design the event agenda. Design sponsorship packages and recruit sponsors. Host and emcee event itself. Work with production company to record all talks in high definition, edit recordings, and share them after the event. Ensure that the event produces a high-quality, on-brand knowledge base of material on “all things Urbit.” Work with artist to plan the artistic component of the event. Post event recap, along with recordings.
69Scope of work: Act as project manager for the event. Consult with Tlon, community members, event staff/volunteers, and speakers to finalize event schedule and budget, and plan event logistics. Review applications for speaking slots and develop process to allocate speaking slots. Recruit guest speakers. Work with speakers to review and prepare talks and decks. Design the event agenda. Design sponsorship packages and recruit sponsors. Host and emcee event itself. Work with production company to record all talks in high definition, edit recordings, and share them after the event. Ensure that the event produces a high-quality, on-brand knowledge base of material on “all things Urbit.” Work with artist to plan the artistic component of the event. Post event recap, along with recordings.
70
70
71**Who am I?** I work full time for a blockchain project called Spacemesh in a hybrid role as a core developer, and as an evangelist/community organizer. I previously worked as an Ethereum core developer 2017-2019, and during my time working on Ethereum, I helped organize a number of community events, online and offline, around the world. I've attended dozens of technical conferences and hackathons. I also co-founded a blockchain co-working space and community based in New York and have hosted dozens of events as part of that community.
71**Who am I?** I work full time for a blockchain project called Spacemesh in a hybrid role as a core developer, and as an evangelist/community organizer. I previously worked as an Ethereum core developer 2017-2019, and during my time working on Ethereum, I helped organize a number of community events, online and offline, around the world. I've attended dozens of technical conferences and hackathons. I also co-founded a blockchain co-working space and community based in New York and have hosted dozens of events as part of that community.
72+
73+## Milestones
74+
75+
76+### Phase I: Developer calls
77+1 stars
78+An introductory series of 3-4 developer calls for the Urbit community. See Details for more information and scope of work.
79+
80+
81+### Phase II: Town Hall
82+2 stars
83+A one-off, 2-3 hour “town hall” event that will be appropriate for both a technical and a non-technical audience. See Details for more information and scope of work.
84+
85+
86+### Phase III: UrbitCon
87+3 stars
88+A daylong virtual summit, the first public Urbit conference. See Details for more information and scope of work.
89+
72
90
content/community/grants-and-bounties/urbit-explainer-video.md+9−1
@@ -2,7 +2,7 @@
2title = "Urbit Explainer Video"
2title = "Urbit Explainer Video"
3date = 2020-09-13
3date = 2020-09-13
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Community"]
6grant_category = ["Community"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -23,4 +23,12 @@ Contrasting the original [Tlon-produced explainer](https://www.youtube.com/watch
23~rivpyl-sidfyl: I am experienced in video, audio and animation work.
23~rivpyl-sidfyl: I am experienced in video, audio and animation work.
24I'll try my best in translating and adapting our idea to the audiovisual medium.
24I'll try my best in translating and adapting our idea to the audiovisual medium.
25Here's a short video [reel](https://streamable.com/lpzh4s) showcasing some of my recent work.
25Here's a short video [reel](https://streamable.com/lpzh4s) showcasing some of my recent work.
26+
27+## Milestones
28+
29+
30+### It's Done
31+2 stars
32+We publish the finalized video, after developing a working storyboard that has been reviewed and shared with people that might add relevant perspectives to the project.
33+
26
34
content/community/grants-and-bounties/urbit-http-api-for-emacs-elisp.md+19−1
@@ -2,7 +2,7 @@
2title = "Urbit HTTP API for Emacs (elisp)"
2title = "Urbit HTTP API for Emacs (elisp)"
3date = 2021-01-18
3date = 2021-01-18
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Dev Tool"]
6grant_category = ["Dev Tool"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -17,4 +17,22 @@ link = ""
17I've been poking around in Emacs to test the feasibility of this project, and I think it will work out pretty well. The biggest obstacle I found was the lack of SSE client library, but I already have a solution.
17I've been poking around in Emacs to test the feasibility of this project, and I think it will work out pretty well. The biggest obstacle I found was the lack of SSE client library, but I already have a solution.
18
18
19 Milestones have been adapted from this google doc: https://docs.google.com/document/d/1no5oos_NE8LrUWz7iG9SKZMTIzruZVevZQ75nD5OHmI/edit
19 Milestones have been adapted from this google doc: https://docs.google.com/document/d/1no5oos_NE8LrUWz7iG9SKZMTIzruZVevZQ75nD5OHmI/edit
20+
21+## Milestones
22+
23+
24+### Basic HTTP Interface
25+1 stars
26+Implementation of the HTTP interface to send JSON to/from an Urbit ship.
27+
28+
29+### Graph Store Interface
30+1 stars
31+Implementation of graph-store interface.
32+
33+
34+### Additional Agent Interfaces
35+1 stars
36+Implementation of at least two of the following interfaces: contact-store, invite-store, group-store, and metadata-store.
37+
20
38
content/community/grants-and-bounties/urbit-http-api-for-kotlin.md+19−1
@@ -2,7 +2,7 @@
2title = "Urbit HTTP API for Kotlin"
2title = "Urbit HTTP API for Kotlin"
3date = 2020-10-27
3date = 2020-10-27
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Other"]
6grant_category = ["App Dev: Other"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -16,4 +16,22 @@ link = ""
16
16
17This proposal project will produce urbit HTTP API in Kotlin language with [these requirements](https://docs.google.com/document/d/1no5oos_NE8LrUWz7iG9SKZMTIzruZVevZQ75nD5OHmI/edit) in mind.
17This proposal project will produce urbit HTTP API in Kotlin language with [these requirements](https://docs.google.com/document/d/1no5oos_NE8LrUWz7iG9SKZMTIzruZVevZQ75nD5OHmI/edit) in mind.
18
18
19+
20+## Milestones
21+
22+
23+### HTTP interface
24+1 stars
25+HTTP interface for sending and receiving JSON from Kotlin programs
26+
27+
28+### graph-store interface
29+1 stars
30+graph-store interface for interacting with urbit's general purpose data storage model
31+
32+
33+### agents interfaces
34+1 stars
35+metadata-store and group-store agents interfaces
36+
19
37
content/community/grants-and-bounties/urbit-http-api-for-rust.md+19−1
@@ -2,7 +2,7 @@
2title = "Urbit HTTP API for Rust"
2title = "Urbit HTTP API for Rust"
3date = 2020-12-16
3date = 2020-12-16
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Other"]
6grant_category = ["App Dev: Other"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -35,4 +35,22 @@ While doing research/testing into the complexity of building out such a http api
35
35
36From a quick look-over, milestones 2/3 do not seem too complex either, however I am also working full-time in tandem, and so my spare dev time is limited. As such the 2nd/3rd milestones are pushed out a bit further to provide some lee-way to ensure they're delivered on time.
36From a quick look-over, milestones 2/3 do not seem too complex either, however I am also working full-time in tandem, and so my spare dev time is limited. As such the 2nd/3rd milestones are pushed out a bit further to provide some lee-way to ensure they're delivered on time.
37
37
38+
39+## Milestones
40+
41+
42+### Basic HTTP Interface
43+1 stars
44+Implementation of the HTTP Interface responsible for sending and receiving JSON to/from an Urbit ship
45+
46+
47+### Graph Store Interface
48+1 stars
49+Implementation of the interface to `graph-store`, which sits on top of the HTTP Interface
50+
51+
52+### Additional Agent Interfaces
53+1 stars
54+Implementation of the `group-store` and `metadata-store` Gall agents.
55+
38
56
content/community/grants-and-bounties/urbit-http-interface-java-edition.md+19−1
@@ -2,7 +2,7 @@
2title = "Urbit HTTP Interface — Java Edition"
2title = "Urbit HTTP Interface — Java Edition"
3date = 2020-10-20
3date = 2020-10-20
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Core Dev"]
6grant_category = ["Core Dev"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -48,4 +48,22 @@ I'm qualified to implement this because I am experienced with Java. I have used
48
48
49 My github profile is at https://github.com/ynx0, where I have written software projects in other languages, such as a parser/interpreter combo for a fantasy assembly language.
49 My github profile is at https://github.com/ynx0, where I have written software projects in other languages, such as a parser/interpreter combo for a fantasy assembly language.
50
50
51+
52+## Milestones
53+
54+
55+### Basic HTTP Interface
56+1 stars
57+Implementation of the HTTP Interface responsible for sending and receiving JSON to/from an Urbit ship
58+
59+
60+### Graph Store Interface
61+1 stars
62+Implementation of the interface to `graph-store`, which sits on top of the HTTP Interface
63+
64+
65+### Additional Agent Interfaces
66+1 stars
67+Implementation of the `group-store` and `metadata-store` Gall agents
68+
51
69
content/community/grants-and-bounties/urbit-http-library-for-ruby.md+19−1
@@ -2,7 +2,7 @@
2title = "Urbit HTTP Library for Ruby"
2title = "Urbit HTTP Library for Ruby"
3date = 2020-11-05
3date = 2020-11-05
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Dev Tool"]
6grant_category = ["Dev Tool"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -18,4 +18,22 @@ Patterned per document:
18https://docs.google.com/document/d/1no5oos_NE8LrUWz7iG9SKZMTIzruZVevZQ75nD5OHmI/edit.
18https://docs.google.com/document/d/1no5oos_NE8LrUWz7iG9SKZMTIzruZVevZQ75nD5OHmI/edit.
19
19
20I am a long-time (20+ years) ruby coder and would love to take this on. I tried my best to ballpark the timeframe off the code I have seen as well as the fact that I still have an pretty full day job. ;) I am open to discussion on the timeframe(s) if it is too long.
20I am a long-time (20+ years) ruby coder and would love to take this on. I tried my best to ballpark the timeframe off the code I have seen as well as the fact that I still have an pretty full day job. ;) I am open to discussion on the timeframe(s) if it is too long.
21+
22+## Milestones
23+
24+
25+### Basic HTTP Interface
26+1 stars
27+This involves building a mechanism for sending and receiving JSON to/from an Urbit ship.
28+
29+
30+### Graph Store Interface
31+1 stars
32+Using the basic HTTP interface referenced above, create an interface to graph-store.
33+
34+
35+### Additional Agent Interfaces
36+1 stars
37+Landscape gall agents that can be interfaced with over the HTTP interface. I will implement at least group-store and contact-store. Time permitting I will also try invite-store and/or metadata-store.
38+
21
39
content/community/grants-and-bounties/urbit-lfs-filehosting.md+32−1
@@ -2,7 +2,7 @@
2title = "Urbit LFS - filehosting"
2title = "Urbit LFS - filehosting"
3date = 2021-03-11
3date = 2021-03-11
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Other"]
6grant_category = ["App Dev: Other"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -34,4 +34,35 @@ When the uploading is finished, the fileserver notifies the provider to update c
34I'm an experienced functional programmer, but amateur hooner. I've read through the Urbit hoon docs, and the GitHub Gall Guide, and I'm starting to appreciate the odd martian soil. I want to try building something real and practical on the platform. I want to run a personal fileserver with my Urbit instead of emailing files and moving USBs.
34I'm an experienced functional programmer, but amateur hooner. I've read through the Urbit hoon docs, and the GitHub Gall Guide, and I'm starting to appreciate the odd martian soil. I want to try building something real and practical on the platform. I want to run a personal fileserver with my Urbit instead of emailing files and moving USBs.
35
35
36After completing an exploratory proof-of-concept, this proposal replaces https://grants.urbit.org/proposals/1760204192 with more detailed project milestones.
36After completing an exploratory proof-of-concept, this proposal replaces https://grants.urbit.org/proposals/1760204192 with more detailed project milestones.
37+
38+## Milestones
39+
40+
41+### Proof of concept
42+1 stars
43+Client – Proivder – Fileserver
44+
45+Client subscribes to a provider, and pokes to request an upload. Provider creates an upload url on the fileserver, and passes it to the client.
46+
47+
48+### Upload limits
49+1 stars
50+Provider tracks uploaded files per client and enforces filesize limits based on groups, %kids, list of ships. Clients store limits locally as well.
51+
52+Fileserver confirms upload to provider
53+
54+
55+### Handle Errors
56+1 stars
57+When any of the servers shutdown, a transaction is either canceled or can be resumed from a checkpoint.
58+
59+Provider can import/export the map from ship to uploaded files to prevent data loss.
60+
61+
62+### Permissions and demo UI
63+1 stars
64+The fileid gives permission to delete the file on the fileserver. Create and manage share-links using fileid. Provider can throttle file requests.
65+
66+Demo html/javascript UI for client to manage files.
67+
37
68
content/community/grants-and-bounties/urbit-online-meetup.md+9−1
@@ -2,7 +2,7 @@
2title = "Urbit online meetup."
2title = "Urbit online meetup."
3date = 2020-06-08
3date = 2020-06-08
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Community"]
6grant_category = ["Community"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -19,4 +19,12 @@ I teach a Python class over Discord to a few friends of mine. Many of them are i
19I would give a lecture or two on Urbit, specifically what it is about the platform that appeals to me. I would then help them though the process of spawning and booting a planet. I would perhaps also even host the planets on a VPS. I would follow up with them afterwards to see that they are not having any issues.
19I would give a lecture or two on Urbit, specifically what it is about the platform that appeals to me. I would then help them though the process of spawning and booting a planet. I would perhaps also even host the planets on a VPS. I would follow up with them afterwards to see that they are not having any issues.
20
20
21Ultimately, it might be nice to move the community over to an Urbit group. The text chat and class transcripts could be hosted there. I would model this closely on Hooniverse, as I think they do that sort of thing very well.
21Ultimately, it might be nice to move the community over to an Urbit group. The text chat and class transcripts could be hosted there. I would model this closely on Hooniverse, as I think they do that sort of thing very well.
22+
23+## Milestones
24+
25+
26+### Urbit Lecture
27+1 stars
28+The Urbit lecture, given by me, as described.
29+
22
30
content/community/grants-and-bounties/urbit-react-cookbook.md+19−1
@@ -2,7 +2,7 @@
2title = "Urbit React Cookbook"
2title = "Urbit React Cookbook"
3date = 2021-04-10
3date = 2021-04-10
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Other"]
6grant_category = ["App Dev: Other"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -25,4 +25,22 @@ The first deliverable is a simple application demonstrating basic subscriptions,
25The first two apps will be very simple and each contained in a single file to keep basic documentation in one place. As such, there will be opportunities for additional instructions such as setting up a React environment, a deeper dive into Hooks, and leveraging things like functional components and Context Provider to help with larger, more complex apps. The third deliverable is aimed to cover these points and address supplementary needs that Tlon identifies while reviewing the first two examples.
25The first two apps will be very simple and each contained in a single file to keep basic documentation in one place. As such, there will be opportunities for additional instructions such as setting up a React environment, a deeper dive into Hooks, and leveraging things like functional components and Context Provider to help with larger, more complex apps. The third deliverable is aimed to cover these points and address supplementary needs that Tlon identifies while reviewing the first two examples.
26
26
27This guide is robust enough for a JavaScript beginner and of course more advanced developers can read from a more general perspective to grok the structure of these development techniques. While this serves Urbit by making it easy for general web developers to start building on Urbit without having to write Hoon, ideologically this guide is aligned and written with Hoon developers in mind.
27This guide is robust enough for a JavaScript beginner and of course more advanced developers can read from a more general perspective to grok the structure of these development techniques. While this serves Urbit by making it easy for general web developers to start building on Urbit without having to write Hoon, ideologically this guide is aligned and written with Hoon developers in mind.
28+
29+## Milestones
30+
31+
32+### First Example App: Groups and Channels
33+1 stars
34+Covering Subscriptions, Pokes, Threads, and Scries to create groups/channels, manage members, and send messages. Delivered as a merged PR into the urbit.org documentation.
35+
36+
37+### Second Example App: Advanced Functions
38+1 stars
39+Notebooks, Collections, and advanced functions not covered in the first app such as parsing mentions and code snippets from channels. Delivered as a merged PR into the urbit.org documentation.
40+
41+
42+### Breakout Lessons
43+1 stars
44+React topics for more complex apps i.e. Context Provider and advanced Hooks. Adding examples Tlon would like to see documented. Delivered as a merged PR into the urbit.org documentation.
45+
28
46
content/community/grants-and-bounties/urbit-ship-and-star-hosting-and-troubleshooting-docs.md+15−2
@@ -2,11 +2,11 @@
2title = "Urbit Ship and Star Hosting and Troubleshooting Docs"
2title = "Urbit Ship and Star Hosting and Troubleshooting Docs"
3date = 2020-08-19
3date = 2020-08-19
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["Documentation"]
6grant_category = ["Documentation"]
7[extra]
7[extra]
8image = ""
8image = ""
9−description = "User docs for ship/star owners around best practices for hosting"
9+description = "Update to: https://grants.urbit.org/proposals/30964804 (post phone call)User docs for ship/star owners around best practices for hosting"
10reward = 2
10reward = 2
11assignee = "~dovsem-bornyl"
11assignee = "~dovsem-bornyl"
12id = "1452740478"
12id = "1452740478"
@@ -21,4 +21,17 @@ This proposal is for getting the above docs into the official Urbit install docu
21Then when that's merged, to use the star from that milestone to similarly document the best practices for hosting a star and common star workflows (escaping, bridge, OTAs). This will include relevant troubleshooting commands that are helpful for someone hosting a star to debug common issues.
21Then when that's merged, to use the star from that milestone to similarly document the best practices for hosting a star and common star workflows (escaping, bridge, OTAs). This will include relevant troubleshooting commands that are helpful for someone hosting a star to debug common issues.
22
22
23All of this will be done with an eye towards maintainability of the docs along with explicit steps that make it easy for users to understand what they're doing (similar in form to the docs on blog linked above). This will also lay the ground work for potential tooling around alerting, debugging, and automation which could be described and scoped more explicitly in a future proposal once the manual processes are documented.
23All of this will be done with an eye towards maintainability of the docs along with explicit steps that make it easy for users to understand what they're doing (similar in form to the docs on blog linked above). This will also lay the ground work for potential tooling around alerting, debugging, and automation which could be described and scoped more explicitly in a future proposal once the manual processes are documented.
24+
25+## Milestones
26+
27+
28+### Add Ship Hosting To Official Urbit Docs
29+1 stars
30+The docs for running your Urbit ship in the cloud with best practices: (https://zalberico.com/essay/2020/06/06/urbit-on-the-cloud.html) will be added to the core Urbit.org documentation for users
31+
32+
33+### Star Hosting/Troubleshooting Docs
34+1 stars
35+Write up docs about the best way to host a star and ways to debug common issues/workflows. End result should be a document that explains how to go from star ownership to hosting and supporting planets
36+
24
37
content/community/grants-and-bounties/verifying-urbit-id-on-keybase.md+8
@@ -63,4 +63,12 @@ Create a Gall app and that creates a Urbit ID based identity service and hosts a
63- You have 90 days from the time of approval to complete this bounty.
63- You have 90 days from the time of approval to complete this bounty.
64
64
65
65
66+
67+## Milestones
68+
69+
70+### PR is merged
71+2 stars
72+Your work is accepted, and your PR is merged.
73+
66
74
content/community/grants-and-bounties/video-content-manager.md+18
@@ -38,4 +38,22 @@ A wealth of Urbit-centric content has been produced in the past several months,
38- [Urbit YouTube Channel](https://www.youtube.com/channel/UCNYIS9_SktINCC9yqO4CFZw/featured)
38- [Urbit YouTube Channel](https://www.youtube.com/channel/UCNYIS9_SktINCC9yqO4CFZw/featured)
39- [urbit.org Media Page](https://urbit.org/media/)
39- [urbit.org Media Page](https://urbit.org/media/)
40- The Tlon Comms team and Urbit Foundation will be available as resources for content direction, questions and feedback.
40- The Tlon Comms team and Urbit Foundation will be available as resources for content direction, questions and feedback.
41+
42+## Milestones
43+
44+
45+### Bring channels up-to-date
46+1 stars
47+Wrangle content from around the web (with creators' permission) and upload it to both channels. Provide organizational structure to content—on YouTube that's creating channels/playlists, on urbit.org it's up to you.
48+
49+
50+### Ongoing maintenance
51+1 stars
52+In the three months following the first month of work, keep an eye out for additional content and upload it as needed.
53+
54+
55+### Optional: Content creation/facilitation
56+1 stars
57+Either create or directly facilitate the creation of new video/audio content (and, of course, upload it).
58+
41
59
content/community/grants-and-bounties/volt-lightning-on-urbit.md+28
@@ -202,4 +202,32 @@ It is possible to re-balance channel liquidity (shifting more of the balance to
202* The contributor will work with the Foundation coordinator to on-board fully to Lightning and Bitcoin within Urbit.
202* The contributor will work with the Foundation coordinator to on-board fully to Lightning and Bitcoin within Urbit.
203* After initial onboarding, the contributor will do a weekly check-in call with the coordinator, more frequently if needed/desired.
203* After initial onboarding, the contributor will do a weekly check-in call with the coordinator, more frequently if needed/desired.
204* The contributor will fork [this Github repo](https://github.com/urbit/volt) and submit PRs to it to get feedback.
204* The contributor will fork [this Github repo](https://github.com/urbit/volt) and submit PRs to it to get feedback.
205+
206+## Milestones
207+
208+
209+### transaction/invoice RFCs
210+2 stars
211+* Implement RFCs 2, 3 and 11 from BOLT.
212+* Create the libs and types that further stages will depend on
213+
214+
215+### on-chain transaction RFC
216+2 stars
217+* implement RFC 5, on-chain transaction handling
218+* test that channels can be opened and closed in the manner described there
219+
220+
221+### provider libraries
222+1 stars
223+* implement the `volt` provider that will talk to `lnd`
224+* create any configuration files needed to start `lnd` locally
225+
226+
227+### `volt` agent and cleanup
228+2 stars
229+* create the Gall agent to manage transactions
230+* connect it to the provider libs
231+* use the RFC libs to wire up all on-chain transactions
232+
205
233
content/community/grants-and-bounties/web-scraper.md+8
@@ -33,4 +33,12 @@ Do not begin work until your request to claim this bounty is accepted. We will a
33- Do not begin work until your request to claim this bounty is accepted. We will assign a designer to work with you on the interface.
33- Do not begin work until your request to claim this bounty is accepted. We will assign a designer to work with you on the interface.
34- Submit your code as a PR to the [urbit](https://github.com/urbit/urbit) repository.
34- Submit your code as a PR to the [urbit](https://github.com/urbit/urbit) repository.
35- You have 45 days from the time of approval to complete this bounty.
35- You have 45 days from the time of approval to complete this bounty.
36+
37+## Milestones
38+
39+
40+### PR is merged
41+1 stars
42+Your pull request is merged.
43+
36
44
content/community/grants-and-bounties/webrtc-gall-agent-and-external-app.md+20−1
@@ -2,7 +2,7 @@
2title = "WebRTC Gall Agent and external app"
2title = "WebRTC Gall Agent and external app"
3date = 2021-01-08
3date = 2021-01-08
4[taxonomies]
4[taxonomies]
5−grant_type = ["bounty"]
5+grant_type = ["grant"]
6grant_category = ["App Dev: Other"]
6grant_category = ["App Dev: Other"]
7[extra]
7[extra]
8image = ""
8image = ""
@@ -55,4 +55,23 @@ Edward Amsden ~ritpub-sipsyl is a vertan software developer and principal of Bla
55## References
55## References
56[Mozilla Developer Network WebRTC walkthrough](https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Signaling_and_video_calling)
56[Mozilla Developer Network WebRTC walkthrough](https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Signaling_and_video_calling)
57[Dealing with connectivity](https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Connectivity)
57[Dealing with connectivity](https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Connectivity)
58+
59+## Milestones
60+
61+
62+### Gall agents (WebRTC, ICE/STUN)
63+2 stars
64+A Gall agent which handles exchanging SDP messages for WebRTC applications
65+Another Gall agent which handles advertising ICE and STUN servers from stars to planets
66+
67+
68+### Standalone WebRTC-via-Urbit app
69+4 stars
70+Urbit app running in browser and hosted/interfaced via Eyre which provides the three categories of calling functionality described in the body of the proposal
71+
72+
73+### Authenticated TURN advertising
74+2 stars
75+Extension of the ICE/STUN Gall agent to allow stars to advertise an authenticated TURN server to some or all of their sponsored planets. Extension of the WebRTC application to use TURN servers.
76+
58
77