User login

Drupal Meetup Etiquette

I've been working with drupal and have been a part of the community for a fews years now. Although I may not be the most active member around, I have attended a decent amount of drupal meetups all over Massachusetts and New York City. I've seen what works, and I've seen what doesn't, the reason for this post is to state my opinion on what the purpose and goal of a meetup should be, and how it should be conducted.

Let's start with the general format, there should be at least one moderator, ideally someone who is not a beginner, this is the person that organized the meetup and posted the location and details to groups.drupal.org. The moderator's job is to start off and end the meeting and to basically moderate during by loosely upholding the rules of the meetup.

So, let's say a group of people have found their way to the meetup location and are sitting around mingling and/or looking around at each other. When it's time to start, you, the moderator starts things off by quickly introducing and saying a couple of words about yourself and having everyone do the same.

After this, you'd explain the idea of Lightning Talks , (A Lightning Talk is a short presentation given at a conference or similar forum. Unlike other presentations, lightning talks last only a few minutes, 5 to 10, and several will usually be delivered in a single period by different speakers -> http://en.wikipedia.org/wiki/Lightning_Talk) and ask the room who wants to give one. People will volunteer, talks will be given, questions will be asked, all the fixins for an interesting and informative meetup.

It's the moderator's job to make sure presenters keep things short, if the room wants to keep the subject alive they will ask questions and conversation will continue, if there's no more interest then presenting for another 45 minutes will just make people tired and bored, it's the moderator's job to not let this happen. I have seen people leave meetups early because of this, I have also seen people decide not to present their own topic just to help end the meetup and get the hell out of there.

The idea of a drupal meetup is closely related to the ideas of open source and free software. The meetup is a place to share ideas, methods, techniques, and code, with a downplay on business. It's all about the software, in our case drupal and it's extensions, and how we're using it, how we've adapted it, to show and learn what is possible with it, and to brainstorm with others about how to make it better. Nobody wants to hear a sales pitch, or learn all about your business, or listen to any kind of advertisement.

We're there to learn from others and share what we know, because that's how the software grows and improves. In a way it all fits in with the mystical aspect of the web and it's effect on human evolution, we help build the software which brings us together, which helps us make the software better, which benefits everyone.

We at Agaric think that's a positive cycle and with that in mind, I'm happy to announce that we're taking on organizing a monthly metrowest [between Boston and Worcester, Massachusetts] drupal meetup. The time and location for the first meetup will be posted at http://groups.drupal.org/boston when everything is finalized, so check for that soon.

Update: Set for next Wednesday, December 10, 6 p.m. at Natick's public library, the Morse Institute Library, 14 East Central Street, Natick, Massachusetts. This is less than one block from the Natick stop on the MBTA Commuter Rail's Worcester/Framingham/Boston line.

Comments

Feedback

I agree with the approach that you have outlined. Based on my experience, this format will alow for a much more interactive session betweent the presenter and the audience. I also very much so agree with the goal of the meetup:

The meetup is a place to share ideas, methods, techniques, and code, with a downplay on business. It's all about the software, in our case drupal and it's extensions, and how we're using it, how we've adapted it, to show and learn what is possible with it, and to brainstorm with others about how to make it better. Nobody wants to hear a sales pitch, or learn all about your business, or listen to any kind of advertisement.

The only "gotcha" that I see if that the "Lightning Talks" will be given by volunteers; if the "agenda" is purely ad hoc, then the meetup may not "flow" nicely. Can presenters be lined up for Lighting Talks (5 - 10 min) before the meetup?

Thank you for taking leadership on the metrowest drupal meetup.

My best experiences have

My best experiences have been with very loosely planned meetups. Having a couple of pre planned discussion items makes a lot of sense, even if just to attract participants, but leaving the meetup open to explore various random presentations and tangents also reduces the possibility of it becoming stale.
So to answer your question, I think a mix of the two is probably the best.
The best thing might be to start the lightning talks list on the groups post and leave the opportunity to add to it open throughout the meetup

Nice website

Hi,

I got here thru http://drupal.org/node/118936. It's been a couple days since I've been shadowing this post as I tame SVN to obedience on my dreamhost based drupal. I have never been to a meetup before, I just wish there were those over here in Puerto Rico. You have a nice website, and looks like a good company also, will consider dropping my resumé in your offices if I ever move from San Juan to New York, I was there for a PHP Boot Camp in Netcom @ the Empire State last year...

Post new comment

The content of this field is kept private and will not be shown publicly.
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.