Running Ruby Meetups

A practical guide for starting and sustaining a local Ruby meetup — from finding your first venue to keeping it going years later.

Why Bother

Ruby is more than a programming language - it’s a community.

Meetups are what keeps this community alive. An active meetup scene produces the people who later travel to conferences, give talks, build open source libraries, and bring others in.

A local meetup is where junior developers get to see what more experienced developers actually think about. Where someone gets a job because they handed out a sticker and had a conversation. Where someone on a bad project hears a talk that reframes what they have been struggling with. None of those things happen online.

You do not need a big reason to start a meetup. You just need to want one to exist.

Starting From Zero

The first meetup is the hardest. You have no track record, no attendee list, and no idea if anyone will show up. The way through is to do the minimum that gets people into a room, and worry about everything else later.

Your first venue

Secure a venue for a specific date. Everything else can be figured out on the fly. The venue cannot.

The best first venue for a tech meetup is an office. After the pandemic, most companies have meeting rooms and common spaces sitting empty in the evenings. A Ruby or Rails shop is the obvious first call, but any tech company with a suitable space will often say yes. They get their name mentioned to a room full of developers; you get a free room.

A university, a co-working space, or even a bar can all work for a first event. All you need is enough chairs for the people you expect, somewhere to plug in a laptop, and ideally a wall or screen to project on.

Create an event

Once you have a venue, pick a date and create an event listing. The event listing needs only the basics: date, time, location, a sentence or two about what the meetup is. You can add speakers or other program details as they are confirmed.

Tell people

Then start telling people directly. Post in any local developer Slack groups. Post in the Ruby Central Slack. Email and text people you know personally who might come. Post on LinkedIn if you have any network there.

Do not wait until the event feels polished or the lineup feels complete. The first event will be a bit rough no matter what, and the only way to have a second event is to have the first one.

Five people is fine

The first event will probably be small. That is not a failure; it is a first event. Some of the best ongoing meetups started with a handful of people in someone’s office conference room. What matters is that the people who came had a decent time and would come again.

Don’t measure the first event against a full room. You created something that didn’t exist before, and some number of people showed up because of you.

Your Format

Every meetup is different - there is no format to rule them all. Find something that works for the specific group of people who show up in your specific city.

That said, some formats are more common than others.

Talks

The most common meetup format is two or three talks followed by — or interspersed with — time for people to hang out and talk to each other. It works because talks give people something to react to. They create shared context that makes starting conversations easier. “What did you think of that talk?” is a much lower-stakes opening than “So, what do you work on?”

For talk length, shorter is almost always better. A talk that runs long eats into the time people came for: seeing each other and talking.

Talks may be the reason people come to the meetup, but the conversations are the reason they come back.

Alternatives

A hack night — where people bring projects to work on and help each other — works well for communities where developers know each other well enough to be comfortable working alongside strangers. It is harder to run cold, because newcomers don’t know what to work on or who to ask for help. It can be a great format for a group that’s been running a while and wants variety.

A workshop format, where one person leads a hands-on exercise, requires more preparation from the organizer and assumes that attendees will have laptops and a willingness to code in public. It is high value when it lands, but harder to run than a talk night.

A hangout format, where the focus is on the community. No talks, no workshops, no pressure. Just grabbing some drinks and/or food.

Promotion

If you have a meetup, and nobody is around to hear about it, are you actually having a meetup?

Promotion isn’t fun for a lot of developers. But to get people into a room, you simply can’t go without it. The good news is, marketing is not as bad as it seems at first glance.

Tell People

Post about the meetup well before it happens. Post when you confirm a speaker. Post the week of the event. Post the day of. Most people will see one of those posts, not all of them. But social-media posting is only part of the story.

Don’t be afraid to stalk LinkedIn to find Ruby developers in your city and sending personal invitations. If there’s a personal connection - i.e you are targeting Ruby people in the vicinity - and deliberate effort, most people are glad to get a personal invitation. Don’t be afraid to reach out to your personal network. If you’re thinking of starting a Ruby meetup changes are you already know someone in your local community - reach out to them first!

This is time-consuming. It is also the most reliably effective tactic for getting people to a first or second event. A personal invitation from a real person says that the event is worth attending; a generic social post is easy to scroll past.

Consistency

A meetup that happens every second month on the third Tuesday becomes a fixture. People know when it is and they plan around it. They might even bring someone new!

A meetup that happens sporadically, whenever the organizer gets around to it, never quite becomes a habit for anyone. The group never builds momentum.

