Marketing/Developer/Meetups HOWTO: Difference between revisions

Jump to navigation Jump to search
Line 31: Line 31:
If you think you want to start a program of developer meetups in your community space, there are a few things to think about:
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?
* Which meetups will you host or sponsor?
* Who will lead the meetups you host?
* What are the criteria for holding a meetup in your space?
* What are the criteria for holding a meetup in your space?
* How often will you host meetups?
* How often will you host meetups?


===Deciding on meetups to host or sponsor===
===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.
The most important step in deciding what meetups to host or sponsor is to find a match between the the needs of your local technical community and the technical interests of potential meetup leaders.


* 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)
* 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)
Line 42: Line 43:


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.
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.
===Roles===
There are a couple of distinct roles for developer meetups, which can be filled by the same person or multiple people, depending on the situation, and the interests of the people involved.
====Meetup host====
The meetup host is responsible for the logistics of the event: planning, promotion, refreshments, sign-ins, etc.
If you are hosting an external group in your space, you still need someone to be responsible for opening and closing the space, and making sure that the group can find what it needs.
====Technical leader====
It's very important for each meetup to have '''technical leader''' who is familiar with the relevant technology. This person plans the technical content of each meeting (but they do not have to present it every time). They also should be able to answer technical questions from meetup attendees, or know where to look to find answers.
This role is not purely technical. It is also about people: encouraging attendees to feel comfortable asking questions and to want to keep coming back.
If there is no technical expert in a subject available, but there is someone who is interested in ''learning'' about the subject, consider call the meetup a "study group" (such as "Rust study group"). This makes clear to attendees that everyone is on the same level of knowledge, and therefore the group will work together to find answers to questions.


===Criteria for all meetups===
===Criteria for all meetups===
canmove, Confirmed users
1,953

edits

Navigation menu