canmove, Confirmed users
1,953
edits
Marketing/Developer/Meetups HOWTO: Difference between revisions
Jump to navigation
Jump to search
→Technical leader
| Line 53: | Line 53: | ||
====Technical leader==== | ====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 | 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. They do not have to present the content every time; they can seek out presenters, from the group's regular attendees or elsewhere, to present on various topics. 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. | 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 | If there is no technical expert in a subject available, but there is someone who is interested in ''learning'' about the subject, consider calling 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=== | ||