19 lines
1.1 KiB
Markdown
19 lines
1.1 KiB
Markdown
permalink: "/{{ year }}/{{ month }}/{{ day }}/ideas-for-rust-meetups"
|
|
title: "Ideas for Rust Meetups"
|
|
published_date: "2018-08-08 12:45:00 +0200"
|
|
layout: post.liquid
|
|
data:
|
|
route: blog
|
|
---
|
|
|
|
Not every meetup follows the same structure. Not every meetup needs to have 75+ attendees.
|
|
If you find a room and 3 people, it's a meetup.
|
|
|
|
LLogiq, organizer of the [Rhein-Main Rust meetup](https://www.meetup.com/Rust-Rhein-Main/),
|
|
published a list with some [Ideas for Rust Meetups](https://llogiq.github.io/2018/08/08/meetup-ideas.html).
|
|
|
|
Here are 2 more:
|
|
|
|
* RFC Lightning talks - Attendees sign up before the meetup to present one open RFC. Allocate some time to discuss it in more detail afterwards. Rust Cologne had [such a meetup](http://rust.cologne/2017/09/06/lightning-rfcs.html).
|
|
* Hack'n'Learn - Open the door, have some desks and let people work on their projects. This works very well for the Berlin Hack'n'Learn. We usually start with a quick introduction round, where everyone also states what they plan to work on. Later that evening people get a couple more minutes to present their results if they want.
|