on master help sign in
Create community-meetups.md
commit122f2f723ad6b2872dbea6b642d3ecb908061ddc author~sarlev-sarsen <tlatfcp@protonmail.com> dateFri 22 Jul 2022, 15:14 (4 years ago) parent2ab2030
1 file changed+43
content/grants/community-meetups.md+43
content/grants/community-meetups.mdnew file+43
@@ -0,0 +1,43 @@
1++++
2+title = "Community Meetup"
3+date = "2022-07-22"
4+
5+[taxonomies]
6+grant_type = [ "Bounty" ]
7+grant_category = [ "Community" ]
8+
9+[extra]
10+image = ""
11+description = "Earn stars by building culture through local, recurring, and in-person urbit events"
12+reward = "1 star"
13+assignee = ""
14+id = "B0165"
15+champion = "~taller-ravnut"
16+completed = false
17+work_request_link = "https://airtable.com/shr4qt9t9kz7RaOIa?prefill_Grant+ID=B0165&prefill_Grant+Name=Meetup%20Bounty"
18++++
19+
20+# Requirements
21+- Meetups should be geographically based; if you have distributed, interest-based communities of which you are a part, check out Urbit Embassies for a way to build digital communities on Mars.
22+- Meetups must be publicized and include a public web line with event details (time, date, location), and should be actively promoted via social media, in-person recruitment, flyers, a website, etc. If you need a signal boost, email support@urbit.org.
23+- You must host a total of six meetups, with a target once a month.
24+- Creation and admin of an Urbit group for your locality to which all meetup attendees will be invited, or a fully public group. This group should be actively maintained with info about upcoming events, copies of past presentation materials, or other related meetup content.
25+- Sharing of materials generated in service of your meetup; similarly, things like presentation materials, flyers, and FAQs from other meetups will be made available for utilization, forking, or inspiration. For more info, contact ~sarlev-sarsen or ask for help in ~siddef/uf-meetups
26+- Completion of a pull request to the urbit.org github repo to add your meetup's information to the urbit.org/community/meetups page. If you have never submitted a pull request on github before, let us know and we will teach you how. You will need to provide the following:
27+ - Location (City, State, GEO)
28+ - `@p` of host(s)
29+ - A link to your urbit group
30+ - A link to your clearweb presence (i.e. Meetup.com)
31+ - a short description of your meetup and typical events (<50 words)
32+- Regular and timely completion of the meetup report form, including:
33+ - Number of attendees
34+ - Email address for attendees who, in your judgement, have earned a planet
35+ - Submission of presentation materials or notes on topics discussed, including presentation recordings if available.
36+ - top 3-5 questions asked and the technical prowess of the questioner
37+# Encouraged Features
38+- Semi-regular presentations that introduce Urbit to newcomers, help members boot a comet, or introduce the more technical side of urbit are strongly suggested. Depending on the makeup of your meetup attendees, these presentations may be highly technical or they may be more philosophical--your call! Materials to get you started are available at ~wolref-podlex/foundation or by reaching out to ~sarlev-sarsen
39+- Having a collection of 'recommended groups' to which you can direct meetup attendees, such that they can begin to explore the Urbit network.
40+- As one of the main goals of meetups is to get people building on Urbit, once your meetup gains some traction, consider looking into proposal development for a grant on which members of your meetup can collaborate!
41+- While the specific requirements of the meetup bounty listed below can be summarized as, "run a regular meetup," the overarching goal is to onboard people to Urbit. To judge a meetup as truly successful, the answers to questions like 'How many proposals have a meetup's attendees submitted and completed?' and 'How many people has a meetup onboarded who go on to positively contribute to the culture, technology, or creativity of the network?' should have powerful answers that the meetup organizers are shouting from the rooftops. This does not mean that every meetup is expected to be full of developers, or that a meetup that does not have a huge and ever-growing attendee list would be considered a failure. What it does mean is that meetup organizers and participants should become true champions for Urbit who can't help but share with everyone around them how Urbit can offer solutions to many of the pains of modern networked computing.
42+# Compensation
43+- Upon the completion of six meetup events and the associated meetup reports, one star will be paid out to the organizer.