canmove, Confirmed users
1,953
edits
Marketing/Developer/Meetups HOWTO: Difference between revisions
Jump to navigation
Jump to search
→Deciding on meetups to host or sponsor
| Line 40: | Line 40: | ||
* 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) | ||
* What areas of content or interest are ''not'' covered by existing meetups? | * What areas of content or interest are ''not'' covered by existing meetups? | ||
* Consider conducting a survey to find out what developers in your area want from meetups that they're not getting. | * Consider conducting a survey to find out what developers in your area want from meetups that they're not getting. ('''Caution:''' If you ask people what they want, the answer is often "we want everything". In that case, start with the knowledge and interests of your core organizing group to decide what to focus on.) | ||
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. | ||