canmove, Confirmed users
1,953
edits
Marketing/Developer/Meetups HOWTO: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 104: | Line 104: | ||
These are not the only ones, and there may be others that are more popular in your locale. | These are not the only ones, and there may be others that are more popular in your locale. | ||
=== | ===Collecting data=== | ||
Collecting information about attendees at your meetups is important for tracking the evolution of your groups, and for sharing your results with larger groups within Mozilla. | |||
====Contact information==== | |||
You probably want to request people to ''sign up'' for the event if they plan to attend. This helps you to have an idea of how many people to expect (even though it's not exact, because some people attend who don't sign up, and vice versa). That way, you know how much refreshments to buy, and whether you might exceed the space capacity. If you have a problem of too many no-shows, try charging a small fee for registration, to encourage commitment. The proceeds can go towards refreshments, or even be returned to registrants who actually show up. | You probably want to request people to ''sign up'' for the event if they plan to attend. This helps you to have an idea of how many people to expect (even though it's not exact, because some people attend who don't sign up, and vice versa). That way, you know how much refreshments to buy, and whether you might exceed the space capacity. If you have a problem of too many no-shows, try charging a small fee for registration, to encourage commitment. The proceeds can go towards refreshments, or even be returned to registrants who actually show up. | ||
| Line 116: | Line 119: | ||
Be sure to follow Mozilla best practices to protect personal information. If you collect sign-ins online (such as a Google form and spreadsheet), ensure that only people who need access to them have access to them. Be sparing in using the information (don't spam), and allow people to opt out later. | Be sure to follow Mozilla best practices to protect personal information. If you collect sign-ins online (such as a Google form and spreadsheet), ensure that only people who need access to them have access to them. Be sparing in using the information (don't spam), and allow people to opt out later. | ||
====Aggregate stats==== | |||
You don't need to share attendee contact information with anyone outside your group. However, for community space meetup programs, the Participation and Developer Marketing groups are interested in the following aggregate statistics: | |||
* For each type of meetup: | |||
** Number of attendees | |||
** Number (or percent) of newcomers | |||
** Number (or percent) of repeat visitors | |||
====Qualitative data==== | |||
Every meeting of a meetup group is an opportunity to learn more about the attendees. Paying close attention to questions that they ask or things they say about themselves can give you clues to: | |||
* What is the level of technical skill within the group? Are there clumps at different levels (beginner vs. experienced)? | |||
* What types of topics are attendees interested in hearing more about? | |||
These insights can guide you toward the needs of attendees, and potential directions for future topics. | |||
===Conducting the meeting=== | ===Conducting the meeting=== | ||