> For the complete documentation index, see [llms.txt](https://circles.logos.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circles.logos.co/readme/for-hacktivists/host-a-meetup.md).

# Host a Meetup

Want to bring more hackers together to explore the Logos stack and build technology for real-world use? We'd love to support you.

You can organise a meetup in your city or bring people together remotely. Whether you're introducing people to the technology, helping them run nodes or working on solutions for local communities, there are several ways to get involved.

### What kind of meetup can you organise?

* **Explore the technology:** Bring people together to discover the Logos stack, experiment with Basecamp, run nodes or share what they're building. Logos can support you with resources and connections, although these meetups don't currently qualify for Circle stipends on their own.
* **Build as a Logos Circle:** If your group wants to tackle a real-world problem with technology, you can [form a Circle or work within an existing one](https://circles.logos.co/readme/about-logos-circles.md). Technical builds can address needs confirmed by at least three active Circles or contribute to longer-term parallel infrastructure on Basecamp. Circles that [meet the requirements of the Charter](https://circles.logos.co/readme/for-hacktivists/technical-builds-eligibility-and-review-guide.md) can receive a stipend to support their activities, including online or cross-city collaboration.
* **Work towards a λ Prize or RFP:** Your meetup can also bring developers together to work on a larger technical challenge. [λ Prizes](https://logos.co/lambda-prize) reward solutions that achieve real adoption, while [RFPs](https://logos.co/rfp) fund teams to deliver defined technical work. These are separate opportunities from Circle stipends.

### Getting started

* **Prepare your meetup:** Explore our [Hacktivist Resources](https://circles.logos.co/readme/for-hacktivists/resources-for-hacktivists.md) to prepare your own presentation or session. You can also [get in touch with the Logos team](https://logos.co/activist-builder) for support, ideas or connections.
* **Create and promote your meetup:** Ready to organise your event? Once you're ready, create your event on Luma and submit it to the Logos calendar. Follow the steps below.
* **Want to form a funded Circle?** Read the [Circles Charter](https://circles.logos.co/readme/about-logos-circles/circles-charter.md) for the general requirements and the [Eligibility & Review Guide](https://circles.logos.co/readme/for-hacktivists/technical-builds-eligibility-and-review-guide.md) for additional guidance on technical projects.

### Create your event on Luma

You decide the format and content of your meetup. It can be a technical workshop, an introduction to Logos, a hands-on building session or simply an opportunity to connect with other hackers.

#### Event title ideas

* Logos Hacktivist Meetup
* Discover the Logos Stack
* Build with Logos: Developer Meetup
* Logos Basecamp & Node Workshop

Feel free to adapt these titles or come up with your own.

#### Suggested event description

*Use this as a starting point and adapt it to your session.*

Join us in {{City}} to explore the Logos technology stack, connect with other hackers and discover what we can build with decentralised, privacy-preserving technology.

**What to expect**

{{Briefly describe your session, whether it's an introduction to Logos, a hands-on workshop, collaborative building or an open discussion.}}

**About Logos**

Logos brings together a technology stack and a social movement to build a parallel society. Its decentralised, private-by-default tools enable communities to communicate, coordinate and build independent alternatives to existing systems.

Discover more:

* [Explore the Logos stack](https://logos.co/get-started)
* [Technical documentation](https://docs.logos.co/)
* [Read the Logos Manifesto](https://logos.co/manifesto)

#### Publish and promote your event

1. **Create your event** on [Luma](https://luma.com/create), including the title, date, location and description.
2. **Submit your event** through the [Logos Luma calendar](https://luma.com/logosevents) using the *Submit Event* option, so it can be featured alongside other Logos events.
3. **Add Logos** **as event co-host** (<team@acid.info>) through the *Add Host* option on your event management page.
4. **Make Logos a manager** through access control, so we can help you invite more people.&#x20;
5. **Share your event** with relevant local communities, hackerspaces, developer groups and your own network.

Logos can help amplify your meetup through its channels and connect you with other contributors.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://circles.logos.co/readme/for-hacktivists/host-a-meetup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
