├── CONTRIBUTING.md
├── code-of-conduct.md
└── README.md
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contribution Guidelines
2 |
3 | 1. Read and adhere to the [Code-of-Conduct](./code-of-conduct.md)
4 | 2. Make sure you put things in the right category!
5 | 3. Always add your items to the end of a list. To be fair, the order is first-come-first-serve.
6 | 4. If you think something belongs in the wrong category, or think there needs to be a new category, feel free to edit things too.
7 |
8 | Please ensure your pull request adheres to the following guidelines:
9 |
10 | - Search previous suggestions before making a new one, as yours may be a duplicate.
11 | - Suggested READMEs should be beautiful or stand out in some way.
12 | - Make an individual pull request for each suggestion.
13 | - New categories, or improvements to the existing categorization are welcome.
14 | - Keep descriptions short and simple, but descriptive.
15 | - Start the description with a capital and end with a full stop/period.
16 | - Check your spelling and grammar.
17 | - Make sure your text editor is set to remove trailing whitespace.
18 |
19 | Thank you for your suggestions!
20 |
--------------------------------------------------------------------------------
/code-of-conduct.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | In the interest of fostering an open and welcoming environment, we as
6 | contributors and maintainers pledge to making participation in our project and
7 | our community a harassment-free experience for everyone, regardless of age, body
8 | size, disability, ethnicity, sex characteristics, gender identity and expression,
9 | level of experience, education, socio-economic status, nationality, personal
10 | appearance, race, religion, or sexual identity and orientation.
11 |
12 | ## Our Standards
13 |
14 | Examples of behavior that contributes to creating a positive environment
15 | include:
16 |
17 | * Using welcoming and inclusive language
18 | * Being respectful of differing viewpoints and experiences
19 | * Gracefully accepting constructive criticism
20 | * Focusing on what is best for the community
21 | * Showing empathy towards other community members
22 |
23 | Examples of unacceptable behavior by participants include:
24 |
25 | * The use of sexualized language or imagery and unwelcome sexual attention or
26 | advances
27 | * Trolling, insulting/derogatory comments, and personal or political attacks
28 | * Public or private harassment
29 | * Publishing others' private information, such as a physical or electronic
30 | address, without explicit permission
31 | * Other conduct which could reasonably be considered inappropriate in a
32 | professional setting
33 |
34 | ## Our Responsibilities
35 |
36 | Project maintainers are responsible for clarifying the standards of acceptable
37 | behavior and are expected to take appropriate and fair corrective action in
38 | response to any instances of unacceptable behavior.
39 |
40 | Project maintainers have the right and responsibility to remove, edit, or
41 | reject comments, commits, code, wiki edits, issues, and other contributions
42 | that are not aligned to this Code of Conduct, or to ban temporarily or
43 | permanently any contributor for other behaviors that they deem inappropriate,
44 | threatening, offensive, or harmful.
45 |
46 | ## Scope
47 |
48 | This Code of Conduct applies both within project spaces and in public spaces
49 | when an individual is representing the project or its community. Examples of
50 | representing a project or community include using an official project e-mail
51 | address, posting via an official social media account, or acting as an appointed
52 | representative at an online or offline event. Representation of a project may be
53 | further defined and clarified by project maintainers.
54 |
55 | ## Enforcement
56 |
57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
58 | reported by contacting the project team at [liran.tal@gmail.com](mailto:liran.tal@gmail.com). All
59 | complaints will be reviewed and investigated and will result in a response that
60 | is deemed necessary and appropriate to the circumstances. The project team is
61 | obligated to maintain confidentiality with regard to the reporter of an incident.
62 | Further details of specific enforcement policies may be posted separately.
63 |
64 | Project maintainers who do not follow or enforce the Code of Conduct in good
65 | faith may face temporary or permanent repercussions as determined by other
66 | members of the project's leadership.
67 |
68 | ## Attribution
69 |
70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71 | available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72 |
73 | [homepage]: https://www.contributor-covenant.org
74 |
75 | For answers to common questions about this code of conduct, see
76 | https://www.contributor-covenant.org/faq
77 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
7 |
8 |
9 | Do you want to start a meetup group but you don't know exactly where to start or what to do?
10 |
11 | This guide will help you get started and provide information on how to run successful meetups based on prior experience of the community.
12 |
13 | [](https://awesome.re)
14 |
15 | *List inspired by the [awesome](https://github.com/sindresorhus/awesome) list thing.*
16 |
17 |
18 |
19 |
20 | # Table of Contents
21 |
22 | - [Establish a Brand](#establish-a-brand)
23 | - [What is your meetup group about?](what-is-your-meetup-group-about)
24 | - [Meetup dot com](#meetup-dot-com)
25 | - [YouTube channel](#youtube-channel)
26 | - [Social media](#social-media)
27 | - [Build a roadmap](#build-a-roadmap)
28 | - [Running a meetup](#running-a-meetup)
29 | - [Moderation](#moderation)
30 | - [Scheduling](#scheduling)
31 | - [Meetup space](#meetup-space)
32 | - [Meetup page](#meetup-page)
33 | - [Meetup survey](#meetup-survey)
34 | - [Meetup checklist](#meetup-checklist)
35 | - [Post meetup](#post-meetup)
36 | - [Meetup retrospective](#meetup-retrospective)
37 | - [DO's and DONT's](#dos-and-donts)
38 |
39 |
40 | ## Establish a brand
41 |
42 | ### What is your meetup group about?
43 |
44 | First you need to decide what is the scope of your meetup.
45 | - What industry are you aiming at?
46 | - What topics are you interested in covering?
47 |
48 | For example, there are meetup groups that are very focused and dedicated to a specific technology,
49 | such as a [React & React Native](https://www.meetup.com/React-IL/). While there are other meetup groups
50 | that are more generic like focusing on the [Startup Scene](https://www.meetup.com/tlv-startup-hub/events/).
51 |
52 | Good to know:
53 | * Meetup Group titles are important, but not as important as the meetup titles themselves.
54 | * Short Meetup Group titles are encouraged
55 | * Avoid using overly generic Meetup titles
56 |
57 | ### Meetup dot com
58 |
59 | [Meetup.com](https://www.meetup.com/) is the defacto platform for managing & scheduling your meetups.
60 |
61 | Meetup dot com is doing a great job with helping you attract members to your meetup group by sharing
62 | it on your behalf to members in your general location as newly suggested meetups. You might even be
63 | surprised in the amount of people that will join your meetup group very shortly after you establish
64 | a meetup group.
65 |
66 | First step is to create a meetup and register as an organizer account which costs around $30/month
67 | (updated to September 2018).
68 |
69 | What you'll need to register a good meetup group page:
70 | - Meetup group title
71 | - Meetup cover image
72 | - Meetup topics as tags
73 | - Location for where meetups will be usually held (city-level, not an accurate address)
74 |
75 | ### YouTube channel
76 |
77 | Recording your meetups and making them available to watch afterwards is a privilege that will benefit you,
78 | the speakers and the audience:
79 |
80 | - **Audience** those that aren't able to participate get to have a second chance to watch the talks in an
81 | offline manner.
82 | - **Speakers** get to have their talks recorded which is good for their own personal branding and a reference
83 | for their talks if they wish to speak in other meetups or conferences. Furthermore, the recorded session is an
84 | asset for speakers to review their talks and learn from it how to improve, what to change, and so on.
85 | - **You** get to spread awareness and branding for your meetup through a dedicated YouTube channel.
86 |
87 | Once you have a meetup group established, title and all, go ahead and register your meetups YouTube channel
88 | where you will be uploading meetup recordings.
89 |
90 |
91 | ### Social media
92 |
93 | Leverage the social media channels that work best in your area. Some regions are known to have a strong
94 | community on Facebook, while in others the Twitter scene is strong.
95 |
96 | It will probably be ideal to register accounts in both platforms and share announcements of meetup talks
97 | in both but focus efforts on the one with the highest ROI for your community attendance rate.
98 |
99 | - **Twitter** - register a dedicated twitter account if this is your main platform. Otherwise it is enough
100 | to get by with just a twitter hashtag from another twitter account where you will be publishing the meetups.
101 | - **Facebook** - having a dedicated meetup group is a two edged sword - from one perspective if there's a
102 | strong facebook community in your region chances are that many people will join it, but on the other side
103 | this will cause fragmentation between your meetup group page and the facebook page as they would be competing
104 | on similar resources such as sharing images, videos, discussions etc. A good social play on Facebook is to
105 | share news about your upcoming meetup talks and tagging key people, with intentions for them to share your post.
106 | If rules of engagement allow, it is ideal to share news of your meetups in existing facebook groups that already
107 | have an established community around them - this will result in a huge visibility gain for your meetups.
108 |
109 | ## Build a Roadmap
110 |
111 | Running meetups takes time, and effort and you'll find that in many occasions it's not always dependent on
112 | how well you are organized because things happen - speakers have last minute problems to attend their talks,
113 | events happen that may push your meetup date, etc.
114 |
115 | Speakers is quite possibly the hardest part as they are hard to come up by and they are the heart and soul
116 | of your meetup. When you start out fresh with organizing a meetup scene it is crucial to build a roadmap
117 | with a schedule for the next 4-6 meetups and secure your speakers ahead of time.
118 |
119 | Leverage the people in your organization to produce a speakers line-up, as well as empowering them with public
120 | speaking, networking and their developer brand. However, consider meetups that are not made up solely of your
121 | own internal speakers and instead strive for meetups that include an internal speaker from your organization
122 | with speakers from outside communities or other meetup groups.
123 |
124 | It is key to keeping an up to date roadmap where you always have at least 3 meetups scheduled and organized
125 | up-front (with approved speakers, venue and date).
126 |
127 | ## Running a meetup
128 |
129 | ### Moderation
130 |
131 | The moderator (aka emcee) is essential to running the meetup.
132 | Successful meetup moderation:
133 | - Ensure there is a dedicated meetup moderator that will be responsible for running the meetup: opening
134 | introductions, manage breaks, summarizing.
135 | - It is preferred to have another person that helps organizing the meetup.
136 | - Avoid situations where the moderator is also one of the speakers.
137 |
138 | ### Scheduling
139 |
140 | Choosing a date for the meetup isn't always a straight-forward decision. Things to consider:
141 | - Usually it's good to avoid the first and last day of the week, and instead choose a day during one of the
142 | 3 mid-week days.
143 | - If your area is very saturated with the meetups scene already, it is best to check that the date you want
144 | to choose doesn't have another competing meetup group scheduled for it already.
145 | - Take into account holidays, events, or company activities to make sure none of those conflict with the meetup date.
146 |
147 | ### Meetup Type
148 |
149 | Meetups in their classic formats feature a speaker (or more) who delivers a presentation. However, meetups are a great ground to also feature different formats of learning. We propose:
150 | - **presentation** - Clasical presentations (one or more subjects)
151 | - **workshop** - Writing code during a meetup helps attendees experience and learn through practical hands-on experience.
152 | - **open talks** - A topic is selected for the meetup, and during the meetup event the attendees share a collection of subjects related to the topic proposed. A whiteboard helps facilitate this activity. Once enough subjects are gathered an open discussion with attendees can take place to share knowledge. An important aspect of this meetup is having a moderator for the conversation so it doesn't get side-tracked.
153 |
154 |
155 | ### Meetup space
156 |
157 | A good open space with a sitting area will work best for networking and free movement for attendees.
158 |
159 | Tips to consider:
160 | - Extra screens in the meetup space can be used to leverage brand awareness and identity
161 | - Extra screens can also be utilized to share open positions
162 |
163 | ### Meetup page
164 |
165 | #### Meetup basic details
166 |
167 | Details that go in every meetup you'll run
168 | 1. Title
169 | 2. Meetup cover image
170 | 3. Meetup location
171 | 4. Meetup schedule
172 |
173 | #### Meetup description
174 |
175 | The meetup description section is the heart of your meetup page - make sure it is organized well, and
176 | provides all the information for attendees as they contemplate whether to join.
177 |
178 | General notes to include in the meetup page:
179 | - Clear meetup schedule including the pre-meetup Pizza & Drinks networking session
180 | - Clear talks schedules
181 | - Talks titles include the speaker's name, title, company and short description
182 | - If multi-language talks are relevant in your region, include the talk's language
183 | - Clear parking information and instructions on how to get to the meetup space (building number, entry, floor, etc)
184 |
185 | Example reference for a meetup description:
186 |
187 | ```
188 | MEETUP SCHEDULE
189 | ===================
190 | 18:00 - 18:30
191 | 🍕🍺Pizza and Beer with cool peeps!
192 |
193 | 18:30 - 19:10
194 | Idan Cohen | UVeye (Hebrew)
195 | - C'mon Baby Light my Firebase
196 | Google has bestowed upon us Firebase: The most robust backed solution, with database, authentication,
197 | storage and hosting. Put together, Angular & Firebase can unleash great powers for those who learn
198 | their (well documented) secrets. In this talk I intend to share real life use cases, code samples,
199 | pro tips and point out the pitfalls.
200 |
201 | 19:10 - 19:15
202 | BREAK
203 | 🍕 Mingle, network, and eat more pizza!
204 | ❓🎁 Quiz and prizes!
205 |
206 | 19:15 - 20:00
207 | Nik Savchenko | Nielsen (Hebrew)
208 | - React-Redux-Island - what about reusing Smart Components? How to add two different Redux Counters
209 | (or more complicated components with business logic and/or domain) to the same screen of React Redux application?
210 |
211 |
212 | * Lectures will be recorded and uploaded to our YouTube channel
213 |
214 | PARKING
215 | =========
216 | There is a free 3 hours parking in TLV Fashion mall (5 minutes walk from the office) and free parking at
217 | Givon parking for Discount bank card holders.
218 |
219 | ----
220 | P.S.
221 | We're looking for speakers and this is your chance!
222 | Don't hesitate, and reach out to me at with any topics you might be interested to cover.
223 | ```
224 |
225 | ### Meetup survey
226 |
227 | Measuring your areas of success and shortcomings is key to know how to make future meetups better.
228 |
229 | Furthermore, your speakers are also hungry for this feedback and how they performed, what they need to
230 | improve and so on.
231 |
232 | Create a **short** meetup survey with questions covering your speakers, the venue and the hosting.
233 |
234 | Consider the following options to execute the survey:
235 | - Create a google webform for the survey so audience can just quickly type-in their feedback in their
236 | mobile and easier for you to collect the feedback later.
237 | - If you encounter a low survey participation rate consider:
238 | - a hard-copy one-page paper survey that you hand out to attendees.
239 | - coupling a prize or give-away at the end of the meetup with submitting a survey.
240 |
241 | ### Meetup checklist
242 |
243 | - [ ] Reserve a date
244 | - [ ] Confirm with office manager or the relevant person the required space or room is available and book it for the meetup.
245 | - [ ] Office buildings usually require guests to leave their personal IDs at the reception - add to the Meetup page a reminder for attendees to come with IDs for the reception guest entry.
246 | - [ ] Notify the office manager two days ahead to order Snacks, Pizza, or anything else that works for you. Note: It's better if the pizza arrives earlier than if it comes late.
247 | - [ ] Organize the space sitting area
248 | - [ ] Pre-test the media equipment: connect laptop screens, projector works as expected, ensure proper cables exist (HDMI, VGA, etc), mics if available etc.
249 | - [ ] Prepare video camera to record the talks. Preferably assign a second organizer to be responsible for recording the talks so you don't miss out on it.
250 | - [ ] Prepare a Camera-man for quality still photos - these make a good asset to later use them in social media and uploading to the meetup group. If no dedicated camera, utilize a good phone-camera.
251 | - [ ] Prints - attendees don't know the rules in your meetup space: are they allowed to take drinks from the fridge? is there a Wi-Fi access available for them? To make the space and hosting more accessible and friendly for them consider:
252 | - [ ] Printing instructions for Guest Wi-Fi access
253 | - [ ] Printing“Free Drinks” paper to put on the beer fridge
254 | - [ ] If your speakers need parking spaces make sure to reserve the parking space in advance or request the proper parking vouchers.
255 | - [ ] If Meetup roll-ups are available, place them in the building lobby for increased awareness and attendees orientation as they enter the building.
256 | - [ ] Confirm the building's lobby reception is expecting a large group of guests on the day of the meetup.
257 |
258 |
259 | ## Post meetup
260 |
261 | 1. Thank your speakers!
262 | 2. Thank your attendees!
263 | 3. Upload photos to the meetup group. Even if you have a dedicated Facebook group make sure you upload the photos
264 | to the meetup page too because future attendees who will sign-up to your meetup group will see them as they survey
265 | several meetups and choose which to join.
266 | 4. Upload meetup recorded videos to YouTube
267 |
268 | ### Meetup retrospective
269 |
270 | Just like running a development sprint, it is important to perform a short retrospective right after the meetup
271 | while the atmosphere is still fresh and discuss together with your co-organizer or general meetup staff
272 | **what went well** and **what can be improved**.
273 |
274 | Items to consider:
275 | 1. How was the organization? Was anything missing? Did we start on time? Were there too many breaks?
276 | Were people engaged? How many people actually attended the meetup?
277 | 2. Was there a good networking between speakers and attendees? Were speakers approached after their
278 | talks with questions from the audience?
279 | 3. Were attendees easily finding the venue? Did they raise any questions or issues? Was there enough
280 | pizza for everyone? They did comment on the talks quality? was it too advanced or too beginner level?
281 |
282 |
283 | ## DO's and DONT's
284 |
285 | ### DOs
286 |
287 | - Do your best to be consistent and follow your scheduling agenda. If you are committed to doing a
288 | meetup once a month - stick to it and do your best to avoid canceling or breaking this routine. Momentum is important!
289 |
290 | ### DONT's
291 |
292 | - Avoid re-scheduling a meetup. There will always be excuses to re-schedule an already set meetup: it is close to a holiday;
293 | the speakers are not well known; the topics are too beginner level; maybe not a lot of people to attend; Some points may be
294 | valid and you should've considered them in advance before scheduling the meetup. Once scheduled, keep to it and don't be
295 | tempted to move the date unless a really critical issue prevents it from happening.
296 |
297 |
--------------------------------------------------------------------------------