| | 1 | = Sprint hosting How-to = |
| | 2 | |
| | 3 | If you're hosting or would like to host a Django sprint, here's how that works |
| | 4 | |
| | 5 | == 0. Volunteer to host == |
| | 6 | |
| | 7 | From time to time, one of the core committers (probably Jacob) will post a call for sprint locations on [http://groups.google.com/group/django-developers django-dev]. Contact that person if you think you can host. |
| | 8 | |
| | 9 | == 1. Get a location == |
| | 10 | |
| | 11 | To host a sprint, you'll need a good location. A good location needs: |
| | 12 | |
| | 13 | * A coordinator who can take RSVPs, give directions, help |
| | 14 | out-of-towners find hotels and dinner, etc. Someone from the Django team will be available to help out and answer questions, but a local liason is a must. |
| | 15 | |
| | 16 | * Room for at least 20 or 30 geeks. You should ask people to RSVP and can cap attendance if needed, but you should expect a minimum of 20 folks to show up, and possibly more (we had over 50 at PyCon 2008, but that's a corner case!). |
| | 17 | |
| | 18 | * Chairs and tables, of course. |
| | 19 | |
| | 20 | * Big enough tubes such that those 30 geeks can all ~~watch YouTube~~ work at the same time. You probably need both wired and wireless. |
| | 21 | |
| | 22 | However, you *don't* need: |
| | 23 | |
| | 24 | * Much money; the Django Software Foundation can help with costs. Ideally the space should be free, but it doesn't have to be. If you can get someone locally to pay for lunch that's even better, but attendees will be fine buying meals for themselves. |
| | 25 | |
| | 26 | * A committer -- the DSF will make sure that at least one committer attends each official sprint. |
| | 27 | |
| | 28 | == 2. Announce the sprint == |
| | 29 | |
| | 30 | * Create a wiki page for your sprint (see SprintTemplate for a template you can copy). Make sure to add details about the location, how people should RSVP, and getting to/from info for out-of-towners. |
| | 31 | |
| | 32 | * Make sure you have your contact information on that page for anyone who has questions! |
| | 33 | |
| | 34 | * Add your sprint to the list on the [wiki:Sprints] page. |
| | 35 | |
| | 36 | * Announce the sprint on [http://groups.google.com/group/django-developers django-dev]. Your contact at the Django team will cross-post your announcement to the Django weblog. |
| | 37 | |
| | 38 | == 3. Prepare yourself == |
| | 39 | |
| | 40 | As the sprint date draws near, you'll need to deal with RSVPs, answer questions from people looking to attend, and generally be available to help people get to the sprint location. |
| | 41 | |
| | 42 | Don't be shy about capping attendance if your chosen space fills up. |
| | 43 | |
| | 44 | You should try to arrange to set up the sprint space the night before the sprint. At the very least, plan to spend at least an hour setting up before anyone shows up. Make sure the Internets work, check that there's enough power strips, etc. If finding the space is non-obvious, post some signs. |
| | 45 | |
| | 46 | == 4. At the sprint == |
| | 47 | |
| | 48 | Once the sprint starts, relax! You're basically don't at this point; from here on out your role will be to help out-of-towners find lunch, dinner, etc. |
| | 49 | |
| | 50 | == 5. After == |
| | 51 | |
| | 52 | As the sprint winds down, make sure to get some volunteers to help clean up. Anybody who shows should be willing to help out, so make sure we don't leave the place a mess. |
| | 53 | |
| | 54 | It's traditional to go drinking afterwards; maybe have a bar in mind? |