|
1 | 1 | A Guide to Running a Python User Group
|
2 | 2 | ======================================
|
3 | 3 |
|
| 4 | +This guide is intended to be a simple collection of wisdom learned by |
| 5 | +watching, participating in, and helping organize in-person Python |
| 6 | +communities over the years. The target audience is anyone who wants to |
| 7 | +make their user group better. It focuses on hands-on tips. |
4 | 8 |
|
| 9 | +If you want to improve it, or you have an idea for new content to add, |
| 10 | +or new questions to answer, email me: < [email protected]>! |
5 | 11 |
|
| 12 | +Meetup.com or not |
| 13 | +================= |
| 14 | + |
| 15 | +*A story*: Two user group organizers were sitting next to each other |
| 16 | +at the PyCon user groups birds of a feather session. One was talking |
| 17 | +about how, nine months earlier, he had put together a Python user |
| 18 | +group for his city. He created an email list, and advertised the |
| 19 | +group, but never got more than a dozen people to show up. The one |
| 20 | +sitting next to him created a group in the very same city, and quickly |
| 21 | +saw meetings of 20+ people. Eventually, they found each other and |
| 22 | +merged their groups. |
| 23 | + |
| 24 | +*A recommendation*: In this guide, I strongly recommend your group use |
| 25 | +Meetup.com. This is despite various reservations: their administration |
| 26 | +panel makes it impossible for group organizers to find attendees' |
| 27 | +email addresses, and the interface is always changing, to the chagrin |
| 28 | +of some users. I personally remember the early days of Meetup.com, |
| 29 | +when its free-of-cost group creation is what powered a political |
| 30 | +campaign I cared about deeply. But I find user groups are larger, more |
| 31 | +diverse, and have more co-organizers if they use Meetup. |
| 32 | + |
| 33 | +Having said that, some user groups seem to do reasonably well with |
| 34 | +their own event announcement software. A handful of those, such as |
| 35 | +ChiPy in Chicago, also host Meetup.com pages so they can reach people |
| 36 | +who use that site. |
| 37 | + |
| 38 | +If you do use Meetup.com, the Python Software Foundation will |
| 39 | +reimburse you for your yearly Meetup.com account fees. See a sample |
| 40 | +grant application (forthcoming) on how to get that. |
| 41 | + |
| 42 | +Lightning talks |
| 43 | +=============== |
| 44 | + |
| 45 | +Lightning talks are brief talks, usually capped at five minutes, where |
| 46 | +someone introduces a topic or tool they care about. This format keeps |
| 47 | +the barrier to entry for speaking low, which means that as an |
| 48 | +organizer, you can walk around and ask people, one-on-one, "What are |
| 49 | +you going to give a lightning talk about?" |
| 50 | + |
| 51 | +Montreal Python found that by focusing on lightning talks, the core |
| 52 | +organizers didn't need to do much publicity for their group. Instead, |
| 53 | +they asked the lightning talkers to invite their friends, and the group |
| 54 | +grew and grew. |
| 55 | + |
| 56 | +More about lighting talks: |
| 57 | + |
| 58 | +* Montreal Python (PyCon 2011 talk) |
| 59 | +* Why you should keep a strict time limit on lightning talks |
6 | 60 |
|
7 | 61 | Navigation aids
|
8 | 62 | ===============
|
|
0 commit comments