Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meetup starter kit: Document advice on starting a meetup #4

Open
erickt opened this issue Mar 19, 2016 · 16 comments
Open

Meetup starter kit: Document advice on starting a meetup #4

erickt opened this issue Mar 19, 2016 · 16 comments
Assignees

Comments

@erickt
Copy link
Contributor

erickt commented Mar 19, 2016

We should start documenting our advice how to organize a Rust-related meetup. @wifelette has a nice writeup about starting a user group here for reference.

@skade
Copy link
Contributor

skade commented Mar 20, 2016

That's an interesting reference, although it is heavily biased towards meetups with a speaker, which isn't necessary - quite the contrary. Do you mind if I assign to me?

@erickt
Copy link
Contributor Author

erickt commented Mar 20, 2016

@skade: You need to accept the invite to the team first :)

@skade
Copy link
Contributor

skade commented Mar 21, 2016

I haven't received a notification...

On 21 Mar 2016, at 00:15, Erick Tryzelaar notifications@github.com wrote:

@skade: You need to accept the invite to the team first :)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@skade
Copy link
Contributor

skade commented Mar 21, 2016

Actually, I did. Just way back. Ignore the noise :).

On 21 Mar 2016, at 09:32, Florian Gilcher florian.gilcher@asquera.de wrote:

I haven't received a notification...

On 21 Mar 2016, at 00:15, Erick Tryzelaar notifications@github.com wrote:

@skade: You need to accept the invite to the team first :)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@erickt
Copy link
Contributor Author

erickt commented Mar 21, 2016

@skade: assigned!

@erickt
Copy link
Contributor Author

erickt commented Mar 23, 2016

Some topics to cover:

  • How to find a meetup space
  • How to attract attendees
  • How to attract speakers
  • How to organize events when you can't find speakers

@huonw
Copy link

huonw commented May 8, 2016

As an amateur meet-up organiser, something like this would've been really helpful and would probably still be quite helpful. I've been lucky enough to find someone to help me who has reliable access to a free meetup space + food etc., but that was through no fault of my own (they approached me).

Other things that may be helpful are things like:

  • Suggestions about how to structure the event on the night, e.g. in Sydney, we've found that leaving 5-10 minutes between talks gives a more relaxed feel and gives people time to get up and get another drink or some more food etc.
  • An easy way to make signs (there could be premade ones like <logo> Rust Meetup in a variety of languages, but it would be good to be able to change the text manually too)
  • A suggested code of conduct
  • Checklists for different sorts of events, e.g. it's easy to forget to about power for a hack-night.

@pnkfelix
Copy link

pnkfelix commented Jun 3, 2016

Regarding the "how to organize events when you can't find speakers", I think the Rust-Paris meetup has been relatively successful when we don't have a full set of presentations employing the Open Spaces format to divide the audience into focused subgroup discussions (after the presentations, if any, are over).

  • The heart of the Open Spaces format is the idea of letting the audience, as in the people who showed up, dynamically determine the set of topics at the outset of the meetup. I have participants nominated topics by writing them on post-it notes, then we put the post-its on a central board where every attendee can vote for as many of the post-its as they want. (But no more than one vote per (post-it x person).)

One big benefit to this structure, from my POV, is that dividing into subgroups means that we can always handle a dedicated "tutorial" subgroup, where someone (often me) delivers a 2 to 3 hour presentation on Rust, with exercises hosted on play.rust-lang.org mixed in to keep things interactive. (The reason this is important is that I frequently see the audience divided into veterans and first-timers, and the first-timers are often there explicitly seeking to learn more about programming in Rust.)

@Manishearth
Copy link
Contributor

For smaller events without speakers Iv

@Manishearth
Copy link
Contributor

On that same topic: For smaller events without speakers aside from the meetup organizer (me) I've found that holding a very-interactive talk where people are highly encouraged to interrupt and derail the speaker is quite fun and makes for an enjoyable meetup. It starts off as a talk, and eventually becomes a sharing of Rust-related experiences and information, where impromptu lightning talk-esque situations emerge. It's a great way to manufacture speakers (the audience ) where there aren't any.

This might not be a sustainable model, though.

@pnkfelix
Copy link

pnkfelix commented Jun 3, 2016

@Manishearth did you mean to close this?

@Manishearth
Copy link
Contributor

Nope, on phone, fat-fingered it probably.

@Manishearth Manishearth reopened this Jun 3, 2016
@carols10cents carols10cents changed the title Document advice on starting a meetup Meetup starter kit: Document advice on starting a meetup Sep 20, 2016
@carols10cents
Copy link
Contributor

Virtual:

Physical:

  • Stickers

@carols10cents
Copy link
Contributor

@skade says:

  • A guide on how to do outreach and find people
  • Info on how to keep you group cool and likeable

@carols10cents
Copy link
Contributor

@badboy badboy self-assigned this Jun 21, 2017
@skade
Copy link
Contributor

skade commented Oct 30, 2017

I got in touch with Joe Nash at Mozfest, who runs Githubs University education program. They were currently searching for someone to facilitate a course about running Meetups.
The resulting material will be open to everyone (also to republish) and they will be giving editorial support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants