canmove, Confirmed users
1,953
edits
(reorg + CoC) |
|||
| Line 7: | Line 7: | ||
==What is a meetup?== | ==What is a meetup?== | ||
The term "meetup" was popularized by the website [http://www.meetup.com/ Meetup.com]. It refers to an informal gathering of people who share a particular interest, typically on a regular interval. In the context of developer-oriented meetups, the key factors are "shared interest" and "regular interval". The shared interest should be broad enough to admit a wide range of topics, but not so broad as to lose cohesion. The interval should be frequent enough that members remember it, but not so frequent that organizer burn out. (More on this below.) | The term "meetup" was popularized by the website [http://www.meetup.com/ Meetup.com]. It refers to an informal gathering of people who share a particular interest, typically on a regular interval. In the context of developer-oriented meetups, the key factors are "shared interest" and "regular interval". The shared interest should be broad enough to admit a wide range of topics, but not so broad as to lose cohesion. The interval should be frequent enough that members remember it, but not so frequent that organizer burn out. (More on this below.) | ||
==Types of meetups == | ==Types of meetups == | ||
| Line 31: | Line 22: | ||
** Tech speaking | ** Tech speaking | ||
==Frequency== | ==Starting a developer meetup program== | ||
If you think you want to start a program of developer meetups in your community space, there are a few things to think about: | |||
* Which meetups will you host or sponsor? | |||
* What are the criteria for holding a meetup in your space? | |||
* How often will you host meetups? | |||
===Deciding on meetups to host or sponsor=== | |||
The most important step in deciding what meetups to host or sponsor is to evaluate the environment of your local technical community. | |||
* Are there existing technical meetups? (Check meetup.com, or local equivalent.) Are these aligned with Mozilla interests? (e.g., JavaScript, Rust, web technology in general) | |||
* What areas of content or interest are not covered by existing meetups? | |||
* Consider conducting a survey to find out developers in your area want from meetups that they're not getting. | |||
If there are no existing meetups for developers in your area, you can start a meetup with a very broad scope, such as "web development". If there are many meetups already, it might not make sense to create another one, but rather invite some existing meetups that are aligned with Mozilla to meet at your space. If there are some existing meetups, try to fill gaps in the content that they cover. | |||
===Criteria for all meetups=== | |||
Each community space has "house rules" that individuals and groups using the space must abide by. In addition, to put into practice Mozilla's [https://www.mozilla.org/en-US/about/governance/policies/participation/ participation principles], be sure that all meetups have a "Code of Conduct", to ensure a safe and respectful environment for all participants. Groups do not have to use exactly the same code of conduct; some groups that are part of a larger movement (for example, [http://www.pyladies.com/CodeOfConduct/ PyLadies]) might have a code of conduct from the broader organization. But all groups should have one, and leaders should be prepared to enforce it. See [http://www.ashedryden.com/blog/codes-of-conduct-101-faq Code of Conduct 101 + FAQ] for more information about why codes of conduct are important, and where to find examples or templates. | |||
===Frequency=== | |||
How often should you hold meetups? Once a month is a good cadence for any specific type of meetup. One developer event per week in the community space is a minimum target to sustain activity and interest; two per week is preferable. Therefore, a good initial target is four monthly technical meetups, one each week. | How often should you hold meetups? Once a month is a good cadence for any specific type of meetup. One developer event per week in the community space is a minimum target to sustain activity and interest; two per week is preferable. Therefore, a good initial target is four monthly technical meetups, one each week. | ||