Pick a cadence. Monthly is the most common, bi-monthly or even quarterly works too — and hold to it. Even if a specific month is difficult, try to run the event anyway. A small event is better than a skipped month.

Word of mouth is slow and the only thing that scales

After six to twelve months of consistent events, you will find that promotion takes less effort. Regulars bring friends. People mention the meetup when colleagues ask where to meet developers. Someone tweets about it after a good night and you get twenty new sign-ups.

This word-of-mouth growth cannot be accelerated by posting more or spending money on ads. It happens because the meetup is good and people who go to it want others to go. The only way to get there is to run good events consistently and wait.

Speakers & Talks

Getting speakers for a local meetup is less daunting than it seems, but it requires active effort. Sometimes you get lucky and you get volunteers - but you shouldn’t rely on that.

Ask directly

The best way to get speakers is to identify someone who has been working on something interesting and send them a message. Not a general “Anyone want to speak?”, but a direct: “I think what you’ve been building with Hotwire would be a great fifteen-minute talk. Would you be up for it?”

Most people who have never given a talk before will say yes more readily to a specific invitation than to an open call. They know the organizer wants to hear what they have specifically.

Lightning talks

A ten-to-fifteen-minute talk is approachable for someone who has never spoken before. They don’t have to fill forty-five minutes. They can show something they built, explain a problem they solved, or share a technique they’ve been using. That’s a real talk.

Short talks also allow more speakers per event, which means more people get the experience of speaking in front of a room. Speakers who start at meetups often go on to give conference talks. The meetup is the first rung.

Money & Sponsors

Most meetups do not need much money. The venue is usually free. The only real cost is food and drink, and even that is optional.

Do you actually need sponsors?

Some meetups run with no budget at all: attendees find the venue, nobody eats or drinks anything particular, the organizer covers a few dollars of incidental costs. This works. Many long-running meetups operate this way.

If you want to offer food and drink — which makes evenings more social and encourages people to stay longer — you will need either a small budget or a sponsor.

The food-sponsor arrangement

The most common model for meetup food is to find a single sponsor who covers the cost of pizza and soft drinks in exchange for a short mention or presentation at the start of the event. This is a clean exchange that has worked for decades. The sponsor gets their name and logo in front of a room of developers for a few minutes. You get $200 to $500 worth of food without fronting the money yourself.

The most natural sponsors are the same people who host your venue. Keep the sponsor arrangement simple: food covered in exchange for a brief mention and their logo on the event page. You find sponsors much the same way you find speakers or venues - search in your local circle for matching companies and reach out to them.

The Logistics Nobody Talks About

The logistics of a meetup are not complicated, but the ones that go wrong tend to go wrong quietly — you don’t notice until you’re standing in front of thirty people and the projector won’t connect.

Beamers are Evil

Bring an HDMI adapter, and a USB-C to HDMI adapter for good measure. Confirm before the event that the venue’s projector or TV is accessible. Know where the input selector is. Know how to turn up the volume. None of this is interesting, and all of it matters. The question is not if you’ll have AV problems - but when.

If the venue has no projection setup, a large TV screen that speakers can connect to directly often works fine for a small room. For a room over thirty people, some form of projection becomes important — people in the back can’t see a laptop screen.

Location Instructions

Even if you describe the location perfectly, people might have a hard time finding it. Be available if someone can’t find their way and is trying to reach you. Have a printout or simply a sheet of paper and a marker handy to point people in the right direction. Send/post photos so people know where to find you. This is especially true if your venu is in an offic ebuilding.

Name Tags

When a meetup is new and attendees don’t know each other, name tags genuinely help. They allow people to approach strangers without the awkwardness of asking for a name they missed. They also give introverts a slightly lower-friction way to read the room and decide who to approach.

Once your meetup has a core of regulars who all know each other, name tags become less essential. But for the first six to twelve months, they do real work.

Starting on time

Start the event within ten minutes of the announced start time, even if not everyone has arrived. People who arrived on time should not be penalized for the benefit of people who arrived late. Starting late trains your attendees to arrive late.

This is a small thing that signals something: you are organized, you respect people’s time, and the meetup is a real event, not an informal hangout that drifts.

Keeping It Fun

The hardest part of organizing a meetup is not the first event. It is the tenth, when the novelty has worn off, you are tired, and you have to do it again.

Burnout is real and predictable

Running a meetup on whichever frequency is a commitment that costs time and energy regardless of how much you enjoy it. The preparation, the communication with speakers and venues, the promotion, the evening itself — all of this adds up. Most organizers who burn out do so quietly. They skip one month, then find a reason to skip another, and just like that the meetup stops happening.

