Community Meetup





July 22, 2022



  • 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.
  • 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 [email protected].
  • You must host a total of six meetups, with a targeted cadence of once a month.
  • 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, and any other related meetup content.
  • 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
  • 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:
    • Location (City, State, GEO)
    • @p of host(s)
    • A link to your urbit group
    • A link to your clearweb presence (i.e. Meetup.com)
    • a short description of your meetup and typical events (<50 words)
  • Regular and timely completion of the meetup report form, including:
    • Number of attendees
    • Email address for attendees who, in your judgement, have earned a planet
    • Submission of presentation materials or notes on topics discussed, including presentation recordings if available.
    • top 3-5 questions asked and the technical prowess of the questioner

Encouraged Features

  • 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
  • Having a collection of 'recommended groups' to which you can direct meetup attendees, such that they can begin to explore the Urbit network.
  • 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!
  • While the specific requirements of the meetup bounty listed below can be summarized as "run a regular meetup", the overarching goal is to build a local community and onboard people to Urbit. Successful meetups will be judged by metrics like how many proposals have attendees submitted and completed and how many people have been onboarded who go on to positively contribute to the culture, technology, or creativity of the network. 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 community 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.


  • Upon the completion of six meetup events and the associated meetup reports, one star will be paid out to the organizer.
Apply for this grant