├── README.md ├── LICENSE.md ├── workshop-organizers.md └── meetup-usergroup-cheatsheet.md /README.md: -------------------------------------------------------------------------------- 1 | # psf-community-resources 2 | Short guides to PSF-related resources 3 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | Creative Commons 0 License 1.0 2 | 3 | Written in 2017 by Python Software Foundation psf@python.org 4 | To the extent possible under law, the author(s) have dedicated all copyright and related and neighboring rights to this software to the public domain worldwide. This software is distributed without any warranty. 5 | You should have received a copy of the CC0 Public Domain Dedication along with this software. If not, see . 6 | -------------------------------------------------------------------------------- /workshop-organizers.md: -------------------------------------------------------------------------------- 1 | # Workshop Organizers 2 | 3 | ### General info 4 | 5 | - The PSF can help fund your workshop. [How to submit grant](https://www.python.org/psf/grants/) 6 | - You can share your workshop on the [list of Python conferences and workshops](https://www.python.org/community/workshops/) 7 | - You can share your workshop on the [list of Python events](https://wiki.python.org/moin/PythonEventsCalendar#Submitting_an_Event) 8 | 9 | ### 5 Possible places to host a workshop 10 | 11 | - The public library 12 | - A co-working space 13 | - Universities/High schools 14 | - Local companies 15 | - Community center 16 | -------------------------------------------------------------------------------- /meetup-usergroup-cheatsheet.md: -------------------------------------------------------------------------------- 1 | Meetup/User Group Organizer Cheat Sheet 2 | 3 | 1. Check to see if there is a user group or meetup already in your area by going to https://wiki.python.org/moin/LocalUserGroups. 4 | 5 | 2. If no group exists that meets your needs create a new group following the directions below. 6 | * Go to https://wiki.python.org/moin/StartingYourUsersGroup where most of this information comes from if this doesn't make sense. 7 | 8 | 3. Join the organizers email list here. http://mail.python.org/mailman/private/group-organizers/2007-June/000003.html 9 | 10 | 4. Define the group name - usually Python 11 | 12 | 5. Have a website (preferably with your own domain name), so you can include the URL when promoting the group. 13 | 14 | 6. Define a meeting location. It's good to have a location you can rely upon, monthly, without fail. 15 | * Businesses that are heavily invested in your technology may sponsor your group. 16 | * Libraries often have space available, although their hours can be limited. 17 | * Bars may host groups on off-nights - they can see it as a way to fill their bar with people. 18 | * Coworking spaces are often a good choice as well, as they want their members to be able to network. 19 | 20 | 7. Define the style of meetings for the group. Decide on the flavor of your meetings. There are lots of different things to do at meetings. 21 | * Presenters 22 | * Lightning talks 23 | * Code reviews 24 | * Display videos 25 | * Standard module of the month 26 | * Some people are looking for social opportunities. 27 | *In Dallas they hold social gatherings once a month, an evening at a local restaurant. 28 | 29 | * Others want something more in-depth; 30 | * They hold twice-monthly Saturday afternoon sesssions at a local bookstore that has wireless. Sometimes they have presentations and other times sprints, with hands-on coding. 31 | * Some people find it works not to have a topic but just have people talk about what they've found interesting and what they're working on. 32 | * Often groups meet for beer/food before and/or after the meeting, to give people a chance to congregate and hang out after the meeting place has closed. 33 | * Group activities: 34 | * Put together a club website using one of the many Python web frameworks. 35 | * Establish a club mailing list, wiki and subversion repository. 36 | * Consider producing audio recordings ala podcasts, an especially good option if your group is geographically dispersed or cannot agree on meeting times/locations. 37 | * Work to run a "scripting conference" in your area, bringing together proponents of the various languages. Some people will convert, either because your group looks like more fun or Python is such a cool language. 38 | * Work to run a "web technology conference" in your area, bringing together proponents of the various approaches. Many just want *something* to easily produce web sites and if Python is more friendly, they'll give it a try. 39 | 40 | 8. Find more people to become part of the organizers team. Getting a second person to sign up as a core organizer helps prevent your own burn-out, and reduces the 'bus number', for when you are indisposed. (on holiday, hospitalized, etc) 41 | 42 | 9. Define the means to promote the group. 43 | * Create a chapter on python.meetup.com. Such chapters cost per month; some say $19.95/month but in Houston they are paying $9.95/month so far. It's a good way for people to find you though, and you can take donations from the membership. In the DFW Pythoneers, they have found many of their members via this method.(Much the same is true for Houston.) 44 | * Apply for a grant from the PSF for meetup fees if needed. Go to https://www.python.org/psf/grants/ for more information on what grants cover and information about how to apply for one. 45 | * Standard ways of communicating meetings (i.e. you don't have to use one of the above sites): 46 | * For each meeting or other event, post an email to mail.python.org email lists "python-announce" and "python-list". While, in my experience, many are not on these lists, it reaches another subset of the Python community you can't reach any other way. (These are mirrored to Google groups comp.lang.python.announce and comp.lang.python) 47 | * Other mailing lists, newsgroups, twitter, RSS, etc. 48 | * Add your group in LocalUserGroups. Some people come here to find such groups. 49 | * Identify other user groups in your area and, with their permission, post an announcement of your meetings. For DFW Pythoneers we use the DFW Unix Users Group, and need to start making use of the .NET Users Group, the Apple Users Group and the North Texas Linux Users Group. 50 | * Hang some flyers at your local college; hold some meetings on a campus and get listed as a campus organization. 51 | * Produce some podcasts (or even better screencasts) and get them listed on video.google.com, Python 411 and such. Be sure to edit in a publicity blurb about your user group. 52 | * Set up a Google adwords (or similar) campaign targeting your local geographic area for search terms such as Python, Java, and scripting. Keeping the spread local keeps the cost reasonable. We targeted the province of Manitoba in Canada, population 1 million, for http://WinniPUG.ca, both Python and Java, for about $60 per year, and it generated a lot of interest. We pass a hat at meetings to cover the cost. 53 | * Consider putting your group on facebook, upcoming, and other places. Note that there is a cost to putting your energies into keeping these multiple places up to date, but it can get you users who would otherwise not find you. So you need to balance your time constraints to your desire to grow the size of the group. 54 | --------------------------------------------------------------------------------