The best prevention is to not organize the meetup alone.

Find a co-organizer

A co-organizer is not a helper. They are someone who is equally invested in the meetup continuing and who can run it when you cannot. They share the cognitive load of remembering what needs to happen and when. They cover for you when you are sick, traveling, or just depleted.

Finding a co-organizer is easier if you are looking for one actively rather than waiting for someone to volunteer. Ask a regular attendee who seems particularly engaged. Offer to share the role explicitly rather than asking if they “want to help out” — people are more likely to commit to a defined role than a vague offer of involvement.

Mix it Up

If you are getting tired of organizing the meetup your attendees can tell. The best remedy is to keep things fresh for yourself. Why not try something new and outside of the usual meetup ceremony? Mix up the format, try somethinng different or add seasonal gags - or even decorations. Showing up with some Christmas cookies really livens up a room.

Keep things fun for yourself and your fellow Rubyists will have fun too.

Building Culture

A meetup’s culture is not what you write in the code of conduct. It is what happens when a newcomer arrives alone and doesn’t know anyone. It is what happens when someone gives a talk that doesn’t quite land. It is what happens when a regular attendee says something dismissive to a first-timer.

Culture is built by what is tolerated, what is celebrated, and what the organizer visibly cares about.

Make the code of conduct real

Post it somewhere visible. Mention it briefly at the start of the event — not the legalese, just: here’s what this community expects, here’s how to reach me if something happens. People notice when an organizer takes this seriously. The people most likely to cause problems are the ones who most need to hear it said out loud.

Welcome new people explicitly

At the start of each meetup, ask who is coming for the first time and give those people a moment of recognition. Invite regulars to introduce themselves to newcomers. This is a small thing that dramatically changes the experience for someone arriving alone to a room where everyone else seems to know each other.

A meetup where regulars exclusively talk to each other is not welcoming, even if it is technically open. The Pac-Man rule — leaving a gap in conversation circles so someone can join — is a simple norm worth promoting. So is the expectation that experienced developers talk to junior ones and take their questions seriously.

Tone-setting is the organizer’s job

You set the tone by what you model and what you permit. If you treat speakers with visible respect, attendees follow. If you shut down a dismissive comment in the Q&A, you signal what the community values. If you publicly thank the people who do unglamorous work — booking the venue, buying the food, setting up chairs — you reinforce that those contributions matter.

You don’t need a manifesto or an elaborate onboarding process. You need to show, consistently, what kind of room this is.

Growing & Evolving

Most meetups that are doing well will, at some point, face the question of what comes next. More attendees, different formats, a spin-off event, a relationship with the broader Ruby community. These are good problems to have.

When to grow and when not to

A meetup does not need to grow to succeed. A consistent forty-person event in a city is more valuable to the community than a hundred-person event that happens twice and stops. Chasing attendance numbers as a metric will push you toward decisions — bigger venues, more marketing, more elaborate programming — that add overhead without adding value.

Grow when you are turning people away, when you have found a venue that supports more people at no extra cost, or when the community explicitly wants more. Don’t grow to prove that you are succeeding. The meetup’s consistency is the proof.

Connecting to the broader Ruby world

Your meetup does not exist in isolation. Ruby Central, which supports meetups and conferences globally, can connect you with other organizers, grant funding, and sponsor relationships. Joining the Ruby Central Slack and the Ruby meetup organizers’ group gives you access to people who have already solved the problems you are encountering.

Connecting with regional conference organizers is also worth doing. Many conferences — Rocky Mountain Ruby, Blue Ridge Ruby, Helvetic Ruby, Tropical on Rails — have explicit relationships with local meetup communities. They promote each other and share audiences. Some conferences have emerged directly from meetups. Irina Nazarova started a monthly Ruby meetup in San Francisco, which eventually became the foundation for SF Ruby Conference.

A meetup that stays connected to the broader Ruby community — through newsletters, Slack groups, conference cross-promotion, and relationships with other organizers — is less isolated when things get hard. And when things go well, that connection is how your local community becomes part of something larger.

Handing it over

If you have been running a meetup for several years and are ready to stop, the best outcome is not for the meetup to quietly die. It is for it to continue under someone else.

The most natural successor is a regular attendee who already cares about the meetup and knows how it works. The transition is easier if you have shared the organizing work rather than done everything yourself. Give someone responsibility for speaker coordination or venue booking for a few months before you hand over. By the time you step back, they will know how the meetup works from the inside.

A meetup that has served a community for years deserves a real transition, not a slow fade.