cms_initial_pages.json

[
{
    "pk": 1, 
    "model": "cms.page", 
    "fields": {
        "body": "PyCon US is a community conference intended for networking and collaboration in the developer community.\r\n\r\nWe value the participation of each member of the Python community and want all attendees to have an enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and courtesy to other attendees throughout the conference and at all conference events, whether officially sponsored by PyCon or not.\r\n\r\nTo make clear what is expected, all delegates/attendees, speakers, exhibitors, organizers and volunteers at any PyCon event are required to conform to the following Code of Conduct. Organizers will enforce this code throughout the event.\r\n\r\nThe Short Version\r\n-----------------\r\n\r\nPyCon is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form.\r\n\r\nAll communication should be appropriate for a professional audience including people of many different backgrounds. Sexual language and imagery is not appropriate for any conference venue, including talks.\r\n\r\nBe kind to others. Do not insult or put down other attendees. Behave professionally. Remember that harassment and sexist, racist, or exclusionary jokes are not appropriate for PyCon.\r\n\r\nAttendees violating these rules may be asked to leave the conference without a refund at the sole discretion of the conference organizers.\r\n\r\nThank you for helping make this a welcoming, friendly event for all.\r\n\r\nThe Longer Version\r\n------------------\r\n\r\nHarassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.\r\n\r\nParticipants asked to stop any harassing behavior are expected to comply immediately.\r\n\r\nExhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.\r\n\r\nBe careful in the words that you choose. Remember that sexist, racist, and other exclusionary jokes can be offensive to those around you. Excessive swearing and offensive jokes are not appropriate for PyCon.\r\n\r\nIf a participant engages in behavior that violates this code of conduct, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.\r\n\r\nContact Information\r\n-------------------\r\n\r\nIf you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff. Conference staff will be wearing \"PyCon Staff\" t-shirts. You may also contact hotel staff and ask to be put in touch with the conference chair &mdash; Diana Clarke.\r\n\r\nIf the matter is especially urgent, please call/contact any of these individuals:\r\n\r\n- Ewa Jodlowska, Event Coordinator<br>\r\n[ewa@python.org](ewa@python.org \"ewa@python.org\")<br>\r\n+1 (773) 599-3845<br>\r\n\r\n- Diana Clarke, Conference Chair<br>\r\n[diana.joan.clarke@gmail.com](mailto:diana.joan.clarke@gmail.com \"diana.joan.clarke@gmail.com\")<br>\r\n+1 (416) 453-3130<br>\r\n\r\n- Mathieu Leduc-Hamel, Conference Co-Chair<br>\r\n[mathieu@montrealpython.org](mailto:mathieu@montrealpython.org \"mathieu@montrealpython.org\")<br>\r\n+1 (514) 569-2911<br>\r\n\r\nConference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance.\r\n\r\nProcedure for Handling Harassment\r\n------------------------------------------\r\n- [Attendee Procedure for incident handling](/2016/about/code-of-conduct/harassment-incidents/)\r\n- [Staff Procedure for incident handling](/2016/about/code-of-conduct/harassment-incidents-staff/)\r\n\r\n[Based on Revision](https://github.com/python/pycon-code-of-conduct/tree/649f6db082ee8068520959a7c498dae14d598b8e \"Based on Revision\")\r\n\r\nLicense\r\n-------\r\n\r\nThis Code of Conduct was forked from the example policy from the [Geek Feminism wiki, created by the Ada Initiative and other volunteers.](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy) which is under a Creative Commons Zero license. \r\n\r\n<a rel=\"license\" href=\"http://creativecommons.org/licenses/by/3.0/\"><img alt=\"Creative Commons License\" style=\"border-width:0\" src=\"//i.creativecommons.org/l/by/3.0/88x31.png\" /></a><br /><span xmlns:dct=\"http://purl.org/dc/terms/\" href=\"http://purl.org/dc/dcmitype/Text\" property=\"dct:title\" rel=\"dct:type\">Conference Code of Conduct</span> by <a xmlns:cc=\"http://creativecommons.org/ns#\" href=\"https://us.pycon.org/2016/about/code-of-conduct/\" property=\"cc:attributionName\" rel=\"cc:attributionURL\">https://us.pycon.org/2016/about/code-of-conduct/</a> is licensed under a <a rel=\"license\" href=\"http://creativecommons.org/licenses/by/3.0/\">Creative Commons Attribution 3.0 Unported License</a>.",
        "status": 2, 
        "updated": "2013-10-15T19:18:19.357", 
        "title": "Code of Conduct", 
        "body_fr": "", 
        "created": "2012-06-21T01:43:56.093", 
        "publish_date": "2012-06-21T01:43:11", 
        "path": "about/code-of-conduct/"
    }
},
{
    "pk": 2, 
    "model": "cms.page", 
    "fields": {
        "body": "Diversity Statement\r\n-----------------------\r\n\r\nOur goal is to create an inclusive, respectful conference environment that invites \r\nparticipation from people of all races, ethnicities, genders, ages, abilities, religions, and \r\nsexual orientations. PyCon and its staff fully support and endorse the Python Software Foundation's [diversity statement](http://www.python.org/psf/diversity/ \"diversity statement\"):\r\n\r\n\r\n\"*The Python Software Foundation and the global Python community welcome and encourage participation by everyone. Our community is based on mutual respect, tolerance, and encouragement, and we are working to help each other live up to these principles. We want our community to be more diverse: whoever you are, and whatever your background, we welcome you.*\"\r\n\r\n\r\nWe're actively seeking to increase the diversity of our attendees, speakers, and sponsors \r\nthrough our calls for proposals, other open submission processes, and through dialogue \r\nwith the larger communities we serve. \r\n\r\nThis is an ongoing process. We are talking to our program chairs, program committees, \r\nand various innovators, experts, and organizations about this goal and about ways they \r\ncan help us achieve it. \r\n\r\nHelp Encourage Diversity\r\n------------------------------\r\n\r\nHere are some ways you can help us build a more diverse conference experience:\r\n\r\n- Recommend appropriate speakers and/or program committee members to the \r\nconference chairs.  You may also send an \r\nemail to [pycon-organizers](mailto:pycon-organizers@python.org \"\").\r\n- Forward our call for proposals to relevant affinity groups with the message that \r\nwe are looking for a diverse speaker roster.\r\n- Suggest to potential speakers that they submit a proposal during our Call for \r\nProposals conference phase (see the [speaker page](../../speaking/speakatpycon/ \"\") for details).\r\n- Organize community-based public speaking trainings and practice events (Ignite\r\nis one popular format).\r\n- Suggest ways that the onsite conference experience can be more welcoming and \r\nsupportive, free from intimidation and marginalization (send an email to [pycon-organizers](mailto:pycon-organizers@python.org \"\")).\r\n- Share your ideas and best practices for how we can realize our vision (send an \r\nemail to [pycon-organizers](mailto:pycon-organizers@python.org \"\")).\r\n\r\nWe value diversity in the communities we bring together. We strive to provide balanced representation of the richness of our collective human experience, and welcome your contributions to helping us achieve that goal by following our [code of conduct](../code-of-conduct/ \"\").\r\n\r\nCredit for the original version of this document goes to [O'Reilly Media](http://assets.en.oreilly.com/1/eventprovider/1/ConfDiversity.pdf \"\").", 
        "status": 2, 
        "updated": "2013-10-10T17:47:14.544", 
        "title": "Conference Diversity", 
        "body_fr": "D\u00e9claration sur la diversit\u00e9\r\n-----------------------\r\n\r\nNotre objectif est de cr\u00e9er un environnement de conf\u00e9rence inclusif et respectueux qui encourage la participation des gens de toutes races, ethnies, sexes, \u00e2ges, capacit\u00e9s, religions et orientations sexuelles. PyCon et son personnel endossent et supportent sans r\u00e9serve [la d\u00e9claration de la diversit\u00e9](http://www.python.org/psf/diversity/ \"diversity statement\") de la Python Software Foundation :\r\n\r\n\r\n\"*La Python Software Foundation et la communaut\u00e9 mondiale Python accueillent et encouragent la participation de tous. Notre communaut\u00e9 est bas\u00e9e sur le respect mutuel, la tol\u00e9rance et l'encouragement et nous travaillons pour aider tous et chacun \u00e0 embrasser ces principes. Nous voulons que notre communaut\u00e9 de soit plus diversifi\u00e9e : qui que vous soyez et quel que soit votre parcours, nous vous accueillons*\".\r\n\r\n\r\nNous recherchons activement \u00e0 accro\u00eetre la diversit\u00e9 de nos participants, conf\u00e9renciers et commanditaires gr\u00e2ce \u00e0 nos appels aux pr\u00e9sentateurs, nos processus de soumission ouvertes et par le dialogue avec les grandes communaut\u00e9s que nous desservons.\r\n\r\nIl s'agit d\u2019un processus continu. Nous parlons \u00e0 nos pr\u00e9sident(e)s et comit\u00e9s de programme, et \u00e0 divers innovateurs, experts et organisations de cet objectif et des moyens \u00e0 leur disposition pour nous aider \u00e0 y parvenir.\r\n\r\nEncourager la diversit\u00e9\r\n------------------------------\r\n\r\nVoici quelques fa\u00e7ons dont vous pouvez nous aider \u00e0 construire une exp\u00e9rience de conf\u00e9rence plus diversifi\u00e9e :\r\n\r\n- Recommander des pr\u00e9sentateurs appropri\u00e9es et/ou des membres du comit\u00e9 de programme aux pr\u00e9sident(e)s de la conf\u00e9rence. Vous pouvez \u00e9galement envoyer un courriel \u00e0 [pycon-organizers](mailto: pycon-organizers@python.org \"\").\r\n- Transmettre nos appels aux pr\u00e9sentateurs \u00e0 des groupes aux affinit\u00e9s similaires avec la mention que nous recherchons une liste de participants diversifi\u00e9e.\r\n- Proposer aux participants potentiels qu'ils soumettent une proposition lors de notre phase d\u2019appel aux participants de la conf\u00e9rence (voir la [page participant](../../speaking/speakatpycon/ \"\" ) pour plus de d\u00e9tails).\r\n- Organiser des formations en art oratoire communautaires et des \u00e9v\u00e9nements de pratique (*Ignite*\r\nest un format populaire ) .\r\n- Proposer des moyens pour que l'exp\u00e9rience de la conf\u00e9rence peut \u00eatre plus accueillante et\r\nsolidaire, libre de toute intimidation et marginalisation (envoyez un email \u00e0 [pycon-organizers](mailto: pycon-organizers@python.org \"\")).\r\n- Partagez vos id\u00e9es et les meilleures pratiques pour savoir comment nous pouvons r\u00e9aliser notre vision (envoyez un courriel \u00e0 [pycon-organizers](mailto: pycon-organizers@python.org \"\")).\r\n\r\nNous valorisons la diversit\u00e9 dans les communaut\u00e9s que nous rassemblons. Nous nous effor\u00e7ons d'assurer une repr\u00e9sentation \u00e9quilibr\u00e9e de la richesse de notre exp\u00e9rience humaine collective et d\u2019accueillir vos contributions pour nous aider \u00e0 atteindre cet objectif en suivant notre [code de conduite](../code-of-conduct/ \"\").\r\n\r\nLes cr\u00e9dits pour la version originale de ce document va \u00e0 [O'Reilly Media]( http://assets.en.oreilly.com/1/eventprovider/1/ConfDiversity.pdf \"\").", 
        "created": "2012-06-21T18:27:57.305", 
        "publish_date": "2012-06-21T18:27:57", 
        "path": "about/diversity/"
    }
},
{
    "pk": 3, 
    "model": "cms.page", 
    "fields": {
        "body": "PyCon is the **largest** annual gathering for the community using and developing the open-source <a href=\"http://python.org\">Python</a> programming language. It is produced and underwritten by the <a href=\"http://www.python.org/psf/\">Python Software Foundation</a>, the 501(c)(3) nonprofit organization dedicated to advancing and promoting Python. Through PyCon, the PSF advances its mission of growing the international community of Python programmers.\r\n\r\nBecause PyCon is backed by the non-profit PSF, we keep registration costs much lower than comparable technology conferences so that PyCon remains accessible to the widest group possible. The PSF also pays for the ongoing development of the software that runs PyCon and makes it available under a liberal open source license.\r\n\r\nPyCon is a <a href=\"/2016/about/diversity/\">diverse conference</a> dedicated to providing an enjoyable experience to everyone. Help us do this by following our <a href=\"/2016/about/code-of-conduct/\">code of conduct</a>.\r\n\r\nPyCon is really four events in a row:\r\n------------------------------------------\r\n\r\n<ul> \r\n<li> \r\n<p><strong>Tutorial Days</strong>: Wednesday April 9 &amp; Thursday April 10, 2016.</p> \r\n<p>Learn something new and relevant in intensive 3-hour sessions.  The evenings are free for socializing and Open Space.</p> \r\n</li> \r\n<li> \r\n<p><strong>Conference Days</strong>: Friday April 11 through Sunday April 13, 2016.</p> \r\n<p>See what's going on in the Python world, meet your fellow Pythonistas, share your knowledge and experience, make contacts, brainstorm projects, discuss prospects... the sky's the limit. </p> \r\n<ul> \r\n<li> \r\n<p><strong>Scheduled talks</strong> will happen in the ballrooms.</p> \r\n<p>5 tracks of talks and panels on a wide variety of topics will be presented, with something for everyone.  Also we'll have keynote talks every day.</p> \r\n</li> \r\n<li> \r\n<p><strong>Open Space</strong> sessions.</p> \r\n<p>PyCon features an <a href=\"http://en.wikipedia.org/wiki/Unconference\" title=\"unconference\">unconference</a> in parallel of the scheduled talks with dedicated rooms for attendees to schedule\r\ninformal presentations or discussions. These rooms are open space to\r\nlet you customize your experience at PyCon to match your specific\r\ninterests. These are available for the duration of the conference\r\ndays.</p>\r\n</li> \r\n<li> \r\n<p><strong>Lightning talks</strong> </p> \r\n<p>Quick, fun, five-minute talks on almost any topic. The fast-paced volleys of lightning talks are fired in the main ballroom in front of a large audience, making them a very effective way to reach out to the community.</p> \r\n</li> \r\n<li> \r\n<p><strong>Poster Session</strong> </p>\r\n<p>Poster sessions are a dedicated expo of PyCon community members\r\nsharing their work in the format of a large graphic poster\r\npresentation.  Presenters are on hand to describe and discuss their\r\ndiscoveries, creations, and projects with the PyCon attendees.</p> \r\n</li> \r\n<li> \r\n<p><strong>Expo Hall</strong></p> \r\n<p>Meet with representatives of companies using Python, supporting Python, and hiring Pythonistas. Snag some swag! Many sponsors will be <strong>recruiting</strong>, so come prepared with business cards and resumes if you're in the job market.</p> \r\n</li> \r\n<li> \r\n<p>And don't forget the <strong>hallway track</strong>!</p> \r\n</li> \r\n</ul> \r\n</li> \r\n<li> \r\n<p><strong>Development Sprints</strong>: Monday April 14 through Thursday April 17, 2016.</p> \r\n<ul> \r\n<li><p>Help advance your favorite project, including Python itself!  We provide the space and the infrastructure (network, power, tables &amp; chairs), you provide the enthusiasm and the brainpower.  All experience levels welcome.  The sprints are free!</p>\r\n</li> \r\n<li> \r\n<p>More information on the <a href=\"https://us.pycon.org/2016/community/sprints/\" title=\"Sprints\">Sprints page</a>!</p>\r\n</li> \r\n</ul> \r\n</li> \r\n<li> \r\n<p><strong>Summits</strong>:</p> \r\n<p>In addition, there are two invitation-only summits scheduled during the tutorials which will bring developers of the various implementations together to discuss technology and strategies: the <a href=\"/2016/events/langsummit/\">Python Language Summit</a> and the <a href=\"/2016/events/edusummit/\">Python in Education Summit</a>.</p> \r\n</li> \r\n</ul> \r\n\r\nContacts\r\n------------------\r\n\r\n- Ewa Jodlowska, Event Coordinator<br>\r\n[ewa@python.org](ewa@python.org \"ewa@python.org\")<br>\r\n+1 (773) 599-3845<br>\r\n\r\n- Diana Clarke, Conference Chair<br>\r\n[diana.joan.clarke@gmail.com](mailto:diana.joan.clarke@gmail.com \"diana.joan.clarke@gmail.com\")<br>\r\n+1 (416) 453-3130\r\n\r\n- Mathieu Leduc-Hamel, Conference Co-Chair<br>\r\n[mathieu@montrealpython.org](mailto:mathieu@montrealpython.org \"mathieu@montrealpython.org\")<br>\r\n+1 (514) 569-2911<br>\r\n\r\n- Brian Curtin, Publicity Coordinator<br>\r\n[brian@python.org](mailto:brian@python.org \"brian@python.org\")<br>\r\n+1 (630) 364-0250<br>\r\n\r\n- PyCon Organizers: [pycon-organizers@python.org](mailto:pycon-organizers@python.org \"pycon-organizers@python.org\")\r\n\r\n", 
        "status": 2, 
        "updated": "2013-10-09T19:35:06.865", 
        "title": "What is PyCon?", 
        "body_fr": "PyCon est le **plus grand** rassemblement annuel pour la communaut\u00e9 qui utilise et qui d\u00e9veloppe le langage de programmation <a href=\"http://python.org\">Python</a>. Il est produit et enregistr\u00e9 par la  <a href=\"http://www.python.org/psf/\">Python Software Foundation</a>, une organisation sans but lucratif 501(c)(3) d\u00e9di\u00e9 \u00e0 l'avancement et \u00e0 la promotion de Python. Par l'entremise de PyCon, la PSF poursuit sa mission de faire grandir la communaut\u00e9 internationale de programmeurs Python.\r\n\r\nC'est parce que PyCon est appuy\u00e9 par la PSF, une organisation sans but lucratif, que nous maintenons les co\u00fbts d'enregistrement beaucoup plus bas que d'autres conf\u00e9rences technologiques comparables afin que PyCon reste accessible au plus grand groupe possible. La PSF contribue \u00e9galement au d\u00e9veloppement de logiciels qui supportent PyCon et le rend disponible sous une licence open source lib\u00e9rale.\r\n\r\nPyCon est une <a href=\"/2016/about/diversity/\">conf\u00e9rence qui encourage la diversit\u00e9</a> d\u00e9di\u00e9e \u00e0 promouvoir une exp\u00e9rience agr\u00e9able \u00e0 tout le monde. Aidez nous dans ce sens en suivant notre <a href=\"/2016/about/code-of-conduct/\">code de conduite</a>.\r\n\r\n\r\nPyCon est v\u00e9ritablement 4 \u00e9v\u00e9nement en un:\r\n-------------------------------------------------------------\r\n\r\n<ul>\r\n<li>\r\n<p><strong>Journ\u00e9es de tutoriaux</strong>: Mercredi le 9 avril &amp; Jeudi le 10 avril 2016.</p>\r\n<p>Apprendre quelque chose de nouveau et pertinent dans des sessions intensives de 3 heures. Les soir\u00e9es sont libres pour socialiser et participer aux espaces ouverts.</p>\r\n</li>\r\n<li>\r\n<p><strong>Journ\u00e9es de conf\u00e9rence</strong>: Vendredi le 11 Avril jusqu'au Dimanche 13 avril 2016</p>\r\n<p>Voyez ce qui se passe dans le monde de Python, rencontrez vous amis pythoneux, partagez vos connaissances et vos exp\u00e9riences, faites vous de nouveaux contacts, brainstormez sur des projets, discutez de projets\u2026 \r\n</li>\r\n<li>\r\n<p>Les <strong>Pr\u00e9sentations</strong> vont avoir lieu dans la salle de bal.</p>\r\n<p>5 pistes de pr\u00e9sentations et des panels sur une vari\u00e9t\u00e9 de sujets seront pr\u00e9sent\u00e9s, avec quelque chose pour tout le monde. De plus nous aurons une pr\u00e9sentation principale chaque jour.</p>\r\n</li>\r\n<li> \r\n<p><strong>Espaces Ouverts</strong>.</p> \r\n<p>PyCon a une  <a href=\"http://en.wikipedia.org/wiki/Unconference\" title=\"unconference\">unconference</a> en parall\u00e8le \u00e0 aux pr\u00e9sentations principales avec des salles d\u00e9di\u00e9s afin de pr\u00e9parer\r\ndes pr\u00e9sentations informelles ou des discussions. Ces salles sont des espaces ouverts afin de vous laisser personnaliser votre exp\u00e9rience \u00e0 PyCon afin de r\u00e9pondre \u00e0 vos int\u00e9r\u00eats sp\u00e9cifiques. Ces salles sont disponibles\r\ndurant les jours de conf\u00e9rences.</p>\r\n</li>\r\n<li>\r\n<p><strong>Pr\u00e9sentations \u00e9clairs</strong></p>\r\n<p>Rapides, amusantes, des pr\u00e9sentations de 5 minutes sur presque n'importe quel sujet. Le volet \u00e0 rythme rapide des pr\u00e9sentations \u00e9claires \u00e0 lieu dans la salle principale, devant une grande audience, ce qui  facilite \r\nl'acc\u00e8s \u00e0 une tr\u00e8s grande communaut\u00e9.</p>\r\n</li>\r\n<li><p><strong>Session d'affiches</p>\r\n<p>La sessions d'affiches est une exposition d\u00e9di\u00e9 membres de la communaut\u00e9 PyCon afin de partager leur travail dans un grand format graphique. Les pr\u00e9sentateurs sont sur places pour d\u00e9crire et discuter de leurs d\u00e9couvertes,\r\nleurs cr\u00e9ations et leurs projets avec les participants de PyCon.</p>\r\n</li>\r\n<li>\r\n<p><strong>La salle d'exposition</strong></p>\r\n<p>Rencontrez les repr\u00e9sentants de compagnies qui utilisent Python, qui supportent Python et qui engagent des pythoneux. C'est le temps de d\u00e9nicher du mat\u00e9riel promotionnel. Plusieurs commanditaires vont <strong>recruter</strong>, alors soyez pr\u00e9par\u00e9s \r\navec vos cartes d'affaires et votre c.v. si vous \u00eates \u00e0 la recherche d'un emploi.</p>\r\n</li>\r\n<li>\r\n<p><strong>Et n'oubliez pas <strong>la conf\u00e9rence des couloirs</strong>!</p>\r\n</li>\r\n<li>\r\n<p><strong>Les sprints de d\u00e9veloppement</strong>: Le lundi 14 avril jusqu'au Jeudi 17 avril 2016.</p>\r\n<p>Aidez votre projet favoris, incluant Python lui-m\u00eame! Nous vous fournissons l'espace et l'infrastructure (r\u00e9seau, courant, tables et chaises),  vous fournissez votre enthousiasme et le pouvoir de votre cerveau. Tous les niveaux d'exp\u00e9riences sont bienvenus. Les sprints sont gratuits!</p>\r\n</li>\r\n<li>\r\n<p><strong>Les sommets</strong></p>\r\n<p>En plus de la conf\u00e9rence, nous organisons deux sommets, sur invitation seulement, durant les tutoriaux, qui vont rassembler des d\u00e9veloppeurs des diff\u00e9rentes impl\u00e9mentations de Python afin de discuter de technologies et de strat\u00e9gies: <a href=\"/2016/events/langsummit/\">Python Language Summit</a> and the <a href=\"/2016/events/edusummit/\">Python in Education Summit</a>.</p>\r\n</li>\r\n</ul>\r\n\r\nContacts\r\n------------------\r\n\r\n- Ewa Jodlowska, Event Coordinator<br>\r\n[ewa@python.org](ewa@python.org \"ewa@python.org\")<br>\r\n+1 (773) 599-3845<br>\r\n\r\n- Diana Clarke, Conference Chair<br>\r\n[diana.joan.clarke@gmail.com](mailto:diana.joan.clarke@gmail.com \"diana.joan.clarke@gmail.com\")<br>\r\n+1 (416) 453-3130\r\n\r\n- Mathieu Leduc-Hamel, Conference Co-Chair<br>\r\n[mathieu@montrealpython.org](mailto:mathieu@montrealpython.org \"mathieu@montrealpython.org\")<br>\r\n+1 (514) 569-2911<br>\r\n\r\n- Brian Curtin, Publicity Coordinator<br>\r\n[brian@python.org](mailto:brian@python.org \"brian@python.org\")<br>\r\n+1 (630) 364-0250<br>\r\n\r\n- PyCon Organizers: [pycon-organizers@python.org](mailto:pycon-organizers@python.org \"pycon-organizers@python.org\")", 
        "created": "2012-06-21T18:29:38.083", 
        "publish_date": "2012-06-21T18:29:38", 
        "path": "about/what-is-pycon/"
    }
},
{
    "pk": 6, 
    "model": "cms.page", 
    "fields": {
        "body": "Presenting PyCon 2016!\r\n======================\r\n\r\nPyCon is the largest annual gathering for the community using and developing the open-source Python programming language. PyCon is organized by the Python community for the community. We try to keep registration far cheaper than most comparable technology conferences in order to keep PyCon accessible to the widest group possible. The conference draws a diverse delegation for which we are dedicated to providing an enjoyable experience to everyone. \r\n\r\nYour sponsorship helps keep PyCon affordable and accessible to the widest possible audience. PyCon is organized by volunteers from the Python community and underwritten by the Python Software Foundation, a 501(c)3 charitable organization set up to manage the growth and development of Python worldwide.\r\n\r\nThe available sponsorships are below. Don't see what you want? Contact us any time, we are flexible and willing to work with you to design the sponsorship package that will fulfill your business needs.\r\n\r\n[Apply here](/2016/sponsors/apply) to become a PyCon sponsor.  <span class=\"label label-important\">Thanks!</span>\r\n\r\nContact\r\n---------\r\nJesse Noller, Sponsorship Chair<br>\r\n[jnoller@python.org](mailto:jnoller@python.org \"jnoller@python.org\")<br>\r\n+1 (978) 212-9863\r\n\r\nConference Profile\r\n---------------------\r\n- **Estimated Attendance:** 2000+\r\n- **Audience Profile:** Developers, technologists, programmers and hackers; bloggers, authors and web developers; CTOs, managers and entrepreneurs; scientists, engineers and domain experts.\r\n- **Conference Schedule:**\r\n * Two tutorial days: April 9\u201310, 2016\r\n * Three day Expo Hall: April 10-12, 2016\r\n * Main Conference: April 11-13, 2016\r\n * Job Fair/Poster Session: April 13, 2016\r\n * Development Sprints: April 14-17, 2016\r\n- **Come Learn About:** \r\nPython internals, beginner and advanced skills. Use cases and Case studies. Python use in a variety of industries including robotics, startups and the enterprise. Python powering some of the Web\u2019s biggest sites. Speeding up your Python applications. The growing Python ecosystem and community.\r\n\r\nExhibit Floor Information and Schedule\r\n---------------------------------------------\r\nThe Exhibit Hall will be located in Hall 220DE in the Palais des Congres.  The Exhibit Hall will be located outside of Registration and in close proximity to all the sessions. The Opening Reception and all Breaks will be located in the Exhibit Hall. This will bring in 98%-100% of all attendees onto the floor. Move-in for \r\nthe Exhibit Hall begins on Thursday, April 10th at 10:00am until 6:00pm. There is an opening reception on the Exhibit Floor at 6:00pm. \r\n\r\n#### Exhibit Floor Times\r\n* **Expo with booths:** Thursday, April 10, 2016 - 6:00pm to 8:00pm \r\n* **Expo with booths:** Friday, April 11, 2016 - 10:00am to 5:00pm\r\n* **Expo with booths:** Saturday, April 12, 2016 - 10:00am to 5:00pm\r\n* **Job Fair:** Sunday, April 13, 2016 - 10:00am to 1:00pm\r\n\r\nMove-out for the Exhibit hall begins at 5:00pm Saturday, April 12th. Everything needs to be cleared out by 7pm. At this point, we transform the Expo Hall into the Job Fair (details for the job fair below).\r\nIf necessary, we will ship back banners to those sponsors who supply us with a shipping account to use. Further details will be included in the Sponsor Manual, which will be sent out later this year.\r\n\r\n**You have an option to opt-out of the Booth Space in the Exhibit Hall. However, if you do not opt-out before the start of the conference and leave your booth empty, a fee will be applied to your sponsorship. This can be arranged with our Event Coordinator, Ewa Jodlowska (ewa@python.org).**\r\n#### Job Fair Information\r\n\r\nIn previous years, we have had an amazing turn out at our Job Fair. Many companies found good prospects during the three hour event, some receiving hundreds of resumes in a short time. \r\n\r\nIn 2016, the Job Fair will be Sunday, April 13th. It will be located in Exhibit Hall 220DE in the Palais des Congres.  Each participant will have a 6 foot table reserved for them. Set up begins at 8:00am Sunday. The Job Fair is open to attendees from 10:00am to 1:00pm (3 hours). At 1:00pm, Exhibit Hall 220DE will be cleared out. \r\n\r\nEvery participant will have a six foot table and chairs set aside for them; we do not use booths during the Job Fair. You are welcome to have a standing banner or customized table cloth.  Give aways/flyers are also welcome. Power will not be provided. \r\n\r\nKeep in mind, if you do not see what you want, contact us any time. We are flexible and willing to work with you to design the sponsorship package that will fulfill your business needs.\r\n\r\nMore information regarding the Expo Hall will be sent out in the Exhibit Manual in November 2016 from our decorator.\r\n\r\nSponsor Packages\r\n----------------------\r\n\r\n###Keystone Level Sponsorship \u2016 $50K (Limit: 1)\r\n* 1 Sponsor Workshop (see description below)\r\n* 2 page full page color ad in PyCon program guide\r\n* 250 word description in PyCon program guide\r\n* Preeminent booth space in Exhibit Hall Thursday, April 10 through Saturday, April 12\r\n* Tote bag insert (provided by sponsor)\r\n* Logo placement alongside the PyCon logo on the tote bag (\"PyCon 2016 sponsored by x and y\")\r\n* KeyStone sponsor link on PyCon website\r\n* Joint press releases highlighting the sponsor\r\n* Blog posts highlighting the sponsor/interviews about what they do with python.\r\n* 12x2 banner (if provided) in main conference room\r\n* Job listing on the PyCon 2016 Jobs Fair page \r\n* Opportunity to reserve a table for the Job Fair on Sunday, April 13, 2016\r\n* Opportunity to contribute to PyCon\u2019s Auction\r\n* Preeminent branding on PyCon Mobile Guide\r\n* 20 free sponsor registrations\r\n\r\n### Diamond Level Sponsorship \u2016 $35K (Limit: 4)\r\n* 1 Sponsor Workshop (see description below)\r\n* 2 page full page color ad in PyCon program guide\r\n* 200 word description in PyCon program guide\r\n* Preeminent booth space in Exhibit Hall Thursday, April 10 through Saturday, April 12\r\n* Tote bag insert (provided by sponsor)\r\n* Logo placement alongside the PyCon logo on the tote bag (\"PyCon 2016 sponsored by x and y\")\r\n* Diamond sponsor link on PyCon website\r\n* Name included in press release and event mailings\r\n* 12x2 banner (if provided) in main conference room\r\n* Job listing on the PyCon 2016 Jobs Fair page\r\n* Opportunity to reserve a table for the Job Fair on Sunday, April 13, 2016\r\n* Opportunity to contribute to PyCon\u2019s Auction\r\n* Banner ad/additional information in the PyCon mobile Guide\r\n* 12 free sponsor registrations\r\n\r\n### Platinum Level Sponsorship \u2016 $17K (Limit: 10)\r\n* Full page color ad in PyCon program guide\r\n* 150 word description in PyCon program guide\r\n* Prominent booth space in Exhibit Hall Thursday, April 10 through Saturday, April 12\r\n* Tote bag insert (provided by sponsor)\r\n* Platinum sponsor link on PyCon website\r\n* Name included in press release and event mailings\r\n* 12x2 banner (if provided) in main conference room\r\n* Job listing on the PyCon 2016 Jobs Fair page\r\n* Opportunity to reserve a table for the Job Fair on Sunday, April 13, 2016\r\n* Opportunity to contribute to PyCon\u2019s Auction\r\n* Banner ad/additional information in the PyCon mobile Guide\r\n* 8 free sponsor registrations\r\n### Gold Level Sponsorship \u2016 $7K\r\n* Medium page color ad in PyCon program guide\r\n* Large booth space in Exhibit Hall Thursday, April 10 through Saturday, April 12\r\n* 100 word description in PyCon program guide\r\n* Tote bag insert (provided by sponsor)\r\n* Gold sponsor link on PyCon website\r\n* Name included in press release and event mailings\r\n* 12x2 banner (if provided) in main conference room\r\n* Opportunity to contribute to PyCon\u2019s Auction\r\n* Job listing on the PyCon 2016 Jobs Fair page\r\n* Opportunity to reserve a table for the Job Fair on Sunday, April 13, 2016\r\n* 5 free sponsor registrations\r\n### Silver Level Sponsorship \u2016 $4K\r\n* Small page color ad in PyCon program guide\r\n* 50 word description in PyCon program guide\r\n* Small booth space in Exhibit Hall \r\n* Tote bag insert (provided by sponsor)\r\n* Silver sponsor link on PyCon website\r\n* Name included in press release and event mailings\r\n* Opportunity to contribute to PyCon\u2019s Auction\r\n* Job listing on the PyCon 2016 Jobs Fair page\r\n* 2 free sponsor registrations\r\n### PyCon Patron \u2016 $1,500 \r\n* (For individuals and start-up businesses)\r\n* Listing in PyCon program guide\r\n* Patron link on Sponsors page\r\n* 1 free sponsor registration\r\n\r\n#### Additional Information\r\nSmall entity discount: Small entities (organizations with fewer than 25 employees) receive a 50% discount for gold and silver sponsorships and for all vendor/exhibitor levels.\r\n\r\nFree booths for F/OSS projects: Free booth space for OSS projects will be provided as requested and while available. Free booth space must be confirmed immediately prior to the conference.\r\n## \u00c0 la carte Options (Can be added to other packages)\r\n\r\n### Conference Day Coffee Break sponsorship \u2016  $12,000 per day\r\n* Provides coffee and tea for the attendees for up to 4 hours during the conference\r\n* Logo placement in Coffee Break area \r\n\r\n### Sprint Day Coffee Break sponsorship \u2016  $6,000 per day\r\n* Provides coffee and tea for the attendees for up to 4-6 hours during the conference\r\n\r\n### Lanyard sponsorship \u2016 ($5K + cost of lanyards and badge holders) (Limit: 1)\r\n* Provides wide recognition during PyCon\r\n* Logo and text on lanyard\r\n* 2 free sponsor registrations\r\n* Can be added to other packages\r\n\r\n### Summit/Sprint Sponsorship \u2016 $4K per day\r\n* Logo placement by Summit/Sprint rooms\r\n* Supports Python development or language summit\r\n* Sprint sponsor link on PyCon website\r\n* 3 free sponsor registrations\r\n* Can be added to other packages\r\n\r\n### Sponsor Workshop \u2016 $3,750 per 1.5 hr slot (Limit: 8)\r\n* Provides a one and a half hour slot during tutorials (Wednesday or Thursday)\r\n* Registrations for attendees will be free\r\n* Coffee Breaks will be provided for the attendees\r\n\r\n### Open Space room branding/signage \u2016 $1,000\r\n* Logo placement on Open Space signs/in Open Space area\r\n### Table in the Job Fair- $5,000\r\n* 6 foot table with 2 chairs provided for your company on Sunday, April 13, 2016 from 10:00am to 1:00pm.\r\n\r\n**Media sponsorship:** Please contact us pycon-sponsors@python.org", 
        "status": 2, 
        "updated": "2013-10-09T22:09:56.494", 
        "title": "Sponsorship Prospectus", 
        "body_fr": "PyCon 2016!\r\n======================\r\n\r\nPyCon est le plus grand rassemblement annuel pour la communaut\u00e9 qui utilise et qui d\u00e9veloppe le langage de programmation Open-Source Python. PyCon est organis\u00e9 par la communaut\u00e9 Python pour la communaut\u00e9. Nous essayons de garder bas les frais d'enregistrement en comparaison avec aux autres conf\u00e9rences technologiques afin de garder PyCon accessible au plus grand groupe possible. PyCon accueille des d\u00e9l\u00e9gations diverses pour qui nous sommes d\u00e9di\u00e9s \u00e0 rendre leur exp\u00e9rience agr\u00e9able.\r\n\r\nVotre commandite nous aide \u00e0 garder PyCon accessible \u00e0 l'audience la plus large. PyCon est organis\u00e9 par des volontaires de la communaut\u00e9 Python et la Python Software Foundation, une organisation sans but lucratif enregistr\u00e9 501(c)3 qui existe afin d\u00e9velopper et de promouvoir le Python mondialement.\r\n\r\nLes niveaux de commandites disponibles sont d\u00e9cris plus bas. Vous n'y trouvez pas ce que vous cherchez ? Contactez-nous \u00e0 n'importe quel moment, nous sommes flexibles et heureux de travailler avec vous afin de mettre en place un plan de commandite qui s'agencera avec votre organisation.\r\n\r\n[Appliquez ici](/2016/sponsors/apply) pour devenir commanditaire de PyCon.  <span class=\"label label-important\">Merci!</span>\r\n\r\nContact\r\n---------\r\nJesse Noller, Responsable des commandites<br>\r\n[jnoller@python.org](mailto:jnoller@python.org \"jnoller@python.org\")<br>\r\n+1 (978) 212-9863\r\n\r\nProfile de la conf\u00e9rence\r\n---------------------\r\n- **Estimation du nombre de participants:** 2000+\r\n- **Profile de l'audience:** Developpeurs, programmeurs and hackers; bloggeurss, auteurs et developpeurs web; CTOs, managers and entrepreneurs; scientifiques, ing\u00e9nieurs et experts.\r\n- **Horaire de la conf\u00e9rence:**\r\n * 2 jours de tutorial: 9\u201310 avril, 2016\r\n * 3 jours d'Expo Hall: 10-12 avril, 2016\r\n * Conf\u00e9rence principale: 11-13 avril, 2016\r\n * Foire \u00e0 l'emploi/Session Poster: 13 avril, 2016\r\n * Sprints de d\u00e9veloppement: 14-17 avril, 2016\r\n- **Venez apprendre \u00e0 propos:** \r\nDu fonctionnement interne de PyCon, de niveau d\u00e9butant et avanc\u00e9. De cas d'utilisations et d'\u00e9tudes de cas. De l'utilisation de Python dans des domaines vari\u00e9s de l'industrie, incluant la robotique, les entreprises en d\u00e9marrage (startups) et les entreprises. Python est derri\u00e8re quelques uns des plus grand sites Web. Acc\u00e9l\u00e9rer votre application Python. La croissance de l'\u00e9cosyst\u00e8me et de la communaut\u00e9.\r\n\r\nSalle d'exposition et horaire \r\n---------------------------------------------\r\n\r\nLa salle d'exposition sera au 220DE du Palais des Congr\u00e8s. La salle d'exposition sera \u00e0 l'ext\u00e9rieur de l'enregistrement et \u00e0 proximit\u00e9 de toutes les sessions. La c\u00e9r\u00e9monie d'ouverture ainsi que les pauses auront lieu dans la salle d'exposition. Cela am\u00e8nera 98%-100% des participants au m\u00eame endroit.\r\n\r\nLa salle d'exposition d'exposition ouvrira le Jeudi, 10 Avril \u00e0 10h00 jusqu'\u00e0 18h00. Il y aura une c\u00e9r\u00e9monie d'ouverture au niveau plancher \u00e0 1800.\r\n\r\n#### Heures d'expositions\r\n* **Expo avec kiosques:** Jeudi, 10 Avril, 2016 - 18h00 \u00e0 20h00 \r\n* **Expo avec kiosques:** Vendredi, 11 Avril, 2016 - 10:00 \u00e0 17h00\r\n* **Expo avec kiosques:** Samedi, 12 Avril, 2016 - 10:00 \u00e0 17:00\r\n* **Foire \u00e0 l'emploi:** Dimanche, 13 Avril, 2016 - 10:00 \u00e0 13:00\r\n\r\nLe d\u00e9part  de la salle d'exposition commencera \u00e0 17h00 Samedi le 12 avril. Tout doit \u00eatre d\u00e9monter pour 19h00. \u00c0 ce moment, nous transformerons la salle d'exposition en foire \u00e0 l'emploi (les d\u00e9tails de la foire \u00e0 l'emploi plus bas).\r\nSi cela est n\u00e9cessaire, nous pourrons renvoyer les banni\u00e8res des commanditaires qui nous fournirons leurs informations de transport. Plus de d\u00e9tails sera inclus dans le manuel du commanditaire que nous envoyons plus tard dans l'ann\u00e9e.\r\n\r\n**Vous pouvez toujours  vous d\u00e9-inscrire de l'espace kiosques dans la salle d'exposition. Toutefois, si vous ne le faites pas avant le d\u00e9but de la conf\u00e9rence et que votre kiosque reste vide, un frais suppl\u00e9mentaire vous sera charg\u00e9. Vous n'avez qu'\u00e0 communiquer avec notre coordinatrice d'\u00e9v\u00e9nement, Ewa Jodlowska (ewa@python.org).**\r\n\r\n#### Informations sur la foire \u00e0 l'emploi\r\n\r\nLors des ann\u00e9es pr\u00e9c\u00e9dentes, la foire \u00e0 l'emploi fut d'un grand succ\u00e8s. Plusieurs compagnies ont trouv\u00e9es des candidats potentiels durant les premi\u00e8res 3 heures de l'\u00e9v\u00e9nement, certains ont re\u00e7u plusieurs centaines de candidatures dans un tr\u00e8s court d\u00e9lais.\r\n\r\nEn 2016, la foie \u00e0 l'emploi sera le dimanche, 13 avril. L'\u00e9v\u00e9nement aura lieu \u00e0 la salle d'exposition 220DE au Palais des Congr\u00e8s. L'installation aura lieu \u00e0 8h00 le dimanche matin. La foire \u00e0 l'emploi est ouverte aux participants de 10h00 \u00e0 13h00 (3 heures). \u00c0 13h00, la salle d'exposition 220DE sera ferm\u00e9e.\r\n\r\nChaque participant aura une table de 3m qui leur sera fournie; Nous n'utilisons pas de kiosques durant la foire \u00e0 l'emploi. Vous pouvez avoir une banni\u00e8re ou un nappe personnalis\u00e9e. Mat\u00e9riel promotionnel et autres sont bienvenus. Il n'y aura pas de prises de courants.\r\n\r\nGardez \u00e0 l'esprit, si quelque ne se passe comme vous le voulez, contactez-nous \u00e0 n'importe quel moment. Nous sommes flexible et nous voulons travailler avec vous pour mettre en place une commandite qui r\u00e9pondra aux besoins de votre entreprise.\r\n\r\nPlus d'informations \u00e0 propos de la salle d'exposition vous sera fournies dans le manuel de l'exposition en Novembre 2013 par notre d\u00e9corateur.\r\n\r\nPlans de commandite\r\n----------------------\r\n\r\n### Niveau de commandite Clef de Voute  \u2016 50 000 $  (Limite: 1)\r\n* 1 Commandite d'un atelier (voire la description plus bas)\r\n* 2 pages couleur d'annonce dans le programme de PyCon\r\n* Description de 250 mots dans le programme de PyCon\r\n* 1 espace pro\u00e9minent de kiosque  dans la salle d'exposition du Jeudi 10 au 12 avril\r\n* Marchandise promotionnelle dans le sac de conf\u00e9rencier (fournit par le commanditaire)\r\n* Positionnement du logo vis-\u00e0-vis du logo de PyCon sur le sac de conf\u00e9rencier (\"PyCon 2016 sponsored by x and y\")\r\n* Lien de la commandite de Clef de Voute sur le site de PyCon\r\n* Communiqu\u00e9s de presse conjoint soulignant le support du commanditaire\r\n* Article de blog de blog soulignant le commanditaire / interview \u00e0 propos de ce qu'ils font en Python\r\n* Banni\u00e8re 12x2 (si fournie) dans la principale salle de la conf\u00e9rence\r\n* Inclus dans la page de la foire \u00e0 l'emploi de PyCon 2016\r\n* Opportunit\u00e9 de r\u00e9serv\u00e9 une table \u00e0 la foire \u00e0 l'emploi du Dimanche 13 avril 2016\r\n* Opportunit\u00e9 de contribuer \u00e0 l'encan PyCon\r\n* Place de choix dans le guide mobile PyCon\r\n* 20 places gratuites pour l'enregistrement\r\n\r\n### Niveau de commandite Diamand \u2016 35 000 $ (Limite: 4)\r\n* 1 Commandite d'un atelier (voire la description plus bas)\r\n* 2 pages couleur d'annonce dans le programme de PyCon\r\n* Description de 200 mots dans le programme de PyCon\r\n* 1 espace pro\u00e9minent de kiosque  dans la salle d'exposition du Jeudi 10 au 12 avril\r\n* Marchandise promotionnelle dans le sac de conf\u00e9rencier (fournit par le commanditaire)\r\n* Positionnement du logo vis-\u00e0-vis du logo de PyCon sur le sac de conf\u00e9rencier (\"PyCon 2016 sponsored by x and y\")\r\n* Lien de la commandite Diamand sur le site de PyCon\r\n* Nom inclus dans les communiqu\u00e9s de presse et les annonces d'\u00e9v\u00e9nements\r\n* Banni\u00e8re 12x2 (si fournie) dans la principale salle de la conf\u00e9rence\r\n* Inclus dans la page de la foire \u00e0 l'emploi de PyCon 2016\r\n* Opportunit\u00e9 de r\u00e9serv\u00e9 une table \u00e0 la foire \u00e0 l'emploi du Dimanche 13 avril 2016\r\n* Opportunit\u00e9 de contribuer \u00e0 l'encan PyCon\r\n* Banni\u00e8re / informations additionnelles dans le guide mobile PyCon\r\n* 12 places gratuites pour l'enregistrement\r\n\r\n### Niveau de comandite Platine \u2016 17 000 $ (Limite: 10)\r\n* Page compl\u00e8te couleur d'annonce dans le programme de PyCon\r\n* Description de 150 mots dans le programme de PyCon\r\n* 1 espace pro\u00e9minent de kiosque  dans la salle d'exposition du Jeudi 10 au 12 avril\r\n* Marchandise promotionnelle dans le sac de conf\u00e9rencier (fournit par le commanditaire)\r\n* Lien de la commandite Platine sur le site de PyCon\r\n* Nom inclus dans les communiqu\u00e9s de presse et les annonces d'\u00e9v\u00e9nements\r\n* Banni\u00e8re 12x2 (si fournie) dans la principale salle de la conf\u00e9rence\r\n* Inclus dans la page de la foire \u00e0 l'emploi de PyCon 2016\r\n* Opportunit\u00e9 de r\u00e9serv\u00e9 une table \u00e0 la foire \u00e0 l'emploi du Dimanche 13 avril 2016\r\n* Opportunit\u00e9 de contribuer \u00e0 l'encan PyCon\r\n* Banni\u00e8re / informations additionnelles dans le guide mobile PyCon\r\n* 8 places gratuites pour l'enregistrement\r\n\r\n### Niveau de comandite Or \u2016 7 000 $ (Limite: 10)\r\n* Annonce de taille moyenne en couleur dans le programme de PyCon\r\n* 1 grand espace de kiosque dans la salle d'exposition du Jeudi 10 au 12 avril\r\n* Description de 100 mots dans le programme de PyCon\r\n* Marchandise promotionnelle dans le sac de conf\u00e9rencier (fournit par le commanditaire)\r\n* Lien de la commandite Or sur le site de PyCon\r\n* Nom inclus dans les communiqu\u00e9s de presse et les annonces d'\u00e9v\u00e9nements\r\n* Banni\u00e8re 12x2 (si fournie) dans la principale salle de la conf\u00e9rence\r\n* Opportunit\u00e9 de r\u00e9serv\u00e9 une table \u00e0 la foire \u00e0 l'emploi du Dimanche 13 avril 2016\r\n* Opportunit\u00e9 de contribuer \u00e0 l'encan PyCon\r\n* Inclus dans la page de la foire \u00e0 l'emploi de PyCon 2016\r\n* 5 places gratuites pour l'enregistrement\r\n\r\n### Niveau de comandite Argent \u2016 4 000 $\r\n* Petite Annonce en couleur dans le programme de PyCon\r\n* Description de 50 mots dans le programme de PyCon\r\n* 1 petit espace de kiosque dans la salle d'exposition du Jeudi 10 au 12 avril\r\n* Marchandise promotionnelle dans le sac de conf\u00e9rencier (fournit par le commanditaire)\r\n* Lien de la commandite Argent sur le site de PyCon\r\n* Nom inclus dans les communiqu\u00e9s de presse et les annonces d'\u00e9v\u00e9nements\r\n* Opportunit\u00e9 de contribuer \u00e0 l'encan PyCon\r\n* Inclus dans la page de la foire \u00e0 l'emploi de PyCon 2016\r\n* 2 places gratuites pour l'enregistrement\r\n\r\n### Supporter PyCon \u2016 $1,500 \r\n* (Pour les individus et les petites entreprises)\r\n* Inclus dans le programme de PyCon\r\n* Inclus comme supporter dans la page des commanditaires\r\n* 1 place gratuite pour l'enregistrement\r\n\r\n#### Informations suppl\u00e9mentaires\r\nLe rabais pour les petites organisations: Les petites organisations (moins de 25 employ\u00e9s) ont droit \u00e0 un rabais de 50 % sur les commandites Or et Argent et pour tous les niveaux vendeurs/exposants.\r\n\r\nKiosques gratuit pour les projets F/OSS: Un kiosque gratuit sera fournit aux projets opensources qui le demandent et si la place est disponible. Les kiosques gratuit doivent \u00eatre confirm\u00e9s imm\u00e9diatement avant la conf\u00e9rence.\r\n\r\n## Options \u00e0 la carte (Peut \u00eatre ajouter \u00e0 n'importe quel autre niveau)\r\n\r\n### Commandite des Pauses Caf\u00e9 durant la conf\u00e9rence \u2016  12 000 $ par jour\r\n* Offre le caf\u00e9 et le th\u00e9 aux participants pour au plus 4 heures durant la conf\u00e9rence\r\n* Positionnement du logo au lieu des pauses caf\u00e9\r\n\r\n### Commandite des Pauses Caf\u00e9 durant les sprints \u2016  6 000 $ par jour\r\n* Offre le caf\u00e9 et le th\u00e9 aux participants durant 4-6 heures durant les sprints\r\n\r\n### Commandite du badge \u2016 ($5K + coup du cordon et du badge) (Limit: 1)\r\n* Offre une grande visibilit\u00e9 durant PyCon\r\n* Logo et texte sur le cordon\r\n* 2 places gratuites pour l'enregistrement\r\n* Peut \u00eatre ajout\u00e9 \u00e0 n'importe quel autre niveau\r\n\r\n### Commandite des Sprints/Sommets \u2016 4 000 $ par jour\r\n* Positionnement du logo dans les salles des sommets/sprints\r\n* Supporte le d\u00e9veloppement de Python ou du sommet du language\r\n* Liens pour la commandite des sprints/sommets sur le site web de PyCon\r\n* 2 places gratuites pour l'enregistrement\r\n* Peut \u00eatre ajout\u00e9 \u00e0 n'importe quel autre niveau\r\n\r\n### Commandite des Ateliers\u2016 3 750 $ par tranche de 1h30  (Limite: 8)\r\n* Tranche de 1h30 durant les tutoriaux (mercredi ou jeudi) \r\n* L'enregistrement pour les participants sera gratuit\r\n* La pause caf\u00e9 sera offerte aux participants\r\n\r\n### Salle d'Open Space branding/signature \u2016 1 000 $\r\n* Positionnement du logo dans les salles des d'openspace\r\n\r\n### Table \u00e0 la foire \u00e0 l'emploi - 5 000 $\r\n* Table de 3m avec 2 chaise pour votre entreprise le Dimanche, 13 Avril, 2016 de 10h00 \u00e0 13h00.\r\n\r\n**Commandite Media:** Veuillez nous contacter \u00e0 pycon-sponsors@python.org", 
        "created": "2012-06-24T11:48:17.514", 
        "publish_date": "2012-06-24T11:48:17", 
        "path": "sponsors/prospectus/"
    }
},
{
    "pk": 7, 
    "model": "cms.page", 
    "fields": {
        "body": "# Exhibit Floor Information and Schedule\r\nThe **Exhibit Hall** will be located in **Hall 220DE** in the **Palais des Congres**.  The Exhibit Hall will be located outside of Registration and in close proximity to all the sessions. The Opening Reception and all Breaks will be located in the Exhibit Hall. This will bring in 98%-100% of all attendees onto the floor.\r\n\r\n- Move-in for the Exhibit Hall begins on Thursday, April 10th at 10:00am until 6:00pm.\r\n- There is an opening reception on the Exhibit Floor at 6:00pm. \r\n\r\n### Exhibit Floor Times\r\n* **Expo with booths:** Thursday, April 10, 2016 - 6:00pm to 8:00pm \r\n* **Expo with booths:** Friday, April 11, 2016 - 10:00am to 5:00pm\r\n* **Expo with booths:** Saturday, April 12, 2013 - 10:00am to 5:00pm\r\n* **Job Fair:** Sunday, April 13, 2013 - 10:00am to 1:00pm\r\n\r\n**Move-out for the Exhibit hall begins at 5:00pm Saturday, April 12th. Everything needs to be cleared out by 7pm.** At this point, we transform the Expo Hall into the Job Fair (details for the job fair below).\r\nIf necessary, we will ship back banners to those sponsors who supply us with a shipping account to use. Further details will be included in the Sponsor Manual, which will be sent out later this year.\r\n\r\n<span class=\"label label-important\">NOTE:</span> You have an option to opt-out of the Booth Space in the Exhibit Hall. However, **if you do not opt-out before the start of the conference and leave your booth empty, a fee will be applied to your sponsorship**. This can be arranged with our Event Coordinator, Ewa Jodlowska (ewa@python.org).\r\n\r\n### Job Fair Information\r\n\r\nIn previous years, we have had an amazing turn out at our Job Fair. Many companies found good prospects during the three hour event, some receiving hundreds of resumes in a short time. \r\n\r\nIn 2016, the Job Fair will be **Sunday, April 13th**. It will be located in **Exhibit Hall 220DE** in the **Palais des Congres**.  Each participant will have a 6 foot table reserved for them. Set up begins at **8:00am Sunday**. The Job Fair is open to attendees from **10:00am to 1:00pm** (3 hours). At 1:00pm, Exhibit Hall 220DE will be cleared out. \r\n\r\n<span class=\"label label-important\">NOTE:</span> **Participating sponsors will have a six foot table and chairs set aside for them; we do not use booths during the Job Fair.** You are welcome to have a standing banner or customized table cloth.  Give aways/flyers are also welcome. Power will not be provided. \r\n\r\nKeep in mind, if you do not see what you want, contact us any time. We are flexible and willing to work with you to design the sponsorship package that will fulfill your business needs.\r\n\r\nMore information regarding the Expo Hall will be sent out in the Exhibit Manual in November 2016 from our decorator.\r\n", 
        "status": 2, 
        "updated": "2013-10-09T21:42:28.456", 
        "title": "Expo Hall Info & Schedule", 
        "body_fr": "# Information et horaire du salon des exposants\r\n\r\nLe **salon des exposants** sera situ\u00e9 dans la **salle 220DE** du **Palais des Congr\u00e8s**.  Le salon des exposants sera situ\u00e9 derri\u00e8re le kiosque d'enregistrement et \u00e0 proximit\u00e9 de toutes les sessions.  Le Gala d'ouverture et toutes les pauses seront tenus dans le salon des exposants.  Ces \u00e9v\u00e9nements compte attirer conjointement de 98% \u00e0 100% des participants au salon des exposants.\r\n\r\n- L'emm\u00e9nagement du salon des exposants commence \u00e0 10h le 10 avril jusqu'\u00e0 18h.\r\n- Le gala d'ouverture se tient dans le salon des exposant le 10 avril \u00e0 partir de 18h.\r\n\r\n### Horaire du salon des exposants\r\n\r\n* **Exposition des kiosques:** jeudi 10 avril, 2016 - de 18h \u00e0 20h \r\n* **Exposition des kiosques:** vendredi 11 avril, 2016 - de 10h \u00e0 17h \r\n* **Exposition des kiosques:** samedi 12 avril, 2016 - de 10h \u00e0 17h \r\n* **Foire de l'emploi:** dimanche 13 avril, 2016 - de 10h \u00e0 13h \r\n\r\n**Le d\u00e9sassemblage du salon des exposants commence \u00e0 17h samedi le 17.  Tout le mat\u00e9riel doit \u00eatre sorti avant 19h.**  C'est \u00e0 ce moment qu'on r\u00e9organise le salon des exposants pour la foire de l'emploi (d\u00e9tails plus bas).  Si n\u00e9cessaire, nous allons exp\u00e9dier les banni\u00e8res en retour aux commanditaires qui nous fournissent un no. compte avec leur compagnie de livraison.  D'autres d\u00e9tails logistiques seront fournis dans le manuel du commanditaire qui sera envoy\u00e9 plus tard cette ann\u00e9e.\r\n\r\n<span class=\"label label-important\">NOTE:</span> Vous avez l'option de ne pas r\u00e9server un kiosque dans le salon des exposants.  **Par contre, si vous gardez la r\u00e9servation de votre kiosque et que ce dernier demeure vide pendant la conf\u00e9rence, des frais additionnels seront ajout\u00e9s \u00e0 votre plan de commandite**.  Les arrangements peuvent \u00eatre faits avec la coordonnatrice de l'\u00e9v\u00e9nement, Ewa Jodloska (ewa@python.org).\r\n\r\n\r\n### Information sur la foire de l'emploi\r\n\r\nPar le pass\u00e9, nous avons re\u00e7u une tr\u00e8s nombreuse participation \u00e0 la foire de l'emploi.  Plusieurs employeurs ont rencontr\u00e9s d'excellents candidats au cours des trois heures de l'\u00e9v\u00e9nement et certains ont m\u00eame mentionn\u00e9 avoir r\u00e9colt\u00e9 plus de 100 CVs durant ce court laps de temps.\r\n\r\nEn 2016, la foire de l'emploi se d\u00e9roulera **dimanche le 13 ao\u00fbt**.  Elle sera situ\u00e9e dans la **salle 220DE** du **Palais des Congr\u00e8s**.  Chaque employeur participant se fera assigner une table de 3m de largeur.  L'emm\u00e9nagement commence \u00e0 **8h dimanche matin**.  La foire de l'emploi est ouverte aux conf\u00e9renciers **entre 10h et 13h** le m\u00eame jour.  \u00c0 13h, le salon de l'emploi sera d\u00e9barrass\u00e9. \r\n\r\n<span class=\"label label-important\">NOTE:</span> **Les commanditaires participants se feront assigner une table de 3m et des chaises; les kiosques du salon des exposants ne sont pas utilis\u00e9s pendant la foire de l'emploi.**  Nous vous invitons \u00e0 installer une banni\u00e8re sur pied et un linge de table personnalis\u00e9 et vous pouvez aussi donner des circulaires ou autre mat\u00e9riel.  Il n'y aura par contre pas de courant \u00e9lectrique disponible aux tables.\r\n\r\nGardez \u00e0 l'esprit que si vous ne trouvez pas ce que vous cherchez comme privil\u00e8ges de commandites, vous pouvez nous en faire part \u00e0 tout moment.  Nous somme flexibles et nous serons ravis de construire un plan de commandite sur mesure qui r\u00e9pondra aux besoins de votre entreprise.\r\n\r\nD'autres informations relatives au salon des exposants et \u00e0 la foire de l'emploi vous seront envoy\u00e9es avec le Guide de l'Exposant en novembre 2013.\r\n", 
        "created": "2012-06-24T12:00:45.449", 
        "publish_date": "2012-06-24T12:00:45", 
        "path": "sponsors/exhibitfloor/"
    }
},
{
    "pk": 8, 
    "model": "cms.page", 
    "fields": {
        "body": "PyCon 2016, taking place for the first time in Canada, will be accepting all types of proposals starting **July 2nd, 2013** through **September 15th, 2013**. Due to the competitive nature of the selection process, we encourage prospective speakers to submit their proposals as early as possible. As with years past, we're looking forward to receiving your best proposals for tutorials, talks, and posters, and for the first time, lightning talks.\r\n\r\n\r\nSubmit a Proposal!\r\n----------------\r\n\r\n<span class=\"label label-important\">Note:</span> **To submit a proposal**, <a href=\"/2016/account/signup/\">sign up</a> or <a href=\"/2016/account/login/\">log in</a> to your account and proceed to your <a href=\"/2016/dashboard/\">account dashboard!</a>\r\n\r\nImportant Dates\r\n-----------------------\r\n\r\n- July 1st, 2013: Call for proposals (talks, lightning talks, tutorials, posters).\r\n- August 13th, 2013: Financial aid application opens.\r\n- September 1st, 2013: Registration opens (early-bird rates are quantity-based).\r\n- September 15th, 2013: Talk and tutorial proposals due.\r\n- October 15th, 2013: Lightning talk proposals due.\r\n- November 1st, 2013: Poster proposals due.\r\n- December 1st, 2013: Financial aid grants awarded (for speakers).\r\n- December 15th, 2013: Conference schedule announced.\r\n- December 15th, 2013: Posters announced.\r\n- January 1st, 2016: Financial aid applications close.\r\n- January 15th, 2016: Financial aid grants awarded.\r\n\r\nAbout PyCon 2016\r\n----------------\r\nThe 2016 conference will run from **April 9, 2016** to **April 17, 2016**, at the Palais des Congr\u00e8s Montr\u00e9al Convention Centre, near the beautiful historic old port of **Montr\u00e9al**. The main conference runs from Friday April 11th through Sunday April 13th, and is preceded by two days of tutorials and followed up by four days of sprints.\r\n\r\n- April 9 \u2013 10, 2016: Tutorials\r\n- April 11 \u2013 13, 2016: Talks\r\n- April 13, 2016: Posters\r\n- April 14 \u2013 17, 2016: Sprints\r\n\r\nAttendance records were once again broken last year, and the schedule was the best we've assembled. Can you help us top 2013?\r\n\r\nWho Should Submit a Proposal?\r\n-----------------------------\r\n**You. Your friends. Your friends' friends.** Anyone with any level of Python knowledge is a candidate for a great topic at this conference. As we get attendees of all kinds, we need speakers of all kinds. In all ways and manners, we try to assemble the most diverse conference we can, and we do that with your help.\r\n\r\nWhether you got started with Python last month or you've been around for 20 years, we think you've got something to share. The Python community is stronger than ever and we're still reaching new areas, new industries, and new users. Be a part of growing Python by helping us change the future.\r\n\r\nYou don't need to be a well traveled professional speaker to get on stage at PyCon. What matters is the topics, the materials, and the drive to present great things to this community. Every year we get first timers and we welcome them and work with them to make everyone feel at home. We also engage our advanced speakers to work with everyone else to share their wisdom and help put together the best show possible.\r\n\r\nAltogether, we received 458 proposals for talks, 129 for tutorials, and a ton of posters in 2013. Let\u2019s see what you have for us this year!\r\n\r\nWhat Kind of Sessions can I Give?\r\n---------------------------------\r\n###Talks: \r\nThese are the traditional talk sessions given during the main conference days, Friday through Sunday. They're mostly **30 minutes long**, but we offer a limited number of 45 minute slots. We organize the schedule into five \"tracks\", grouping talks by topic and having them in the same room for consecutive sessions.\r\n\r\nAs for the topic, that's up to you. We want something for everyone. We want the hot topics in the community right now. We also want the hot topics for the future. Where is Python going? You tell us. You're the people who make those decisions and we want to share them.\r\n\r\nIf you think you have a topic but aren't sure how to propose it, contact our program committee and we'll work with you. We'd love to help you come up with a great proposal.\r\n\r\nTake a look at which talks made it in the last few years. There are a ton of great presentations in there. Hopefully we can include yours in 2016.\r\n\r\n- <a href=\"http://us.pycon.org/2013/schedule/talks/\">PyCon 2013 Talks</a>\r\n- <a href=\"http://us.pycon.org/2012/schedule/\">PyCon 2012 Talks</a>\r\n\r\n###Tutorials: \r\nAs with the talks, we are looking for tutorials that can grow this community at any level. We aim for tutorials that will advance Python, advance this community, and shape the future. There are **3-hour tutorial sessions** presented on Wednesday and Thursday - the two days preceding the main conference. We schedule two tutorial sessions on each day, one in the morning and the other in the afternoon. \r\n\r\nAttention full-time trainers! Please bring your course work to PyCon. Every year we get several educators to bring their show on the road, so show us what you have on the syllabus for 2016!\r\n\r\nAs tutorials are longer than talks and are in an interactive classroom-like setting, they require much more preparation. Due to the amount of work involved, tutorial instructors are compensated, but they are also limited to teaching two tutorials.\r\n\r\n- <a href=\"http://us.pycon.org/2013/schedule/tutorials/\">PyCon 2013 Tutorials</a>\r\n- <a href=\"http://us.pycon.org/2012/schedule/\">PyCon 2012 Tutorials</a>\r\n- <a href=\"https://us.pycon.org/2016/speakers/tutorials/proposals/\">How to submit a tutorial proposal</a>\r\n- <a href=\"http://us.pycon.org/2016/tutorials/suggested_topics/\">Suggested tutorial topics</a>\r\n- <a href=\"https://us.pycon.org/2016/speakers/tutorials/instructors/\">Tutorial information for instructors</a>\r\n\r\n### Lightning Talks:\r\n\r\nWant to give a talk, but do not have enough material for a full talk?  Have a shout-out for an open source project or tool? Want to share a community story (everyone loves stories!)?   Preach the must-know fundamentals of virtualenv, PyPI, import this, etc?  Then lightning talks are for **you**!  These talks are, at **max**, 5 minute talks done in quick succession in the main hall.  No need to fill the whole slot, though!\r\n\r\nThis year, to help you prepare, we are accepting, reviewing, and selecting proposals for lightning talks in advance.\r\n\r\nLightning talks are low stress, tons of fun, and are rumoured to have originated at one of the very first PyCons years ago.\r\n\r\n- <a href=\"http://pyvideo.org/search?models=videos.video&q=lightning+talks\">Past Lightning Talks</a>\r\n- <a href=\"http://us.pycon.org/2016/speakers/lightning-talks/proposals/\">How to submit a lightning talk proposal</a>\r\n\r\n### Posters:\r\nPosters are a recent addition to the Python schedule, but they're a definite hit and back for another round in 2016. The poster session provides a more **interactive**, attendee-driven presentation than the speaker-driven conference talks. Poster presentations have fostered extensive discussions on the topics, with many that have gone on much longer than the actual \"session\" called for. That is *exactly* what we wanted!\r\n\r\nThe idea is to present your topic on a 4' x 4' poster board and as attendees mingle through the rows, they find your topic, read through what you've written, then strike up a discussion on it. It's as simple as that. You could be doing Q&A in the first minute of the session with a group of 10 people.\r\n\r\nAs with the other proposal types, we're really looking to you to talk about what's going on in this community and tell everyone where it's going. If you're doing something awesome, share it.\r\n\r\nFor more information about Posters and the Poster session, see:\r\n\r\n- <a href=\"https://us.pycon.org/2016/posters/\">Poster Session CFP</a>\r\n- <a href=\"https://us.pycon.org/2016/posters/faq\">Poster FAQ</a>\r\n- <a href=\"http://us.pycon.org/2013/schedule/posters/list/\">PyCon 2013 Posters</a>\r\n- <a href=\"http://us.pycon.org/2012/schedule/lists/posters/\">PyCon 2012 Posters</a>\r\n\r\nConference Registration and Travel\r\n----------------------------------\r\nPyCon is entirely volunteer-organized and run, and works hard to keep costs as low as possible. This includes having an <a href=\"http://jessenoller.com/blog/2011/05/25/pycon-everybody-pays\">everyone pays</a> policy: everyone, from the conference chair on down, pays for their own ticket and travel expenses.\r\n\r\nThat said, we do appreciate those who share their knowledge at the conference: Speakers with accepted proposals will receive early bird pricing and have a guaranteed spot at the conference even if we hit the attendance cap. For registration pricing see: [http://us.pycon.org/2016/registration/](http://us.pycon.org/2016/registration/).\r\n\r\nIf early bird pricing and travel would still be a burden, PyCon also has a large **financial aid program** to help those who can\u2019t afford to attend PyCon. Speakers will be prioritized in the financial aid program. For more details, see [http://us.pycon.org/2016/assistance/](http://us.pycon.org/2016/assistance/).\r\n\r\n### Thank you!", 
        "status": 2, 
        "updated": "2013-10-15T19:31:00.813", 
        "title": "Call For Proposals", 
        "body_fr": "PyCon 2016, qui aura lieu pour la premi\u00e8re fois au Canada, acceptera tous les types de propositions entre le **2 juillet 2013** et le **15 septembre 2013**. En raison de la nature comp\u00e9titive du processus de s\u00e9lection, nous encourageons les pr\u00e9sentateurs potentiels \u00e0 soumettre leurs propositions le plus t\u00f4t possible. Comme les ann\u00e9es pass\u00e9es, nous sommes impatients de recevoir vos propositions pour des tutoriels, pr\u00e9sentations et affiches et pour la premi\u00e8re fois, des pr\u00e9sentations \u00e9clair.\r\n\r\n\r\nSoumettre une proposition!\r\n----------------\r\n\r\n<span class=\"label label-important\"> Note: </ span > ** Pour soumettre une proposition **, <a href=\"/2016/account/signup/\">enregistrez-vous</a> ou <a href = \"/ 2016/account/login / \">connectez-vous</a> \u00e0 votre compte et chargez votre <a href=\"/2016/dashboard/\">tableau de bord</a>\r\n\r\nDates \u00e0 retenir\r\n-----------------------\r\n\r\n- 1er juillet 2013 : Appel aux pr\u00e9sentateurs (pr\u00e9sentations, pr\u00e9sentations \u00e9clair, tutoriels, affiches).\r\n- 13 ao\u00fbt 2013 : Ouverture des demandes dl'aide financi\u00e8re.\r\n- 1er septembre 2013 : Ouverture des inscriptions (tarif pr\u00e9liminaires bas\u00e9 sur la quantit\u00e9).\r\n- 15 septembre 2013 : Date butoir pour la proposition de pr\u00e9sentations et tutoriels.\r\n- 15 octobre 2013 : Date butoir pour la proposition de pr\u00e9sentations \u00e9clair.\r\n- 1er novembre 2013 : Date limite pour la proposition d\u2019affiches.\r\n- 1er d\u00e9cembre 2013 : Annonce des demandes d\u2019aide financi\u00e8re retenues (pr\u00e9sentateurs).\r\n- 15 d\u00e9cembre 2013 : Annonce du calendrier de la conf\u00e9rence.\r\n- 15 d\u00e9cembre 2013 : Annonce des affiches retnues.\r\n- 1er janvier 2016 : Annonce des demandes d'aide financi\u00e8re retenues.\r\n- 15 janvier 2016 : Octroi de l\u2019aide financi\u00e8re.\r\n\r\n\u00c0 propos de PyCon 2016\r\n----------------\r\nLa conf\u00e9rence PyCon 2016 aura lieu du **9 avril 2016** au **17 avril 2016** au Palais des Congr\u00e8s de Montr\u00e9al, pr\u00e8s du magnifique vieux port historique de **Montr\u00e9al**. La conf\u00e9rence principale se d\u00e9roule du vendredi 11 avril au dimanche 13 avril et est pr\u00e9c\u00e9d\u00e9e par deux jours de tutoriels et d'un suivi par quatre jours de sprints.\r\n\r\n- 9 - 10 avril 2016 : tutoriels\r\n- 11 - 13 avril 2016 : pr\u00e9sentations\r\n- 13 avril 2016 : affiches\r\n- 14 - 17 avril 2016 : sprints\r\n\r\nUn taux de participation record a \u00e9t\u00e9 atteint l\u2019ann\u00e9e derni\u00e8re pour assister \u00e0 la meilleure conf\u00e9rence PyCon jusqu\u2019\u00e0 ce jour. Pouvez-vous nous aider \u00e0 faire encore mieux qu\u2019en 2013 ?\r\n\r\nQui devrait pr\u00e9senter une proposition ?\r\n-----------------------------\r\nVous. Vos amis. Les amis de vos amis. N'importe qui avec n'importe quel niveau de connaissance en Python est un candidat pour un magnifique sujet \u00e0 cette conf\u00e9rence. Comme nous participants sont divers, nous avons besoin de pr\u00e9sentateurs de toutes sortes. De toutes les mani\u00e8res possibles, nous essayons de r\u00e9unir la conf\u00e9rence la plus diversifi\u00e9e que nous pouvons et nous r\u00e9ussissons gr\u00e2ce \u00e0 vous.\r\n\r\nQue vous avez d\u00e9but\u00e9 en Python le mois dernier ou si vous avez 20 ans d\u2019exp\u00e9rience, nous pensons que vous avez quelque chose \u00e0 partager. La communaut\u00e9 Python est plus forte que jamais et nous continuons \u00e0 nous \u00e9tendre \u00e0 de nouveaux domaines, de nouvelles industries et de nouveaux utilisateurs.\r\n\r\nVous n'avez pas besoin d'\u00eatre un conf\u00e9rencier professionnel qui a beaucoup voyag\u00e9 \u00e0 monter sur sc\u00e8ne \u00e0 PyCon. L\u2019important r\u00e9side dans les th\u00e8mes, le mat\u00e9riel et la volont\u00e9 de pr\u00e9senter de grandes choses pour cette communaut\u00e9. Chaque ann\u00e9e, nous souhaitons la bienvenue \u00e0 de nouveaux participants et travaillons avec eux pour que chacun se sente \u00e0 la maison. Nous t\u00e2chons \u00e9galement de mettre \u00e0 profit le savoir et la sagesse des pr\u00e9sentateurs agu\u00e9ris afin de produire le meilleur \u00e9v\u00e8nement possible.\r\n\r\nAu total, nous avons re\u00e7u 458 propositions de pr\u00e9sentations, 129 tutoriels et une tonne d\u2019affiches en 2013. Nous attendons impatiemment vos propositions pour cette ann\u00e9e !\r\n\r\nQuel type de s\u00e9ance puis-je donner ?\r\n---------------------------------\r\n### Pr\u00e9sentations :\r\nCe sont les s\u00e9ances de d\u00e9bat traditionnelles donn\u00e9es pendant les principaux jours de la conf\u00e9rence, du vendredi au dimanche. Ils durent normalement **30 minutes**, mais nous offrons un nombre limit\u00e9 de s\u00e9ances de 45 minutes. Nous r\u00e9alisons l\u2019horaire en cinq groupes  organis\u00e9s par sujet afin de proposer ces pr\u00e9sentations cons\u00e9cutivement dans une m\u00eame salle.\r\n\r\nEn ce qui concerne le sujet, il vous est libre. Nous voulons qu\u2019il y ait quelque chose pour tout le monde. Nous voulons des sujets d'actualit\u00e9 de la communaut\u00e9. Nous voulons aussi que les sujets d'avenir. O\u00f9 va Python ? Dites-le nous ! Vous \u00eates ceux et celles qui prennent ces d\u00e9cisions et nous voulons les partager avec vous.\r\n\r\nSi vous pensez que vous avez un sujet mais vous ne savez pas comment le proposer, contactez notre comit\u00e9 de programme et nous vous aiderons \u00e0 r\u00e9aliser votre proposition et la rendre parfaite.\r\n\r\nJetez un oeil aux pr\u00e9sentations des ann\u00e9es pr\u00e9c\u00e9dentes. Il y a beaucoup de bonnes pr\u00e9sentations dans le lot. Nous esp\u00e9rons pouvoir inclure la v\u00f4tre en 2016.\r\n\r\n- <a href=\"http://us.pycon.org/2013/schedule/talks/\">Pr\u00e9sentations de PyCon 2013</a>\r\n- <a href=\"http://us.pycon.org/2012/schedule/\">Pr\u00e9sentations de PyCon 2012</a>\r\n\r\n### Tutoriels:\r\nComme pour les pr\u00e9sentations, nous recherchons des tutoriels qui peuvent pousser cette communaut\u00e9 sur tous les plans. Nous visons des tutoriels qui feront avancer Python, avancer la communaut\u00e9 et fa\u00e7onner son avenir. Il y a des **s\u00e9ances de tutoriel de 3 heures** pr\u00e9sent\u00e9es mercredi et jeudi - les deux jours pr\u00e9c\u00e9dant la conf\u00e9rence principale. Nous pr\u00e9voyons deux s\u00e9ances de tutoriel chaque jour : une le matin et l'autre l'apr\u00e8s-midi.\r\n\r\nSi vous \u00eates un formateur \u00e0 temps plein, nous vous encourageons \u00e0 proposer vos cours \u00e0 PyCon. Chaque ann\u00e9e, nous promouvons le travail des enseignants et formateurs. Profitez-en pour nous montrer ce que vous avez sur votre programme pour 2016 !\r\n\r\nComme les tutoriels sont plus longs que les pr\u00e9sentations et sont dans un cadre de type classe interactive, ces s\u00e9ances ont besoin d\u2019une plus grande pr\u00e9paration. En raison de la quantit\u00e9 de travail n\u00e9cessaire, les instructeurs de tutoriel sont indemnis\u00e9s, mais ils sont \u00e9galement limit\u00e9es \u00e0 deux tutoriels chacun.\r\n\r\nUne liste de documents int\u00e9ressants sont disponibles en suivant ces liens :\r\n\r\n- <a href=\"http://us.pycon.org/2013/schedule/tutorials/\">Tutoriels PyCon 2013</a>\r\n- <a href=\"http://us.pycon.org/2012/schedule/\">Tutoriels PyCon 2012</a>\r\n- <a href=\"https://us.pycon.org/2016/speakers/tutorials/proposals/\">Comment soumettre une proposition de tutoriel</a>\r\n- <a href=\"http://us.pycon.org/2016/tutorials/suggested_topics/\">Sujets de tutoriel sugg\u00e9r\u00e9s</a>\r\n- <a href=\"https://us.pycon.org/2016/speakers/tutorials/instructors/\">Informations pour les formateurs de tutoriel</a>\r\n\r\n### Pr\u00e9sentations \u00e9clair:\r\n\r\nVous voulez donner une conf\u00e9rence, mais n'ont pas assez de mat\u00e9riel pour une pr\u00e9sentation compl\u00e8te? Vous d\u00e9sirez partager un projet libre ou un outil que vous avez r\u00e9cemment d\u00e9nich\u00e9 ? Vous souhaitez partager une histoire de communaut\u00e9 (tout le monde aime les histoires !) ? Pr\u00eachez les connaissances fondamentales de virtualenv, PyPI, *import from*, etc ? Les pr\u00e9sentations \u00e9clair sont pour **vous** ! Ces pr\u00e9sentations durent un **maximum** de 5 minutes et sont organis\u00e9es en succession rapide dans le hall principal. Il n\u2019est cependant pas n\u00e9cessaire de remplir ces plages horaire!\r\n\r\nCette ann\u00e9e, pour vous aider \u00e0 pr\u00e9parer vos pr\u00e9sentations \u00e9clair, nous passons en revue et proc\u00e9dons \u00e0 la s\u00e9lection des propositions de pr\u00e9sentations \u00e9clair \u00e0 l'avance.\r\n\r\nDes pr\u00e9sentations \u00e9clair sont peu stressantes, plaisantes et les rumeurs disent m\u00eame qu\u2019elles datent des premiers PyCons il y a des ann\u00e9es.\r\n\r\n- <a href=\"http://pyvideo.org/search?models=videos.video&q=lightning+talks\">Pr\u00e9sentations \u00e9clair pass\u00e9es</a>\r\n- <a href=\"http://us.pycon.org/2016/speakers/lightning-talks/proposals/\">Comment soumettre une proposition de pr\u00e9sentation \u00e9clair</a>\r\n\r\n### Affiches:\r\nLes affiches sont un ajout r\u00e9cent \u00e0 l'horaire de PyCon, mais leur grand succ\u00e8s leur assure un retour en 2016. La s\u00e9ance d\u2019affiches fournit une pr\u00e9sentation **int\u00e9ractive** ax\u00e9e sur l\u2019auditoire plus que l\u2019orateur comme le sont les pr\u00e9sentations. Les pr\u00e9sentations d\u2019affiches ont favoris\u00e9 des discussions approfondies sur plusieurs sujets. Plusieurs pr\u00e9sentatoins d\u2019affiches ont dur\u00e9 beaucoup plus longtemps qu\u2019une pr\u00e9sentation l\u2019aurait permi par le pass\u00e9. C'est *exactement* ce que nous voulons !\r\n\r\nL'id\u00e9e est de pr\u00e9senter votre sujet sur \u200b\u200bune affiche de 4' x 4' (environ 122 cm x 122 cm) et pendant que l\u2019auditoire traversent les lignes d\u2019affiches, ils trouvent votre sujet, lisent ce que vous avez \u00e9crit puis ent\u00e2ment une discussion \u00e0 ce sujet. C'est aussi simple que cela. Vous pourriez, par exemple, faire une formule Foire Aux Questions (F.A.Q.) dans la premi\u00e8re minute de la s\u00e9ance avec un groupe de 10 personnes.\r\n\r\nComme pour les autres types de propositions, nous cherchons \u00e0 vous laisser vous exprimer ce qui se passe dans cette communaut\u00e9 et d\u2019annoncer vos pronostics. Si vous faites quelque chose de g\u00e9nial, l\u2019affiche est la fa\u00e7on id\u00e9ale de le partager!\r\n\r\nPour plus d'informations sur les affiches et la s\u00e9ance d\u2019affiches, voir :\r\n\r\n- <a href=\"https://us.pycon.org/2016/posters/\">S\u00e9ance d\u2019affiches au CFP</a>\r\n- <a href=\"https://us.pycon.org/2016/posters/faq\">FAQ sur les affiches</ a>\r\n- <a href=\"http://us.pycon.org/2013/schedule/posters/list/\">Affiches de PyCon 2013</a>\r\n- <a href=\"http://us.pycon.org/2012/schedule/lists/posters/\">Affiches de PyCon 2012</a>\r\n\r\nInscription \u00e0 la conf\u00e9rence et voyages\r\n----------------------------------\r\nPyCon est un \u00e9v\u00e8nement enti\u00e8rement organis\u00e9 et ex\u00e9cut\u00e9 par des b\u00e9n\u00e9voles et nous travaillons dur pour maintenir les co\u00fbts aussi bas que possible. Cela implique d'avoir un politique <a href=\"http://jessenoller.com/blog/2011/05/25/pycon-everybody-pays\">tout le monde paie</ a> : du pr\u00e9sident de la conf\u00e9rence jusqu\u2019au pr\u00e9sentateurs. Tout le monde paie pour leur propre billet et leur frais de d\u00e9placement.\r\n\r\nCela dit, nous appr\u00e9cions ceux qui partagent leurs connaissances lors de la conf\u00e9rence : les pr\u00e9sentateurs ayant des propositions accept\u00e9es recevront des tarifs r\u00e9duits et verront leur place garantie lors de la conf\u00e9rence, m\u00eame si nous avons atteint la limite de participants. Pour les tarifs d'inscription, voir : [ http://us.pycon.org/2016/registration/ ](http://us.pycon.org/2016/registration/ ).\r\n\r\nSi les tarifs r\u00e9duits ou les co\u00fbts de voyage sont encore prohibitifs pour vous, PyCon dispose \u00e9galement d'un vaste **programme d'aide financi\u00e8re** pour aider ceux qui ne peuvent pas se permettre d'assister PyCon . Les conf\u00e9renciers seront prioritaires dans le programme d'aide financi\u00e8re. Pour plus de d\u00e9tails, voir [http://us.pycon.org/2016/assistance/](http://us.pycon.org/2016/assistance/ ).\r\n\r\n### Merci !\r\n", 
        "created": "2012-07-03T13:56:43.532", 
        "publish_date": "2012-07-03T13:56:43", 
        "path": "speaking/cfp/"
    }
},
{
    "pk": 10, 
    "model": "cms.page", 
    "fields": {
        "body": "#### [This page has moved (click to go there).](/2013/community/welcome)", 
        "status": 2, 
        "updated": "2012-08-13T16:31:50.758", 
        "title": "Welcoming (Un)committee (moved)", 
        "body_fr": "", 
        "created": "2012-07-03T21:28:25.332", 
        "publish_date": "2012-07-03T21:28:25.332", 
        "path": "about/volunteers/welcome/"
    }
},
{
    "pk": 11, 
    "model": "cms.page", 
    "fields": {
        "body": "**Monday, April 14th 2016 \u2013 Thursday, April 17th 2016**\r\n\r\nDevelopment sprints are a key part of PyCon, a chance for the contributors to\r\nopen-source projects to get together face-to-face for up to four days of\r\nintensive learning, development and camaraderie. Newbies sit with gurus,\r\ngo out for lunch and dinner together, and have a great time while advancing\r\ntheir project.\r\n\r\nWhat's a sprint?\r\n-------------------\r\n\r\nPyCon Development Sprints are four days of intensive learning and development\r\non an open source project of your choice, in a team environment.\r\nIt's a time to come together with colleagues, old and new, to share what\r\nyou've learned and apply it to an open source project. \r\n\r\nIn the crucible of a sprint room, teaming with both focus and humor, it's\r\na time to test, fix bugs, add new features, and improve documentation.\r\nAnd it's a time to network, make friends, and build relationships that go\r\nbeyond the conference.\r\n\r\nPyCon provides the space and infrastructure (network, power, tables & chairs);\r\nyou bring your skills, humanity, and brainpower (oh! and don't forget your computer).\r\n\r\n<span style=\"text-align:center\"><a href=\"http://www.youtube.com/watch?v=hOtKgFaFcz0\"><img src=\"http://necaris.net/images/pycon-sprint-video-link.png\" alt=\"Come for PyCon, stay for the sprints!\"/></a></span>\r\n\r\nWho can participate?\r\n--------------------\r\n\r\n**You!** All experience levels are welcome; sprints are a great opportunity\r\nto get connected with, and start contributing to your favorite Python project. **Participation in the sprints is free!**\r\n\r\nWhat's the schedule?\r\n-------------------------\r\n\r\nTBD\r\n\r\nWhere will the sprints be?\r\n-------------------------------\r\n\r\nTBD\r\n\r\nWhich projects are sprinting?\r\n----------------------------------\r\n\r\nTBD\r\n\r\n", 
        "status": 2, 
        "updated": "2013-10-15T19:28:53.868", 
        "title": "Development Sprints", 
        "body_fr": "** Lundi le 14 avril 2016 - Jeudi le 17 avril 2016 **\r\n\r\nLes sprints de d\u00e9veloppement sont un \u00e9l\u00e9ment cl\u00e9 de PyCon qui donnent la chance aux contributeurs de projets libres de se retrouver ensemble pour quatre jours d\u2019apprentissage intensif, le d\u00e9veloppement et la camaraderie. Les d\u00e9butants si\u00e8gent parmis les gourous,\r\nsortir pour d\u00e9jeuner et d\u00eener ensemble et passer un bon moment tout en faisant progresser\r\nleur projet.\r\n\r\nQu'est-ce qu'un sprint ?\r\n-------------------\r\n\r\nLes sprints de d\u00e9veloppement de PyCon se r\u00e9partissent sur quatre jours et permettent l'apprentissage et de d\u00e9veloppement intensifs d\u2019un projet libre de votre choix, dans un environnement d'\u00e9quipe. C'est un moment id\u00e9al pour se r\u00e9unir avec des coll\u00e8gues, anciens et nouveaux, et partager ce que vous avez appris et l'appliquer \u00e0 un projet libre.\r\n\r\nL\u2019atmosph\u00e8re d\u2019une salle de sprint allie collaboration et humour et permet de tester, de corriger les bugs et d\u2019ajouter de nouvelles fonctionnalit\u00e9s et d\u2019am\u00e9liorer la documentation d\u2019un projet.\r\nC'est le moment id\u00e9al pour faire du r\u00e9seautage, se faire des amis et \u00e9tablir des relations qui vont au-del\u00e0 de la conf\u00e9rence.\r\n\r\nPyCon fournit l'espace et l'infrastructure (r\u00e9seau, \u00e9lectricit\u00e9, tables et chaises); vous apportez vos comp\u00e9tences, votre bonne humeur et votre mati\u00e8re grise (oh, n'oubliez pas votre ordinateur!).\r\n\r\n<span style=\"text-align:center\"><a href=\"http://www.youtube.com/watch?v=hOtKgFaFcz0\"><img src=\"http://necaris.net/images/pycon-sprint-video-link.png\" alt=\"Venez \u00e0 PyCon , rester pour les sprints !\"/></a></span>\r\n\r\nQui peut participer ?\r\n--------------------\r\n\r\n**Vous!** Tous les niveaux d'exp\u00e9rience sont les bienvenus; Les sprints sont une excellente occasion d\u2019entrer en contact et de commencer \u00e0 contribuer \u00e0 votre projet Python pr\u00e9f\u00e9r\u00e9.\r\n**La participation aux sprints est gratuite!**\r\n\r\nQuel est le calendrier ?\r\n-------------------------\r\n\r\n\u00c0 d\u00e9finir\r\n\r\nO\u00f9 vont les sprints \u00eatre?\r\n-------------------------------\r\n\r\n\u00c0 d\u00e9finir\r\n\r\nQuels sont les projets sprint ?\r\n----------------------------------\r\n\r\n\u00c0 d\u00e9finir\r\n", 
        "created": "2012-07-04T15:27:26.046", 
        "publish_date": "2012-07-04T15:27:26", 
        "path": "community/sprints/"
    }
},
{
    "pk": 12, 
    "model": "cms.page", 
    "fields": {
        "body": "The more Pythonistas (and Pythonistas-to-be) we gather, the more we can do for the Python community and the better PyCon is. We depend on the Python community to get the word out and make sure people know how fun and useful the conference is! Here are just some of the ways you can help.\r\n\r\n<div style=\"float: left; margin-right: 30px\">\r\n<img src=\"https://github.com/PyCon/2016/blob/master/assets/logos/pycon2015-logo-hires.png?raw=true\" width=\"200\" />\r\n<br />\r\n<br />\r\n<div align=\"center\"><strong>Official PyCon 2016 Logo</strong></div>\r\n<br />\r\n</div>\r\n\r\n- Talk, blog, and tweet about PyCon\r\n- If you have a blog, add PyCon blog badges to it (*coming soon*)\r\n- Spread the news to mailing lists you're on whose members may be interested. Consider not just Python-specific lists, but other lists that Python users or on. (Just be careful not to spam - make sure it's a list where conference announcements are OK!)\r\n- Likewise, spread the news to user groups you belong to.\r\n\r\nPyCon badges are updated year to year, so keep an eye on the [PyCon Blog](http://pycon.blogspot.com) and the Organizer's Mailing list for information on how to correctly include the PyCon badge on your posts.\r\n\r\nAlso, be aware of the [Press Information](../../../about/press/).\r\n", 
        "status": 2, 
        "updated": "2013-09-10T22:03:49.168", 
        "title": "Publicizing PyCon", 
        "body_fr": "Plus nous recrutons de Pythonistas (et de Pthonistas en herbe), plus nous pouvons servir la communaut\u00e9 Python et meilleur est le Pycon. Nous comptons sur la communaut\u00e9 Python \u00e0 faire passer le mot et s'assurer que les gens savent \u00e0 quel point la conf\u00e9rence est amusante et utile! Voici un aper\u00e7u de ce que vous pouvez faire afin de contribuer:\r\n<div style=\"float: left; margin-right: 30px\">\r\n<img src=\"https://github.com/PyCon/2016/blob/master/assets/logos/pycon2015-logo-hires.png?raw=true\" width=\"200\" />\r\n<br />\r\n<br />\r\n<div align=\"center\"><strong>Official PyCon 2016 Logo</strong></div>\r\n<br />\r\n</div>\r\n\r\n- Parler, bloguer, tweeter \u00e0 propos du PyCon\r\n- Si vous avez un blogue, y ajouter des insignes du blog PyCon (*\u00e0 venir*)\r\n- R\u00e9pandre les nouvelles sur des listes de diffusions dont les membres pourraient \u00eatre int\u00e9ress\u00e9s. Consid\u00e9rez non seulement les listes sp\u00e9cifiques \u00e0 Python, mais aussi d'autres listes auxquelles des utilisateurs de Python sont abonn\u00e9s (attention de ne pas faire du spam - assurez-vous que ce soient des listes o\u00f9 les annonces de conf\u00e9rence sont appropri\u00e9es!)\r\n- Pareillement, r\u00e9pandre les nouvelles aux groupes usages auxquels vous appartenez.\r\n\r\nLes insignes PyCon sont mises \u00e0 jour d'ann\u00e9e en ann\u00e9e, alors surveillez le [blogue PyCon](http://pycon.blogspot.com) et la liste de diffusion de l'organisateur pour conna\u00eetre l'information  relatant l'inclusion correcte des insignes PyCon dans vos billets.\r\n\r\nJetez aussi un coup d'oeil sur l'[information pour les m\u00e9dias](../../../about/press/).", 
        "created": "2012-07-04T15:56:55.846", 
        "publish_date": "2012-07-04T15:56:55", 
        "path": "community/volunteers/publicizing/"
    }
},
{
    "pk": 13, 
    "model": "cms.page", 
    "fields": {
        "body": "Press Information\r\n---------------------\r\n\r\nInterested in covering PyCon 2016? Feel free to contact Brian Curtin or Diana Clarke. We also offer Media Passes and Sponsorship which includes:\r\n\r\n- Recognition on PyCon site\r\n- One free conference registration\r\n\r\nContacts\r\n-----------\r\n\r\n- Brian Curtin, Publicity Coordinator<br>\r\n[brian@python.org](mailto:brian@python.org \"brian@python.org\")<br>\r\n+1 (630) 364-0250<br>\r\n\r\n- Diana Clarke, Conference Chair<br>\r\n[diana.joan.clarke@gmail.com](mailto:diana.joan.clarke@gmail.com \"diana.joan.clarke@gmail.com\")<br>\r\n+1 (416) 453-3130\r\n\r\n- PyCon Organizers: [pycon-organizers@python.org](mailto:pycon-organizers@python.org \"pycon-organizers@python.org\")\r\n\r\nPyCon Logos\r\n-----------------\r\n\r\n<img src=\"https://github.com/PyCon/2016/blob/master/assets/logos/pycon2015-logo-hires.png?raw=true\" width=\"200\" />\r\n\r\n<br/>\r\n\r\n<img src=\"https://github.com/PyCon/2016/blob/master/assets/logos/pycon2015-blog-image.png?raw=true\" width=\"300\"/>\r\n", 
        "status": 2, 
        "updated": "2013-09-10T18:40:03.073", 
        "title": "Press Information", 
        "body_fr": "Informations pour les m\u00e9dias\r\n---------------------\r\n\r\nInt\u00e9ress\u00e9 \u00e0 couvrir PyCon 2016? Veuillez contacter Brian Curtin ou Diana Clarke. Nous offrons \u00e9galement des passes M\u00e9dia et du parrainage, ce qui inclut:\r\n\r\n- Reconnaissance sur le site du PyCon\r\n- Inscription gratuite \u00e0 une conf\u00e9rence\r\n\r\nContacts\r\n-----------\r\n\r\n- Brian Curtin, coordonateur de la publicit\u00e9<br>\r\n[brian@python.org](mailto:brian@python.org \"brian@python.org\")<br>\r\n+1 (630) 364-0250<br>\r\n\r\n- Diana Clarke, pr\u00e9sidente de la conf\u00e9rence<br>\r\n[diana.joan.clarke@gmail.com](mailto:diana.joan.clarke@gmail.com \"diana.joan.clarke@gmail.com\")<br>\r\n+1 (416) 453-3130\r\n\r\n- Organisateurs du PyCon 2016: [pycon-organizers@python.org](mailto:pycon-organizers@python.org \"pycon-organizers@python.org\")\r\n\r\nLogos du PyCon\r\n-----------------\r\n\r\n<img src=\"https://github.com/PyCon/2016/blob/master/assets/logos/pycon2015-logo-hires.png?raw=true\" width=\"200\" />\r\n\r\n<br/>\r\n\r\n<img src=\"https://github.com/PyCon/2016/blob/master/assets/logos/pycon2015-blog-image.png?raw=true\" width=\"300\"/>\r\n", 
        "created": "2012-07-04T16:00:04.180", 
        "publish_date": "2012-07-04T16:00:04", 
        "path": "about/press/"
    }
},
{
    "pk": 14, 
    "model": "cms.page", 
    "fields": {
        "body": "Contact\r\n---------\r\n\r\n- PyCon Organizers: [pycon-organizers@python.org](mailto:pycon-organizers@python.org \"pycon-organizers@python.org\")\r\n\r\nIf the matter is especially urgent, please call/contact any of these individuals:\r\n\r\n- Ewa Jodlowska, Event Coordinator<br>\r\n[ewa@python.org](mailto:ewa@python.org \"ewa@python.org\")<br>\r\n+1 (773) 599-3845<br>\r\n\r\n- Diana Clarke, Conference Chair<br>\r\n[diana.joan.clarke@gmail.com](mailto:diana.joan.clarke@gmail.com \"diana.joan.clarke@gmail.com\")<br>\r\n+1 (416) 453-3130<br>\r\n\r\n- Mathieu Leduc-Hamel, Conference Co-Chair<br>\r\n[mathieu@montrealpython.org](mailto:mathieu@montrealpython.org \"mathieu@montrealpython.org\")<br>\r\n+1 (514) 569-2911<br>\r\n\r\nStaff Information\r\n--------------------\r\n\r\nThis page lists the primary points of contact for PyCon 2016. This does not list all of the volunteers, without whom PyCon would not be possible.\r\n\r\n- PyCon Chair: **Diana Clarke**\r\n- PyCon Co-Chair: **Mathieu Leduc-Hamel**\r\n- Sponsorship Chair: **Jesse Noller**\r\n- Sponsorship Co-Chair:\r\n- Publicity Coordinator: **Brian Curtin**\r\n- Operations Chair: **Douglas Napoleone**\r\n- Operations Co-Chair:\r\n- Event Coordinator: **Ewa Jodlowska**\r\n- Tech Lead: **Noah Kantrowitz**\r\n- Tech Co-Lead: **Pior Bastida**\r\n- Networking: **Sean Reifschneider**\r\n- Diversity Outreach Chair: **Jessica McKellar**\r\n- Program Committee Chair: **Luke Sneeringer**\r\n- Program Committee Co-Chair: **Alex Gaynor**\r\n- Tutorials Chair: **Stuart Williams**\r\n- Tutorials Co-Chair: **Ruben D. Orduz**\r\n- Posters Chair: **Juan Gomez**\r\n- Posters Co-Chair: **Gustavo Pinto**\r\n- Lightning Talk Chair: **Lynn Root**\r\n- Lightning Talk Co-Chair: **Nilovna Bascunan-Vasquez**\r\n- Financial Aid Chair: **Peter Kropf**\r\n- Financial Aid Co-Chair: **Jean-Philippe Caissy**\r\n- Session Staff Chair: **David Wolever**\r\n- Session Staff Co-Chair: **Anna Ravenscroft**\r\n- Startup Row Coordinators: **Yannick Gingras** & **Don Sheu**\r\n- Open Spaces Coordinators: **Laurens Van Houtven** & **Terry Peppers**\r\n- Sprint Coordinators: **Kushal Das** & **Rami Chowdhury** & **Dan Callahan**\r\n- Volunteer Coordinators: **Yarko Tymciurak**\r\n- Print Program Coordinator:\r\n- Mobile Guide Coordinator: **Felix Crux**\r\n- Sponsors Coordinator: **Greg Aker**\r\n- International Travel Coordinator: **Rami Chowdhury**\r\n- Python Language Summit Coordinators: **Michael Foord**\r\n- Education Summit Coordinators: **Naomi Ceder**\r\n- Young Coders Coordinators: **\u00c9ric Araujo**\r\n- 5k Charity Run Coordinators: **Cyril Robert**\r\n- Charity Auction Coordinators: **Douglas Napoleone**\r\n- Swag Head: **Paul Hildebrandt**\r\n- Insiders Guide Coordinators: **Davin Baragiotta**\r\n- Memories Officer: **Taavi Burns**\r\n- Green Committee Chair: **Marianne Corvellec**", 
        "status": 2, 
        "updated": "2013-10-14T09:53:06.405", 
        "title": "Staff Information", 
        "body_fr": "", 
        "created": "2012-07-04T16:04:00.607", 
        "publish_date": "2012-07-04T16:04:00", 
        "path": "about/staff/"
    }
},
{
    "pk": 15, 
    "model": "cms.page", 
    "fields": {
        "body": "### Help choose the talks that will make up the PyCon Conference Days.\r\n\r\nWe regularly receive more than twice as many proposals as we have slots to fill (lately, 5x). It is tough choosing. We expect many high-quality proposals to choose from this coming year too, so we need reviewers! Be aware that as proposals may contain sensitive information, only people known in the Python/PyCon community will be invited to participate.\r\n\r\nExpect to commit, on average, from 4 to 8 hour per week, from August into December.\r\n\r\n### How to volunteer\r\n\r\nIf you're ready to make the commitment:\r\n\r\n- [Sign up for the program committee mailing list](http://mail.python.org/mailman/listinfo/pycon-pc)\r\n- Review the [program committee guide](/2016/pc/guide).\r\n- Log into your account, and confirm you have access to review and vote on proposals.\r\n\r\nThe more reviewers we have the fewer talks each person will need to review. Our review meetings have evolved a process which is now quite streamlined, fun (yes, fun!), and rather consistent.", 
        "status": 2, 
        "updated": "2013-07-01T20:32:34.197", 
        "title": "Program Committee", 
        "body_fr": "", 
        "created": "2012-07-04T16:06:43.216", 
        "publish_date": "2012-07-04T16:06:43.216", 
        "path": "community/volunteers/programcommittee/"
    }
},
{
    "pk": 17, 
    "model": "cms.page", 
    "fields": {
        "body": "### Help choose the courses presented on Tutorial Days.\r\n\r\nTutorials are offered on the days preceding the conference. Every year, more people attend tutorials.\r\n\r\nA partial list of what's needed to prepare for PyCon tutorial offerings:\r\n\r\n- get the word out about tutorials;\r\n- review and select proposals;\r\n- organize class rooms, equipment, class notes, class slides, release forms...\r\n\r\nThere is no shortage of things to do.\r\n\r\n### How to Volunteer\r\n\r\nIf this sounds appealing to you, get in touch with the tutorial coordinator (listed on the [PyCon Staff page](../../../about/staff/) and ask how you can help.", 
        "status": 2, 
        "updated": "2012-07-08T13:08:18.021", 
        "title": "Tutorial Committee", 
        "body_fr": "", 
        "created": "2012-07-04T16:08:43.669", 
        "publish_date": "2012-07-04T16:08:43.669", 
        "path": "community/volunteers/tutorialcommittee/"
    }
},
{
    "pk": 18, 
    "model": "cms.page", 
    "fields": {
        "body": "### Figure out what is going to happen, and make it happen.\r\n\r\n- Who is going to talk?\r\n- How are we going to find them?\r\n- What will they talk about?\r\n- What will we eat?\r\n- How should the chairs/tables be arranged?\r\n- How can we get more sprinters involved?\r\n- ...what else can you think of to go on this list?\r\n\r\nIf you think this is all under control... think again. We need your help!\r\n\r\n### How to volunteer\r\n\r\nPlease subscribe to [the pycon-organizers mailing list][pycon-organizers]. This is the central list, so anyone doing anything (or spotting things that need to be done!) should be on it.\r\n\r\n[pycon-organizers]: http://mail.python.org/mailman/listinfo/pycon-organizers \"PyCon Organizers' Mailing List\"", 
        "status": 2, 
        "updated": "2012-07-04T16:10:23.771", 
        "title": "Conference Committee", 
        "body_fr": "", 
        "created": "2012-07-04T16:10:01.384", 
        "publish_date": "2012-07-04T16:10:01.384", 
        "path": "community/volunteers/conferencecommittee/"
    }
},
{
    "pk": 19, 
    "model": "cms.page", 
    "fields": {
        "body": "Poster Sessions\r\n-------------------\r\n\r\nA poster is a 4' x 4' graphical summary of the key points about your project which forms the starting point for a brief and interactive presentation to interested viewers. The presentation space is one side of a standalone poster board that you can tack posters or individual pages onto. \r\n\r\nThe poster sessions provide another way of presenting that encourages more **one-on-one communication** between the presenter and the audience. Poster sessions are particularly suited for topics of interest to a subset of the community, and we anticipate these sessions will provide an \"incubator\" for further discussions.\r\n\r\n<span class=\"label label-important\">Note:</span>: To submit a poster proposal, <a href=\"/2016/account/signup/\">sign up</a> or <a href=\"/2016/account/login/\">log in</a> to your account and proceed to your <a href=\"/2016/dashboard/\">account dashboard!</a>\r\n\r\nCall for Poster Proposals\r\n-------------------------\r\n\r\nYou must create a speaker profile on the website (and be logged in) in order to submit a poster proposal. \r\n\r\nBe sure to include a one paragraph biography, written in the third person (\"Presenter Name is...\"); include where you live, your job, your projects, books you've written, volunteer activities, etc. We use this for the conference guide, and other promotional materials.\r\n\r\nThe primary author should submit the proposal, after which additional authors can be added (they must have accounts too).\r\n\r\nFor general advice on developing and submitting a proposal see :\r\n\r\n- [So You Want To Present a Talk/Tutorial/Poster At PyCon](/2016/speaking/proposal_advice/ \"So You Want To Present a Talk/Tutorial/Poster At PyCon\")\r\n- [Poster Session FAQ](/2016/posters/faq \"Poster Session FAQ\") \r\n\r\nAlso take a look at past poster sessions to get a sense of the breadth of topics.\r\n\r\n- <a href=\"http://us.pycon.org/2013/schedule/posters/list/\">PyCon 2013 Posters</a>\r\n- <a href=\"http://us.pycon.org/2012/schedule/lists/posters/\">PyCon 2012 Posters</a>\r\n\r\nIf your questions still aren't answered feel free to email [Juan Gomez](mailto:juan.gomez@ieee.org).\r\n\r\nImportant Dates\r\n---------------\r\n\r\n- July 1st, 2013: Call for poster proposals.\r\n- September 1st, 2013: Registration opens.\r\n- September 1st, 2013: Financial aid application opens.\r\n- November 1st, 2013: Poster proposals due.\r\n- December 1st, 2013: Financial aid awards announced.\r\n- December 15th, 2013: Posters announced.\r\n- April 13, 2016: Poster sessions.\r\n\r\n### Thank-you!", 
        "status": 2, 
        "updated": "2013-10-12T19:55:42.138", 
        "title": "Poster Session", 
        "body_fr": "Session d'affiches\r\n------------------\r\n\r\nUne affiche est un r\u00e9sum\u00e9 graphique des points cl\u00e9s de votre projet.  C'est l'\u00e9tincelle qui allume des discussions br\u00e8ves et interactives avec les visiteurs int\u00e9ress\u00e9s.  Les pr\u00e9sentation se donnent devant un tableau et vous \u00eates libre d'y accrocher une affiche, une s\u00e9rie de feuilles d\u00e9tach\u00e9es, ou un autre support visuel.\r\n\r\n<span class=\"label label-important\">Note:</span> Pour soumettre une affiche, <a href=\"/2016/account/login/\">authentifiez vous</a> ou <a href=\"/2016/account/signup/\">cr\u00e9ez un compte</a> puis acc\u00e9dez \u00e0 votre <a href=\"/2016/dashboard/\">tableau de bord</a>.\r\n\r\n\r\nAppel aux propositions d'affiches\r\n---------------------------------\r\n\r\nVous devez cr\u00e9er un profile de pr\u00e9sentateurs sur le site web (et par cons\u00e9quent \u00eatre authentifi\u00e9) pour soumettre une proposition d'affiche.\r\n\r\nAssurez vous d'inclure une biographie en un paragraphe \u00e0 la troisi\u00e8me personne (\"le pr\u00e9sentateur s'appelle...\"); mentionnez o\u00f9 vous vivez, votre travail, vos projets, les livres que vous avez \u00e9crits, votre implication dans la communaut\u00e9, et autre...  Nous affichons ces informations dans le programme de la conf\u00e9rence et dans notre mat\u00e9riel publicitaire.\r\n\r\nL'auteur principal devrait soumettre la proposition.  Par la suite, les auteurs additionnels peuvent \u00eatre ajout\u00e9s (ils doivent tous avoir un compte sur le site web).\r\n\r\nPour d'autres conseils sur la soumission d'une propositon, voir: \r\n- [Donc, vous voulez pr\u00e9sentez \u00e0 PyCon](/2016/speaking/proposal_advice/ \"So You Want To Present a Talk/Tutorial/Poster At PyCon\")\r\n- [Foire aux questions: sessions d'affiches](/2016/posters/faq \"Poster Session FAQ\") \r\n\r\nAussi, jettez un oeil aux affiches soumises par le pass\u00e9 pour voir le genre de sujets couverts:\r\n- <a href=\"http://us.pycon.org/2013/schedule/posters/list/\">PyCon 2013: affiches</a>\r\n- <a href=\"http://us.pycon.org/2012/schedule/lists/posters/\">PyCon 2012: affiches</a>\r\n\r\nSi vous avez d'autres questions, n'h\u00e9sitez pas \u00e0 contacter [Juan Gomez](mailto:juan.gomez@ieee.org).\r\n\r\n\r\nDates \u00e0 retenir\r\n-----------\r\n\r\n- 1er juillet 2013: Appel aux propositions d'affiches.\r\n- 1er septembre 2013: Ouverture des inscriptions.\r\n- 1er septembre 2013: Ouverture des demandes d'aide financi\u00e8re.\r\n- 1er novembre 2013: Date butoir pour les propositions d'affiches.\r\n- 1er d\u00e9cembre 2013: D\u00e9voilement des attributions d'aide financi\u00e8re.\r\n- 15 d\u00e9cembre 2013: D\u00e9voilement des affiches s\u00e9lectionn\u00e9es.\r\n- 13 avril 2013: Sessions d'affiche.\r\n\r\n### Merci!", 
        "created": "2012-07-04T16:46:32.472", 
        "publish_date": "2012-07-04T16:46:32", 
        "path": "posters/"
    }
},
{
    "pk": 20, 
    "model": "cms.page", 
    "fields": {
        "body": "Poster session questions and answers\r\n------------------------------------\r\n\r\n### Q: What is a poster session?\r\n\r\nA: A poster session is a plenary session where each speaker is given space to display their work as a poster. During the session, speakers stand with their posters, and the audience circulate freely, seeking out the particular presentations they are interested in and talking directly to the presenter in small groups. For PyCon 2011, we will have a designated plenary poster session and will be providing space for posters 4x4 feet in size. [This video](http://www.youtube.com/watch?v=1dyzaZjwdfE \"poster video\") will give you an idea of what poster sessions are.\r\n\r\n### Q: What makes a good poster presentation?\r\n\r\nA: First, a good proposal. Poster sessions are intended to give you the chance to present interesting ideas and start conversations with others. Additionally, proposal titles and abstracts are one of the major tools the audience will use to identify posters of interest, so it is important to communicate clearly.\r\n\r\nSecond, the poster itself. It is important to understand that a poster is neither a paper nor a slideshow. The poster isn't there for the audience to just read, it is a visual aid for you to use in creating a quick engaging impromptu presentation, and to refer to in answering questions and fueling discussion. Use this session as a way to make connections with people that you can continue through the open spaces or informally during the conference.\r\n\r\n### Q: Can I submit both a poster and a talk proposal?\r\n\r\nA: Absolutely! We encourage everyone to submit a poster proposal even if they have also submitted a talk proposal. If both are accepted, we encourage authors to adapt their presentation to make the best use of each venue. Even if a talk proposal can not be accommodated by the program committee, it may still be well suited for a poster presentation.\r\n", 
        "status": 2, 
        "updated": "2013-10-10T11:58:24.764", 
        "title": "Poster FAQ", 
        "body_fr": "Foire aux questions: session d'affiches\r\n----------------------------------------\r\n### Q: Qu'est-ce que la session d'affiche?\r\n\r\nR: La session d'affiches est un moment  pendant lequel chaque pr\u00e9sentateur est assign\u00e9 \u00e0 une espace o\u00f9 il peut pr\u00e9senter son travail sur une affiche.  Au cours de la session, le pr\u00e9sentateur se tiens devant son affiche alors que l'audience arpente librement le plancher en qu\u00eate d'une affiche qui pique sa curiosit\u00e9.  Les participants s\u2019agglom\u00e8rent autour d'un pr\u00e9sentateur en petit groupes et l'engage, soit par des questions, soit en \u00e9coutant son discourt.  L'espace d\u00e9sign\u00e9 pour les affiches peut accommoder des imprim\u00e9s de 2m par 2m.  [Cette vid\u00e9o](http://www.youtube.com/watch?v=1dyzaZjwdfE \"poster video\") est un bon exemple de session d'affiche.\r\n\r\n\r\n### Q: Qu'est qui rend une affiche int\u00e9ressante?\r\n\r\nR: Premi\u00e8rement, une proposition bien mont\u00e9e.  Le but de la session d'affiches et de vous donner l'occasion d'\u00e9changer vos id\u00e9es et d'engager la conversation avec d'autres participants.   Autrement, le titre et la description de l'affiche est le principal facteur utilis\u00e9 pas les visiteurs pour choisir quelles affiches aller voir.  Il est donc crucial que ces descriptifs soient int\u00e9ressants et engageants. \r\n\r\nEn second lieu c'est l'affiche elle m\u00eame.  Il est important de comprendre qu'une affiche n'est ni une dissertation ni un diaporama.  L'affiche n'est pas la pour la faire lire aux visiteurs, c'est une aide visuelle pour faciliter des pr\u00e9sentations dynamiques, impromptu, et interactives devant de petits groupes.  Utilisez se moment pour b\u00e2tir des liens avec les visiteurs que vous pouvez solidifier pendant le reste de la conf\u00e9rence.\r\n\r\n\r\n### Q: Puis-je \u00e0 la fois soumettre une affiche et une pr\u00e9sentation magistrale?\r\n\r\nR: D\u00e9finitivement!  Nous invitons tout le monde \u00e0 soumettre une affiche m\u00eame si ils ont d\u00e9j\u00e0 soumit une pr\u00e9sentation magistrale.  Si les deux sont accept\u00e9s, nous vous encourageons \u00e0 adapter les deux pr\u00e9sentations pour \u00eatre compl\u00e9mentaires.  Aussi, quand une proposition de pr\u00e9sentation magistrale n'est pas retenue, il est quand m\u00eame sugg\u00e9r\u00e9 de la proposer comme une affiche car ce format offre plus de flexibilit\u00e9.", 
        "created": "2012-07-04T16:48:28.253", 
        "publish_date": "2012-07-04T16:48:28", 
        "path": "posters/faq/"
    }
},
{
    "pk": 21, 
    "model": "cms.page", 
    "fields": {
        "body": "## So You Want To Present at PyCon?\r\n\r\nWe are grateful for your interest in presenting at PyCon 2016. This document is a guide to help you submit the best possible proposal, and tips to make your proposal more likely to be accepted. Please keep in mind that many more proposals are submitted for talks, tutorials, and posters than can be accepted; following the recommendations provided here will increase your chance of acceptance.\r\n\r\n### Good Ideas\r\n\r\n* **Submit your proposal early.** The program committee will provide feedback to talks in our system, and we _will_ work with you to improve your proposal if we have issues with it, but we can only do this if your talk is in before the deadline.\r\n\r\n* In your abstract, be sure to include answers to some basic questions:\r\n\r\n    * Who is the intended audience for your talk? (Be specific; \"Python programmers\" is not a good answer to this question.)\r\n\r\n    * What will attendees get out of your talk? When they leave the room, what will they know that they didn't know before?\r\n\r\n* Your outline should be an _enumeration_ of what you intend to say, along with time estimates.\r\n\r\n    * It is not necessary to have completely written or planned your talk already, but you should have a basic idea of what the over-arching points you intend to make are, and roughly how long you will spend on each one.\r\n\r\n    * If you are requesting a 45-minute slot, remember that these are in very limited supply. Be sure to explain how you will change your talk if we can only offer you a 30-minute slot.\r\n\r\n* Ensure that your talk will be relevant to a non-trivial set of people. If your talk is on a particular Python package or piece of software, it should be something that a decent number of people use or want to use. If your talk is about a package that you are writing, ensure that it's gained _some_ acceptance before submitting a talk.\r\n\r\n* Include links to source code, articles, blog posts, or other writing that adds context to the presentation.\r\n\r\n* If you've given a talk, tutorial, or other presentation before, especially at an earlier PyCon or another conference, include that information as well as a link to slides or a video if they're available.\r\n\r\n* Fill out your outline and biography completely, but concisely. The outline and background information often are used to eliminate proposals during the first cut, so incomplete details may be a cause for early rejection of a potentially great talk or tutorial. Don't let this happen to you!\r\n\r\n### Bad Ideas\r\n\r\n* Avoid infomercials.\r\n\r\n    * That doesn't mean you can't talk about your work or company at PyCon. For instance, we welcome talks on how you or your company solved a problem, or notable open source projects that may benefit attendees.\r\n\r\n    * On the other hand, talks on \"how to use our product\" (or similar) usually aren't appropriate.\r\n\r\n* Avoid presenting a proposal for code that is far from completion. The program committee is _very_ skeptical of \"conference-driven development\". \r\n\r\n* Avoid \"state of our project\" talks, unless you can make a compelling argument that the talk will be well-attended and that attendees will gain value from it.\r\n\r\n* Do not assume that everyone on the Program Committee will know who you are simply because you have presented at PyCon in the past. Everyone should submit a full proposal.\r\n\r\n### More Information\r\n\r\nFor more resources to help prepare your proposal, see [Proposal Resources](http://us.pycon.org/2016/speaking/proposal-resources/).", 
        "status": 2, 
        "updated": "2013-07-01T21:54:15.529", 
        "title": "Proposal Advice", 
        "body_fr": "", 
        "created": "2012-07-05T14:17:21.879", 
        "publish_date": "2012-07-05T14:17:21.879", 
        "path": "speaking/proposal_advice/"
    }
},
{
    "pk": 23, 
    "model": "cms.page", 
    "fields": {
        "body": "Python Language Summit\r\n------------------------------\r\n\r\nThe Python Language Summit is an invitation-only event for the\r\ndevelopers of Python implementations (CPython, IronPython, Jython,\r\nParrot, PyPy, etc.) to share information, discuss our shared problems\r\nand hopefully solve them.\r\n\r\nThese issues might be related to the language itself, the standard\r\nlibrary, the development process, Python 3.x and 2.x, the\r\ndocumentation, package index, web site, etc.  The Summit will focus on\r\ndiscussion more than on presentations.\r\n\r\n_More information coming soon._", 
        "status": 2, 
        "updated": "2013-10-10T12:17:49.885", 
        "title": "  Python Language Summit", 
        "body_fr": "\r\n\r\nSommet du langage Python\r\n------------------------------\r\n\r\nLe Sommet du langage Python est un \u00e9v\u00e9nement sur invitation seulement pour les d\u00e9veloppeurs des impl\u00e9mentations de Python (CPython, IronPython, Jython, Parrot, PyPy, etc) afin de partager des informations, de discuter de nos probl\u00e8mes communs et, nous esp\u00e9rons, de les r\u00e9soudre.\r\n\r\nCes probl\u00e8mes peuvent \u00eatre li\u00e9s au langage-m\u00eame, \u00e0 la biblioth\u00e8que standard, au processus de d\u00e9veloppement, \u00e0 Python 3.x et 2.x, \u00e0 la documentation, \u00e0 l'indice de paquetage, au site web, etc. Le sommet se concentrera davantage sur des discussions plut\u00f4t que des pr\u00e9sentations.\r\n\r\n_Plus d'informations bient\u00f4t._\r\n", 
        "created": "2012-07-05T16:18:04.460", 
        "publish_date": "2012-07-05T16:18:04", 
        "path": "events/langsummit/"
    }
},
{
    "pk": 24, 
    "model": "cms.page", 
    "fields": {
        "body": "Tutorial Information For Instructors\r\n====================================\r\n\r\n\r\nThis page provides information about [Tutorials](/2016/tutorials/) at PyCon for (potential) Instructors.\r\n\r\nSubmitting a Tutorial Proposal\r\n------------------------------\r\n\r\nIf you're interested in teaching a tutorial, please read these:\r\n\r\n- The [Call for Proposals](/2016/speaking/cfp/) &mdash; specifically the section on\r\n  Tutorials.\r\n\r\n- [So You Want To Present a Talk/Tutorial/Poster At\r\n  PyCon](/2016/speaking/proposal_advice) for general advice on developing and\r\n  submitting a proposal.\r\n\r\n- [How to Submit a Tutorial Proposal](/2016/speakers/tutorials/proposals/ ) for more specific information about\r\n  developing and submitting a tutorials proposal.\r\n\r\n- [Past Topic Suggestions](/2016/tutorials/suggested_topics) for tutorial ideas.  However, you are\r\n  free to submit a proposal for a topic that has not been suggested.\r\n\r\nOther Information\r\n-----------------\r\n\r\nAll of the links above are related to developing and submitting a\r\nproposal.  As the conference approaches we plan to add more information for\r\ninstructors such as:\r\n\r\n- Preparing for tutorials\r\n- Advice and deadlines for creating handouts\r\n- Ensuring students have their laptops configured correctly\r\n- Communicating to students\r\n", 
        "status": 2, 
        "updated": "2013-10-15T19:26:50.139", 
        "title": "Tutorial Instructors", 
        "body_fr": "Informations sur les tutoriels pour les instructeurs\r\n====================================\r\n\r\n\r\nCette page fournit des informations sur les [Tutoriels](/2016/tutorials/) \u00e0 PyCon pour les instructeurs potentiels.\r\n\r\nSoumission d'une proposition de tutorat\r\n------------------------------\r\n\r\nSi vous \u00eates int\u00e9ress\u00e9 par la pr\u00e9sentation d'un tutoriel, veuillez lire ces documents:\r\n\r\n- L\u2019[Appel aux pr\u00e9sentations](/2016/speaking/cfp/) - sp\u00e9cifiquement la section\r\n  Tutoriels.\r\n\r\n- [Donc vous voulez pr\u00e9senter une conversation / Tutorial / affiche de PyCon](/2016/speaking/proposal_advice) pour des conseils g\u00e9n\u00e9raux sur le d\u00e9veloppement et la soumission une proposition.\r\n\r\n- [Comment soumettre une proposition d'un tutoriel](/2016/speakers/tutorials/proposals/ ) pour des renseignements plus pr\u00e9cis sur l\u2019\u00e9laboration et la soumission d\u2019une proposition de tutoriel.\r\n\r\n- [Suggestions de sujet ant\u00e9rieures](/2016/tutorials/suggested_topics/ ) pour des id\u00e9es de didacticiel. Cependant, vous \u00eates libre de soumettre une proposition sur un sujet qui n'a pas \u00e9t\u00e9 sugg\u00e9r\u00e9.\r\n\r\nInformations compl\u00e9mentaires\r\n----------------------------\r\n\r\nTous les liens ci-dessus sont li\u00e9s au d\u00e9veloppement et \u00e0 la soumission d\u2019une\r\nproposition. \u00c0 l'approche de la conf\u00e9rence, nous pr\u00e9voyons l\u2019ajout d'informations compl\u00e9mentaires pour les instructeurs telles que :\r\n\r\n- La pr\u00e9paration des tutoriels\r\n- Des conseils et dates butoires pour la cr\u00e9ation de prospectus\r\n- S\u2019assurer que les \u00e9l\u00e8ves aient leur ordinateur portable configur\u00e9 correctement\r\n- La communication aux \u00e9tudiants", 
        "created": "2012-07-05T20:32:23.760", 
        "publish_date": "2012-07-05T20:32:23", 
        "path": "speakers/tutorials/instructors/"
    }
},
{
    "pk": 25, 
    "model": "cms.page", 
    "fields": {
        "body": "<h1 class=\"shift\">How to Submit a Tutorial Proposal</h1>\r\n\r\nThis page gives detailed instructions and advice on how to submit a proposal for a tutorial at PyCon.\r\n\r\nFor general information about tutorials, see [Tutorial Information for Instructors](/2016/speakers/tutorials/instructors/).\r\n\r\nFor general advice on developing and submitting a proposal see [So You\r\nWant To Present a Talk/Tutorial/Poster at PyCon](/2016/speaking/proposal_advice/), Tutorials given in [2013](/2013/schedule/tutorials), and [Past Tutorial Topic Suggestions](/2016/tutorials/suggested_topics).\r\n\r\n\r\nWhat information to submit\r\n--------------------------\r\n\r\n1. First, <a href=\"/2016/account/signup/\">sign up for a new account</a> or <a href=\"/2016/account/login/\">log in</a> to your account.\r\n2. Once you are logged in; proceed to your <a href=\"/2016/dashboard/\">account dashboard</a> and create a speaker profile.\r\n3. At this point, you can submit tutorials, fill in the fields as follows:\r\n\r\n### Title\r\n\r\nGive your tutorial a name that accurately describes what it's about to potential students.\r\n\r\n### Description\r\n\r\nA high-level description of the tutorial, limited to 400 characters.\r\n\r\n### Abstract\r\n\r\nTry to include the following to help participants decide if this is a good match for them:\r\n\r\n- What the tutorial aims to teach students.\r\n\r\n- Prerequisites for the tutorial, i.e., what students should know or be able to do before the tutorial.  For example, \"Students should have at least intermediate-level Python and SQL and have some experience using an ORM.\"\r\n\r\n- Prerequisites for their laptop (assuming one is required).  Note that these prerequisites serve two purposes:\r\n\r\n    1. They may help the potential student understand more precisely what\r\n       you plan to teach.\r\n\r\n    2. They help ensure students arrive with the software they need to\r\n       take the tutorial.  If possible, finalize these prerequisites and\r\n       submit them with your proposal.  However, we realize that in some\r\n       cases the prerequisites may change as you prepare to teach your\r\n       tutorial, and in a few cases the prerequisites will be complex enough\r\n       that they'll need their own page on instructions.  We're working on\r\n       how best to communicate to students in both cases.\r\n\r\n- Any information you're providing to reviewers (such as tutorial format or outline) that potential students will also want to know to help them decide if this tutorial is a good match for them.\r\n\r\n### Audience Level\r\n\r\nAt what level of Python and other topic-specific experience or\r\nexpertise is the tutorial aiming for?  We realize this may be too\r\nnarrow for a tutorial, for example if the tutorial is aimed at\r\nExperienced programmers but Novices to Python, but give it your best\r\nshot.  If this field doesn't work well, be sure to include a note in\r\nthe Additional Notes section, and you may also wish to add to your\r\nDescription or Abstract.\r\n\r\n### Additional Notes\r\n\r\nThis is the one section that is for reviewers only, so it should have\r\nlots and lots of information to help reviewers decide which tutorials\r\nto accept, based on both the subject being taught and the ability of\r\nthe teacher.  The following information should be included:\r\n\r\n- Any explanation or fleshing out of the public fields that would help\r\n  reviewers.\r\n\r\n- Intended audience: more than just novice/intermediate/etc.\r\n  Reviewers need to know what level of Python experience/expertise is\r\n  targeted but also what level(s) of domain-specific\r\n  experience/expertise is targeted, for example networking, SQL,\r\n  database, etc.\r\n\r\n- Tutorial format: lab, lecture, workshop, etc.  However, don't just\r\n  pick a label, describe what will happen during the tutorial.\r\n\r\n- Interest in tutorial assistants: We're considering making tutorial\r\n  assistants available to instructors.  These would be volunteers with\r\n  Python experience who will provide one-on-one help during the\r\n  tutorial when students are working on exercises.  If we do this,\r\n  would you be interested and if so how many students per assistant\r\n  would you want?\r\n\r\n- Preferences or requirements with respect to class size or\r\n  scheduling.\r\n\r\n- Outline: of the tutorial content for reviewers.\r\n\r\n- Previous experience: tell us what experience you have in the\r\n  subject, in activities such as teaching or public speaking, or\r\n  anything else that would help us understand and gauge your abilities\r\n  as a tutorial presenter. Ideal would be a link to a video.\r\n\r\n- Biography: You'll be asked to enter your biography when you register\r\n  on this site and that information will be made public.\r\n  However, you may wish to include more information for reviewers to\r\n  complement information about your Previous Experience.\r\n\r\nMiscellaneous Notes About Proposals and Tutorials\r\n----\r\n\r\nHere are some notes about the proposal, selection, and delivery process for tutorials.\r\n\r\n- There will be some duplication of information between the public\r\n  information contained in the Description and Abstract, and the\r\n  Additional Notes which only reviewers will read.  That duplicate\r\n  information is for two different audiences so if you just copy and\r\n  paste between them neither will likely be served well.  A better\r\n  strategy, if you don't want to write two versions, is to reference\r\n  the public version (Description and Abstract) in the Additional\r\n  Notes for reviewers and then expound on it.\r\n\r\n- The tutorial selection process attempts to choose a good variety of\r\n  tutorial topics and levels that will be in demand, i.e., it doesn't\r\n  just select the best proposals!\r\n\r\n- The selection process has also tended to prefer Python-related\r\n  topics over more general software development tools or practices\r\n  that aren't Python-specific.\r\n\r\n- Tutorial are subject to cancellation if enrollment is low.  In the\r\n  past the cancellation criterion has been less than 10 students\r\n  registered.\r\n\r\n\r\nQuestions or Suggestions\r\n------------------------\r\n\r\nIf you have questions about any of this, or suggestions, please contact us at\r\n<a href=\"mailto:pycon-tutorials@python.org?subject=Question/Suggestion about Tutorial Proposal\">pycon-tutorials@python.org</a>.", 
        "status": 2, 
        "updated": "2013-10-15T19:12:18.453", 
        "title": "Submitting a Tutorial", 
        "body_fr": "", 
        "created": "2012-07-05T20:55:07.532", 
        "publish_date": "2012-07-05T20:55:07", 
        "path": "speakers/tutorials/proposals/"
    }
},
{
    "pk": 26, 
    "model": "cms.page", 
    "fields": {
        "body": "Python Education Summit\r\n------------------------------\r\n\r\nComing soon!\r\n\r\nAttending\r\n---------\r\n\r\nIf you are interested in participating in this summit, please contact [Naomi Ceder](mailto:naomi.ceder@gmail.com).\r\n", 
        "status": 2, 
        "updated": "2013-06-26T23:41:07.530", 
        "title": "Python Education Summit", 
        "body_fr": "", 
        "created": "2012-07-06T10:17:39.752", 
        "publish_date": "2012-07-06T10:17:39.752", 
        "path": "events/edusummit/"
    }
},
{
    "pk": 27, 
    "model": "cms.page", 
    "fields": {
        "body": "Speaking at PyCon\r\n=================\r\nThe 2016 conference will run from April 9, 2016 to April 17, 2016, at the Palais des congr\u00e8s de Montr\u00e9al Convention Centre, near the beautiful historic Old Port of Montr\u00e9al. The main conference runs from Friday April 11th through Sunday April 13th. It is preceded by two days of tutorials and followed by one day for posters and four days of sprints.\r\n\r\n- April 9 \u2013 10, 2016: Tutorials\r\n- April 11 \u2013 13, 2016: Talks\r\n- April 13, 2016: Posters\r\n- April 14 \u2013 17, 2016: Sprints\r\n\r\nImportant Dates\r\n-----------------------\r\n\r\n- July 1st, 2013: Call for proposals (talks, tutorials, posters).\r\n- September 1st, 2013: Registration opens.\r\n- September 1st, 2013: Financial aid application opens.\r\n- September 15th, 2013: Talk and tutorial proposals due.\r\n- November 1st, 2013: Poster proposals due.\r\n- December 1st, 2013: Financial aid awards announced.\r\n- December 15th, 2013: Conference schedule announced.\r\n- December 15th, 2013: Posters announced.\r\n\r\nWho can submit a proposal?\r\n--------------------------\r\nYou. Your friends. Your friends' friends. Anyone with any level of Python knowledge is a candidate for a great topic at this conference. As we get attendees of all kinds, we need speakers of all kinds. In all ways and manners, we try to assemble the most diverse conference we can, and we do that with your help.\r\n\r\nWhether you got started with Python last month or you've been around for 20 years, we think you've got something to share. The Python community is stronger than ever and we keep on reaching new areas, new industries, and new users.\r\n\r\nYou don't need to be a well-travelled professional speaker to get on stage at PyCon. What matters are the topics, the materials, and the drive to present great things to this community. Every year we get first-timers and we welcome them and work with them to make everyone feel at home. We also engage our advanced speakers to work with everyone else to share their wisdom and help put together the best show possible.\r\n\r\nTo Submit a Proposal\r\n--------------------\r\n\r\n1. First, <a href=\"/2016/account/signup/\">sign up for a new account</a> or <a href=\"/2016/account/login/\">log in</a> to your account.\r\n2. Once you are logged in; proceed to your <a href=\"/2016/dashboard/\">account dashboard</a> and create a speaker profile.\r\n3. Once completed, submit one or more proposals!\r\n\r\nSee [Proposal Advice](/2016/speaking/proposal_advice) for pointers about proposals, and [Proposal Resources](/2016/speaking/proposal-resources) for a list of resources to help you write a great proposal. ", 
        "status": 2, 
        "updated": "2013-10-12T19:43:48.462", 
        "title": "Speak at PyCon", 
        "body_fr": "Pr\u00e9senter \u00e0 PyCon\r\n=================\r\nLa conf\u00e9rence PyCon 2016 aura lieu du 9 au 17 avril 2016 au Palais des congr\u00e8s de Montr\u00e9al, \u00e0 proximit\u00e9 du magnifique quartier historique du Vieux -Port de Montr\u00e9al. La conf\u00e9rence principale se d\u00e9roule du vendredi 11 au dimanche 13 avril. Elle est pr\u00e9c\u00e9d\u00e9e par deux jours de tutoriels et suivie d'une journ\u00e9e de pr\u00e9sentation d\u2019affiches et quatre jours de sprints.\r\n\r\n- 9 - 10 avril : Tutoriels\r\n- 11 - 13 avril : Pr\u00e9sentations\r\n- 13 avril : Affiches\r\n- 14 - 17 avril : Sprints\r\n\r\nDates \u00e0 retenir\r\n-----------------------\r\n\r\n- 1er juillet 2013 : Appel aux participants (pr\u00e9sentations, tutoriaux, affiches).\r\n- 1er septembre 2013 : Ouverture des inscriptions.\r\n- 1er septembre 2013 : Ouverture des demandes d'aide financi\u00e8re.\r\n- 15 septembre 2013 : Date butoir des pr\u00e9sentations et tutorials.\r\n- 1er novembre 2013 : Date butoir pour la propositions d\u2019une affiche.\r\n- 1er d\u00e9cembre 2013 : Annonce des demandes d'aide financi\u00e8re retenues.\r\n- 15 d\u00e9cembre 2013 : Annonce du calendrier de la conf\u00e9rence.\r\n- 15 d\u00e9cembre 2013 : Annonce des affiches retenues.\r\n\r\nQui peut soumettre une proposition ?\r\n--------------------------\r\nVous. Vos amis. Les amis de vos amis. N'importe qui avec n'importe quel niveau de connaissance en Python est un candidat pour un magnifique sujet \u00e0 cette conf\u00e9rence. Comme nous participants sont divers, nous avons besoin de pr\u00e9sentateurs de toutes sortes. De toutes les mani\u00e8res possibles, nous essayons de r\u00e9unir la conf\u00e9rence la plus diversifi\u00e9e que nous pouvons et nous r\u00e9ussissons gr\u00e2ce \u00e0 vous.\r\n\r\nQue vous avez d\u00e9but\u00e9 en Python le mois dernier ou si vous avez 20 ans d\u2019exp\u00e9rience, nous pensons que vous avez quelque chose \u00e0 partager. La communaut\u00e9 Python est plus forte que jamais et nous continuons \u00e0 nous \u00e9tendre \u00e0 de nouveaux domaines, de nouvelles industries et de nouveaux utilisateurs.\r\n\r\nVous n'avez pas besoin d'\u00eatre un conf\u00e9rencier professionnel qui a beaucoup voyag\u00e9 \u00e0 monter sur sc\u00e8ne \u00e0 PyCon. L\u2019important r\u00e9side dans les th\u00e8mes, le mat\u00e9riel et la volont\u00e9 de pr\u00e9senter de grandes choses pour cette communaut\u00e9. Chaque ann\u00e9e, nous souhaitons la bienvenue \u00e0 de nouveaux participants et travaillons avec eux pour que chacun se sente \u00e0 la maison. Nous t\u00e2chons \u00e9galement de mettre \u00e0 profit le savoir et la sagesse des pr\u00e9sentateurs agu\u00e9ris afin de produire le meilleur \u00e9v\u00e8nement possible.\r\n\r\nPour soumettre une proposition\r\n--------------------\r\n\r\n1. Tout d'abord, <a href=\"/2016/account/signup/\">inscrivez-vous</a> ou <a href=\"/2016/account/login/\">connectez-vous</a> \u00e0 votre compte.\r\n2. Une fois connect\u00e9, chargez votre <a href=\"/2016/dashboard/\">tableau de bord</a> et cr\u00e9ez un profil de pr\u00e9sentateur.\r\n3. Une fois termin\u00e9, soumettez une ou plusieurs propositions!\r\n\r\nVoir [Conseils de pr\u00e9sentation](/2016/speaking/proposal_advice) pour des informations sur les propositions et [Ressources de pr\u00e9sentation](/2016/speaking/proposal-resources) pour une liste des ressources disponibles pour vous aider \u00e0 \u00e9crire une proposition g\u00e9niale.\r\n", 
        "created": "2012-07-06T14:15:22.963", 
        "publish_date": "2012-07-06T14:15:22", 
        "path": "speaking/speakatpycon/"
    }
},
{
    "pk": 28, 
    "model": "cms.page", 
    "fields": {
        "body": "Overview\r\n--------\r\n\r\nThe PyCon Tutorial days are Wednesday, April 9th and Thursday, April\r\n10th 2016.  Each day has two 3-hour tutorials periods, one in the morning (from\r\n9:00 a.m. to 12:20 p.m.) and one in the afternoon (from 1:20 p.m. to\r\n4:40 p.m.), with multiple tutorial being given in parallel during a period.  The evenings are free for socializing and Open Space.\r\n\r\nTutorials are a great opportunity to learn something new related to\r\nPython from experts, and they are a great value.\r\n\r\nTeaching\r\n--------\r\n\r\nIf you are interested in teaching a tutorial see the [Call for\r\nProposals](/2016/speaking/cfp/) and [Tutorial Information for\r\nInstructors](/2016/speakers/tutorials/instructors/).\r\n\r\n\r\nTaking a Tutorial\r\n-----------------\r\n\r\nCloser to the conference we plan to add information to this page about how\r\nto get the most out of tutorials you take.  The best thing you can do\r\nto prepare for a tutorial is be sure your laptop has the required\r\nsoftware loaded on it before the tutorial.  Specific requirements will\r\nbe listed in the tutorial descriptions, and for a few tutorials,\r\ninstructors will communicate more detailed or revised instructions to\r\nparticipants closer to the conference.\r\n\r\n\r\nVolunteering\r\n------------\r\n\r\nThere are several ways you can help with tutorials.\r\n\r\n- Volunteer for the tutorial review committee to review proposals\r\n  and decide which ones to accept. To join the review committee list,\r\n  email [pycon-tutorials@python.org](mailto:pycon-tutorials@python.org)\r\n\r\n- Volunteer to help as a TA (Teacher's Assistant) during a tutorial if\r\n  you have some Python experience and like helping others learn.  This\r\n  was new at PyCon in 2012 and it was a boon for TAs and students alike.  If you're interested email us at\r\n  [pycon-tutorials@python.org](mailto:pycon-tutorials@python.org?subject=Volunteer\r\n  to be a Tutorial TA)\r\n\r\n\r\nFeedback\r\n--------\r\n\r\nIf you have any other questions or suggestions, please contact us at\r\n[pycon-tutorials@python.org](mailto:pycon-tutorials@python.org?subject=Feedback from http://us.pycon.org/2016/tutorials page)\r\n", 
        "status": 2, 
        "updated": "2013-06-27T20:31:56.513", 
        "title": "Tutorials", 
        "body_fr": "", 
        "created": "2012-07-06T14:18:14.376", 
        "publish_date": "2012-07-06T14:18:14.376", 
        "path": "tutorials/"
    }
},
{
    "pk": 29, 
    "model": "cms.page", 
    "fields": {
        "body": "Poster Board Size\r\n-----------------\r\n\r\nThe presentation space is one side of a standalone poster board, 4 feet wide by 4 feet high, that you can tack posters or individual pages onto. \r\n\r\nCreating your poster\r\n--------------------\r\n\r\nA poster should be more than just some slides tacked onto a board. You want to call attention to a few key points which you can expand upon in your presentation and which might inspire questions from your viewers. Whether you use graphics, text, or some combination, things should be easily visible from several feet away. For a good sketch of how to construct a poster presentation, refer to [this summary](http://www.siam.org/meetings/guidelines/poster.php \"poster guidelines\").\r\n\r\nPrinting your poster and getting it to Santa Clara\r\n--------------------------------------------------\r\n\r\nThe main logistical problem with a poster is getting it printed and transported to the show site. Beware that it can be pricey to have a poster printed as a single 4 foot by 4 foot sheet. You have several options:\r\n\r\n### Printing your poster\r\n\r\n- The simplest and cheapest option is to print your poster as series of smaller sheets, bring them in your luggage and assemble them on site. This approach can work well, but you need to take care of how the pieces fit together, etc.\r\n\r\n- You can also have it printed full size or in larger segments by the printer of your choice and bring it along with you - folded or in a mailing tube. Of course airline baggage fees/carry on policies are the issue in this case, please check with your carrier for details.\r\n\r\n- Unfortunately, **onsite printing is not available** within a reasonable distance of the Santa Clara Convention Center. \r\n\r\n### Shipping your poster\r\n\r\nIf you are shipping your poster you will need to allow as much as a couple of weeks extra time. **Your poster MUST arrive no later than March 8th, or it will not make it to the conference.** Once you arrive at the conference, you may pick up your poster at the PyCon staff office onsite.\r\n\r\nMail your poster to:\r\n\r\n| |\r\n|:---------|\r\n| Ewa Jodlowska - PyCon Show Management |\r\n| c/o TRICORD TRADESHOWS |\r\n| 738 Neeson Road |\r\n| Marina, CA 93933 |\r\n| |\r\n\r\nLocation, schedule and setup\r\n----------------------------\r\n\r\nThe poster session location within the conference layout will be in the official PyCon program.  The room and poster boards will be available for setup from first thing in the morning Sunday, and (if all goes well) Saturday evening. However, the room won't be locked, and there will be no special security if you set up the night before. We'll get the slots marked as soon as we can, but you can refer to the diagram which will be posted here to see where you should place your poster, based on your poster's submission number.\r\n\r\nDuring the poster session\r\n-------------------------\r\n\r\nIt's expected that presenters will be by or near their posters for the entire poster session, explaining their poster and interacting with interested viewers. (Of course you can grab snacks, etc.) This is your chance to interact with a large segment of the PyCon population, so make the most of it. Want to score extra points with your attendees? Print out smaller, readable versions of your poster to hand out.\r\n\r\nWe will have photographers taking pictures of you and your poster, which we intend to post on the PyCon website. We may also have some informal roving video efforts as well.\r\n\r\nTo get an idea of what to expect, check out some of the PyCon US 2012 poster session interviews on [pyvideo.org](http://pyvideo.org/category/17/pycon-us-2012 \"\") (just look for summary photos that have people standing in front of a poster).\r\n\r\nIf you need help contact [Zac Miller](mailto:zmiller1@gmail.com) at 678-971-9361 or [Chad Cooper](mailto:chad.cooper@pyarkansas.org).", 
        "status": 2, 
        "updated": "2013-01-20T09:59:28.450", 
        "title": "Information for poster presenters", 
        "body_fr": "", 
        "created": "2012-07-06T14:44:46.243", 
        "publish_date": "2012-07-06T14:44:46.243", 
        "path": "posters/presenters/"
    }
},
{
    "pk": 30, 
    "model": "cms.page", 
    "fields": {
        "body": "Suggested Tutorial Topics\r\n-------------------------\r\n\r\nHere are ideas we've collected from surveys (newest at the top):\r\n\r\n- [PyCon 2012 as part of Tutorial Evaluations](/2013/tutorials/suggested_topics_2012/#pycon_2012_tutorial_evaluations)\r\n- [PyCon 2012 Guidance Survey in August 2011](/2013/tutorials/suggested_topics_2012/#pycon_2012_guidance_survey_in_august_2011)\r\n- [PyCon 2011 during the conference](/2013/tutorials/suggested_topics_2012/#pycon_2011_conference_evaluations)\r\n- [PyCon 2011 during tutorials](/2013/tutorials/suggested_topics_2012/#pycon_2011_tutorial_evaluations)\r\n\r\n#### <a id=\"pycon_2012_tutorial_evaluations\">PyCon 2012 Tutorial Evaluations</a>\r\n\r\nThe following are suggestions for future tutorial topics gathered as part of tutorial evaluations at PyCon 2012, lightly organized into groups:\r\n\r\n- Best practices, do's and don'ts (Django and general Python Dev), continuous integration, agile development, development methodologies for startups and small teams\r\n- Web frameworks\r\n    - Django (advanced)\r\n    - Django Views\r\n    - Setting up a Django server from Scratch\r\n    - Comparsion of Python Frameworks\r\n    - Virtualenv and PIP\r\n    - web2py\r\n    - Pyramid\r\n    - websockets\r\n    - scalability\r\n- GUI\r\n    - PyQt,\r\n    - GUIs\r\n    - GUIs PyQt, wxPython, etc\r\n    - GUI development Language bridges (PyObjC, .NET, C)\r\n- SQL\r\n    - SQL Alchemy\r\n- PyDATA\r\n    - More on pydata\r\n    - Google Analytics\r\n    - Google Analytics and Python\r\n    - Data analysis, Big Data, UI design using HTML5 with javascript as the new platform, javascript and Python\r\n    - Redis\r\n    - Data mining related.\r\n    - Practical NLTK tutorial\r\n    - big data and machine learning.\r\n    - Python/Hadoop interface libraries (mrjob?)\r\n- IDE\r\n    - Using PyCharm\r\n    - IDE options for developers (Comparison)\r\n- Diagnostics/Opitmizations\r\n    - Using the logging module and testing\r\n    - Advanced debugging techniques.\r\n    - performance optimizations\r\n    - argparse hands-on, logging subsystem hands-on\r\n    - Profiling python code with real-world examples of code that isn't written efficiently, and is improved as part of the tutorial. I would also like to see a tutorial on intermediate-advanced usage of Exceptions. A tutorial on how NOT to write bad python code.\r\n    - PyPy hacking\r\n- Python Ecosystem\r\n    - Building consistent web development environments with vagrant. Getting up to speed with pycrypto (e.g. using public key encryption to generate user licenses). Python and cross-platform (desktop) app development: options for embedding python runtimes, writing models in python and view/controllers in native code, using python as your app's scripting language, etc.\r\n    - ctypes for fun and profit\r\n- Programmming models\r\n    - Functional programming with Python\r\n    - more/different advanced python topics\r\n    - More on general programming advice at an intermediate level such as good practice on designing classes and testing practices.\r\n    - hand-ons and in-depth topics\r\n    - twisted\r\n    - arduino talks, beaglebone with python\r\n- Parallel/Distributed Computing\r\n    - more performance stuff, that makes sense.\r\n    - Distributed parallel computation - cloud, message passing, large scale stuff. Auto-scaling, too.\r\n    - hand-ons and in-depth topics\r\n- Visualization/Gaming\r\n    - Generating map data (not just web mapping with existing web data).\r\n    - More science/plotting/visualization topics.\r\n    - Python for the GIS community\r\n    - ArcGIS.\r\n    - Python specific mapping tools (Mapnik, QGIS, etc)\r\n    - practical data analysis\r\n    - Advanced video games ... Eve, Maya.\r\n- Commercial offerings\r\n    - Boto, and other integration of Python with actual company offerings\r\n\r\n#### <a id=\"pycon_2012_guidance_survey_in_august_2011\">PyCon 2012 Guidance Survey in August 2011</a>\r\n\r\nAs of September 7th, 2011\r\n\r\n- Business\r\n    - Business-related or non-programming content for programmers who are independent contractors or work in a small environment. Things like running your own consultancy, managing clients and expectations, project management, identifying tactical advantages that Python can bring to your business.\r\n    - Documentation Tools\r\n    - Project development using Python. i.e. project planning, prototyping, development, test, release in a Pythonic method, perhaps using Python in an Agile framework.\r\n- Community\r\n    - How to Get Involved in Project X (lead in to a sprint and ongoing participation) This could be any project with a leader willing to give a tutorial walkthough of the code and the history of the project.\r\n    - How to participate in the Python community (uploading packages, how to submit & fix bugs, etc.)\r\n    - Sprint lead-in (So you want to get involved in project so & so).\r\n- Core Python\r\n    - A detailed look at the implementation at the C Interpreter, and understanding the relationship between the Python and the C implementation.\r\n    - Advanced Python 1 and 2\r\n    - Advanced Python concepts\r\n    - Advanced Python, fiddling with AST, advanced data structures, distributed processing and data mining\r\n    - Anything about the Python language to deepen my understanding\r\n    - Core Python Development\r\n    - Decorators and properties\r\n    - Distributed Python\r\n    - Embedding python in applications distributing computing\r\n    - Hidden Treasures of stdlib tutorial\r\n    - High performance python\r\n    - Killer features of Python 3\r\n    - Language handling overviews of python structure\r\n    - Migrating to Python 3\r\n    - More about C extensions.\r\n    - Porting to Py3 and handing dual python 2/3 codebases\r\n    - Python 3\r\n    - Python 3 porting\r\n    - Python C API\r\n    - Python and C++ integration\r\n    - Review of the standard library, what tools are available to us in Python\r\n    - The standard library in-depth\r\n    - Things I might not know I can do with the standard library.\r\n    - Using the data structures in Python (not a tutorial on what data structures are)\r\n    - Wrapping C libs in python, Cython / ctypes\r\n- Data\r\n    - AST Manipulation\r\n    - Anything having to do with maps\r\n    - BigData (mapreduce, parallelism, etc.)\r\n    - Data visualization\r\n    - Database connectivity and plugging in to things like GIS and maps\r\n    - GIS\r\n    - Large scale data processing & visualization\r\n    - NoSQL\r\n    - Non-rel\r\n    - SQLAlchemy\r\n    - Statistics in/with Python\r\n    - Storage with Python\r\n    - ZODB\r\n    - data visualization with python and other tools\r\n- Deployment\r\n    - Automated / scripted deploy (Chef? Puppet? Fabric?)\r\n    - Best Practices on deploying projects (especially web apps).\r\n    - Continous Integration\r\n    - Fabric, gunicon\r\n    - Python webapp deployment using vagrant, chef, fabric, etc\r\n    - Tutorials to do specific things: automate a Unix Server build, build an ecommerce site in DJango\r\n- Development\r\n    - \"Learning X for Python Developers\" (where X is a not-necessarily-python tool).\r\n    - A good intro to C class\r\n    - A patterns, algorithms and recipes class discussing common ways of generalizing problems.\r\n    - AI programming in Python\r\n    - API Design\r\n    - Advanced language techniques\r\n    - Anything on machine learning or genetic programming.\r\n    - Build A Compiler in Python\r\n    - Build A Processor Emulator in Python\r\n    - Computer Vision topics\r\n    - Concurrency\r\n    - Continuous Integration\r\n    - DevOps\r\n    - Front-end integrations\r\n    - Full stack web application testing (unit, browser, etc)\r\n    - Game Development\r\n    - High performance computing\r\n    - Jython Intro\r\n    - Machine learning\r\n    - Multiprocessing\r\n    - Multiprocessing with Python\r\n    - NLTK (Natural language toolkit\r\n    - Novice to Ninja\r\n    - Python toolchain: virtualenv, pip, nose, etc\r\n    - Python web development basics\r\n    - Real time web development with support of asynchronous longer running tasks\r\n    - Redis + Socketio + Gevent == Realtime web\r\n    - Social Network related development\r\n    - Test driven development\r\n    - Tools to make web development easier\r\n    - Tutorial for people coming to python from other languages - advantages, disadvantages, what to watch out for, being pythonic, etc.\r\n    - Web Frameworks\r\n    - Writing DSLs\r\n- General\r\n    - Graph theory\r\n    - In-depth dives into limited subject matter.\r\n    - More advanced talks\r\n    - Python idioms\r\n    - The same instructor teach a tutorial in the same format, but at an advanced level.\r\n    - Thinking As a Programmer - Taking ideas and dissecting them (the how to of dissecting programs before putting them into code.\r\n    - Writing great python code\r\n    - more advanced python (less application / framework specific)\r\n- Interface / Visual design\r\n    - 3d related material\r\n    - GUI programming\r\n    - Graphics applications\r\n    - HTML 5\r\n    - Microsoft Kinect device and pattern recognition.\r\n    - Nodebox\r\n    - Visualisation tutorials\r\n    - Visualization w. Python\r\n    - Web-based app / mobile / django or django alternatives\r\n    - making music with python\r\n- Packaging\r\n    - Migrating to PyPy\r\n    - Migrating to distutils2 + distribute\r\n    - PyPy\r\n    - Pypy internals\r\n- Python Packages/Frameworks\r\n    - A SciPy exclusive tutorial would be great, or a combined Numpy/SciPy exclusive tutorial.\r\n    - Cython\r\n    - Django ORM optimizations\r\n    - Django internals\r\n    - Django tutorials - beginner, intermediate and advance level\r\n    - More on Pinax, Pyramid and Turbogears (if they get Turbogears moved over to Pyramid).\r\n    - More packaging stuff. Maybe a tutorial about pyramid\r\n    - PyCuda\r\n    - Pygame\r\n    - Pyjamas\r\n    - Pylons\r\n    - Pyramid, SQLAlchemy, Celery\r\n    - Python OpenGL\r\n    - SciPy/NumPy\r\n    - Twisted Matrix\r\n    - ctypes, Cython and pyrex\r\n    - writing web applications in Pyramind\r\n- Security\r\n    - Defending Your App From Attacks (ex. timing attack)\r\n- Servers / Sys Admin\r\n    - AWS\r\n    - Advanced server management/deployment\r\n    - Configuration automation (chef, puppet)\r\n    - Distributed / high performance computing\r\n    - EC2\r\n    - Eucalyptus or OpenStack\r\n    - Maybe address packages like chef or libCloud\r\n    - Memory debugging\r\n    - More stuff about distributed systems and how to build them\r\n    - Network programming and libraries (twisted, gevent, etc)\r\n    - Python for sysadmins\r\n    - Scaling, dealing with caching, etc.....\r\n    - System/network level programming with Python.\r\n    - Testing, Cloud, Operations, SysAdmin\r\n    - eventlet / gevent\r\n    - wsgi\r\n- Testing\r\n    - How Python works with web interfaces, like selenium.\r\n    - Intermediate Django Unit testing\r\n    - More packet crafting geared towards QA\r\n    - Testing\r\n    - Testing Frameworks\r\n    - Unit testing\r\n    - Unit testing web applications\r\n\r\n#### <a id=\"pycon_2011_conference_evaluations\">PyCon 2011 Conference Evaluations</a>\r\n\r\n\"Please list 3 tutorial subjects you would like to attend.\"\r\n\r\n- Python 3\r\n- SciPy/NumPy\r\n- Graph theory\r\n- Statistics in/with Python\r\n- Testing Frameworks\r\n- Web Frameworks\r\n- API Design\r\n- intermediate python\r\n- writing web applications in Pyramind\r\n- Advanced server management/deployment\r\n- Full stack web application testing (unit, browser, etc)\r\n- Large scale data processing & visualization\r\n- Redis + Socketio + Gevent == Realtime web\r\n- Python webapp deployment using vagrant, chef, fabric, etc\r\n- Unit testing web applications\r\n- Python idioms\r\n- Test driven development\r\n- Core Python Development\r\n- AST Manipulation\r\n- Writing DSLs\r\n- ctypes, Cython and pyrex\r\n- making music with python\r\n- data visualization with python and other tools\r\n- Django\r\n- SQLAlchemy\r\n- Pyramid\r\n- porting to Python 3\r\n- distributing Python apps\r\n- Anything having to do with maps\r\n- Anything having to do with django\r\n- Advanced Python\r\n- c extensions\r\n- Non-rel\r\n- A good intro to C class\r\n- A basic Django class\r\n- Python 3 porting\r\n- High performance computing\r\n- Django internals\r\n- Django\r\n- Core Python development\r\n- advanced python\r\n- real time web apps\r\n- sqlalchemy\r\n- Pyramid\r\n- ZODB\r\n- Testing\r\n- PyCuda\r\n- Python C API\r\n- Python OpenGL\r\n- Django/Pinax\r\n- Python 3\r\n- EC2\r\n- DevOps\r\n- Concurrency\r\n- PyPy\r\n- Machine learning\r\n- BigData (mapreduce, parallelism, etc.)\r\n- Advanced Python concepts\r\n- Pygame\r\n- AI programming in Python\r\n- Build A Compiler in Python\r\n- Build A Processor Emulator in Python\r\n- Defending Your App From Attacks (ex. timing attack)\r\n- NLTK\r\n- numpy, data analysis, specific machine learning topics\r\n- Nodebox\r\n- Advanced Python data structures\r\n- Visualisation tutorials\r\n- Network programming and libraries (twisted, gevent, etc)\r\n- Python toolchain: virtualenv, pip, nose, etc\r\n- The standard library in-depth\r\n- Multiprocessing with Python\r\n- Porting to Py3 and handing dual python 2/3 codebases\r\n- Configuration automation (chef, puppet)\r\n- GIS\r\n- Hidden Treasures of stdlib tutorial\r\n- Cpython or pypy internals\r\n- deep dive into scipy/numpy\r\n- Pylons\r\n- SQLAlchemy\r\n- \"Writing great python code\"\r\n- HTML 5\r\n- Django\r\n- eventlet / gevent\r\n- Using the data structures in Python (not a tutorial on what data structures are)\r\n- Anything about the Python language to deepen my understanding\r\n- Review of the standard library, what tools are available to us in Python\r\n- Django\r\n- NLTK or similar tools\r\n- Statistical analysis with Python\r\n- More networking\r\n- 102, 201, 202 level python coding\r\n- Packaging\r\n- Documentation Tools\r\n- Advanced language techniques\r\n- Novice to Ninja\r\n- Scaling, dealing with caching, etc.....\r\n- Jython Intro\r\n- SQLAlchemy\r\n- Decorators and properties\r\n- Django ORM optimizations\r\n- SQL, or PostgresSQL specifically\r\n- WSGI and webframework, aka Pyramid\r\n- Porting to python3\r\n- Memory debugging\r\n- Distributed / high performance computing\r\n- Standard Library\r\n- A 2nd Intermediate tutorial\r\n\r\n#### <a id=\"pycon_2011_tutorial_evaluations\">PyCon 2011 Tutorial Evaluations</a>\r\n\r\n\"What tutorial topics would you like to see in the future?\"\r\n\r\n- Graph database-backed Web applications.\r\n- Data visualization\r\n- Business-related or non-programming content for programmers who are independent contractors or work in a small environment. Things like running your own consultancy, managing clients and expectations, project management, identifying tactical advantages that Python can bring to your business.\r\n- real time web development with support of asynchronous longer running tasks\r\n- Anything having to do with maps\r\n- I would like to see the same instructor teach a tutorial in the same format, but at an advanced level.\r\n- A SciPy exclusive tutorial would be great, or a combined Numpy/SciPy exclusive tutorial.\r\n- Migrating to PyPy\r\n- Continous Integration\r\n- Migrating to Python 3\r\n- How to participate in the Python community (uploading packages, how to submit & fix bugs, etc.)\r\n- Sprint lead-in (So you want to get involved in project so & so).\r\n- more experienced topics, and  topics for more experienced\r\n- More stuff about distributed systems and how to build them\r\n- Nodebox\r\n- Advanced Python 1 and 2\r\n- More topics related to Django\r\n- Deployment, tools to make web development easier\r\n- Visualization w. Python\r\n- more aws, with automated/scripted deploy (chef? puppet? fabric?) Perhaps also Eucalyptus or OpenStack\r\n- 3d related material\r\n- High performance python\r\n- More multiprocessing, more \"Learning X for Python Developers\" (where X is a not-necessarily-python tool).\r\n- sqlalchemy, unit testing\r\n- embedding python in applications  distributing computing\r\n- Testing, Cloud, Operations, SysAdmin\r\n- Wrapping C libs in python, Cython / ctypes\r\n- More packaging stuff. Maybe a tutorial about pyramid\r\n- More python 3.\r\n- wsgi\r\n- Python!\r\n- more language handling  overviews of python structure\r\n- Something using the NLTK (Natural Language Toolkit).  Something using the Microsoft Kinect device and pattern recognition.\r\n- Nodebox!\r\n- System/network level programming with Python.\r\n- Computer Vision topics\r\n- Cython\r\n- web-based app dev, django or equivalent specific\r\n- Tutorials to do specific things:  automate a Unix Server build, build an ecommerce site in DJango\r\n- Intermediate Django  Unit testing\r\n- Thinking As a Programmer - Taking ideas and dissecting them (the how to of dissecting programs before putting them into code.\r\n- GUI programming\r\n- web-based app / mobile / django or django alternatives\r\n- Distributed Python\r\n- web-based applications, more django (or equiv) content\r\n- more django/python framework/front-end integrations/web-based applications.\r\n- python language specific\r\n- Python web development basics\r\n- pyjamas\r\n- Game Development\r\n- advanced stuff\r\n- Django tutorials - intermediate and advance level\r\n- I am interested in Social Network related development.\r\n- More advanced talks\r\n- Things I might not know I can do with the standard library.\r\n- Killer features of Python 3\r\n- Migrating to PyPy\r\n- Migrating to distutils2 + distribute\r\n- Continuous Integration\r\n- How to Get Involved in Project X (lead in to a sprint and ongoing participation) This could be any project with a leader willing to give a tutorial walkthough of the code and the history of the project.\r\n- Python 3 porting\r\n- storage with Python\r\n- Pyramid, SQLAlchemy, Celery\r\n- Best Practices on deploying projects (especially web apps).\r\n- Tutorial for people coming to python from other languages - advantages, disadvantages, what to watch out for, being pythonic, etc.\r\n- more advanced python (less application / framework specific)\r\n- SQLAlchemy\r\n- Advanced Python, fiddling with AST, advanced data structures, distributed processing and data mining\r\n- Maybe more about C extensions.\r\n- Project development using Python. i.e. project planning, prototyping, development, test, release in a Pythonic method, perhaps using Python in an Agile framework.\r\n- A detailed look at the implementation at the C Interpreter, and understanding the relationship between the Python and the C implementation.\r\n- A patterns, algorithms and recipes class discussing common ways of generalizing problems.\r\n- Graphics applications\r\n- Maybe address packages like chef or libCloud\r\n- a NoSQL smackdown?\r\n- pinax workshop?\r\n- Anything on machine learning or genetic programming.\r\n- more advanced stuff\r\n- How Python works with web interfaces, like selenium.\r\n- Fabric, gunicon\r\n- python and c++ integration\r\n- python for sysadmins / more intermediate level courses\r\n- more packet crafting geared towards QA\r\n- Testing\r\n- More on Pinax, Pyramid and Turbogears (if they get Turbogears moved over to Pyramid).\r\n- Database connectivity and plugging in to things like GIS and maps make two topics.\r\n- In-depth dives into limited subject matter. The subjects, of course, must be immediately relevant to whatever-it-is I'm wanting to learn at the time. ;)\r\n- An advanced-level Django tutorial would be very cool\r\n- Twisted Matrix", 
        "status": 2, 
        "updated": "2013-09-11T08:58:16.554", 
        "title": "Suggested Tutorial Topics", 
        "body_fr": "", 
        "created": "2012-07-06T14:51:50.657", 
        "publish_date": "2012-07-06T14:51:50", 
        "path": "tutorials/suggested_topics/"
    }
},
{
    "pk": 31, 
    "model": "cms.page", 
    "fields": {
        "body": "Most talks spend the first 15-20 minutes going over introductory material -- what something is, who the presenters are, etc. There's a lot of repeated information, and a lot of wasted time.\r\n\r\nEnter the Extreme track.\r\n\r\n\"Extreme PyCon\" will be a series of advanced talks with very specific requirements:\r\n\r\n- They must be technical in nature. \"State of\" and other meta talks will not qualify for the \"Extreme\" track.\r\n- You should spend a maximum of 5 minutes (and preferably less) \"setting the stage\". Best to approach the audience as having context and prerequisite backgound, and just dive right in.\r\n- Talks should focus on a single subject, e.g. \"threads\" or \"twisted\".\r\n- Avoid introductory material \u2013 assume that if you're talking about Django, your audience knows what MVC and web frameworks are.\r\n- The deeper, the better. If you have examples of previous deep-dive technical talks you have done in the past, please include that information in your proposal.\r\n\r\nPlease Note: Even if your talk is not accepted for an \"Extreme\" talk, you may be accepted into the regular conference talk.\r\n\r\nIf you have questions about the \"Extreme\" track, please contact the PyCon Program committee (pycon-pc@python.org), or its chairs, Luke Sneeringer (luke@sneeringer.com) and Alex Gaynor ().\r\n", 
        "status": 2, 
        "updated": "2013-10-09T22:12:30.858", 
        "title": "Extreme Talks", 
        "body_fr": "La plupart des pr\u00e9sentations passent les premi\u00e8res 15 \u00e0 20 minutes sur du mat\u00e9riel d'initiation \u2013 d\u00e9finitions, pr\u00e9sentations du conf\u00e9rencier, etc.  Il y a souvent de l'information redondante et du temps perdu.\r\n\r\nVoici donc les **Pr\u00e9sentations extr\u00eames**.  \r\n\r\nLes pr\u00e9sentations extr\u00eames sont une s\u00e9rie de pr\u00e9sentations avanc\u00e9es qui remplissent les d\u00e9finitions suivantes:\r\n\r\n- Les pr\u00e9sentations sont \u00e0 caract\u00e8re technique.  Les survols, \u00e9tat de l'art, et autre meta-pr\u00e9sentations ne se qualifient pas comme extr\u00eame.\r\n- Elles passent au plus cinq minutes \u00e0 pr\u00e9parer la sc\u00e8ne.  Elles pr\u00e9sument que l'audience est famili\u00e8re avec le sujet et poss\u00e8de le bagage requis pour comprendre.\r\n- Elles se concentrent sur un seul sujet, par exemple, les \"threads\" ou \"twisted\".\r\n- Elles \u00e9vitent le mat\u00e9riel d'initiation \u2013 par exemple, si vous parlez de Django, vous pouvez supposer que votre audience sait ce qu'est un framework web ou l'approche \"model-document-vue\".\r\n- Le plus pouss\u00e9, le mieux.  Si vous avez des exemples de pr\u00e9sentations techniques approfondies que vous avez donn\u00e9es par le pass\u00e9, mettez les dans votre proposition.\r\n\r\nPrenez note: m\u00eame si votre pr\u00e9sentation n'est pas accept\u00e9e comme \"extr\u00eame\", elle peut \u00eatre accept\u00e9e comme une pr\u00e9sentation r\u00e9guli\u00e8re.\r\n\r\nSi vous avez des questions sur les pr\u00e9sentations extr\u00eames, n\u2019h\u00e9sitez pas \u00e0 contacter le comit\u00e9 de programme (pycon-pc@python.org) ou ses pr\u00e9sidents Luke Sneeringer (luke@sneeringer.com) et Alex Gaynor(alex.gaynor@gmail.com). \r\n", 
        "created": "2012-07-07T14:25:06.950", 
        "publish_date": "2012-07-07T14:25:06", 
        "path": "speaker/extreme/"
    }
},
{
    "pk": 32, 
    "model": "cms.page", 
    "fields": {
        "body": "Registration is Open\r\n---\r\n\r\n[<span class=\"label label-important\">Now Open! </span>][registerlink] PyCon 2016 Conference Registration is now open! [<strong>Register now</strong>][registerlink]!\r\n\r\n<br />\r\n\r\nRegistration Prices\r\n-------------------------\r\n\r\n<table cellpadding=\"7\">\r\n<tr><th align=\"left\">Conference Registration</th><th>Early Bird Rate</th><th align=\"center\">Regular Rate</th></tr>\r\n<tr><td align=\"left\"><a href=\"/2016/registration/#Corporate\" title=\"Registration Information\"> Corporate Rate</a></td><td align=\"center\">$450 <small>USD</small></td><td align=\"center\">$600 <small>USD</small> </td></tr>\r\n<tr><td align=\"left\"><a href=\"/2016/registration/#Individual\" title=\"Registration Information\"> Individual  Rate</a></td><td align=\"center\">$300 <small>USD</small></td><td align=\"center\">$350 <small>USD</small> </td></tr>\r\n<tr><td align=\"left\"><a href=\"/2016/registration/#Student\" title=\"Registration Information\">Student Rate</a></td><td align=\"center\">$100  <small>USD</small> </td><td align=\"center\">$125 <small>USD</small> </td></tr>\r\n</table>\r\n\r\n<table cellpadding=\"7\">\r\n<tr><th align=\"left\">Tutorial Registration</th><th>Pre Conference Rate</th><th align=\"center\">On Site Rate</th></tr>\r\n<tr><td align=\"left\"><a href=\"/2016/registration/#Tutorial\" title=\"Registration Information\">Tutorial Rate</a></td><td align=\"center\">$150 <small>USD</small> each </td><td align=\"center\">$200 <small>USD</small> each </td></tr>\r\n</table>\r\n\r\n<p><br/></p>\r\n<span class=\"label label-note\">Note:</span> Early Bird rates apply to the first 800 tickets sold.\r\n\r\n<span class=\"label label-note\">Note:</span> PyCon 2016 is now accepting applications for <a href=\"/2016/assistance/\">Financial Aid</a>. \r\n\r\n<span class=\"label label-note\">Note:</span> Tutorial registration is not included in regular conference registration prices.\r\n\r\n[<span class=\"label label-important\">Register Now:</span> https://us.pycon.org/2016/registration/register/][registerlink]\r\n\r\n<br />\r\n\r\nFinancial Aid\r\n-----------------\r\nEveryone - even the conference chair - pays for registration so that we can assist those who might not otherwise be able to attend. To learn more about Financial Aid for flights, hotel, and registration to attend PyCon, see the <a href=\"/2016/assistance/\">Financial Aid</a> page.\r\n\r\nWhat's Included?\r\n-----------------------\r\nConference registration includes a light breakfast, lunch, and morning/afternoon break refreshments on the three conference days (Friday, Saturday, & Sunday).\r\n\r\nTutorial attendees will be provided with lunch and break refreshments. Tutorials are charged separately from registration and do not include admission to the main conference.\r\n\r\nHotel\r\n--------\r\nPyCon has negotiated discount rates at the Westin and Hyatt Regency. The conference rate is only available to attendees of the PyCon conference who make reservations through the conference registration site.\r\n\r\nCurrently we have the following hotels available:\r\n\r\n - Westin Hotels - $169 <small>CAD</small>/night (plus tax)\r\n - Hyatt Regency- $149 <small>CAD</small>/night (plus tax)\r\n\r\nMore information can be found on the <a href=\"/2016/venue\">venue</a> page.\r\n\r\nQuestions?\r\n---------------\r\nIf you have questions or issues with registration, please send email to [pycon-reg@python.org](mailto:pycon-reg@python.org \"pycon-reg@python.org\").\r\n\r\n<a id=\"Corporate\"></a>Corporate Rate\r\n---------------------\r\nIf your company is paying for you to attend PyCon, you should register at the corporate rate. You'll be helping to keep the conference affordable for all, especially for students and those needing financial aid. Government employees should also register at the corporate rate. [<strong>Register now</strong>][registerlink]!\r\n\r\n<a id=\"Individual\"></a>Individual Rate\r\n--------------------\r\nIf you are paying for yourself to attend PyCon, feel free to come as an individual. Employees of non-profits may register at the individual rate. [<strong>Register now</strong>][registerlink]!\r\n\r\n<a id=\"Student\"></a>Student Rate\r\n------------------\r\nThis rate is for full-time students and academics.  [<strong>Register now</strong>][registerlink]!\r\n\r\n<a id=\"Tutorial\"></a>Tutorial Rate\r\n------------------\r\nTutorial registration is not included in regular conference registration prices. Each tutorial is in addition to normal registration.\r\n\r\n<span class=\"label label-note\">Coming soon</span> Tutorial registration will open December 1st. Follow @[PyCon](https://twitter.com/PyCon) for announcements.\r\n\r\nIf you are only attending one or more PyCon Tutorials and not the conference, there is no additional registration fee. You can use the online registration system linked above to register for tutorials only, if you have issues, please contact [pycon-reg@python.org](mailto:pycon-reg@python.org \"pycon-reg@python.org\").\r\n\r\n[registerlink]: https://us.pycon.org/2016/registration/register/",
        "status": 2, 
        "updated": "2013-09-20T14:08:52.947", 
        "title": "Registration Information", 
        "body_fr": "", 
        "created": "2012-07-08T11:51:58.477", 
        "publish_date": "2012-07-08T11:51:58", 
        "path": "registration/"
    }
},
{
    "pk": 33, 
    "model": "cms.page", 
    "fields": {
        "body": "Do you want to share a room at one of the <a href=\"/2016/venue/\">PyCon hotels</a> (Hyatt Regency, Westin Hotel) or another hotel with other attendees? List yourself on this wiki page (click the edit button to the upper right, after logging in), along with:\r\n\r\n- how many other people you want to share with,\r\n- what nights you'll be there,\r\n- whether you've already reserved a room, and\r\n- any other requirements (e.g. male/female, smoking/non-smoking).\r\n\r\nNote: If any of your roommates will be arriving separately, be sure to list their names on the reservation as having permission to check in and get a key to your shared room from the front desk by showing photo ID.\r\n\r\nWhen reserving your room, be sure to specify the type and number of beds! Some rooms only have a single king size bed; not ideal for platonic room sharing. Cots may be available, but they are not very comfortable.\r\n\r\nCaution: Room sharing arrangements are the responsibilities of the individual parties involved. The Python Software Foundation and PyCon Staff takes no responsibility, and cannot get involved in any disputes.\r\n\r\nIn order to edit this page; you must have a valid site login, and use markdown syntax.\r\n\r\n----------------------------\r\n\r\n## I Already Have A Room Reservation\r\n\r\nIf you have a room reservation and you're looking for a roommate to share costs, list your info here:\r\n\r\n1. \r\n - **Dates**: Apr10 - Apr 12; 3 room nights\r\n - **Hotel**: Hyatt Regency, 1 roommate, Non-smoking, 2 double beds\r\n - **Contact Info**:  Example Person, person@example.com\r\n\r\n\r\n1. \r\n - **Dates**: April 8 - April 16; 8 nights\r\n - **Hotel**: Westin Hotel. 1 roommate; non-smoking; I am a woman and I prefer (but I don't need) a female roommate. Room with 2 queen beds.\r\n - **Contact Info**: Marta Maria Casetti, mmcasetti@gmail.com\r\n\r\n1. \r\n - **Dates**:  April 10-16th for sure (6 room nights), depending on the tutorials I may be there starting the 8th or 9th (+1 or +2 room nights)\r\n - **Hotel**: Westin Hotel. 1 bed in 2 bed non-smoking room. I am a cisgender male and queer friendly. \r\n - **Contact Info**: Michael R. Crusoe: [@biocrusoe][1] / [mcrusoe@msu.edu][2]\r\n\r\n1. \r\n - **Dates**:\r\n - **Hotel**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **Hotel**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **Hotel**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **Hotel**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **Hotel**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **Hotel**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **Hotel**:\r\n - **Contact Info**:\r\n\r\n\r\n----------------------------\r\n\r\n## I'm Looking For A Room\r\n\r\nIf you're looking to share a room (but you haven't made a reservation yet), list your info here:\r\n\r\n1. \r\n - **Dates**: Apr10 - Apr 12; 3 room nights\r\n - **More Info**: Non-smoker, first PyCon\r\n - **Contact Info**: Example Person, person@example.com\r\n\r\n1. \r\n - **Dates**: Apr8-Apr17; 9 room nights\r\n - **More Info**: Non-smoker, first PyCon\r\n - **Contact Info**: Alex Lord, lostdogs101@gmail.com\r\n\r\n1. \r\n - **Dates**:\r\n - **More Info**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **More Info**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **More Info**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **More Info**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **More Info**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **More Info**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **More Info**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **More Info**:\r\n - **Contact Info**:\r\n\r\n1. \r\n - **Dates**:\r\n - **More Info**:\r\n - **Contact Info**:\r\n\r\n\r\n----------------------------\r\n\r\n  [1]: http://twitter.com/biocrusoe\r\n  [2]: mailto:mcrusoe@msu.edu\r\n", 
        "status": 2, 
        "updated": "2013-10-14T10:36:45.437", 
        "title": "Room Sharing", 
        "body_fr": "", 
        "created": "2012-07-08T12:28:25.619", 
        "publish_date": "2012-07-08T12:28:25.619", 
        "path": "community/roomsharing/"
    }
},
{
    "pk": 34, 
    "model": "cms.page", 
    "fields": {
        "body": "Part of the motivation for PyCon is to help with Python education and advocacy around the world. Accordingly, we intend to record all PyCon presentations and release the recordings on the web (see [http://pyvideo.org/](http://pyvideo.org/ )).\r\n\r\nBy submitting your talk or tutorial proposal, or by signing up to give a lightning talk, you agree to give permission to the Python Software Foundation to record, edit, and release audio and/or video of your presentation.  We also perform interviews with poster presenters and require recording releases to publish them.\r\n\r\nBy default, the recording release checkbox is checked when submitting a proposal. If you wish to opt-out, uncheck the release checkbox, note that no recordings of your talk will be made. You cannot opt out of recording for lightning talks.\r\n\r\nYou agree to the following legalese, which certifies that you are the author of your presentation (or otherwise allowed to present it at PyCon), and which allows the Python Software Foundation 1) to perform the necessary audio and video editing needed to prepare your presentation, and 2) to distribute the recordings to other people, including on YouTube, or video sites. It also allows other people to watch the recordings.\r\n\r\nLegalese:\r\n\r\n\tI certify that I, the Submitter, am authorized to license this proposal\r\n\tand its associated presentation (the \"User Submission\") to the Python\r\n\tSoftware Foundation (the \"PSF\") for use in association with PyCon 2016.\r\n\tSpecifically:\r\n\t\r\n\t- I, the Submitter, certify that I am either the copyright owner of the\r\n\tUser Submission or an authorized licensee of the copyright owner. If I\r\n\tam an authorized licensee of the copyright owner, I certify that I have\r\n\tsublicensable distribution rights.\r\n\t\r\n\t- I, the Submitter, hereby grant the PSF a worldwide, royalty-free, fully\r\n\tpaid-up, non-exclusive, perpetual (for the duration of the applicable\r\n\tcopyright), sublicensable and transferable license to exercise the rights\r\n\tin the User Submission as follows:\r\n\t\r\n\t1) The PSF is granted a license to reproduce the User Submission,\r\n\tto incorporate the User Submission into one or more Collective\r\n        Works, and to reproduce the User Submission as incorporated in\r\n        the Collective Works;\r\n\t\r\n\t2) The PSF is granted a license to create and reproduce Derivative\r\n        Works;\r\n\r\n\t3) The PSF is granted a license to distribute copies or\r\n        phonorecords of, display publicly, perform publicly, and\r\n        perform publicly by means of a digital audio transmission the\r\n        User Submission including as incorporated in Collective Works;\r\n        and\r\n\r\n\t4) The PSF is granted a license to distribute copies or\r\n        phonorecords of, display publicly, perform publicly, and\r\n        perform publicly by means of a digital audio transmission\r\n        Derivative Works.\r\n\r\n\t- I, the Submitter, waive the exclusive right to collect, whether individually\r\n\tor via a performance-rights society, royalties for the public\r\n        digital performance of the User Submission, subject to the\r\n        compulsory license created by 17 U.S.C. Section 114 (or the\r\n        equivalent in other jurisdictions).\r\n\t\r\n\t- I, the Submitter, specifically affirm the right to perform the User\r\n\tSubmissions on the PSF's web sites or on other web sites\r\n        designated by the PSF (including, but not necessarily limited to\r\n        YouTube).\r\n\t\r\n\t- I, the Submitter, also hereby grant each person receiving the User\r\n\tSubmission distributed by the PSF a non-exclusive license to\r\n \taccess, use, display, and perform the User Submission in a\r\n\tnon-commercial, private context.", 
        "status": 2, 
        "updated": "2013-07-01T19:48:54.133", 
        "title": "PyCon Recording Release", 
        "body_fr": "", 
        "created": "2012-07-08T12:38:58.260", 
        "publish_date": "2012-07-08T12:38:58", 
        "path": "speaking/recording/"
    }
},
{
    "pk": 35, 
    "model": "cms.page", 
    "fields": {
        "body": "Charity Auction\r\n------------------\r\n\r\nComing soon!\r\n\r\n<span class=\"label label-info\">PARTICIPANTS: </span> Here is a list of sponsors contributing to the second annual PyCon Charity Auction! If you would like to be added to the list, please contact [Ewa Jodlowska](mailto:ewa@python.org).\r\n\r\n- Coming soon!\r\n", 
        "status": 2, 
        "updated": "2013-10-10T11:55:23.123", 
        "title": "PyCon Charity Auction", 
        "body_fr": "\r\n\r\nVente aux ench\u00e8res caritative\r\n------------------\r\n\r\n\u00c0 venir !\r\n\r\n<span class=\"label label-info\">PARTICIPANTS: </span> Voici une liste des commanditaires qui contribuent \u00e0 la seconde vente aux ench\u00e8res caritative annuelle de PyCon ! Si vous souhaitez \u00eatre ajout\u00e9 \u00e0 la liste, merci de contacter [Ewa Jodlowska](mailto:ewa@python.org).\r\n\r\n- \u00c0 venir !\r\n", 
        "created": "2012-07-08T12:43:49.940", 
        "publish_date": "2012-07-08T12:43:49", 
        "path": "sponsors/charityauction/"
    }
},
{
    "pk": 36, 
    "model": "cms.page", 
    "fields": {
        "body": "_[General installation help][]: 6:30-8:00PM Tuesday & Wednesday in Open Spaces._\r\n[General installation help]: /2013/about/volunteers/welcome\r\n\r\nIf you want to help others prepare for their Tutorial Installations at PyCon, here are some basic guidelines.\r\n\r\n### **Assume no network**\r\n\r\nAssume there may not be any network available.\r\n\r\n### **Use virtualenv**\r\n\r\nNormally, you want to setup using _virtualenv_ (assume people will take more than one tutorial), however there are some packages that will not install easily under virtualenv (pygame, for example; potentially some other packages which require your compilation environment and dependencies).  If you're going to use virutalenv, it would look something like this for example:\r\n\r\n        mkdir -p PyCon2012/tutorials/django\r\n        cd PyCon2012/tutorials/django\r\n        virtualenv --no-site-packages Vdjango\r\n\r\n<br/>\r\nSince virtualenv typically modifies the shell prompt to show which environment your operating under, pick a meaningful name.  I typically start all v-env's with \"V\" or \"E\"  (so they show together in a directory listing).\r\n\r\nPeople may want to add this to their bash login script:\r\n\r\n        activate() # for python virtualenv\r\n        {\r\n            source \"$*\"/bin/activate\r\n        }\r\n\r\n<br/>\r\nIt may help newcomers, as it makes the idioms for virtualenv a little more symmetrical and thus easier to remember, e.g.:\r\n\r\n         mkvirtualenv Vsomename\r\n         activate Vsomename\r\n         ... do stuff ...\r\n         deactivate\r\n\r\n<br/>\r\nOnce your virtualenv is activated, you can begin installing into it.\r\n\r\n\r\n### **Install from USB**\r\n\r\nPrepare your packages for USB Install (not from the network):\r\n\r\n        MY_USB = /path/to/usb\r\n        pip install -d $MY_USB/pkgs -r requirements.txt\r\n\r\n<br/>\r\nInstall from your own USB:\r\n\r\n        pip install --find-links=file://$MY_USB/pkgs --no-index -r requirements.txt\r\n\r\n<br/>\r\nYou don't need to use a _requirements.txt_ file; you can simply load packages individually by name, if that is more convenient.\r\n\r\n### **Ubiquitous USB**\r\n\r\nWhen downloading binary packages, whenever possible save for 3 platforms on your USB (Linux, Mac, Win).\r\n\r\nSo that all the USBs floating around Tutorial Prep nights look the same, follow this pattern:\r\n\r\n- USB top level directory **pkgs** - for python packages\r\n- USB top level directory **lin**, **mac**, **win** - for platform specific archives\r\n- USB top level directory **requirements** - pip requirements files, by course (e.g.: requirements/django.txt)\r\n", 
        "status": 2, 
        "updated": "2013-10-10T11:42:34.878", 
        "title": "Notes for Tutorial Preparation", 
        "body_fr": "_[Aide g\u00e9n\u00e9rale pour l'installation][]: 6:30-8:00PM le mardi et le mercredi dans Open Spaces._\r\n[Aide g\u00e9n\u00e9rale pour l'installation]: /2013/about/volunteers/welcome\r\n\r\nSi vous voulez aider d'autres pr\u00e9sentateurs pour leur Instalion de tutoriel au PyCon, voici quelques lignes directrices.\r\n\r\n### **Supposez qu'il n'y ait pas de r\u00e9seau**\r\n\r\nSupposez qu'il puisse n'y avoir de r\u00e9seau disponible.\r\n\r\n### **Utilisez virtualenv**\r\n\r\nNormalement, il vaut mieux installer en utilisant _virtualenv_ (supposez que les gens vont suivre plus d'un tutoriel). Toutefois, il existe certains paquetages qui sont difficiles \u00e0 installer avec virtualenv (pygame, par exemple, et potentiellement d'autres paquetages qui requi\u00e8rent votre environnement et vos d\u00e9pendances de compilation). Voici un example de virtualenv:\r\n\r\n        mkdir -p PyCon2012/tutorials/django\r\n        cd PyCon2012/tutorials/django\r\n        virtualenv --no-site-packages Vdjango\r\n\r\n<br/>\r\nComme virtualenv modifie habituellement l'invite de commandes afin de montrer sous quel environnement vous \u00eates, choisissez un nom pertinent. D'habitude, je commence tous les v-env avec un V ou un E, afin qu'ils soit regroup\u00e9 dans une liste de r\u00e9pertoires.\r\n\r\nOn peut ajouter ceci au script de connexion bash:\r\n\r\n        activer() # pour le  virtualenv Python\r\n        {\r\n            source \"$*\"/bin/activate\r\n        }\r\n\r\n<br/>\r\n\u00c7a peut aider les d\u00e9butants, comme les raccourcis sont un peu plus sym\u00e9triques et ainsi, plus facile \u00e0 m\u00e9moriser, par exemple:\r\n\r\n         mkvirtualenv Vsomename\r\n         activer Vsomename\r\n         ... faire quelque chose ...\r\n         desactiver\r\n\r\n<br/>\r\nUne fois votre virtualenv activ\u00e9, vous pouvez commencer \u00e0 y installer des choses.\r\n\r\n### **Installer \u00e0 partir d'un port USB**\r\n\r\nPr\u00e9parez vos paquetages pour l'installation USB (et non \u00e0 partir d'un r\u00e9seau):\r\n\r\n        MY_USB = /path/to/usb\r\n        pip install -d $MY_USB/pkgs -r requirements.txt\r\n\r\n<br/>\r\nInstallez \u00e0 partir de votre propre port USB:\r\n\r\n        pip install --find-links=file://$MY_USB/pkgs --no-index -r requirements.txt\r\n\r\n<br/>\r\nIl n'est pas n\u00e9cessaire d'avoir recours \u00e0 un fichier _requirements.txt_. Dans le cas o\u00f9 c'est plus pratique, vous pouvez simplement charger vos paquetages individuellement par leurs noms.\r\n\r\n### **USB universel**\r\n\r\nLorsque vous t\u00e9l\u00e9chargez des paquetages binaires, sauvegardez, si possible, pour les 3 plateformes sur votre USB (Linux, Mac, Win).\r\n\r\nAfin que tous les USB des soir\u00e9es de pr\u00e9paration aux tutoriels soient identiques, suivez ce mod\u00e8le:\r\n\r\n- r\u00e9pertoire racine USB **pkgs** - pour les paquetages python\r\n- r\u00e9pertoire racine USB **lin**, **mac**, **win** - pour les archives sp\u00e9cifiques \u00e0 une plateforme\r\n- r\u00e9pertoire racine USB **requirements** - fichiers de sp\u00e9cifications pip, par cours (par exemple: requirements/django.txt)\r\n", 
        "created": "2012-07-08T19:00:36.579", 
        "publish_date": "2012-07-08T19:00:36", 
        "path": "about/volunteers/welcome/usb/"
    }
},
{
    "pk": 37, 
    "model": "cms.page", 
    "fields": {
        "body": "Tutorial Assistants (TAs) are volunteers that help students learn by removing\r\nroadblocks from their learning such as setup issues, or by offering one on one\r\nhelp during exercises where's it's impractical for an instructor to answer\r\nquestions from everyone in the tutorial.\r\n\r\nWhat Does a TA Do?\r\n------------------\r\n\r\n- As a TA your primary purpose is to help students.  Your secondary purpose may\r\n  be to learn from the instructor, but don't let it interfere with your primary\r\n  purpose.  Don't bring a laptop, take a spot at a table, or take a handout.  Do\r\n  listen and learn when you're not helping.\r\n\r\n- Help with diagnosing platform-specific problems on a platform the instructor\r\n  doesn't know or use.\r\n\r\n- Give general Python help with exercises for students that are relatively new\r\n  to Python.\r\n\r\n- Give subject-specific help with exercises where you have expertise in the\r\n  tools or concepts being taught.\r\n\r\n- Try to be visible to students who need help, but invisible to the instructor\r\n  and not distract from their teaching.\r\n\r\n- By default, don't ask questions and don't correct the instructor, unless\r\n  they've said they want that.  They'd love to hear your feedback after the\r\n  tutorial, but during a tutorial it may interefere with their teaching.\r\n\r\n- Ask the instructor how else you can help.\r\n\r\n- Enjoy your experience!  Assisting in a tutorial is a very rewarding\r\n  experience, helping participants get unstuck, seeing their ah-hah moments, and\r\n  getting to know them.  In large tutorials teachers can't make connections with\r\n  very many students - but you can with a few.\r\n\r\n- Help people new to PyCon feel welcome.  Reach out to wallflowers during\r\n  breaks.\r\n\r\n- Join us for the catered snacks and lunch on us.\r\n\r\nHow Do I Volunteer?\r\n-------------------\r\n\r\n- Add an entry to the table below.  Indicate the slots for which you're\r\n  available, and list your expertise areas so we know where you're best suited\r\n  to help.  This information will be shared with Instructors who are looking for\r\n  more TAs.\r\n\r\n- Show up at the [Tutorial Preparation\r\n  Sessions](/2013/about/volunteers/welcome/ \"\") to meet\r\n  instructors, get last minute assignments to assist in tutorials, and help\r\n  tutorial participants with laptop setup.\r\n\r\n- Show up during the Tutorial days to offer ad hoc tutorial support.\r\n\r\n### TA Volunteers\r\n\r\n| Wed a.m. | Wed p.m. | Thu a.m. | Thu p.m. | Contact Info | Expertise and Notes |\r\n|:--------:|:--------:|:--------:|:--------:|:-------------|:--------------------|\r\n| yes | yes | no | no | <contact@example.com> | 10 years using Python, 6 with numpy, some Django |\r\n\r\nHow Do I Get Picked?\r\n--------------------\r\n\r\nWait to be contacted by Instructors.  They may ask questions to be sure you'd be\r\na good match for their tutorial.\r\n\r\nIf you don't hear ahead of time, show up at the Tutorial Support sessions or on\r\nTutorial Days to help out.\r\n\r\nIf you get an assignment, edit your availability in the table above or remove\r\nyour name entirely.", 
        "status": 2, 
        "updated": "2012-07-08T19:24:57.020", 
        "title": "Tutorial Assistants", 
        "body_fr": "", 
        "created": "2012-07-08T19:24:19.009", 
        "publish_date": "2012-07-08T19:24:19.009", 
        "path": "about/volunteers/assistants/"
    }
},
{
    "pk": 38, 
    "model": "cms.page", 
    "fields": {
        "body": "### [This page has moved (click to go there)](/2013/about/volunteers/)", 
        "status": 2, 
        "updated": "2013-02-18T16:07:45.922", 
        "title": "Volunteering On-Site", 
        "body_fr": "", 
        "created": "2012-07-08T19:29:59.292", 
        "publish_date": "2012-07-08T19:29:59", 
        "path": "about/volunteers/onsite/"
    }
},
{
    "pk": 39, 
    "model": "cms.page", 
    "fields": {
        "body": "Apply Now!\r\n--------\r\n<span class=\"label label-important\">Apply Now!</span> **To submit a financial aid application**, <a href=\"/2016/account/signup/\">sign up</a> or <a href=\"/2016/account/login/\">log in</a> to your account and proceed to the **Financial Aid** section of your <a href=\"/2016/dashboard/\">account dashboard</a>!\r\n\r\n## Philosophy/Outreach\r\n\r\nEveryone - even the conference chair - pays for registration so that we can assit those who might not otherwise be able to attend. This includes major diversity and outreach programs through [PyLadies](http://www.pyladies.com/), [CodeChix](http://www.codechix.org/), and [Python User Groups](http://wiki.python.org/moin/LocalUserGroups) to attract new speakers, students, and attendees.\r\n\r\nAn interest\u00ading aspect of this is that PyCon, as a conference, offers a very generous financial aid program \u2016 this means that some attendees, speakers, tutorial presenters, etc have some, or in rare cases, all of their expenses such as flight, hotel and admission provided to them from the PyCon bud\u00adget. PyCon goes out of its way to encourage people to apply for financial aid \u2016 even if we can\u2019t cover all of your expenses, we will give you free admission based on need. The FA application process is simple, and straight\u00ad for\u00adward. It\u2019s also very liberal \u2016 the only caveat is that speakers at the conference \u201cget bumped to the top\u201d of the applications so that we don\u2019t lose a good talk because of financial need. \r\n\r\nWe use the FA bud\u00adget to help individuals that would otherwise not be able to attend the conference. We also keep an eye towards diversity \u2016 for example in 2010 we had a specific grant pro\u00adgram (funded by Google) for women to attend PyCon \u2016 which they did in amazing numbers! We also try to help more people with less money than less people with more money \u2016 we want to spread assistance out as much as possible. This is why FA requires room-sharing at the conference hotel, this is why we may only cover part of a given applicant\u2019s costs \u2016 we want to help more people.\r\n\r\nEssentially, the financial aid program is the PyCon Outreach program - it's the community holding up the community and making itself accessible at this major event through these financial grants. It is the very spirit of the conference; make the information, knowledge, friendships and connection available to everyone or at least everyone we can budget in.\r\n\r\nFinancial aid is core to the mission of the PSF - The mission of the Python Software Foundation is to promote, protect, and advance the Python programming language, and to support and facilitate the growth of a [diverse](http://www.python.org/psf/diversity/) and international community of Python programmers.\r\n\r\nWe are happy to say, that on most years, we very happily break our financial aid bud\u00adget \u2016 mean\u00ading, if we have a positive out\u00adlook, we will gladly over\u00adspend on financial aid and take less \u201cprofit\u201d for the conference. The point of the conference is the community, it\u2019s not about the conference! We help the community as much as we can by help\u00ading to cover the costs of people who would not other\u00adwise be able to attend. \r\n\r\n### Timeline\r\n\r\n- Financial aid application opens: August 13th, 2013\r\n- Financial aid letters sent out to those giving talks: December 1st, 2013\r\n- Financial aid applications closed: January 1st, 2016\r\n- Financial aid awards sent: January 15th, 2016\r\n\r\nApply Now!\r\n--------\r\n<span class=\"label label-important\">Apply Now!</span> **To submit a financial aid application**, <a href=\"/2016/account/signup/\">sign up</a> or <a href=\"/2016/account/login/\">log in</a> to your account and proceed to the **Financial Aid** section of your <a href=\"/2016/dashboard/\">account dashboard</a>!\r\n\r\n<span class=\"label label-note\">Questions?</span> Please don't hesitate to email: [pycon-aid@python.org](mailto:pycon-aid@python.org \"pycon-aid@python.org\")", 
        "status": 2, 
        "updated": "2013-10-20T13:40:24.768", 
        "title": "Financial Assistance", 
        "body_fr": "## Philosophie/Sensibilisation\r\n\r\nTout le monde - m\u00eame la pr\u00e9sidente de la conf\u00e9rence - paie pour l'inscription afin de venir en aide \u00e0 ceux qui, autrement, ne pourrait assister \u00e0 l'\u00e9v\u00e8nement. Ceci permet l'existence de programmes de diversit\u00e9 et de sensibilisation tels que [PyLadies](http://www.pyladies.com/), [CodeChix](http://www.codechix.org/) et [Python User Groups](http://wiki.python.org/moin/LocalUserGroups) qui recrutent de nouveaux pr\u00e9sentateurs, \u00e9tudiants et participants. \r\n\r\nUn aspect int\u00e9ressant de cette formule est le g\u00e9n\u00e9reux programme d'aide financi\u00e8re de PyCon. Celui-ci soutient certains participants, pr\u00e9sentateurs et animateurs de tutoriels en couvrant une partie ou plus rarement, la totalit\u00e9 de leurs d\u00e9penses, telles que le billet d'avion, l'h\u00f4tel et l'admission \u00e0 la conf\u00e9rence. PyCon pers\u00e9v\u00e8re \u00e0 encourager quiconque d'appliquer pour l'aide financi\u00e8re - m\u00eame si on ne peut couvrir toutes vos d\u00e9penses, l'admission sera gratuite, en fonction des besoins. Appliquer pour l'aide financi\u00e8re consiste en une d\u00e9marche simple et directe. C'est \u00e9galement tr\u00e8s lib\u00e9ral - toutefois, nous donnons la priorit\u00e9 aux pr\u00e9sentateurs afin de ne pas perdre un s\u00e9minaire int\u00e9ressant pour des raisons financi\u00e8res.\r\n\r\nNous utilisons le budget de l'aide financi\u00e8re pour venir en aide \u00e0 des personnes qui ne pourraient pas assister \u00e0 la conf\u00e9rence autrement. Nous portons \u00e9galement attention \u00e0 la diversit\u00e9 : par exemple, en 2010, nous avions un programme de subvention (financ\u00e9 par Google) visant la participation des femmes - qui a \u00e9t\u00e9 un succ\u00e8s! Nous essayons aussi d'aider un maximum de gens avec moins d'argent, plut\u00f4t qu'un minimum avec beaucoup d'argent - nous voulons optimiser l'aide financi\u00e8re. C'est pourquoi l'aide financi\u00e8re, par exemple, exige le partage de chambres \u00e0 l'h\u00f4tel ou ne couvre qu'une partie des d\u00e9penses d'un candidat - afin d'aider le plus grand nombre d'individus possible.\r\n\r\nIntrins\u00e8quement, le programme d'aide financi\u00e8re est le programme de sensibilisation PyCon. C'est la communaut\u00e9 qui soutient la communaut\u00e9 et qui se rend accessible \u00e0 cet \u00e9venement important \u00e0 travers les subventions. C'est l'esprit-m\u00eame de la conf\u00e9rence: rendre l'information, le savoir, les amiti\u00e9s et les liens accessibles \u00e0 tous, ou au moins, \u00e0 tous ceux que l'on peut soutenir.\r\n\r\nL'aide financi\u00e8re est au coeur de la mission du PSF (_Python Software Foundation_), qui consiste \u00e0 promouvoir, prot\u00e9ger et faire progresser le langage de programmation Python, ainsi que soutenir et faciliter la croissance d'une communaut\u00e9 [diversifi\u00e9e](http://www.python.org/psf/diversity/) et internationale de d\u00e9veloppeurs Python.\r\n\r\nNous sommes heureux de pouvoir affirmer qu'au courant des derni\u00e8res ann\u00e9es, nous avons d\u00e9pass\u00e9, avec plaisir, notre budget pour l'aide financi\u00e8re. Autrement dit, avec une perspective positive, il nous fait plaisir de d\u00e9bourser plus que pr\u00e9vu pour l'aide financi\u00e8re et avoir moins de \u00abprofits\u00ab pour la conf\u00e9rence. L'objectif de la conf\u00e9rence, c'est la communaut\u00e9, et non la conf\u00e9rence elle-m\u00eame! Nous appuyons la communaut\u00e9 autant que possible en couvrant les d\u00e9penses des individus qui ne pourrait pas autrement participer.\r\n\r\n### Timeline\r\n\r\n- D\u00e9but des demandes d'aide financi\u00e8re : 13 ao\u00fbt 2013\r\n- R\u00e9ponses pour l'aide financi\u00e8re envoy\u00e9es aux pr\u00e9sentateurs : 1er d\u00e9cembre 2013\r\n- Date limite pour les demandes d'aide financi\u00e8re : 1er janvier 2016\r\n- Envoi des prix de l'aide financi\u00e8re : 15 janvier 2016\r\n\r\nAppliquez maintenant!\r\n--------\r\n<span class=\"label label-important\">Appliquez maintenant!</span> **Pour soumettre une demande \u00e0 l'aide financi\u00e8re**, <a href=\"/2016/account/signup/\">inscrivez-vous</a> ou <a href=\"/2016/account/login/\">connectez-vous</a> \u00e0 votre compte et dirigez-vous vers la section **Aide financi\u00e8re** de votre <a href=\"/2016/dashboard/\">tableau de bord</a>!\r\n\r\n<span class=\"label label-note\">Des questions?</span> N'h\u00e9sitez pas \u00e0 nous envoyer un courriel: [pycon-aid@python.org](mailto:pycon-aid@python.org \"pycon-aid@python.org\")\r\n", 
        "created": "2012-07-08T21:05:01.541", 
        "publish_date": "2012-07-08T21:05:01", 
        "path": "assistance/"
    }
},
{
    "pk": 40, 
    "model": "cms.page", 
    "fields": {
        "body": "PyCon is organized and run by volunteers from the Python community. Everyone who is attending PyCon is welcome, and all help is very much appreciated.\r\n\r\nWant to get started? Read about the various opportunities to get involved below, and consider signing up for the [pycon-organizers mailing list][pycon-organizers]! It's how our community stays informed throughout the year, and signing up doesn't commit you to anything.\r\n\r\nHelp Before & After the Conference\r\n------------------------------------\r\n\r\nPyCon may only be one week out of the year, but there's plenty to be done in the 51 weeks leading up to it!\r\n\r\nHere are some ways you can help.\r\n\r\nPublicize & Promote PyCon\r\n---------------------------\r\n\r\nOne great way you can help is by simply letting people know about PyCon. It's never too early to promote PyCon, and the more interest we have, the more we are able to do for the community! Head over to the [Publicizing Pycon][publicize] page for some ideas.\r\n\r\nJoin the Mailing List\r\n---------------------\r\n\r\nThe [pycon-organizers mailing list][pycon-organizers] is the go-to place for conference planning. The list is active year-round, since we start planning in mid-Summer for the following year's PyCon.  Head over to the [pycon-organizers mailing list][pycon-organizers] and sign up!\r\n\r\nStep up as a Local Expert\r\n-------------------------\r\n\r\nIf you're familiar with the area around the venue, consider joining the [pycon-organizers mailing list][pycon-organizers] and suggesting improvements for the [Venue pages][venue].\r\n\r\nTake a Leadership Role\r\n-------------------------\r\n\r\nDo you want to develop your leadership skills?  [Sign up for a role on the PyCon Conference Staff](/2016/about/staff/). There are always openings to fill, or you can suggest creating a new role if you see an unmet need.\r\n\r\nJoin one of the Planning Committees\r\n-----------------------------------\r\n\r\nYou might consider joining one of the three core committees that help create PyCon:\r\n\r\n1. The [Program Committee](/2016/community/volunteers/programcommittee/) selects the talks that are presented during PyCon.\r\n2. The [Tutorial Committee](/2016/community/volunteers/tutorialcommittee/) selects the classes that are offered during PyCon.\r\n3. The [Conference Committee](/2016/community/volunteers/conferencecommittee/) handles the logistics of when, where, and how PyCon happens.\r\n\r\n[publicize]: /2016/community/volunteers/publicizing/\r\n[pycon-organizers]: http://mail.python.org/mailman/listinfo/pycon-organizers \"PyCon Organizers' Mailing List\"\r\n[venue]: /2016/venue/", 
        "status": 2, 
        "updated": "2013-10-10T17:27:49.983", 
        "title": "Volunteering", 
        "body_fr": "PyCon est organis\u00e9 et g\u00e9r\u00e9 par des b\u00e9n\u00e9voles de la communaut\u00e9 Python. Tout le monde est le bienvenu \u00e0 assister \u00e0 PyCon, et toute aide est tr\u00e8s appr\u00e9ci\u00e9e .\r\n\r\nVous voulez nous aider ? Venez d\u00e9couvrir les nombreuses opportunit\u00e9s pour s'impliquer list\u00e9es ci-dessous et n'h\u00e9sitez pas \u00e0 vous inscrire sur la liste de diffusion pycon-organizers ! C'est par ce biais que notre communaut\u00e9 s'informe tout au long de l'ann\u00e9e, et s'inscrire ne vous engage en rien \u00e0 participer.\r\n\r\nAidez avant et apr\u00e8s la conf\u00e9rence\r\n------------------------------------\r\n\r\nPyCon ne dure qu'une semaine par an, mais il y a beaucoup \u00e0 faire durant les 51 semaines qui pr\u00e9c\u00e8dent !\r\nVoici quelques fa\u00e7ons dont vous pouvez aider.\r\n\r\nFaites conna\u00eetre et promouvez PyCon\r\n---------------------------\r\n\r\nUne excellente fa\u00e7on dont vous pouvez aider est de simplement informer les gens \u00e0 propos de PyCon . Il n'est jamais trop t\u00f4t pour promouvoir PyCon, et plus l'int\u00e9r\u00eat grandit, plus nous sommes en mesure d'aider la communaut\u00e9 ! Rendez-vous sur la page [publicit\u00e9 de PyCon][publicize] pour avoir quelques id\u00e9es.\r\n\r\nRejoignez la liste de diffusion\r\n---------------------------\r\n\r\nLa [liste de diffusion pycon-organizers][pycon-organizers] est le point de rassemblement pour l'organisation de la conf\u00e9rence. La liste est active toute l'ann\u00e9e, puisque nous commen\u00e7ons la planification \u00e0 la mi-\u00e9t\u00e9 pour la PyCon de l'ann\u00e9e suivante. Rendez-vous sur la [liste de diffusion pycon-organizers][pycon-organizers] et inscrivez-vous !\r\n\r\nD\u00e9marquez-vous en tant qu'expert local\r\n---------------------------\r\n\r\nSi vous \u00eates familier avec la r\u00e9gion autour du lieu de la conf\u00e9rence, envisager de rejoindre la [liste de diffusion pycon-organizers][pycon-organizers] et sugg\u00e9rer des am\u00e9liorations pour les [pages parlant du site][venue].\r\n\r\nAssumez un r\u00f4le de dirigeant\r\n---------------------------\r\n\r\nVous souhaitez d\u00e9velopper vos comp\u00e9tences en dirigeant ? [Inscrivez-vous pour jouer un r\u00f4le dans l'\u00e9quipe de conf\u00e9rence PyCon](/2016/about/staff/). Il y a toujours des postes \u00e0 remplir, ou vous pouvez sugg\u00e9rer la cr\u00e9ation d'un nouveau r\u00f4le si vous voyez un besoin non satisfait.\r\n\r\nRejoignez l'un des comit\u00e9s de planification\r\n-----------------------------------\r\n\r\nVous pouvez envisager de rejoindre l'un des trois comit\u00e9s qui sont au coeur de l'organisation du PyCon :\r\n\r\n1. Le [Comit\u00e9 du programme](/2016/community/volunteers/programcommittee/) qui s\u00e9lectionne les conf\u00e9rences qui sont pr\u00e9sent\u00e9es durant PyCon.\r\n2. Le [Comit\u00e9 de tutoriels](/2016/community/volunteers/tutorialcommittee/) qui s\u00e9lectionne les cours qui sont offerts durant PyCon.\r\n3. Le [Comit\u00e9 d'organisation](/2016/community/volunteers/conferencecommittee/) qui s'occupe de la logistique de quand, o\u00f9 et comment PyCon \u00e0 lieu.\r\n\r\n\r\n[publicize]: /2016/community/volunteers/publicizing/\r\n[pycon-organizers]: http://mail.python.org/mailman/listinfo/pycon-organizers \"PyCon Organizers' Mailing List\"\r\n[venue]: /2016/venue/", 
        "created": "2012-07-08T21:43:16.336", 
        "publish_date": "2012-07-08T21:43:16", 
        "path": "about/volunteers/"
    }
},
{
    "pk": 41, 
    "model": "cms.page", 
    "fields": {
        "body": "Tutorial Assistants (TAs) are volunteers that help students learn by removing\r\nroadblocks from their learning such as setup issues, or by offering one on one\r\nhelp during exercises where's it's impractical for an instructor to answer\r\nquestions from everyone in the tutorial.\r\n\r\nWhat Does a TA Do?\r\n------------------\r\n\r\n- As a TA your primary purpose is to help students.  Your secondary purpose may\r\n  be to learn from the instructor, but don't let it interfere with your primary\r\n  purpose.  Don't bring a laptop, take a spot at a table, or take a handout.  Do\r\n  listen and learn when you're not helping.\r\n\r\n- Help with diagnosing platform-specific problems on a platform the instructor\r\n  doesn't know or use.\r\n\r\n- Give general Python help with exercises for students that are relatively new\r\n  to Python.\r\n\r\n- Give subject-specific help with exercises where you have expertise in the\r\n  tools or concepts being taught.\r\n\r\n- Try to be visible to students who need help, but invisible to the instructor\r\n  and not distract from their teaching.\r\n\r\n- By default, don't ask questions and don't correct the instructor, unless\r\n  they've said they want that.  They'd love to hear your feedback after the\r\n  tutorial, but during a tutorial it may interfere with their teaching.\r\n\r\n- Ask the instructor how else you can help.\r\n\r\n- Enjoy your experience!  Assisting in a tutorial is a very rewarding\r\n  experience, helping participants get unstuck, seeing their ah-hah moments, and\r\n  getting to know them.  In large tutorials teachers can't make connections with\r\n  very many students - but you can with a few.\r\n\r\n- Help people new to PyCon feel welcome.  Reach out to wallflowers during\r\n  breaks.\r\n\r\n- Join us for the catered snacks and lunch on us.\r\n\r\nHow Do I Volunteer?\r\n-------------------\r\n\r\n- Add an entry to the table below.  Indicate the slots for which you're\r\n  available, and list your expertise areas so we know where you're best suited\r\n  to help.  This information will be shared with Instructors who are looking for\r\n  more TAs.\r\n\r\n  *Note:*  Also consider signing up as a Host / Greeting at the start of tutorials:\r\n   [Tutorial Host Signup](http://goo.gl/p8cDt)\r\n\r\n- Show up at the [Tutorial Preparation\r\n  Sessions](/2013/community/welcome/ \"\") to meet\r\n  instructors, get last minute assignments to assist in tutorials, and help\r\n  tutorial participants with laptop setup.\r\n\r\n- Show up during the Tutorial days to offer ad hoc [Tutorial\r\n  Support](/2013/community/volunteer/onsite/#tutorials \"\").\r\n\r\n### TA Volunteers\r\n\r\nEnter your availability:\r\n\r\n| Wed a.m. | Wed p.m. | Thu a.m. | Thu p.m. | Contact Info (include your name) | Expertise and Notes |\r\n|:--------:|:--------:|:--------:|:--------:|:-------------|:--------------------|\r\n| yes | yes | no |no  | <crg.mabrey@gmail.com> | 1 year of python, matplotlib and some Django |\r\n| no | yes | no | yes | Will Farley <webpowerlabs@gmail.com> | 1 year python, primarily Django, reading 2 scoops ;) |\r\n| no  | no  | no  | yes | Senthil Kumaran <senthil@uthcode.com> | Few years of Python development. Been a tutorial instructor at previous pycons.\r\n| yes | yes | yes | yes | Ramya Narayanaswamy <nramya@udel.edu> | 1 year of Python\r\n| yes | yes | yes | yes | Luiz Irber <luiz.irber@gmail.com> | 7 years of Python, HPC, SciPy stack\r\n| yes | yes | yes | no | Maxim Brieiev <lacrima.maxim@gmail.com> | 4 years of Python. Linux, Twisted. Can help with setting up dev environment.\r\n\r\n\r\nHow Do I Get Picked?\r\n--------------------\r\n\r\nWait to be contacted by Instructors.  They may ask questions to be sure you'd be\r\na good match for their tutorial.\r\n\r\nIf you don't hear ahead of time, show up at the Tutorial Support sessions or on\r\nTutorial Days to help out.\r\n\r\nIf you get an assignment, edit your availability in the table above or remove\r\nyour name entirely.", 
        "status": 2, 
        "updated": "2013-03-10T00:02:20.255", 
        "title": "Tutorial Assistants", 
        "body_fr": "", 
        "created": "2012-07-08T22:43:01.822", 
        "publish_date": "2012-07-08T22:43:01.822", 
        "path": "community/assistants/"
    }
},
{
    "pk": 42, 
    "model": "cms.page", 
    "fields": {
        "body": "\r\nWe need volunteers to support each session and keep them on track. The duties are simple yet vital to the success of the conference. You\u2019ll help keep an eye on the clock, make sure everyone is in the right place, give the audience a voice, and get a front seat.\r\n\r\nThere are two roles: [**Session Chairs**](#chairs) and [**Session Runners**](#runners). Each needs to be present for the full session.  A session is the group of talks in between breaks (usually 2-3 talks).\r\n\r\n### [**SESSION CHAIRS**](#chairs) {#chairs}\r\n\r\nSession Chairs take charge of the session. You start by getting on stage to introduce the speaker. Keep the intro simple -- something like their name, where they\u2019re from, and the talk title.  Then head back and close the doors to keep it quiet. You watch the clock and let the speaker know when it\u2019s time to stop for questions. If there are multiple questions, you juggle who gets the microphone, pass it around, then let the speaker know when it\u2019s time to wrap it all up. After that, help them disconnect the microphone equipment and make any last announcements (open spaces, BoF, etc).\r\n\r\n### [**SESSION RUNNERS**](#runners) {#runners}\r\n\r\nSession Runners are the shepherds of the session. You start in the elusive Green Room fifteen minutes before each talk and help the speaker get ready. The first step is a test run of the speaker\u2019s laptop on the projector to make sure they can walk up and get started immediately. After everything is alright, you'll show the speaker where to upload their slides -- attendees like a copy for later, and everyone following along with the videos online does too. Five minutes before talk time, the **runner** and speaker head to the session and get situated. Assuming everything gets connected and ready to roll, the runner hands it off to the chair to do their introduction (tip off the chair on pronunciation, and any other requests from the speaker, as needed).\r\n\r\nAre you willing to help? If so, signing up is as easy as viewing the [Conference Schedule](/2013/schedule/) and signing up an open time slot.\r\n\r\nFirst login to the site, then find a time slot, then click the blue S in one of the talk slots for the session (the entire session is outlined in black).\r\n<center>\r\n![Session Staff Signup](http://i.imgur.com/jgHXQ.png)\r\n</center>", 
        "status": 2, 
        "updated": "2012-07-08T23:58:32.037", 
        "title": "Session Staff", 
        "body_fr": "", 
        "created": "2012-07-08T22:57:06.107", 
        "publish_date": "2012-07-08T22:57:06.107", 
        "path": "community/volunteer/onsite/sessionstaff/"
    }
},
{
    "pk": 43, 
    "model": "cms.page", 
    "fields": {
        "body": "The tutorials below have pages with revised instructions for setting\r\nup a laptop before the tutorial session, or other communications from\r\ninstructors to participants.\r\n\r\nIf you don't see the tutorials(s) you're taking in the list below and\r\nwant to know how to prepare your laptop, check for prerequisites or\r\ninstructions listed with the tutorial description via the [Tutorial\r\nSchedule](. \"Check back when the schedule is available!\").  For many\r\ntutorials the setup is very simple and is handled in the first few\r\nminutes of the tutorial.\r\n\r\n### **Tutorial Preparation Sessions**\r\n\r\n[Tutorial Preparation Sessions][welcome] are held\r\nfrom 6:30-8:00PM\r\non Tuesday and Wednesday in the Registration area.\r\nYou can get help there setting up your laptop for the tutorials.\r\n\r\n### **Use virtualenv**\r\n\r\nYou may want to make installations for your tutorials using virtualenv (particularly if you are taking more than one tutorial).\r\nVirtualenv is part of Python-3.3.  If your tutorial is using Python-2.7, install current versions of virtualenv and pip.\r\nThere will be a virtualenv orientation in the Tutorial Preparation Sessions.\r\n\r\n### **Pre-Tutorial Notes from the Instructors**\r\n\r\n| Notes from Instructors                                     |  I can help install |\r\n|:-----------------------------------------------------------|-------------------|\r\n| [virtualenv][] - for any Tutorial                   | Yarko Tymciurak, Peter Kropf       |\r\n| [Going from web pages to web apps with Python](8)|           |\r\n| [Introduction to SQLAlchemy](16 \"Introduction to SQLAlchemy\") - reading and software requirements!                     | Mike Bayer      |\r\n| [Bayesian Statistics Made Simple](21 \"Bayesian Statistics Made Simple\") | |\r\n| [Introduction to PyGame](19 \"Introduction to PyGame\") | |\r\n| [IPython in-depth: high-productivity interactive and parallel python](20 \"IPython in-depth: high-productivity interactive and parallel python\") | |\r\n| [Applied Parallel Computing with Python](27 \"Applied Parallel Computing with Python\") - Essential VirtualBox | Ian Ozsvald |\r\n| [A Gentle Introduction To Computer Vision](30 \"A Gentle Introduction to Computer Vision\") - | Katherine Scott and Anthony Oliver |\r\n| [A beginner's introduction to Pydata: how to build a minimal recommendation engine](28 \"A beginner's introduction to Pydata: how to build a minimal recommendation engine\") | Ramya Narayanaswamy |\r\n| [Fully Test-Driven Web Development with Django and Selenium](10 \"Fully Test-Driven Web Development with Django and Selenium\") - Git, Firefox, Django, Selenium | Harry Percival |\r\n| [An Introduction to scikit-learn: Machine Learning in Python](22 \"An Introduction to scikit-learn: Machine Learning in Python\") | Ramya Narayanaswamy |\r\n| [Pyramid for Humans](12 \"Pyramid for Humans\") |\r\n| [Rapid Web Prototyping with Lightweight Tools](13 \"Rapid Web Prototyping with Lightweight Tools\") |\r\n| [Effective Django](9 \"Effective Django\") |\r\n| [Advanced Machine Learning with scikit-learn](23 \"Advanced Machine Learning with scikit-learn\") | Olivier Grisel |\r\n| [Shiny, Let's Be Bad Guys: Exploiting and Mitigating the Top 10 Web App Vulnerabilities](14 \"Shiny, Let's Be Bad Guys\") | |\r\n| [Intermediate Twisted: Test-Driven Networking Software](15 \"Test-Driven Twisted\") ||\r\n| [Learn Python Through Public Data Hacking](2 \"Learn Python Through Public Data Hacking\") | |\r\n| [Faster Python Programs through Optimization](24 \"Faster Python Programs through Optimization\") | |\r\n| [Code to Cloud in under 45 minutes](17 \"Code to Cloud in under 45 minutes\") |John Wetherill|\r\n| [Python beyond the CPU](25 \"Python beyond the CPU\") | Andy Terrel\r\n| [Documenting Your Project in Sphinx](18 \"Documenting Your Project in Sphinx\") | Brandon Rhodes\r\n----\r\n\r\n### **Successfully Installed for your Tutorial?**\r\n\r\nIf you have successfully installed packages for a tutorial you're attending, and would like to help others at the [Tutorial Preparation][welcome] sessions, then follow the [guidelines to prepare a USB][usb] installation package, and come help!\r\n\r\n_Note:_  Since the network might not be ready, you might want to install from your own USB, just to be sure the installation works.\r\n\r\n[tutorials]: /2013/schedule/tutorials/\r\n[usb]: /2013/community/welcome/usb/\r\n[virtualenv]: http://www.virtualenv.org/\r\n[welcome]: /2013/community/welcome/", 
        "status": 2, 
        "updated": "2013-03-13T01:58:05.276", 
        "title": "Tutorials", 
        "body_fr": "", 
        "created": "2012-07-08T23:17:00.296", 
        "publish_date": "2012-07-08T23:17:00.296", 
        "path": "community/tutorials/"
    }
},
{
    "pk": 44, 
    "model": "cms.page", 
    "fields": {
        "body": "| [Volunteering][volunteers] | \r\n{#top}\r\n\r\nPurpose\r\n-------\r\nThe Welcoming (Un)committee provides a welcoming experience for newbies of all kinds to PyCon.  If you are new to:\r\n\r\n* PyCon\r\n* public speaking\r\n* presenting at PyCon\r\n* Santa Clara\r\n* other\r\n\r\nthen the Welcoming (Un)committee may be of service to you.\r\n\r\nWelcoming (Un)committee members may be identified by pink ribbons on their conference badges.\r\n\r\nRead [about PyCon 2013](https://us.pycon.org/2013/about/what-is-pycon/ \"about PyCon 2013\").\r\n\r\n\r\n### ** WELCOME EVENTS **\r\n\r\n_Have a quick look at the [Schedule of Volunteering Events](http://goo.gl/TehrR)!_\r\n\r\n#### **Tutorial Preparation**\r\n- 6:30-8:00PM, Tuesday and Wednesday March 12-13\r\n- Open Spaces area\r\n\r\nWelcome (Un)committee members will help with installations for your Tutorials.  We will help attendees install a proper python development environment, download and install required packages and files, and how to avoid common newbie mistakes.  Common issues include using the default Macintosh python installation (not recommended) and how to use virtualenv.\r\n\r\n[Sign up **here**](/2013/community/tutorials/) to prepare one (or more) of the installations, so you can help others.  Follow the guidelines to [prepare a USB installation](usb/), complete one of the installations based on the [Notes from an Instructor](/2013/community/tutorials/), then [put your name down](/2013/community/tutorials/) to help people on Tutorial Preparation nights.  \r\n\r\n_Note_: Since we may not have network on Tuesday (and possibly Wednesday),  [prepare the packages for installation from a USB](usb/).\r\n\r\n#### **Tutorial Hosts & Hostesses / Tutorial Troubleshooting** \r\n- Wednesday and Thursday March 13-14\r\n- Tutorials Area\r\n\r\nBeing **_Welcoming_** means being good hosts to fellow conference attendees! From 20 minutes before, through 20 minutes after the start of Tutorial sessions, Welcome members will help make sure people are in the right tutorial, help with printed handouts, and be ready to give any more help as needed.  See the [onsite volunteer page][tutorials_info] for more details.\r\n\r\nAfter [ushering in people to their Tutorials][host_info], Welcome (Un)committee members will be available to troubleshoot issues as they arise.  If you'd like to help, sign up on the [Tutorial Assistant's](/2013/community/assistants/) page.\r\n\r\n#### **Newbie Nights** {#newbie_nights}\r\n- Thursday and Friday March 14-15\r\n- Open space area\r\n\r\nNewbie Nights will be Open Space sessions to welcome all newbies of all kinds. Check the board in the Open Spaces area for times.\r\n\r\n### ** Did we miss anything? **\r\nPlease take a moment to help us by answering the question, \"How (else) could the PyCon community help you feel welcome?\"\r\n\r\n****\r\n- Put your suggestions / requests here (edit this page)\r\n-\r\n\r\n****\r\n\r\n## ** Join the Welcome (Un)committee **\r\n\r\nThe Welcoming (Un)committee is a sub-committee of the PyCon Organizers group.  Anyone who wants to own any part of Welcoming may participate.  If you like helping, being a good host, and are comfortable saying \"I don't know - let's find someone who does!\" then you're our kind of people!\r\n\r\nThe \"(Un)committee\" (it's something of a joke name, since it does not meet or vote) is loosely made up of the following people, possibly plus unnamed others. Please add yourself if you wish to help.  Also, be sure to [sign up to the organizer's][pycon-organizers] mailing list.\r\n\r\n[pycon-organizers]: http://mail.python.org/mailman/listinfo/pycon-organizers \"PyCon Organizers' Mailing List\"\r\n\r\n- SteveHolden\r\n- PeterKropf\r\n- Yarko Tymciurak (@yarkot, yarkot1@gmail.com)\r\n- Lydia Pierce (@liddy_pierce, liddy.pierce@gmail.com)\r\n- Rami Chowdhury (@necaris, rami.chowdhury@gmail.com)\r\n- Gloria W (@gloriajw, strangest@comcast.net)\r\n\r\n[volunteers]:  /2013/about/volunteers/\r\n[tutorials_info]: /2013/about/volunteers/#tutorials\r\n[host_info]: /2013/community/volunteer/tutorial_hosts/", 
        "status": 2, 
        "updated": "2013-03-11T20:23:56.788", 
        "title": "Welcoming (Un)committee", 
        "body_fr": "", 
        "created": "2012-07-08T23:25:00.821", 
        "publish_date": "2012-07-08T23:25:00.821", 
        "path": "community/welcome/"
    }
},
{
    "pk": 45, 
    "model": "cms.page", 
    "fields": {
        "body": "\r\nA Tutorial Host is a volunteer who helps at the start of a specific\r\ntutorial session.  Their purpose:\r\n\r\n- Welcome students and help them get settled.  For many students (and\r\n  possibly you, too) this is their first PyCon and their first\r\n  impression of PyCon.  The tone we set with each person sets the tone\r\n  for PyCon this year and going forward.  We are a welcoming and\r\n  friendly community.\r\n\r\n- Help Instructors by offloading some of the administrative work of\r\n  getting people settled.  In a small class of 20 the Instructor can\r\n  usually do all of this alone, but in most classes they can't.  This\r\n  also helps classes start on time.\r\n\r\n- Be sure people who have signed up for the tutorial can attend.\r\n  Unfortunately, room is limited in most tutorials and we only have\r\n  room for those who have signed up.  In a few cases last year, people\r\n  who signed up for a tutorial were left standing or sitting on the\r\n  floor because all the seats had been taken by the time they arrived.\r\n\r\n- Help PyCon track tutorial attendance more closely (how many\r\n  no-shows, how many TAs are helping, etc.)\r\n\r\nBefore the Tutorial\r\n====\r\n\r\n- Go to the tutorial/registration desk about 20 minutes before the start of the tutorial session\r\n\r\n- Pick up a Tutorial Host sheet for a tutorial.  The sheet will have:\r\n\r\n    - A list of students sorted by badge number\r\n    - A list of tutorials and locations (in case someone is lost or is requesting to change tutorials)\r\n    - These instructions.\r\n\r\n- Go to the classroom\r\n\r\nIn the Classroom\r\n====\r\n\r\n- Introduce yourself to the instructor\r\n\r\n    - Ask if they have handouts to hand out to students as they\r\n      arrive.  We prefer these not be left on tables ahead of time to\r\n      be sure each student gets one.\r\n\r\n    - Ask if they have any specific instructions to pass on to arriving students.\r\n\r\n    - Find out if there are TAs in the tutorial who are ready to help\r\n      with laptop setup if required.\r\n\r\n    - Ask them how many TAs they have and make a note of it on the\r\n      sheet for our records.\r\n\r\n- Go around the classroom to greet any students that have arrived\r\n       early, check their name on the list, etc., as per below.\r\n\r\n- Set-up your greeting station - stand at the door, sit on a chair,\r\n    sit at a table with handouts - whatever you prefer.\r\n\r\nAs students arrive\r\n====\r\n\r\n- Greet them at the classroom door\r\n\r\n- Make sure they're in the right tutorial\r\n\r\n- Check off their name/badge number on the registration list\r\n\r\n- Give them a printed handout if there is one for the tutorial\r\n\r\n- Ask if they need any help setting up their laptop for the class, directing them to a TA if required\r\n\r\n- Answer any other questions they may have, or try to direct them to someone who can\r\n\r\n- Encourage them to leave the back row or two for people arriving late\r\n\r\nAs the Tutorial starts\r\n====\r\n\r\n- Stay around for about 20 minutes to be sure people\r\n  arriving late find a place to sit and get any help they need.  You\r\n  can hang out inside or outside the door.\r\n\r\n- Double-check the number of TAs.  If there are more than the\r\n  Instructor says, for example if some extras were added last\r\n  minute, please update the TA count on the sheet for our records.\r\n\r\n- If you're not in the tutorial (as a student or a TA), please give\r\n  the sheet to a TA (if there is one) or the Instructor as you\r\n  leave.  They will be collected at the break.\r\n\r\nWhat to do if...\r\n===\r\n\r\n- If someone doesn't have their PyCon badge and number, direct them to\r\n  the registration desk to pick up their badge.\r\n\r\n- If someone's badge number or name isn't on the sheet, have them show\r\n  you the back of their badge which lists the tutorials they've signed\r\n  up for.  They may be in the wrong room, or their tutorial may be\r\n  later.\r\n\r\n- If someone says they signed up for a different tutorial and want to\r\n  switch:\r\n\r\n  - If you're hosting a tutorial that has 75 or more students on the\r\n    list, tell them it's full.  There may be more than 75 chairs, but\r\n    that's to give enough room to students that they won't be bumping\r\n    elbows.\r\n\r\n  - If the tutorial has less than 75 students and lots of space in the\r\n    room, we might be able to accommodate them, but it's complicated:\r\n\r\n    - Check with the Instructor to see if they mind someone switching\r\n      into their tutorial.\r\n\r\n    - If others have already switched into this one, stop at 10%,\r\n      i.e. don't allow more than 10% to switch into this tutorial.\r\n\r\n    - Have the person who wants to switch show you their badge to\r\n      verify which other tutorial they signed up for in the same time\r\n      slot.\r\n\r\n    - Ask them to tell the host of the other tutorial that they won't\r\n      be attending.\r\n\r\n    - Add their badge number, name, and the tutorial they had signed\r\n      up for (by number is fine) to the list.\r\n\r\n    - Don't give them a handout (if the tutorial has handouts).\r\n\r\n    - If they offer to stand or sit on the floor, either tell them no,\r\n      that diminishes the tutorial experience for others, but they can\r\n      go to the Tutorial Coordinator at the registration/tutorial desk\r\n      to discuss, or just say you're not sure and direct them to the\r\n      tutorial desk to ask that question.\r\n\r\n    - Use your judgement.  The guidelines above are intended to reduce\r\n      problems and maximize the quality of the tutorials for everyone,\r\n      but primarily for those that signed up for this tutorial, not\r\n      those that want to switch.  If the rules aren't working to\r\n      accomplish that, bend them.\r\n\r\n- If someone is uncooperative, ask a TA or the Instructor for help, or\r\n  go to the tutorial desk to ask for help.\r\n", 
        "status": 2, 
        "updated": "2013-10-12T19:08:45.328", 
        "title": "Tutorial Hosts", 
        "body_fr": "Un assistant tutoriel est un b\u00e9n\u00e9vole qui offre son aide au d\u00e9but d'une pr\u00e9sentation sp\u00e9cifique. Son r\u00f4le est : \r\n\r\n- D'accueillir les \u00e9tudiants et de les aider \u00e0 s'installer. Pour beaucoup d'\u00e9tudiants (et peut-\u00eatre vous); il s'agit de leur premi\u00e8re PyCon et donc, de leur premi\u00e8re impression \u00e0 propos de PyCon. Le ton donn\u00e9 par chaque personne d\u00e9fini le ton g\u00e9n\u00e9ral pour cette PyCon et celles \u00e0 venir. Nous sommes une communaut\u00e9 accueillante et cordiale.\r\n\r\n- D'aider les enseignants en les d\u00e9laissant d'une partie des t\u00e2ches administratives consistant \u00e0 s'assurer que les personnes sont bien install\u00e9es. Pour une classe de 20 personnes, l'enseignant peut g\u00e9n\u00e9ralement s'en occuper seul, mais dans la plupart des cas, c'est impossible. De plus, cela permet de commencer le cours \u00e0 l'heure.\r\n\r\n- Aider PyCon \u00e0 conna\u00eetre plus pr\u00e9cis\u00e9ment le taux de participation des tutoriaux (combien de personnes ne se sont pas pr\u00e9sent\u00e9es, combien de responsables tutoriel ont aid\u00e9, etc.)\r\n\r\n\r\nAvant le tutoriel\r\n====\r\n\r\n- Allez au tutoriel/bureau d'enregistrement environ 20 minutes avant le d\u00e9but de la session\r\n\r\n- Prenez une pochette pour assistant d'enseignement assign\u00e9e \u00e0 un tutoriel. Cette pochette comporte :\r\n\r\n    - Une liste d'\u00e9tudiant tri\u00e9e par ordre croissant\r\n    - Une liste des tutoriaux et de leurs emplacements respectifs (au cas o\u00f9 une personne est perdue ou demande \u00e0 changer de tutoriel)\r\n    - Les pr\u00e9sentes instructions.\r\n\r\n- Allez dans la salle du tutoriel\r\n\r\n\r\nDans la salle\r\n====\r\n\r\n- Pr\u00e9sentez-vous \u00e0 l'enseignant\r\n\r\n    - Demandez s'ils ont des polycopi\u00e9s \u00e0 remettre aux \u00e9tudiants lorsqu'ils arrivent. Nous pr\u00e9f\u00e9rons ne pas les d\u00e9poser en avance sur la table afin de s'assurer que chaque \u00e9tudiant en r\u00e9cup\u00e8re un exemplaire.\r\n\r\n    - Demandez s'ils ont des instructions sp\u00e9cifiques \u00e0 donner aux \u00e9tudiants avant qu'ils n'arrivent.\r\n\r\n    - Trouvez s'il y a un ou des assistants d'enseignement qui sont pr\u00eat \u00e0 aider, avec un ordinateur configur\u00e9 si besoin est.\r\n\r\n    - Demandez le nombre d'assistants d'enseignement qu'ils ont et le noter dans la pochette pour nos archives.\r\n\r\n- Promenez-vous autour de la salle pour accueillir tout \u00e9tudiant arrivant en avance, v\u00e9rifier son nom sur la liste, etc, comme ci dessous.\r\n\r\n\r\nQuand les \u00e9tudiants arrivent\r\n====\r\n\r\n- Les accueillir \u00e0 la porte d'entr\u00e9e.\r\n\r\n- S'assurer qu'ils sont au bon tutoriel.\r\n\r\n- Cochez leurs noms ou num\u00e9ros de badges sur la liste d'inscription.\r\n\r\n- Donnez-leur un polycopi\u00e9 s'il y a un pour ce tutoriel.\r\n\r\n- Leur demander s'ils ont besoin d'aide pour configurer leur ordinateur pour cette classe, les diriger vers un assistant d'enseignement si besoin.\r\n\r\n- R\u00e9pondre \u00e0 toute question qu'ils peuvent poser, ou essayer de les rediriger vers quelqu'un qui peut leur r\u00e9pondre.\r\n\r\n- Les encourager \u00e0 laisser une ou deux rang\u00e9es \u00e0 l'arri\u00e8re de la classe pour les personnes arrivant en retard.\r\n \r\n\r\nQuand le tutoriel commence\r\n====\r\n\r\n- Restez dans les alentours pendant environ 20 minutes pour \u00eatre sur que les retardataires trouver une place o\u00f9 s'assoir et obtiennent toute l'aide n\u00e9cessaire. Vous pouvez rester dans ou en dehors de la salle.\r\n\r\n- Rev\u00e9rifiez le nombre d'assistant d'enseignement. S'il y en a plus que le nombre fourni par l'enseignant, par exemple, si certains se sont ajout\u00e9s \u00e0 la derni\u00e8re minute, merci de mettre \u00e0 jour le nombre not\u00e9 dans la pochette pour les archives.\r\n\r\n- Si vous n'\u00eates plus dans le tutoriel (en tant que participant ou assistant d'enseignement), merci de remettre votre pochette \u00e0 un assistant d'enseignement (s'il y en a un) ou un instructeur quand vous partez. Elles seront collect\u00e9es \u00e0 la pause.\r\n\r\n\r\nQue faire si...\r\n====\r\n\r\n- Si quelqu'un n'a pas son badge et son num\u00e9ro PyCon, redirigez-le vers le bureau d'enregistrement central o\u00f9 il pourra le r\u00e9cup\u00e9rer. \r\n\r\n- Si quelqu'un n'a ni son nom ni son num\u00e9ro de badge inscrit sur la liste, lui montrer le dos de son badge sur lequel est la liste des tutoriaux auxquels il s'est inscrit. Cette personne est peut-\u00eatre dans la mauvaise salle ou son tutoriel est peut-\u00eatre plus tard.\r\n\r\n- Si quelqu'un explique qu'il s'est enregistr\u00e9 pour un autre tutoriel mais veut changer:\r\n\r\n  - Si vous vous occupez d'un tutoriel qui a 75 \u00e9tudiants ou plus, lui dire que la liste est compl\u00e8te. Il peut y avoir plus de 75 chaises mais cela permet de laisser de la place aux \u00e9tudiants sans \u00eatre trop serr\u00e9s.\r\n\r\n  - Si le tutoriel a moins de 75 \u00e9tudiants et beaucoup d\u2019espace dans la salle, vous pouvez l\u2019accommoder mais cela est compliqu\u00e9:\r\n\r\n    - Voir avec l'enseignant s'il accepte une personne suppl\u00e9mentaire voulant assister au tutoriel.\r\n\r\n    - Si d'autres participants se sont d\u00e9j\u00e0 ajout\u00e9s, arr\u00eater \u00e0 10%, i.e. ne pas laisser plus de 10% de l'audience s'ajouter au tutoriel.\r\n\r\n    - Demandez \u00e0 la personne concern\u00e9e de vous montrer son badge pour v\u00e9rifier le tutoriel auquel il s'est enregistr\u00e9 pour le m\u00eame cr\u00e9neau horaire.\r\n\r\n    - Demandez \u00e0 la personne concern\u00e9e de pr\u00e9venir l'autre enseignant qu'il n'assistera pas au tutoriel.\r\n\r\n    - Ajoutez son num\u00e9ro de badge, son nom et le tutoriel originellement suivi sur la liste.\r\n\r\n    - Ne lui donnez pas de polycopi\u00e9 (si le tutoriel en poss\u00e8de).\r\n\r\n    - S'il offre de rester debout ou de s'assoir par terre, vous pouvez soit refuser car cela att\u00e9nue l'exp\u00e9rience des autres participants, et les diriger vers le coordinateur du tutoriel au bureau d'enregistrement pour en discuter, soit dire que vous n'\u00eates pas s\u00fbr et rediriger la personne vers le bureau de pr\u00e9sentation o\u00f9 il pourra faire sa demande.\r\n\r\n    - Usez votre jugement. Les r\u00e8gles ci-dessus sont l\u00e0 pour \u00e9viter les probl\u00e8mes et maximiser la qualit\u00e9 des tutoriaux pour tout le monde, mais en priorit\u00e9 pour ceux s'\u00e9tant pr\u00e9alablement enregistr\u00e9 et non pas ceux voulant changer. Si les r\u00e8gles ne le permettent pas, passez outre.\r\n\r\n- Si quelqu'un n'est pas coop\u00e9ratif, demandez \u00e0 un assistant d'enseignement ou \u00e0 l'enseignant de l'aide ou aller directement au bureau de pr\u00e9sentation demander de l'aide.\r\n", 
        "created": "2012-07-08T23:39:58.832", 
        "publish_date": "2012-07-08T23:39:58", 
        "path": "community/volunteer/tutorial_hosts/"
    }
},
{
    "pk": 46, 
    "model": "cms.page", 
    "fields": {
        "body": "_[General installation help][]: 6:30-8:00PM Tuesday & Wednesday in Open Spaces._\r\n[General installation help]: /2013/about/volunteers/welcome\r\n\r\nIf you want to help others prepare for their Tutorial Installations at PyCon, here are some basic guidelines.\r\n\r\n### **Assume no network**\r\n\r\nAssume there may not be any network available.\r\n\r\n### **Use virtualenv**\r\n\r\nNormally, you want to setup using _virtualenv_ (assume people will take more than one tutorial), however there are some packages that will not install easily under virtualenv (pygame, for example; potentially some other packages which require your compilation environment and dependencies).  If you're going to use virutalenv, it would look something like this for example:\r\n\r\n        mkdir -p PyCon2013/tutorials/django\r\n        cd PyCon2013/tutorials/django\r\n        virtualenv --no-site-packages Vdjango\r\n\r\n<br/>\r\nSince virtualenv typically modifies the shell prompt to show which environment your operating under, pick a meaningful name.  I typically start all v-env's with \"V\" or \"E\"  (so they show together in a directory listing).\r\n\r\nPeople may want to add this to their bash login script:\r\n\r\n        activate() # for python virtualenv\r\n        {\r\n            source \"$*\"/bin/activate\r\n        }\r\n\r\n<br/>\r\nIt may help newcomers, as it makes the idioms for virtualenv a little more symmetrical and thus easier to remember, e.g.:\r\n\r\n         mkvirtualenv Vsomename\r\n         activate Vsomename\r\n         ... do stuff ...\r\n         deactivate\r\n\r\n<br/>\r\nOnce your virtualenv is activated, you can begin installing into it.\r\n\r\n\r\n### **Install from USB**\r\n\r\nPrepare your packages for USB Install (not from the network):\r\n\r\n        MY_USB = /path/to/usb\r\n        pip install -d $MY_USB/pkgs -r requirements.txt\r\n\r\n<br/>\r\nInstall from your own USB:\r\n\r\n        pip install --find-links=file://$MY_USB/pkgs --no-index -r requirements.txt\r\n\r\n<br/>\r\nYou don't need to use a _requirements.txt_ file; you can simply load packages individually by name, if that is more convenient.\r\n\r\n### **Ubiquitous USB**\r\n\r\nWhen downloading binary packages, whenever possible save for 3 platforms on your USB (Linux, Mac, Win).\r\n\r\nSo that all the USBs floating around Tutorial Prep nights look the same, follow this pattern:\r\n\r\n- USB top level directory **pkgs** - for python packages\r\n- USB top level directory **lin**, **mac**, **win** - for platform specific archives\r\n- USB top level directory **requirements** - pip requirements files, by course (e.g.: requirements/django.txt)\r\n", 
        "status": 2, 
        "updated": "2013-10-10T11:50:06.609", 
        "title": "Notes for Tutorial Preparation", 
        "body_fr": "_[Aide g\u00e9n\u00e9rale pour l'installation][]: 6:30-8:00PM le mardi et le mercredi dans Open Spaces._\r\n[Aide g\u00e9n\u00e9rale pour l'installation]: /2013/about/volunteers/welcome\r\n\r\nSi vous voulez aider d'autres pr\u00e9sentateurs pour leur Instalion de tutoriel au PyCon, voici quelques lignes directrices.\r\n\r\n### **Supposez qu'il n'y ait pas de r\u00e9seau**\r\n\r\nSupposez qu'il puisse n'y avoir de r\u00e9seau disponible.\r\n\r\n### **Utilisez virtualenv**\r\n\r\nNormalement, il vaut mieux installer en utilisant _virtualenv_ (supposez que les gens vont suivre plus d'un tutoriel). Toutefois, il existe certains paquetages qui sont difficiles \u00e0 installer avec virtualenv (pygame, par exemple, et potentiellement d'autres paquetages qui requi\u00e8rent votre environnement et vos d\u00e9pendances de compilation). Voici un example de virtualenv:\r\n\r\n        mkdir -p PyCon2012/tutorials/django\r\n        cd PyCon2012/tutorials/django\r\n        virtualenv --no-site-packages Vdjango\r\n\r\n<br/>\r\nComme virtualenv modifie habituellement l'invite de commandes afin de montrer sous quel environnement vous \u00eates, choisissez un nom pertinent. D'habitude, je commence tous les v-env avec un V ou un E, afin qu'ils soit regroup\u00e9 dans une liste de r\u00e9pertoires.\r\n\r\nOn peut ajouter ceci au script de connexion bash:\r\n\r\n        activer() # pour le  virtualenv Python\r\n        {\r\n            source \"$*\"/bin/activate\r\n        }\r\n\r\n<br/>\r\n\u00c7a peut aider les d\u00e9butants, comme les raccourcis sont un peu plus sym\u00e9triques et ainsi, plus facile \u00e0 m\u00e9moriser, par exemple:\r\n\r\n         mkvirtualenv Vsomename\r\n         activer Vsomename\r\n         ... faire quelque chose ...\r\n         desactiver\r\n\r\n<br/>\r\nUne fois votre virtualenv activ\u00e9, vous pouvez commencer \u00e0 y installer des choses.\r\n\r\n### **Installer \u00e0 partir d'un port USB**\r\n\r\nPr\u00e9parez vos paquetages pour l'installation USB (et non \u00e0 partir d'un r\u00e9seau):\r\n\r\n        MY_USB = /path/to/usb\r\n        pip install -d $MY_USB/pkgs -r requirements.txt\r\n\r\n<br/>\r\nInstallez \u00e0 partir de votre propre port USB:\r\n\r\n        pip install --find-links=file://$MY_USB/pkgs --no-index -r requirements.txt\r\n\r\n<br/>\r\nIl n'est pas n\u00e9cessaire d'avoir recours \u00e0 un fichier _requirements.txt_. Dans le cas o\u00f9 c'est plus pratique, vous pouvez simplement charger vos paquetages individuellement par leurs noms.\r\n\r\n### **USB universel**\r\n\r\nLorsque vous t\u00e9l\u00e9chargez des paquetages binaires, sauvegardez, si possible, pour les 3 plateformes sur votre USB (Linux, Mac, Win).\r\n\r\nAfin que tous les USB des soir\u00e9es de pr\u00e9paration aux tutoriels soient identiques, suivez ce mod\u00e8le:\r\n\r\n- r\u00e9pertoire racine USB **pkgs** - pour les paquetages python\r\n- r\u00e9pertoire racine USB **lin**, **mac**, **win** - pour les archives sp\u00e9cifiques \u00e0 une plateforme\r\n- r\u00e9pertoire racine USB **requirements** - fichiers de sp\u00e9cifications pip, par cours (par exemple: requirements/django.txt)\r\n", 
        "created": "2012-07-09T00:12:43.973", 
        "publish_date": "2012-07-09T00:12:43", 
        "path": "community/welcome/usb/"
    }
},
{
    "pk": 47, 
    "model": "cms.page", 
    "fields": {
        "body": "##### _Back for another year in Santa Clara, PyCon 2013 is sure to sell out. Proposals for tutorials, talks, and posters are now being accepted._\r\n\r\n\r\n**Santa Clara, CA (PRWEB) July 09, 2012** -- Following the incredible successes of PyCon 2012, the PyCon organizers have been hard at work to introduce the [new PyCon 2013 website](https://us.pycon.org/2013/ \"PyCon website\"). After record breaking numbers in many areas, from attendance to talk proposals, this conference is already shaping up to be another blowout. Sponsors have been rolling in since March, and the organizers are interested in working with all organizations wanting to sponsor the 2013 conference.\r\n\r\nAs with 2012, PyCon will again be at the Santa Clara Convention Center in Santa Clara, California. The tutorials run on March 13 and 14, the main conference talks begin Friday March 15 and run through Sunday March 17, and the event wraps up with development sprinting through Thursday March 21.\r\n\r\nJust a short distance from the San Jos\u00e9 Airport, the conference center is in the perfect area for a week-long event showcasing the Python programming language. The new website brings back a well liked feature of last year\u2019s site, the [venue page](https://us.pycon.org/2013/venue/santa-clara/ \"Venue Page\"), listing restaurants, attractions, and other activities in the South Bay and surrounding areas. As Paul Graham said in his 2012 keynote, \u201cthis is the center of Silicon Valley,\u201d referring to Python\u2019s and PyCon\u2019s role in the future of technology.\r\n\r\nAttendance will be strictly limited to 2500 attendees, and the organizers look forward to opening ticket sales this fall. While they are exploring different ways to go about early bird pricing, conference chairman Jesse Noller mentions, \u201canyone wishing to attend the conference should begin any necessary preparations with their employer.\u201d As with the last several years, 2013 is sure to be a sell out so be ready.\r\n\r\nComing over a month earlier than last year\u2019s announcement, the organizers have opened their [Call for Proposals](https://us.pycon.org/2013/speaking/cfp/ \"Call for Proposals\") to present tutorials, talks, and posters at the 2013 conference. After receiving 519 proposals, a record for all three presentation categories, the program committee is expecting even more to roll in through the proposal deadline.\r\n\r\nFrom first timers to well traveled speakers, the program committee is asking for presentations from all levels of the community. Expanding diversity in all aspects of the conference schedule is a goal, from the speakers themselves to the topics and everything in between. All interested presenters should register and check the speaker section of the new site.\r\n\r\nThe organizers would like to especially thank all of the launch sponsors who show amazing dedication to PyCon.\r\n\r\nPyCon 2013\u2019s launch day sponsors include: [Heroku](http://www.heroku.com/ \"Heroku\"), [Walt Disney Animation Studios](http://www.disneyanimation.com/ \"Walt Disney Animation Studios\"), [RedHat](http://www.redhat.com/ \"RedHat\"), [Twilio](http://www.twilio.com/ \"Twilio\"), [Mailgun](https://mailgun.net/ \"Mailgun\"), [Continuum Analytics](http://continuum.io/ \"Continuum Analytics\"), [Counsyl](https://www.counsyl.com/ \"Consyl\"), [Milo](http://milo.com/ \"Milo\"), [Wingware](http://wingware.com/ \"Wingware\"), [devsAr](http://www.devsar.com/ \"DevsAr\"), [AWeber Communications](https://labs.aweber.com/ \"AWeber\"), [Stratasan](http://www.stratasan.com/ \"Stratasan\"), [LeapFrog Online](http://www.leapfrogonline.com/ \"LeapFrog Online\"), [PlaidCloud](http://help.plaidcloud.com/ \"PlaidCloud\"), [Linode](http://www.linode.com/ \"Linode\"), [Jetbrains](http://www.jetbrains.com/pycharm/ \"JetBrains\"), [WebCube CMS](http://www.webcubecms.com/ \"WebCube\"), [net-ng](http://www.net-ng.com/en \"net-ng\"), [Python Academy](http://www.python-academy.com/ \"Python Academy\"), [Thumbtack](http://www.thumbtack.com/ \"thumbtack\"), and [Raspberry Pi](http://www.raspberrypi.org/ \"Raspberry Pi\").\r\n\r\nWithout them, PyCon would not be what it is, and with many of them being repeat sponsors, they keep PyCon alive from year to year.\r\n\r\nFor more information about sponsoring PyCon 2013, see our [sponsor page](https://us.pycon.org/2013/sponsors/ \"Sponsor Page\") and contact [jnoller@python.org](mailto:jnoller@python.org \"Jesse Noller contact\").\r\n\r\n-----\r\n###### Originally published at [http://www.prweb.com/releases/PyCon/2013/prweb9675926.htm](http://www.prweb.com/releases/PyCon/2013/prweb9675926.htm \"PRWeb posting\")", 
        "status": 2, 
        "updated": "2012-07-09T11:45:40.250", 
        "title": "PyCon 2013 Launches, Calls for Proposals", 
        "body_fr": "", 
        "created": "2012-07-09T11:34:15.985", 
        "publish_date": "2012-07-09T11:34:15.985", 
        "path": "about/press/20120709_launch_release/"
    }
},
{
    "pk": 48, 
    "model": "cms.page", 
    "fields": {
        "body": "This guide details how the PyCon Program Committee operates. It's designed to be a working document for the PC itself to follow, and also for prospective PC members to get an idea of what being on the PC entails.\r\n\r\nThis is a living document; it describes the PyCon process as it is \"right now\"; it'll be updated continuously as our process grows and changes.\r\n\r\n**The program committee's mission is to craft the best possible program for PyCon out of the pool of proposals submitted.** It's a tough job: PyCon 2013 received roughly 600 proposals for only 110 slots. The committee tries to go beyond simple review: committee members interact with proposal authors and try to help them put forward the best possible proposals. Often the final form a talk takes is shaped by feedback, comments, and criticism from the committee.\r\n\r\nJoining the committee\r\n=====================\r\n\r\nCommittee membership is open to anyone - more voices, more diversity of viewpoints, make for a better conference. To join the program committee, sign up for the [pycon-pc mailing list][pycon-pc]. We use the mailing list to coordinate all the rest of our activities.\r\n\r\nCommittee membership is a time commitment. Expect to spend something approaching 4-8 hours per week, August through December, with the bulk of that work coming towards the end of November as the final selections are made. The bulk of the work involves reviewing proposals on the PyCon website (see initial review,\r\nbelow) and then later participating in IRC meetings (Kittendome and Thunderdome, below).\r\n\r\nCommittee structure, consensus, and voting\r\n==========================================\r\n\r\nThe committee's led by a chair and co-chair. In 2016, the chair is [Luke Sneeringer][luke]; the co-chair is\r\n[Alex Gaynor][alex].\r\n\r\nWhenever possible we strive to operate in a way drawn from the open source process that's worked so well for Python. That means that we'll try to find rough consensus where we can. This doesn't scale for review itself, so during the review process, we'll use voting and majority rule to select the bulk of the talks.\r\n\r\nUltimately, the responsibility for the program falls on the chair, so the chair has the final say. The chair is the Benevolent Dictator for the PyCon Program, if you will. However, the chair will try to use chair fiat as little as possible.\r\n\r\nThe review process\r\n==================\r\n\r\nAfter someone submits a talk proposal, it goes through three rounds of review:\r\n\r\n1. Initial review takes place on the website. The committee reviews each proposal, leaves feedback for the author, and votes on the proposal using an \"identify the champion\" system. We also meet occasionally on IRC to discuss talks and coordinate feedback to presenters.\r\n\r\n2. Once the call for proposals closes, IRC review begins. The first round, nicknamed \"kittendome\", reviews each talk in isolation, determining if the proposal would be a \"good talk\" for PyCon. Some talks will be rejected at this point; the rest will pass on to\u2026\r\n\r\n3. The second round, nicknamed \"Thunderdome\". The remaining talks (typically about half of the proposals) will be grouped by topic into groups of 3-5. During Thunderdome, we'll discuss one group at a time, and select the best talk(s) from each group.\r\n\r\nWhen Thunderdome completes, we'll have the list of selected talks. Authors will be notified of acceptance or rejection, the selected talks will be published, and the conference schedule will be written.\r\n\r\n2016 Timeline\r\n-------------\r\n\r\nThis is a rough idea of the schedule we're looking at:\r\n\r\n* Website reviews: July 1, 2013 \u2013 September 15, 2013\r\n* Kittendome meetings: August 15, 2013 \u2013 November 1, 2013\r\n* Thunderdome meetings: November 4, 2013 \u2013 November 20, 2013\r\n* Talk list published: December 1, 2013\r\n* Schedule published: December 15, 2013\r\n\r\nInitial review\r\n--------------\r\n\r\nOnce talks start to roll in, we'll review them using tools on the website. This happens concurrently with the CFP - we don't wait for the call to close to start this work. The committee has two goals here:\r\n\r\n1. Give feedback to authors and help them improve their proposals (authors can\r\n   edit proposals up until the CfP closes).\r\n\r\n2. Get an initial set of votes from as many committee members as possible. This\r\n   will inform the later meetings.\r\n\r\nWe try to make sure that each talk gets reviewed by at least 3 committee\r\nmembers (and ideally more).\r\n\r\n### Voting\r\n\r\nThe process we use to assess proposals is based on the [Identify the\r\nChampion](http://scg.unibe.ch/download/champion/) process. The idea is to to\r\nassess each talk and identify \"champions\" and/or \"anti-champions\" -- people who\r\nwill argue strongly for or strongly against a talk in initial review.\r\n\r\nThe document linked above uses an \"A/B/C/D\" scale for reviewing; we use the\r\nsame idea, but use \"+1/+0/-0/-1\" labels (after the Apache voting system).\r\nThese votes mean:\r\n\r\n* **+1** -- I will champion the talk at the program committee meeting.  The\r\n  topic sounds good and the proposal is solid. This vote means you're willing\r\n  to put your reputation on the line in favor of the proposal and its author,\r\n  and that you believe PyCon would be worse off for *not* having the talk.\r\n\r\n* **+0** -- This topic is good and the proposal is solid. The speaker is\r\n  capable of correcting any deficiencies, and I think a significant number of\r\n  PyCon attendees would want it available. I don't feel strongly enough about\r\n  it to serve as its champion at the program committee meeting.\r\n\r\n* **-0** -- I am not in favor of this talk as proposed. The talk, the topic,\r\n  or the proposal has problems that concern me.  I'd rather see it not\r\n  accepted.\r\n\r\n* **-1** -- This talk or its proposal has significant problems. I believe that\r\n  PyCon would be worse off for having it, so I will argue strongly to reject\r\n  this talk.\r\n\r\nIf you don't know enough about a topic to judge a proposal's coverage of it, or\r\nit's a topic you tend to actively avoid, you should not recuse yourself from\r\nvoting on that basis alone. You can still judge the structure of the proposal,\r\nthe likelihood that the speaker can cover the material proposed in the time\r\nallotted, whether the topic is likely to appear to others, etc.\r\n\r\n### Criteria for evaluating talks\r\n\r\nIt's hard to come up with an objective set of criteria for evaluating a talk.\r\nUltimately, scoring talks is a subjective endeavor; we're all trying to select\r\nwhat we think are the \"best\" talks for the conference. We don't expect everyone\r\nto use the same set of criteria, but some valuable questions you might ask\r\nyourself as you review are:\r\n\r\n* Would *I* go to see this talk?\r\n* Are there a significant group of likely attendees that would want to see this talk?\r\n* Does the proposal seem well-thought-out?\r\n* Does it seem like the author knows enough about the topic?\r\n* Is the proposal too ambitious (or too paltry) for the time allotted?\r\n\r\n### \"Obvious\" accepted/rejected talks\r\n\r\nAfter the initial review, there will be a small set of talks that are \"obviously\r\ngood\" or \"obviously bad\". We'll set a threshold, by committee consensus, for\r\ntalks that are automatically rejected or get to automatically skip ahead to\r\nThunderdome. This is usually something like \"reject all talks with 3 or more -1s\r\nand no +0s or better\" or \"accept all talks with at least 4 +1s and no -1s\".\r\n\r\nThese accepted talks aren't a free pass to PyCon - it just means that the talk\r\ngoes directly to Thunderdome. A reject *is* final, however; it weeds out the\r\nfew obviously-bad proposals that nobody on the PC wants to support.\r\n\r\nIRC Meetings\r\n------------\r\n\r\nNext, we hold meetings in IRC. (The committee chairs can help any committee\r\nmembers who aren't familiar with IRC.) Meetings run for an hour, and are usually\r\nscheduled a week or two in advance.\r\n\r\nProgram Committee meetings are held in IRC on Freenode. If you're not familiar\r\nwith IRC, ask Luke or Alex and we can help you get set up.\r\n\r\nWe'll announce each meeting's itinerary in advance on the PC list, including the\r\nlist of talks to be covered.\r\n\r\nKittendome\r\n----------\r\n\r\nIn the first round of meetings, we go through each proposal individually. The\r\nhere is simple to determine if a given talk -- reviewed in isolation -- is\r\npotentially good enough for PyCon. That is, in the first round we review talks\r\nstrictly on their merits and avoid holding them up against similar talks\r\n(we do that next, in Thunderdome_).\r\n\r\nWe'll review talks, one at a time. We'll give a couple minutes for the champion\r\n(identified by the website votes) to make an argument for the talk. Then,\r\na few minutes of general debate. Finally, we'll vote yay/nay on each talk.\r\nMajority rules - a majority of \"yay\" votes will indicate that the talk is\r\n**accepted** -- it moves onto Thunderdome. A majority of \"nay\" votes indicates\r\nthat the talk is **rejected** -- it's out. The chair will break ties.\r\n\r\n### Meeting format\r\n\r\nMeetings will be in IRC; we use an IRC 'bot to keep us on track. A Kittendome\r\nmeeting will look like this:\r\n\r\nFirst, the bot will announce the talk is under consideration (note that\r\nthe format has changed slightly since 2012, but the principle remains the\r\nsame):\r\n\r\n    <pycon_bot> === Talk 456: Monitoring parrot liveliness - http://us.pycon.org/2012/review/456/ ===\r\n    <pycon_bot> (http://us.pycon.org/2012/review/123/ will be next)\r\n    <pycon_bot> If you are (a/the) champion for #456, or willing to champion it,\r\n                please type a succinct argument for inclusion of this talk. (2 Minutes).\r\n                Say 'done' when you are finished.\r\n\r\nA champion \u2016 usually someone who's given the talk a \"+1\" on the website -- then\r\nhas 2 minutes to give a succinct argument for the talk. Many champions prepare\r\nthese summaries in advance (the schedule goes out a day or two prior to the\r\nmeeting):\r\n\r\n    <champion> Love the approach. Very clear what the talk will accomplish, and\r\n               how, and in a valuable topic. done.\r\n\r\nThe bot then announces general debate:\r\n\r\n    <pycon_bot> === General Debate (3 minutes) for Talk: #456 ===\r\n\r\nMembers debate, and anything goes at this point (but please see the meeting\r\nguidlines below).\r\n\r\nOnce debate concludes, it's voting time:\r\n\r\n    <pycon_bot> === Voting time! yay/nay votes for talk #24 ===\r\n    <pycon_bot> Please do not speak after voting until we've gotten our report.\r\n    <champion> yay\r\n    <otherperson> nay\r\n    <someoneelse> yay\r\n\r\nAfter a short voting period, the bot summarizes the results:\r\n\r\n    <pycon_bot> === Talk Votes on #456: 3 yays, 10 nays, 0 abstentions ===\r\n    <pycon_bot> The nays have it.\r\n\r\nThe bot records the final decision. Rinse and repeat.\r\n\r\nThunderdome\r\n-----------\r\n\r\nAfter round one has ended, we're left with a set of talks that are all \"good\r\nenough\" for PyCon. Unfortunately, this'll typically be more than double the\r\nnumber of talks we can actually accept, so we pit similar talks head-to-head\r\nand try to select the best.\r\n\r\nIn each \"round\" of Thunderdome we review 3-5 talks, roughly grouped by\r\ntheme/content/topic/etc. Out of each group we'll get one or more **winners**,\r\npossibly some **damaged** talks, and some talks that are **out**. We'll do this\r\nby discussing, and then the committee will vote for the talks they like.\r\nMembers may vote for any number of talks (including none or all of them).\r\n\r\nThe **winners** are the talks from the group that absolutely should be at\r\nPyCon. It advances and is safe from future cuts. It's on the program! There\r\ndoesn't have to be a winner from each group, but there probably should be. The\r\nwinners are any talks that have a 75% supermajority.\r\n\r\n**Damaged** talks are ones that have been hurt by Thunderdome but aren't quite\r\nout of the running yet. They'll be put into the damaged pool and if at the end\r\nwe've still got spaces left we'll fill those spaces from the damaged pool. There\r\nmay not be any damaged talks in a given group, or all talks may end up damaged.\r\nDamaged talks are are any talks that didn't win, but did receive votes from at\r\nleast 50% of the committee.\r\n\r\nTalks are selected by fewer than 50% of the committee in attendance are **out**\r\n\u2013 they will not appear at PyCon.\r\n\r\nThe result of Thunderdome will be the ~100 talks that'll appear on the PyCon\r\nprogram.\r\n\r\n### Thunderdome process\r\n\r\nLike the first round we'll use a bot to keep us on track.\r\n\r\nThe bot will announce each group:\r\n\r\n    <pycon_bot> === Thunderdome for \u201cBirds of a feather\u201d begins now! ===\r\n    <pycon_bot> Talk #123: Modelling flight patterns of swallows\r\n    <pycon_bot> Talk #456: Monitoring parrot liveliness\r\n    <pycon_bot> Talk #789: SciPy for aerodynamics engineers\r\n    <pycon_bot> You now have 2 minutes to review these talks and collect\r\n        your thoughts prior to debate. Please refrain from speaking until\r\n        debate begins.\r\n\r\nMembers will have 2 minutes to read talk descriptions, collect their thoughts,\r\nand formulate arguments; please try to stay silent during this time so everyone\r\ncan think.\r\n\r\nThe bot will then announce 5 minutes of open debate:\r\n\r\n    <pycon_bot> === General debate (5 min) for \u201cBirds of a feather\u201d ===\r\n\r\nMembers debate, and anything goes at this point (but please see the meeting\r\nguidlines below).\r\n\r\nThen we vote! Vote for as many talks as you like, but please keep in mind the\r\nvery limited number of spots. Voting will look like this:\r\n\r\n    <pycon_bot> === Voting time! ===\r\n    <pycon_bot> Enter your vote in the form \u201c123, 456, 789\u201d. You may vote for as many talks as you like, but please keep in mind the limited number of available slots.\r\n    <jacob> 123, 456\r\n    <jesse> 456\r\n    <tim> 456\r\n    \u2026\r\n\r\nThe bot will tally the scores, telling us the results:\r\n\r\n    <pycon_bot> === Results ===\r\n    <pycon_bot> WINNER - Talk #456: 9 votes (90%)\r\n    <pycon_bot> DAMAGED - Talk #123: 5 votes (50%)\r\n    <pycon_bot> OUT - Talk #789: 3 votes (30%)\r\n\r\nRemember there may be no winner, and there may be any number of damaged talks.\r\n\r\nFinally, the chair will record the talks as in, damaged, or out, based on the\r\nvoting.\r\n\r\nMeeting guidelines\r\n------------------\r\n\r\nTo keep things moving smoothly and quickly, please try to follow these guidelines\r\nduring all IRC meetings:\r\n\r\n* The chair will send an agenda for each meeting to the mailing list in advance.\r\n  This'll list all the talks we plan to discuss. If you're a champion for\r\n  one of the talks up for that meeting, please try extra-hard to make it\r\n  to the meeting! Otherwise we'll have to \"channel\" you based on what you\r\n  wrote on the website, and that won't do your voice justice.\r\n\r\n* Please use the time before each meeting to refresh your memory on the talks\r\n  for each meeting; you'll only have  a short period of time during the meeting\r\n  to read each talk. Please come prepared.\r\n\r\n* Please stay on topic. We have a lot to do, and not much time to do it. Please\r\n  direct any unrelated chatter to private chat, other chat rooms, or the mailing\r\n  list.\r\n\r\n* For Kittendome, focus only on the talk itself, not on other talks. If there's\r\n  another, better talk on the same topic try to ignore it; we'll sort it out in\r\n  Thunderdome. In this round, just deal with each talk on its (de-)merits.\r\n\r\n* In Thunderdome, focus on the talks in each group, and not on other groups,\r\n  other talks that didn't make it to Thunderdome, talks you wish had been\r\n  submitted, etc. It's impossible to evaluate every talk against every other\r\n  talk, so we have to work in groups.\r\n\r\n* Disclose bias if it exists. If the speaker is a friend, colleague, coworker,\r\n  competitor or nemesis that's completely okay, but tell the group. If you wrote\r\n  a piece of software covered by a talk, say so. Bias, in and of itself,\r\n  isn't really an issue -- we have a big enough pool of reviewers that it'll\r\n  balance out. But if you are biased, tell us so that we know where your\r\n  review is coming from.\r\n\r\n* No talks will be tabled once the meeting begins. Thus, if you feel strongly\r\n  about a group, topic, or talk then make a special effort to come to the\r\n  meeting! If you absolutely can't make it, email the chair and a talk can be\r\n  moved to a different meeting, but please let the chair know well in advance.\r\n\r\n* Generally, debate will not be extended. Again, we have too much to get through\r\n  to spend extra time. However, if there's a particular contentious debate,\r\n  the chair may choose to extend debate, so ask the chair if you think the group\r\n  deserves extra time.\r\n\r\n* The chair gets the final call. Most of the time the votes will identify a\r\n  clear winner, and the chair should follow the votes 99% of the time. However,\r\n  if there's a tie, or if votes are really close, or if the voting is otherwise\r\n  not quite clear, the chair gets to make a judgement call. This should\r\n  happen rarely, but it will happen.\r\n\r\n* Decisions are final. Once a decision has been made, discussion should end and\r\n  we'll move on. If you feel a decision was made in error, bring it up on the\r\n  mailing list or via private email to the chair.\r\n\r\n* If a talk under discussion has been submitted by you, you'll need to recuse\r\n  yourself. Do this by leaving the chat room; the chair will invite you back\r\n  when discussion is over.\r\n\r\n_(last updated: June 24, 2013)_\r\n\r\n  [pycon-pc]: http://mail.python.org/mailman/listinfo/pycon-pc\r\n  [luke]: mailto:luke@sneeringer.com\r\n  [alex]: mailto:alex.gaynor@gmail.com", 
        "status": 2, 
        "updated": "2013-06-24T14:15:44.259", 
        "title": "Program Committee Guide",
        "body_fr": "", 
        "created": "2012-07-10T15:06:41.398", 
        "publish_date": "2012-07-10T15:06:41", 
        "path": "pc/guide/"
    }
},
{
    "pk": 49, 
    "model": "cms.page", 
    "fields": {
        "body": "- [Program Committee Guide](guide/)", 
        "status": 2, 
        "updated": "2012-07-10T15:09:49.826", 
        "title": "Program Committee Stuff", 
        "body_fr": "", 
        "created": "2012-07-10T15:09:49.824", 
        "publish_date": "2012-07-10T15:09:49.824", 
        "path": "pc/"
    }
},
{
    "pk": 50, 
    "model": "cms.page", 
    "fields": {
        "body": "As we round up the volunteers, activate the mailing lists, and get the community hyped up for another year of PyCon, there\u2019s another group we need to engage: [the sponsors](https://us.pycon.org/2016/sponsors/ \"Sponsor List\"). PyCon 2013 had an amazing outpouring of support from [a record 160 sponsors](https://us.pycon.org/2013/sponsors/ \"2013 Sponsors\"), and with your help, we\u2019re trying make 2016 another record breaker.\r\n\r\nSponsors are what make this conference possible. From low ticket prices to financial aid to video recording, the organizations who step forward to support PyCon in turn support the entire Python community. They make it possible for so many to attend, for so many to present, and for the world at home to watch along.\r\n\r\nAlong with the benefits sponsorship gives the conference and the community, we think they come in exchange for an excellent set of benefits to our sponsors. See our full prospectus at [https://us.pycon.org/2016/sponsors/prospectus/](https://us.pycon.org/2016/sponsors/prospectus/ \"Prospectus\").\r\n\r\nRecruiting\r\n----------\r\nWhat better place to find Python developers than a gathering of 2000 of them? If you\u2019re hiring, PyCon is the place to be.\r\n\r\nThe conference has long been a great way to find the talented developers so many companies are searching for, so much that we added on-site Job Fair to make it even easier. Some sponsors even host their own recruiting events! In 2012 alone, we had sponsors participating in the job fair that they received over _one hundred_ resumes in under an hour!\r\n\r\nMarketing\r\n---------\r\nGetting your name and product out there through the promotional aspects of our sponsorship packages is a great competitive advantage. If your business is built on Python, you can get the attendees' attention with our banner and print advertising options. Having a booth in our Expo Hall will allow you to reach out and get more face time with the community.\r\n\r\nGiven PyCon\u2019s size and importance in the yearly conference calendar, people look to the sponsors to see who is using and supporting Python. These are the organizations that attendees want to buy from and work for!\r\n\r\nVisibility\r\n----------\r\nOur expo hall is _the_ place to be seen. Many organizations do product demos, hand out coupons and t-shirts, and engage their visitors by talking tech and sharing their experiences with Python. Some companies like to use their booth to interview PyCon\u2019s talented attendees right then and there.\r\n\r\nThe expo hall is centrally located and gets a lot of traffic throughout the day, and for 2016 we've made changes to ensure even more visibility. We even heard from several sponsors that VCs and angel investors frequented the expo hall as well as our Startup Row!\r\n\r\nAudience\r\n--------\r\nPyCon\u2019s ever diversifying audience puts your organization in front of a wide variety of people. From beginners to experts, PyCon draws attendees from those with zero experience all the way through a significant group of the contributors to the language itself. We also see people of all levels from many industries. From developers to managers, executives to owners, startups to big businesses, PyCon draws attendees from all sorts of places. Some organizations send entire teams, and in the case of many startups, the entire company may be there.\r\n\r\nCompetitive Pricing\r\n-------------------\r\nWhen you consider the cost of conference passes that all packages include, we think we\u2019ve put together a great value in each PyCon sponsorship package. Our smallest package, the Silver level at $4000, includes two passes valued at $1200! The Gold level includes five passes, a $3000 value. Each successive package includes more tickets. Keep in mind that these are full conference passes -- not just expo hall passes.\r\nPersonnel who will only be staffing booths do not get charged for passes to the conference - passes for employees staffing booths are complimentary and do not count against the attendee registration cap.\r\n\r\nSmall Business Discount\r\n-----------------------\r\nPyCon loves small businesses. From our long-time small business sponsors to up-and-coming startups, we want to make sponsorship work for you. For Gold sponsorships and below, we give a 50% discount for any organization under 25 people. When you factor in the cost of tickets, that deal gets even sweeter!\r\n\r\nFlexibility\r\n-----------\r\nIf you want to help PyCon, we want to help you construct a sponsorship package that fits your needs. If a small booth would work better than a large one, perhaps we can swap it in exchange for a larger program advertisement. For some organizations, a booth is not practical at all, but adding another conference pass may work better.\r\n\r\n----\r\nIf you are interested in sponsoring PyCon, please contact our Sponsorship Chair, Jesse Noller, at [jnoller@python.org](mailto:jnoller@python.org \"\").", 
        "status": 2, 
        "updated": "2013-10-07T19:23:35.938", 
        "title": "Why become a PyCon sponsor?", 
        "body_fr": "", 
        "created": "2012-07-23T10:13:40.353", 
        "publish_date": "2012-07-23T10:13:40.353", 
        "path": "sponsors/whysponsor/"
    }
},
{
    "pk": 51, 
    "model": "cms.page", 
    "fields": {
        "body": "Coming soon!", 
        "status": 2, 
        "updated": "2013-06-26T23:41:34.382", 
        "title": "The Young Coder: Let's Learn Python", 
        "body_fr": "", 
        "created": "2012-07-26T10:12:21.099", 
        "publish_date": "2012-07-26T10:12:21.099", 
        "path": "events/letslearnpython/"
    }
},
{
    "pk": 52, 
    "model": "cms.page", 
    "fields": {
        "body": "## John Perry Barlow\r\n\r\n<div style=\"float: left; margin-right: 30px\">\r\n<img src=\"http://i.imgur.com/0hd19wf.png\" width=\"150\" />\r\n<br />\r\n<br />\r\n<div align=\"center\"><strong>EFF Co-founder</strong></div>\r\n<br />\r\n</div>\r\n\r\n<a href=\"https://twitter.com/JPBarlow\">John Perry Barlow</a> was, for several decades, a Wyoming rancher and a songwriter for the <a href=\"http://www.dead.net/band\">Grateful Dead</a>. He co-founded the <a href=\"https://www.eff.org/\">Electronic Frontier Foundation</a>, an organization that has been protecting the free flow of information on the Internet since 1990. He remains actively engaged in running that organization. He has been writing about society in Cyberspace since 1988 and was first to apply that name to the global social space it presently describes. In 2013, he was inducted into the Internet Hall of Fame. He was a founding Fellow at Harvard Law School's Berkman Center for Internet and Society and recently created the Freedom of the Press Foundation with Daniel Ellsberg to fund WikiLeaks and other conduits of transparency journalism. In 2013, He was inducted into the <a href=\"http://www.internethalloffame.org/inductees/john-perry-barlow\">Internet Hall of Fame</a>, his second Hall of Fame induction after Rock and Roll. His startup company <a href=\"http://algaesystems.com/\">Algae Systems</a>, is presently building a plant in Alabama to turn sewage into carbon negative jet fuel. He is the father of three daughters and his primary aspiration is to be a good ancestor.\r\n\r\n------------------------------------------------\r\n\r\n\r\n## Guido van Rossum\r\n\r\n<div style=\"float: left; margin-right: 30px\">\r\n<img src=\"https://us.pycon.org/2013/site_media/media/images/2012/08/15/guido_avatar_big2_1.jpg\" width=\"150\" />\r\n<br />\r\n<br />\r\n<div align=\"center\"><strong>Python's Creator</strong></div>\r\n<br />\r\n</div>\r\n\r\n<a href=\"https://twitter.com/gvanrossum\">Guido van Rossum</a> is the author of the Python programming language. He continues to serve as the \"Benevolent Dictator For Life\" (BDFL), meaning that he continues to oversee the Python development process, making decisions where necessary. He is currently employed by <a href=\"https://www.dropbox.com/\">Dropbox</a>.\r\n\r\n<br />\r\n<br />\r\n<br />\r\n<br />\r\n<br />\r\n\r\n------------------------------------------------\r\n\r\n## Jessica McKellar\r\n\r\n<div style=\"float: left; margin-right: 30px\">\r\n<img src=\"http://i.imgur.com/esEocC2.png\" width=\"150\" />\r\n<br />\r\n<br />\r\n<div align=\"center\"><strong>Python Outreach</strong></div>\r\n<br />\r\n</div>\r\n\r\n<a href=\"https://twitter.com/jessicamckellar\">Jessica McKellar</a> is an entrepreneur, software engineer, and open source developer from Cambridge, MA. She is a Python Software Foundation board member and an organizer for the <a href=\"http://bostonpython.com/\">largest Python user group in the world</a>. With that group she runs the <a href=\"http://bostonpythonworkshop.com/\">Boston Python Workshop</a> -- an introductory programming pipeline that has brought hundreds of women into the local Python community and is being replicated in cities across the US. Jessica is a veteran open source contributor and a maintainer for several open source projects, including OpenHatch and the Twisted event-driven networking engine; she wrote a <a href=\"http://www.aosabook.org/en/twisted.html\">chapter on Twisted</a> for The <a href=\"http://aosabook.org/en/index.html\">Architecture of Open Source Applications</a> Volume II and the second edition of O'Reilly's Twisted Networking Essentials.\r\n\r\n<br />\r\n<br />\r\n<br />\r\n\r\n------------------------------------------------\r\n\r\n\r\n## Fernando P\u00e9rez\r\n\r\n<div style=\"float: left; margin-right: 30px\">\r\n<img src=\"http://i.imgur.com/lHJkt5E.jpg\" width=\"150\" />\r\n<br />\r\n<br />\r\n<div align=\"center\"><strong>IPython  Creator</strong></div>\r\n<br />\r\n</div>\r\n\r\n<a href=\"https://twitter.com/fperez_org\">Fernando P\u00e9rez</a> is a research scientist at UC Berkeley, working at the intersection of brain imaging and open tools for scientific computing.  He created <a href=\"http://ipython.org/\">IPython</a> while a PhD student in Physics at the University of Colorado in Boulder.  Today, with all the hard work done by a talented team, he continues to lead IPython's development as the interface between the humans at the keyboard and the bits in the machine. Fernando P\u00e9rez is a founding member of <a href=\"http://numfocus.org/\">NumFOCUS</a>, a PSF member, and received the 2012 FSF Award for the Advancement of Free Software for IPython and contributions to scientific Python.\r\n\r\n<br />\r\n<br />\r\n\r\n------------------------------------------------\r\n\r\n## Van Lindberg\r\n\r\n<div style=\"float: left; margin-right: 30px\">\r\n<img src=\"http://i.imgur.com/q8fAybp.png\" width=\"150\" />\r\n<br />\r\n<br />\r\n<div align=\"center\"><strong>PSF Chair</strong></div>\r\n<br />\r\n</div>\r\n\r\n<a href=\"https://twitter.com/VanL\">Van Lindberg</a> is Vice President of Intellectual Property at Rackspace. He is trained as a computer engineer and lawyer, but what he does best is \u201ctranslate\u201d to help businesses, techies and attorneys understand each other. Van likes working with both computer code and legal code. For the past several years, he has been using natural language processing and graph theory to help him digest and map the U.S. Patent Database.  Van is currently chairman of the board of the <a href=\"http://python.org/psf/\">Python Software Foundation</a>, as well as the author of <a href=\"http://shop.oreilly.com/product/9780596517960.do\">Intellectual Property and Open Source</a>.\t  \r\n\r\n<br />\r\n<br />\r\n\r\n------------------------------------------------", 
        "status": 2, 
        "updated": "2013-10-11T22:15:32.169", 
        "title": "PyCon 2016 Keynote Speakers", 
        "body_fr": "", 
        "created": "2012-07-27T10:12:06.247", 
        "publish_date": "2012-07-27T10:12:06", 
        "path": "events/keynotes/"
    }
},
{
    "pk": 53, 
    "model": "cms.page", 
    "fields": {
        "body": "We've provided a sample proposal to help you get some ideas on how to structure your own proposals. It's not perfect, but we wrote it that way. At the end of the proposal is a review and summary showing what's good about the proposal, as well as what parts need work.\r\n\r\n* The [SpacePug](https://us.pycon.org/2016/speaking/proposal_advice/samples/SpacePug/ \"SpacePug\") proposal", 
        "status": 2, 
        "updated": "2013-07-01T00:47:27.256", 
        "title": "Sample Proposals", 
        "body_fr": "", 
        "created": "2012-08-27T23:50:28.640", 
        "publish_date": "2012-08-27T23:50:28.640", 
        "path": "speaking/proposal_advice/samples/"
    }
},
{
    "pk": 54, 
    "model": "cms.page", 
    "fields": {
        "body": "Here's a sample talk proposal for a fictional project called SpacePug\r\n\r\nTITLE: SpacePug: How Python 3 Launched The First Pug In Space\r\n\r\nCATEGORY: Industry Uses\r\n\r\nAUDIENCE LEVEL: Intermediate\r\n\r\nDURATION: I prefer a 30 minute slot\r\n\r\nBRIEF OUTLINE: When the Soviets launched Laika the dog into space in 1957, the first question on many minds was, \u201cbut when will a pug be in space?\u201d That time is now thanks to the Animal Aeronautics and Space Administration\u2019s latest multi-bazillion bitcoin project, SpacePug.\r\n\r\nAll of SpacePug\u2019s systems run on Python 3, and this talk aims to explain the choice for 3, the introduction of a new library, and detailed discussion of a new test runner. Complete with a live demo, you\u2019ll get to see what goes into sending the crew of three - officers Buster and Tobias, lead by Captain Barry Zuckerkorn - into space.\r\n\r\nDETAILED ABSTRACT: \r\n\r\nBuilt entirely on Python 3, the SpacePug project is one of the first major projects to run on Python 3, and it\u2019s the first to launch pugs into orbit.\r\n\r\n* Why Python 3?\r\n\r\nYears ago, developers made an attempt to build a system on Python 2, but they found that it just wasn\u2019t good enough to launch a dog into space, let alone a pug. One of the first problems they encountered was the GIL and the fact that the thrust controllers didn\u2019t perform well enough to launch a dog of short, stocky stature. After switching to Python 3.2, which has an improved implementation of the GIL, the thrust controller performed so much better that analysis shows pugs could potentially join the Curiosity rover on the surface of Mars.\r\n\r\nThe astropugs are able to communicate back to mission control via a special keyboard to speak their language, represented in a previously unassigned Unicode plane. While developing the communications systems, the developers found that Python 3\u2019s distinction between bytes and text makes their code more readable and easier to understand. They prepared benchmarks comparing a Python 2.7 implementation against a Python 3.3 implementation to show the 3.3 version is more memory efficient thanks to PEP 393.\r\n\r\n* A new library: multipugging\r\n\r\nEarly versions of the project only supported one pug per spacecraft. Feeding and cleaning up after multiple pugs was a significant issue, so much that early testing sent the engineers back to the drawing board to start from scratch. In comes multipugging, a system to control multiple feeders and cleaners, removing the common bottleneck of dealing with the needs of multiple pugs in orbit.\r\n\r\nThis talk will show a live demo of multipugging scaling out to feed 16 pugs at once.\r\n\r\n* A new test runner: treadmill\r\n\r\nEveryone knows the first thing a project should do is write their own test runner, so we did just that with treadmill. It\u2019s like putting a pug on a treadmill, but for code.\r\n\r\nADDITIONAL NOTES: SpacePug is entirely open source software. You can check out the source tree at rcs.aasa.gov/pugware\r\n\r\nThis would be my first time speaking at a conference like PyCon. I\u2019ve spoken at my local user group a few times and may have the opportunity to give a practice run to my local group. I have posted slides of past talks on my site at www.pypug.net/presentations.\r\n\r\nHere\u2019s what I\u2019m thinking for timing:\r\n\r\nIntro (5 min)\r\nWho am I?\r\nHistory of dogs in space\r\nExplain why pugs are awesome for space\r\nWhy Python 3? (10 min)\r\nGIL changes\r\nText/bytes distinction, PEP 393 improvements\r\nUnder active development (it\u2019s the future)\r\nmultipugging library (10 min)\r\nThe problem: single feeder and cleaner doesn\u2019t scale\r\nThe solution: distributed feeders and cleaners\r\nEach pug gets their own food in their own space, less fighting for food\r\nLive demo (4 min)\r\ntreadmill test runner (5 min)\r\nExplain why other solutions don\u2019t work and why we needed to write our own", 
        "status": 2, 
        "updated": "2012-08-27T23:52:18.601", 
        "title": "SpacePug", 
        "body_fr": "", 
        "created": "2012-08-27T23:52:18.598", 
        "publish_date": "2012-08-27T23:52:18.598", 
        "path": "speaking/proposal_advice/samples/SpacePig/"
    }
},
{
    "pk": 55, 
    "model": "cms.page", 
    "fields": {
        "body": "Here's a sample talk proposal for a fictional project called SpacePug by the Animal Aeronautics and Space Administration. They use Python for everything, and they put pugs into space. \r\n\r\nIt's a good proposal, but it's not perfect. It does some good things, and some bad things, and we'll let you know what could be done to improve it.\r\n\r\n#### TITLE\r\n\r\nSpacePug: How Python 3 Launched The First Pug In Space\r\n\r\n#### CATEGORY\r\n\r\nScience\r\n\r\n#### DURATION\r\n\r\nI prefer a 30 minute slot\r\n\r\n#### DESCRIPTION\r\n\r\nWhen the Soviets launched Laika the dog into space in 1957, the first question on many minds was, \u201cbut when will a pug be in space?\u201d That time is now thanks to the Animal Aeronautics and Space Administration\u2019s latest multi-bazillion bitcoin project, SpacePug.\r\n\r\nAll of SpacePug\u2019s systems run on Python 3, and this talk aims to explain the choice for 3, the introduction of a new library, and detailed discussion of a new test runner. Complete with a live demo, you\u2019ll get to see what goes into sending the crew of three - officers Buster and Tobias, lead by Captain Barry Zuckerkorn - into space.\r\n\r\n#### AUDIENCE\r\n\r\nDevelopers interested in moving to Python 3, those who may want to use\r\nthe \"multipugging\" library, and space cainine enthusiasts.\r\n\r\n#### PYTHON LEVEL\r\n\r\nIntermediate\r\n\r\n#### OBJECTIVES\r\n\r\nAttendees will learn tips on porting to Python 3, as well as how to leverage\r\nmultipugging to save development time when processing space dogs in parallel.\r\n\r\n#### DETAILED ABSTRACT\r\n\r\nBuilt entirely on Python 3, the SpacePug project is one of the first major\r\nprojects to run on Python 3, and it\u2019s the first to launch pugs into orbit.\r\n\r\n##### Why Python 3?\r\n\r\nYears ago, developers made an attempt to build a system on Python 2, but they found that it just wasn\u2019t good enough to launch a dog into space, let alone a pug. One of the first problems they encountered was the GIL and the fact that the thrust controllers didn\u2019t perform well enough to launch a dog of short, stocky stature. After switching to Python 3.2, which has an improved implementation of the GIL, the thrust controller performed so much better that analysis shows pugs could potentially join the Curiosity rover on the surface of Mars.\r\n\r\nThe astropugs are able to communicate back to mission control via a special keyboard to speak their language, represented in a previously unassigned Unicode plane. While developing the communications systems, the developers found that Python 3\u2019s distinction between bytes and text makes their code more readable and easier to understand. They prepared benchmarks comparing a Python 2.7 implementation against a Python 3.3 implementation to show the 3.3 version is more memory efficient thanks to PEP 393.\r\n\r\n##### A new library: multipugging\r\n\r\nEarly versions of the project only supported one pug per spacecraft. Feeding and cleaning up after multiple pugs was a significant issue, so much that early testing sent the engineers back to the drawing board to start from scratch. In comes multipugging, a system to control multiple feeders and cleaners, removing the common bottleneck of dealing with the needs of multiple pugs in orbit.\r\n\r\nThis talk will show a live demo of multipugging scaling out to feed 16 pugs at once.\r\n\r\n##### A new test runner: treadmill\r\n\r\nEveryone knows the first thing a project should do is write their own test runner, so we did just that with treadmill. It\u2019s like putting a pug on a treadmill, but for code.\r\n\r\n#### OUTLINE\r\n\r\n1. Intro (5 min)\r\n    1. Who am I?\r\n    2. History of dogs in space\r\n    3. Explain why pugs are awesome for space\r\n2. Why Python 3? (10 min)\r\n    1. GIL changes\r\n    2. Text/bytes distinction, PEP 393 improvements\r\n    3. Under active development (it\u2019s the future)\r\n3. multipugging library (10 min)\r\n    1. The problem: single feeder and cleaner doesn\u2019t scale\r\n    2. The solution: distributed feeders and cleaners\r\n    3. Each pug gets their own food in their own space, less fighting for food\r\n    4. Live demo (4 min)\r\n4. treadmill test runner (5 min)\r\n    1. Explain why other solutions don\u2019t work and why we needed to write our own\r\n\r\n#### ADDITIONAL NOTES\r\n\r\n  * SpacePug is entirely open source software. You can check out the source tree at rcs.aasa.gov/pugware\r\n\r\n  * This would be my first time speaking at a conference like PyCon. I\u2019ve spoken at my local user group a few times and may have the opportunity to give a practice run to my local group. I have posted slides of past talks on my site at www.pypug.net/presentations.\r\n\r\n#### ADDITIONAL REQUIREMENTS\r\n\r\nA 50 lb. bag of IAMS dog food.\r\n\r\n\r\n----\r\n\r\nReview\r\n------\r\n\r\n- Brief Outline: Not bad. It simply sells the topic and draws in the audience and sets up what's going to be covered.\r\n- Detailed Abstract:\r\n    - Why Python 3: Covers two big issues with explanation, includes benchmarks\r\nfor the Unicode stuff, knowledgeable of new features/PEPs. If done\r\nright, this could be good advocacy.\r\n    - multipugging: Live demos are _really_ hard to do well. They provided\r\ntime estimates in the additional notes and give 4 minutes for a demo.\r\nThat seems like a lot of time for a demo, especially if it bombs.\r\n    - Test runner: No detail at all. Since it's generally not needed to rewrite your own test runner, it would be nice to have some head's up of why they needed to go down this path.\r\n- Additional Information\r\n    - Nice that it's open source. Has a good take-home value in that attendees can look up the code later on and learn more.\r\n    - First-time speaker but they're not totally new, uploaded slides look\r\nalright for a quick local talk.\r\n    - Outline is nice to have, and it shows they don't plan to have time for questions at the end. Although it's optional, the common convention is 25 minutes talking time and 5 minutes for questions. May want to reach out to the speaker to gauge their thoughts.\r\n\r\n#### Summary\r\n\r\nThis proposal gives a good look at what's going to be presented. It gives the reviewers a good indication that the proposer has thought this out, has thought about timing, and seems to have a good grasp on what people might want to know about the project. It does leave some open questions.\r\n\r\nWhat's the backup plan for the live demo? If it falls apart, that's four minutes the audience might lose out on. Especially for a relatively inexperienced speaker, it would be nice to know what the backup plan is if the live demo starts to fall apart. In this silly proposal, consider the pugs as hardware. Many hardware related talks at PyCon have skipped the live demo and instead shown video, and they're some of the coolest talks we've seen. For example, see David Beazley's [SuperBoard talk](http://blip.tv/pycon-us-videos-2009-2010-2011/pycon-2011-using-python-3-to-build-a-cloud-computing-service-for-my-superboard-ii-4896844 \"SuperBoard\") in 2011 and Kurt Grandis' [squirrel-shooting computer vision talk](http://www.youtube.com/watch?v=QPgqfnKG_T4 \"Squirrel Shooting Talk\") in 2012.\r\n\r\nLeaving time for questions isn't a hard requirement, merely a convention, so it would be nice to hear from them that they acknowledge that they'd be foregoing the Q&A. Additionally, a reviewer would probably want to know more about the test runner section because it's light on details, especially when you put it side-by-side with the other sections.", 
        "status": 2, 
        "updated": "2013-07-08T12:06:19.353", 
        "title": "SpacePug", 
        "body_fr": "", 
        "created": "2012-08-28T00:06:28.249", 
        "publish_date": "2012-08-28T00:06:28", 
        "path": "speaking/proposal_advice/samples/SpacePug/"
    }
},
{
    "pk": 56, 
    "model": "cms.page", 
    "fields": {
        "body": "Markdown Guide\r\n==============\r\n\r\nThis should cover 99% of your PyCon Markdown needs.\r\n\r\nPro-tip: Make sure your submission looks good\r\n----------------------------------------------\r\n\r\nAlways add extra newlines/breaks between blocks and elements. The official documentation isn't clear on this issue, and not all parsers support the requirement of newlines/breaks between blocks. \r\n    \r\nBlockquotes\r\n-----------\r\n\r\nTo enclose a segment of text in blockquotes, one must prefix each written line\r\nwith a less-than sign. Don't forget to add a newline before creating a blockquote.\r\n\r\nMarkdown:\r\n\r\n    > ## Blockquoted header\r\n    >\r\n    > This is blockquoted text.\r\n    >\r\n    > This is a second paragraph within the blockquoted text.\r\n    \r\nOutput:\r\n\r\n    <blockquote>\r\n        <h2>Blockquoted header</h2>\r\n    \r\n        <p>This is blockquoted text.</p>\r\n\r\n        <p>This is a second paragraph within the blockquoted text.</p>\r\n\r\n    </blockquote>\r\n\r\nCode: Block\r\n-----------\r\n\r\nTo specify an entire block of pre-formatted code, indent every line of the block by 1 tab or 4 spaces. Ampersands and angle brackets will automatically be translated into HTML entities. Don't forget to add a newline before creating a code block.\r\n\r\nMarkdown:\r\n\r\n    If you want to mark something as code, indent it by 4 spaces.\r\n\r\n        <p>This has been indented 4 spaces.</p>\r\n\r\nOutput:\r\n\r\n    <p>If you want to mark something as code, indent it by 4 spaces.</p>\r\n    \r\n        &lt;p&gt;This has been indented 4 spaces.&lt;/p&gt;\r\n\r\nCode: Inline\r\n-------------\r\n\r\nInline code descriptions can be done via the use of the backtick quotes. Any ampersands and angle brackets will automatically be translated into HTML entities.\r\n\r\nMarkdown:\r\n\r\n    Markdown is a `<em>text-to-html</em>` conversion tool for writers.\r\n\r\nOutput:\r\n\r\n    <p>Markdown is a `&lt;em&gt;text-to-html&lt;/em&gt;` conversion tool for writers.</p>\r\n\r\n    \r\nEmphasis: Italics\r\n-----------------\r\n\r\nTo emphasize text wrap it with either a asterisk or underscore.\r\n\r\nMarkdown:\r\n\r\n    This is *emphasized* _text_.\r\n\r\nOutput:\r\n\r\n.. code-block:: html\r\n\r\n    <p>This is <em>emphasized</em> <em>text</em>.</p>\r\n\r\nEmphasis: Strong\r\n----------------\r\n\r\nTo boldly emphasize text, wrap it with either double asterisks or double underscores.\r\n\r\nMarkdown:\r\n\r\n    This is very heavily **emphasized** __text__.\r\n\r\nOutput:\r\n\r\n    <p>This is very heavily <strong>emphasized</strong> <strong>text</strong>.</p>\r\n\r\n    \r\nHeaders\r\n----------------\r\n\r\nHTML headings are produced by placing a number of hashes before the header\r\ntext corresponding to the level of heading desired (HTML offers six levels of\r\nheadings). Don't forget to add a newline before creating a header.\r\n\r\nMarkdown:\r\n\r\n    # First-level heading\r\n\r\n    #### Fourth-level heading\r\n\r\nOutput:\r\n\r\n    <h1>First-level heading</h1>\r\n\r\n    <h4>Fourth-level heading</h4>\r\n\r\n\r\nHorizontal rules\r\n----------------\r\n\r\nYou can create a horizontal rule (``<hr />``) by placing 3 or more phens, asterisks, or underscores on a single line. You can also place spaces between them. Don't forget to add a newline before creating a horizontal rule.\r\n\r\nMarkdown:\r\n\r\n    * * *\r\n\r\n    ***\r\n\r\n    *****\r\n\r\n    - - -\r\n\r\n    ---------------------------------------\r\n\r\nOutput:\r\n\r\n    <hr />\r\n\r\n    <hr />\r\n\r\n    <hr />\r\n\r\n    <hr />\r\n\r\n    <hr />\r\n\r\nImages: Inline\r\n----------------\r\n\r\nImage syntax is very similar to Link syntax, but prefixed with an exclamation point.\r\n\r\nMarkdown:\r\n\r\n    ![alt text](http://path/to/img.jpg \"Title\")\r\n\r\nOutput:\r\n\r\n    <img src=\"http://path/to/img.jpg\" alt=\"alt text\" title=\"Title\" />\r\n\r\nLine Return\r\n----------------\r\n\r\nTo force a line return, place two empty spaces at the end of a line.\r\n\r\nMarkdown:\r\n\r\n    Forcing a line-break\\s\\s\r\n    Next line in the list\r\n\r\nOutput:\r\n\r\n    Forcing a line-break<br>\r\n    Next line in the list\r\n\r\nLinks: Inline\r\n----------------\r\n\r\nInline-style links use parentheses immediately after the link text.\r\n\r\nMarkdown:\r\n\r\n    This is an [example link](http://example.com/).\r\n\r\nOutput:\r\n\r\n    <p>This is an <a href=\"http://example.com/\">example link</a>.</p>\r\n    \r\nLinks: Inline with title\r\n--------------------------------\r\n\r\nMarkdown:\r\n\r\n    This is an [example link](http://example.com/ \"With a Title\").\r\n\r\nOutput:\r\n\r\n    <p>This is an <a href=\"http://example.com/\" \r\n        title=\"With a Title\">example link</a>.</p>\r\n\r\nLinks: Reference\r\n----------------\r\n\r\nReference-style links allow you to refer to your links by names, which you define elsewhere.\r\n\r\nMarkdown:\r\n\r\n    This is a guide on Markdown [Markdown][1].\r\n\r\n    [1]: http://en.wikipedia.org/wiki/Markdown        \"Markdown\"\r\n    \r\nOutput:\r\n\r\n    <p>This is a guide on <a href=\"http://en.wikipedia.org/wiki/Markdown\">Markdown</a>.</p>\r\n    \r\nLists: Simple\r\n----------------\r\n\r\nCreating simple links is done by using plus, hyphens or asterisks as list markers. These list markers are interchangeable. Don't forget to add a newline before starting a list sequence.\r\n\r\nMarkdown:\r\n\r\n    + One\r\n    - Two\r\n    * Three\r\n    \r\nOutput:\r\n    \r\n    <ul>\r\n        <li>One</li>\r\n        <li>Two</li>\r\n        <li>Three</li>\r\n    </ul>\r\n    \r\nLists: Nested\r\n----------------\r\n\r\nNest a list requires you to indent by **exactly** four spaces. Don't forget to add a newline before creating a list sequence.\r\n\r\nMarkdown:\r\n\r\n    + One\r\n    + Two\r\n    + Three\r\n        - Nested One\r\n        - Nested Two\r\n\r\nOutput:\r\n\r\n    <ul>\r\n        <li>One</li>\r\n        <li>Two</li>\r\n        <li>Three\r\n            <ul>\r\n                <li>Nested One</li>\r\n                <li>Nested Two</li>\r\n            </ul>\r\n        </li>\r\n    </ul>\r\n\r\n\r\nParagraphs\r\n----------\r\n\r\nA paragraph is one or more consecutive lines of text separated by one or more\r\nblank lines. Normal paragraphs should not be indented with spaces or tabs. Don't forget to add a newline before creating a new paragraph.\r\n\r\nMarkdown:\r\n\r\n    This is a paragraph. It has two sentences.\r\n\r\n    This is another paragraph. It also has two sentences.\r\n\r\nOutput:\r\n\r\n    <p>This is a paragraph. It has two sentences.</p>\r\n\r\n    <p>This is another paragraph. It also has two sentences.</p>", 
        "status": 2, 
        "updated": "2012-08-29T21:11:48.620", 
        "title": "Markdown Guide", 
        "body_fr": "", 
        "created": "2012-08-29T21:06:48.428", 
        "publish_date": "2012-08-29T21:06:48.428", 
        "path": "speaking/markdown_guide/"
    }
},
{
    "pk": 57, 
    "model": "cms.page", 
    "fields": {
        "body": "Coming soon!", 
        "status": 2, 
        "updated": "2013-06-26T23:56:00.241", 
        "title": "The PyCon 5k Charity Fun Run", 
        "body_fr": "", 
        "created": "2012-09-02T12:43:38.310", 
        "publish_date": "2012-09-02T12:43:38.310", 
        "path": "5k/"
    }
},
{
    "pk": 58, 
    "model": "cms.page", 
    "fields": {
        "body": "This procedure has been adopted from the Ada Initiative's guide titled \"[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports)\u201d.\r\n\r\n1. Keep in mind that all conference staff will be wearing a conference t-shirt/button with the word \u201cSTAFF\u201d on it (or otherwise clearly marked as staff). The staff will also be prepared to handle the incident.  All of our staff are informed of the [code of conduct policy](/2016/about/code-of-conduct/) and guide for handling harassment at the conference. *There will be a mandatory staff meeting onsite at the conference when this will be reiterated as well.*\r\n\r\n2. Report the harassment incident (preferably in writing) to a conference staff member - all reports are confidential.\r\n   \r\n   When reporting the event to staff, try to gather as much information as available, but do not interview people about the incident - Staff will assist you in writing the report/collecting information. \r\n   \r\n   The important information consists of:\r\n\r\n- Identifying information (name/badge number) of the participant doing the harassing\r\n- The behavior that was in violation\r\n- The approximate time of the behavior (if different than the time the report was made)\r\n- The circumstances surrounding the incident\r\n- Other people involved in the incident\r\n\r\nThe staff is well informed on how to deal with the incident and how to further proceed with the situation.\r\n\r\n3. If everyone is presently physically safe, involve law enforcement or security only at a victim's request. If you do feel your safety in jeopardy please do not hesitate to contact local law enforcement by dialing 911. If you do not have a cell phone, you can use any hotel phone or simply ask a staff member.\r\n\r\nA listing of [PyCon staff is located here](/2016/about/staff/), including contact phone numbers. If at all possible, all reports should be made directly to:\r\n\r\n- Ewa Jodlowska, Event Coordinator<br>\r\n[ewa@python.org](ewa@python.org \"ewa@python.org\")<br>\r\n+1 (773) 599-3845<br>\r\n\r\n- Diana Clarke, Conference Chair<br>\r\n[diana.joan.clarke@gmail.com](mailto:diana.joan.clarke@gmail.com \"diana.joan.clarke@gmail.com\")<br>\r\n+1 (416) 453-3130<br>\r\n\r\n- Mathieu Leduc-Hamel, Conference Co-Chair<br>\r\n[mathieu@montrealpython.org](mailto:mathieu@montrealpython.org \"mathieu@montrealpython.org\")<br>\r\n+1 (514) 569-2911<br>\r\n\r\n[Based on Revision](https://github.com/python/pycon-code-of-conduct/tree/649f6db082ee8068520959a7c498dae14d598b8e \"Based on Revision\")", 
        "status": 2, 
        "updated": "2013-10-15T22:10:13.825", 
        "title": "Attendee Procedure for Handling Harassment  ", 
        "body_fr": "", 
        "created": "2012-10-21T15:34:45.976", 
        "publish_date": "2012-10-21T15:34:45", 
        "path": "about/code-of-conduct/harassment-incidents/"
    }
},
{
    "pk": 59, 
    "model": "cms.page", 
    "fields": {
        "body": "This procedure has been adopted from the Ada Initiative's guide titled \"[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports)\u201d.\r\n\r\n-------------------------------------------------------------------------------------------------\r\nBe sure to have a good understanding of our Code of Conduct policy, which can be found here: [https://us.pycon.org/2016/about/code-of-conduct/](https://us.pycon.org/2016/about/code-of-conduct/)\r\n\r\nAlso have a good understanding of what is expected from an attendee that wants to report a harassment incident. These guidelines can be found here: [/2016/about/code-of-conduct/harassment-incidents/](/2016/about/code-of-conduct/harassment-incidents/)\r\n\r\nTry to get as much of the incident in written form by the reporter. If you cannot, transcribe it yourself as it was told to you. The important information to gather include the following:\r\n\r\n - Identifying information (name/badge number) of the participant doing the harassing\r\n - The behavior that was in violation\r\n - The approximate time of the behavior (if different than the time the report was made) \r\n - The circumstances surrounding the incident\r\n - Other people involved in the incident\r\n\r\nPrepare an initial response to the incident. This initial response is very important and will set the tone for PyCon. Depending on the severity/details of the incident, please follow these guidelines:\r\n\r\n - If there is any general threat to attendees or the safety of anyone including conference staff is in doubt, summon security or police.\r\n - Offer the victim a private place to sit\r\n - Ask \"is there a friend or trusted person who you would like to be with you?\" (if so, arrange for someone to fetch this person)\r\n - Ask them \"how can I help?\"\r\n - Provide them with your list of emergency contacts if they need help later\r\n - If everyone is presently physically safe, involve law enforcement or security only at a victim's request.\r\n\r\nThere are also some guidelines as to what not to do as an initial response:\r\n\r\n - Do not overtly invite them to withdraw the complaint or mention that withdrawal is OK. This suggests that you want them to do so, and is therefore coercive. \"If you're OK with it [pursuing the complaint]\" suggests that you are by default pursuing it and is not coercive.\r\n - Do not ask for their advice on how to deal with the complaint. This is a staff responsibility\r\n - Do not offer them input into penalties. This is the staff's responsibility\r\n\r\nOnce something is reported to a staff member, immediately meet with the conference chair and/or event coordinator. The main objectives of this meeting is to find out the following:\r\n\r\n - What happened?\r\n - Are we doing anything about it?\r\n - Who is doing those things?\r\n - When are they doing them?\r\n\r\nAfter the staff meeting and discussion, have a staff member (preferably the conference chair or event coordinator if available) communicate with the alleged harasser. Make sure to inform them of what has been reported about them.\r\n\r\nAllow the alleged harasser to give their side of the story to the staff. After this point, if report stands, let the alleged harasser know what actions will be taken against them. \r\n\r\nSome things for the staff to consider when dealing with Code of Conduct offenders:\r\n\r\n- Warning the harasser to cease their behavior and that any further reports will result in sanctions\r\n- Requiring that the harasser avoid any interaction with, and physical proximity to, their victim for the remainder of the event\r\n- Ending a talk that violates the policy early\r\n- Not publishing the video or slides of a talk that violated the policy\r\n- Not allowing a speaker who violated the policy to give (further) talks at the event now or in the future\r\n- Immediately ending any event volunteer responsibilities and privileges the harasser holds\r\n- Requiring that the harasser not volunteer for future events your organization runs (either indefinitely or for a certain time period)\r\n- Requiring that the harasser refund any travel grants and similar they received (this would need to be a condition of the grant at the time of being awarded)\r\n- Requiring that the harasser immediately leave the event and not return\r\n- Banning the harasser from future events (either indefinitely or for a certain time period)\r\n- Removing a harasser from membership of relevant organizations\r\n- Publishing an account of the harassment and calling for the resignation of the harasser from their responsibilities (usually pursued by people without formal authority: may be called for if the harasser is the event leader, or refuses to stand aside from the conflict of interest, or similar, typically event staff have sufficient governing rights over their space that this isn't as useful)\r\n\r\nGive accused attendees a place to appeal to if there is one, but in the meantime the report stands. Keep in mind that it is not a good idea to encourage an apology from the harasser. \r\n\r\nIt is very important how we deal with the incident publicly. Our policy is to make sure that everyone aware of the initial incident is also made aware that it is not according to policy and that official action has been taken - while still respecting the privacy of individual attendees.  When speaking to individuals (those who are aware of the incident, but were not involved with the incident) about the incident it is a good idea to keep the details out. \r\n\r\nDepending on the incident, the conference chair or his designate may decide to make one or more public announcements. If necessary, this will be done with a short announcement either during the plenary and/or through other channels. No one other than the conference chair or someone delegated authority from the conference chair should make any announcements.\r\n\r\nIf some attendees were angered by the incident, it is best to apologize to them that the incident occurred to begin with.  If there are residual hard feelings, suggest to them to write an email to the conference chair or to the event coordinator. It will be dealt with accordingly.\r\n\r\nA listing of [PyCon staff is located here](/2016/about/staff/), including contact phone numbers. If at all possible, all reports should be made directly to:\r\n\r\n- Ewa Jodlowska, Event Coordinator<br>\r\n[ewa@python.org](ewa@python.org \"ewa@python.org\")<br>\r\n+1 (773) 599-3845<br>\r\n\r\n- Diana Clarke, Conference Chair<br>\r\n[diana.joan.clarke@gmail.com](mailto:diana.joan.clarke@gmail.com \"diana.joan.clarke@gmail.com\")<br>\r\n+1 (416) 453-3130<br>\r\n\r\n- Mathieu Leduc-Hamel, Conference Co-Chair<br>\r\n[mathieu@montrealpython.org](mailto:mathieu@montrealpython.org \"mathieu@montrealpython.org\")<br>\r\n+1 (514) 569-2911<br>\r\n\r\n[Based on Revision](https://github.com/python/pycon-code-of-conduct/tree/649f6db082ee8068520959a7c498dae14d598b8e \"Based on Revision\")", 
        "status": 2, 
        "updated": "2013-10-15T21:23:05.636", 
        "title": "Staff Procedure for Handling Harassment ", 
        "body_fr": "Cette proc\u00e9dure a \u00e9t\u00e9 adopt\u00e9e \u00e0 partir du guide de l'Ada Initiative intitul\u00e9 \u00ab[Conf\u00e9rence anti-harc\u00e8lement / R\u00e9agir aux rapports]( http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports)\u00bb.\r\n\r\n-------------------------------------------------- -----------------------------------------------\r\nAssurez-vous d'avoir une bonne compr\u00e9hension de notre Code de conduite de la politique, disponible ici: [https://us.pycon.org/2013/about/code-of-conduct/](https://us.pycon .org/2013/about/code-of-conduct/)\r\n\r\nAussi avoir une bonne compr\u00e9hension de ce qui est attendu d' un participant qui souhaite signaler un incident de harc\u00e8lement. Ces lignes directrices peuvent \u00eatre trouv\u00e9s ici :\r\n\r\nEssayez d'obtenir de la victime par \u00e9crit autant d\u2019informations que possible \u00e0 propos de l'incident. Si vous ne pouvez pas, transcrivez vous-m\u00eame l\u2019incident comme il vous a \u00e9t\u00e9 relat\u00e9. Les informations importantes \u00e0 recueillir sont les suivants:\r\n\r\n - Des informations d'identification (nom / num\u00e9ro de badge ) du participant faisant le harc\u00e8lement\r\n - Le comportement fautif\r\n - La date et l\u2019heure approximative du comportement (si diff\u00e9rente de celle o\u00f9 le rapport a \u00e9t\u00e9 fait )\r\n - Les circonstances entourant l'incident\r\n - La liste des personnes impliqu\u00e9es dans l'incident\r\n\r\nPr\u00e9parer une premi\u00e8re intervention \u00e0 l'incident. Cette intervention initiale est tr\u00e8s importante et donnera le ton pour PyCon. Selon la gravit\u00e9 ou d\u00e9tails de l'incident, veuillez suivre ces instructions:\r\n\r\n - S'il ya une menace g\u00e9n\u00e9rale pour les participants ou la s\u00e9curit\u00e9 de toute personne, y compris le personnel de conf\u00e9rence, est mise en doute, appeler la s\u00e9curit\u00e9 ou de la police.\r\n - Offrir \u00e0 la victime un endroit priv\u00e9 pour s'asseoir\r\n - Demandez \u00e0 la victime s\u2019il y a un ami ou une personne de confiance dont vous d\u00e9sireriez la compagnie. Si c'est le cas, demandez \u00e0 quelqu'un d'aller chercher cette personne.\r\n - Demandez \u00e0 la victime \"comment puis-je vous aider?\"\r\n - Partagez votre liste de contacts d'urgence avec la victime, s'ils ont besoin d'aide plus tard\r\n - Si la s\u00e9curit\u00e9 physique de tout le monde est actuellement assur\u00e9e, n\u2019impliquez la police ou des membres de la s\u00e9curit\u00e9 qu'\u00e0 la demande de la victime.\r\n\r\nIl ya aussi quelques lignes directrices quant \u00e0 ce qu\u2019il ne faut pas faire en premi\u00e8re intervention :\r\n\r\n - Ne pas ouvertement inviter la victime \u00e0 retirer sa plainte ou mentionner que son retrait est acceptable. Ce comportement coercitif sugg\u00e8re que vous d\u00e9sirez qu'elle la retire. Vous pouvez \u00e9noncer cette demande de fa\u00e7on neutre et sans pression en disant: \u00abSi vous \u00eates d\u2019accord avec la poursuite de la plainte, [...]\u00bb, ce qui sugg\u00e8re que vous \u00eates par d\u00e9faut en accord avec la poursuite de la plainte.\r\n - Ne pas demander l\u2019avis de la victime sur la fa\u00e7on de traiter la plainte. C'est une responsabilit\u00e9 du personnel\r\n - Ne vous prononcez pas sur les p\u00e9nalit\u00e9s possibles. C'est la responsabilit\u00e9 du personnel\r\n\r\nUne fois qu\u2019un incident est signal\u00e9 \u00e0 un membre du personnel, rencontrer imm\u00e9diatement le pr\u00e9sident de la conf\u00e9rence et / ou le coordonnateur de l'\u00e9v\u00e9nement. Les principaux objectifs de cette r\u00e9union est de savoir:\r\n\r\n - Qu'est-il arriv\u00e9?\r\n - Devons-nous effectuer des actions par rapport \u00e0 cet \u00e9v\u00e8nement?\r\n - Qui est en train de r\u00e9aliser ces actions?\r\n - Quand est-ce que ces actions seront effectu\u00e9es?\r\n\r\nApr\u00e8s la r\u00e9union et discussion du personne, un membre du personnel (de pr\u00e9f\u00e9rence le pr\u00e9sident de la conf\u00e9rence ou de coordonnateur de l'\u00e9v\u00e9nement, si disponible) communiquent avec le pr\u00e9sum\u00e9 harceleur. Assurez-vous de les informer de ce qui a \u00e9t\u00e9 rapport\u00e9 \u00e0 leur sujet.\r\n\r\nLaisser le pr\u00e9sum\u00e9 harceleur donner leur version de l'histoire au personnel. \u00c9noncez ensuite les mesures pouvant \u00eatre prises contre lui, s\u2019il y a lieu.\r\n\r\nCertaines choses que le personnel doit consid\u00e9rer lorsqu\u2019il fait affaire avec un contrevenant au code de conduite :\r\n\r\n- Avertir le harceleur de cesser leur comportement et que toute autre plainte entra\u00eenera des sanctions\r\n- Exiger que le harceleur \u00e9vite toute interaction et la proximit\u00e9 physique avec leur victime pour le reste de l'\u00e9v\u00e9nement\r\n- Mettre fin promptement \u00e0 toute conversation qui viole la politique du code de conduite\r\n- Ne pas publier la vid\u00e9o ou des diapositives d'un discours qui a viol\u00e9 la politique\r\n- Ne pas permettre \u00e0 un participant qui a viol\u00e9 le code de conduite de pr\u00e9senter \u00e0 nouveau \u00e0 l'\u00e9v\u00e9nement actuel ou dans un \u00e9v\u00e8nement futur\r\n- Conclure imm\u00e9diatement toute responsabilit\u00e9 et privil\u00e8ges que le harceleur d\u00e9tient\r\n- Exiger que le harceleur ne se porte plus volontaires pour les \u00e9v\u00e9nements futurs de votre organisation (ind\u00e9finiment ou pour une certaine p\u00e9riode de temps)\r\n- Exiger que le harceleur rembourser les bourses de voyage ou similaire re\u00e7ues (ce devrait \u00eatre une condition de la subvention au moment de son attribution)\r\n- Exiger que le harceleur quitte imm\u00e9diatement l'\u00e9v\u00e9nement sans possibilit\u00e9 de retour\r\n- Interdire au harceleur la participation aux \u00e9v\u00e9nements futurs (ind\u00e9finiment ou pour une certaine p\u00e9riode de temps)\r\n- Retirer l\u2019adh\u00e9sion de l\u2019harceleur aux organisations\r\n- Publication d\u2019un compte rendu du harc\u00e8lement et l\u2019appel au renoncement du harceleur \u00e0 ses responsabilit\u00e9s (en g\u00e9n\u00e9ral propos\u00e9 par des personnes sans autorit\u00e9 formelle : peut \u00eatre demand\u00e9 si le harceleur est le directeur de l'\u00e9v\u00e9nement ou refuse de rester \u00e0 l'\u00e9cart du conflit d'int\u00e9r\u00eat, ou similaire. G\u00e9n\u00e9ralement, le personnel de l\u2019\u00e9v\u00e9nement a des droits qui r\u00e9gissent suffisants le cadre de leur fonction, ce qui rendent ce point moins utile)\r\n\r\nDonner au participant accus\u00e9 un lieu de faire appel \u00e0 s'il en existe un, mais en attendant, la plainte est maintenue. Gardez \u00e0 l'esprit que ce n'est pas une bonne id\u00e9e d'encourager les excuses du harceleur.\r\n\r\nIl est tr\u00e8s important de voir comment l'incident est trait\u00e9 publiquement. Notre politique est de faire en sorte que tout le monde au courant de l'incident initial soit conscient du fait que l\u2019incident n'est pas conforme au code de conduite et qu\u2019une intervention officielle a \u00e9t\u00e9 effectu\u00e9e - tout en respectant la vie priv\u00e9e de tous les participants. Lorsque l'on parle \u00e0 des individus (ceux qui sont au courant de l'incident, mais n'ont pas \u00e9t\u00e9 impliqu\u00e9s dans celui-ci) concernant l'incident, il est pr\u00e9f\u00e9rable d\u2019en omettre les d\u00e9tails.\r\n\r\nSelon l'incident, le pr\u00e9sident de la conf\u00e9rence ou son d\u00e9l\u00e9gu\u00e9 peut d\u00e9cider de proc\u00e9der \u00e0 une ou plusieurs annonces publiques. Si n\u00e9cessaire, cela sera fait avec une courte annonce, soit au cours de la pl\u00e9ni\u00e8re et / ou par d'autres voies. Personne d'autre que le pr\u00e9sident de la conf\u00e9rence ou quelqu'un avec une autorit\u00e9 d\u00e9l\u00e9gu\u00e9e par le pr\u00e9sident de la conf\u00e9rence devraient faire des annonces.\r\n\r\nSi certains participants ont \u00e9t\u00e9 irrit\u00e9s par l'incident, il est pr\u00e9f\u00e9rable de pr\u00e9senter des excuses \u00e0 ceux-ci. Si il reste ressentiment face \u00e0 la situation, il est possible de sugg\u00e9rer d'\u00e9crire un e-mail au pr\u00e9sident de la conf\u00e9rence ou au coordonnateur de l'\u00e9v\u00e9nement. Cette demande sera trait\u00e9e en cons\u00e9quence.\r\n\r\nUne liste des [personnel de PyCon se trouve ici](/2016/about/staff/), y compris les num\u00e9ros de t\u00e9l\u00e9phone. Si possible, tous les rapports doivent \u00eatre faits directement \u00e0: \r\n\r\n- Ewa Jodlowska, Event Coordinator<br>\r\n[ewa@python.org](ewa@python.org \"ewa@python.org\")<br>\r\n+1 (773) 599-3845<br>\r\n\r\n- Diana Clarke, Conference Chair<br>\r\n[diana.joan.clarke@gmail.com](mailto:diana.joan.clarke@gmail.com \"diana.joan.clarke@gmail.com\")<br>\r\n+1 (416) 453-3130<br>\r\n\r\n- Mathieu Leduc-Hamel, Conference Co-Chair<br>\r\n[mathieu@montrealpython.org](mailto:mathieu@montrealpython.org \"mathieu@montrealpython.org\")<br>\r\n+1 (514) 569-2911<br>\r\n\r\n[Bas\u00e9 sur la r\u00e9vision](https://github.com/python/pycon-code-of-conduct/tree/649f6db082ee8068520959a7c498dae14d598b8e \"Bas\u00e9 sur la r\u00e9vision\")", 
        "created": "2012-10-21T15:53:58.084", 
        "publish_date": "2012-10-21T15:53:58", 
        "path": "about/code-of-conduct/harassment-incidents-staff/"
    }
},
{
    "pk": 60, 
    "model": "cms.page", 
    "fields": {
        "body": "#### DEADLINES\r\n\r\nCompany logos, descriptions, banners, advertising pages, tote bag inserts and similar must be provided by the applicable deadlines for inclusion in the promotional materials for PyCon. See the PyCon website and sponsor mailings for details.\r\n\r\n\r\n#### COMPANY LOGO AND INFORMATION\r\n\r\nYou will be required to submit a company logo and company/product description as outlined in the sponsorship details above. The Python Software Foundation is authorized to make use of this information for the PyCon program, web site, and associated materials. Company descriptions and print and web logos should be submitted via the sponsor controls on the PyCon website and should comply with the following specifications:\r\n\r\n* For tote bag logos: A black and white vector images (SVG, EPS, AI) with text converted to outlines (no gradients);\r\n* For program guide logos: A color vector image (SVG, EPS, AI) with text converted to outlines;\r\n* For web logos: A 160x80px 72 ppi .png image with a transparent background color.\r\n\r\nWe emphasize, all text in vector artwork must be converted to outlines; the PSF is not responsible for providing fonts for printing sponsor-submitted logos.\r\n\r\n\r\n#### GOOD FAITH EFFORT\r\n\r\nAll sponsor and vendor benefits will be provided on the basis of a good faith effort on the part of both the Python Software Foundation (PSF) and the sponsor/vendor/exhibitor (Sponsor). The failure of Sponsor to provide a good faith effort to comply with PSF deadlines and guidelines may, in the PSF's sole discretion, result in the revocation of some or all Sponsor benefits without recourse.\r\n\r\n\r\n#### ASSIGNMENT OF SPACE\r\n\r\nThe PSF shall assign the display space to Sponsor for the period of the display, such assignment to be made within six weeks after the PSF's receipt of this application and full payment of all monies owed. Location assignments will be on a first-come, first-served basis and will be made solely at the discretion of the PSF.\r\n\r\n\r\n#### USE OF DISPLAY SPACE\r\n\r\nSponsor is allowed to distribute literature, run demonstrations, and sell products in its assigned exhibit space. Sponsor shall not assign to a third party its display space or any portion of that space without the prior written consent of the PSF, which the PSF may grant or withhold at its sole discretion. If such permission is given, Sponsor shall assume full responsibility for the conduct of the assignee and all its representatives. Sponsor product demonstrations may in no way interfere with demonstrations at adjacent tables.\r\n\r\n\r\n#### INDEMNITY AND LIMITATION OF LIABILITY\r\n\r\nNeither the PSF, any co-sponsor or display space provider nor any of their officers, agents, employees, facilities, other representatives or assigns shall be liable for, and Sponsor hereby releases them from, any claims for damage, loss, harm or injury to the person, property or business of Sponsor or any of its visitors, officers, agents, employees or other representatives, resulting from theft, fire, earthquake, water, unavailability of the facility, accident or any other reason in connection with the display at the conference. Sponsor shall indemnify, defend and protect the PSF and hold the PSF, any co-sponsor and space provider harmless from any and all claims, demands, suits, liability, damages, losses, costs, attorney's fees and expenses which might result or arise from Sponsor's participation in the conference. Under no circumstance will the PSF, any co-sponsor or the exhibit space provider be liable for lost profits or other incidental or consequential damages, for any acts or omissions whatsoever, including negligence on the part of the PSF, any co-sponsor or display space provider, whether or not appraised of the possibility or likelihood of such damages or lost profits. In no event shall the PSF's liability under any circumstance exceed the amount actually paid to it by Sponsor for display space. The PSF makes no representations or warranties regarding the number of persons who will attend the conference.\r\n\r\n\r\n#### OBSERVANCE OF LAWS\r\n\r\nSponsor shall abide by and observe all laws, rules, regulations and ordinances.\r\n\r\n\r\n#### CANCELLATION OR TERMINATION OF EXHIBITS\r\n\r\nIf for any reason beyond its reasonable control, including fire, strike, earthquake, damage, construction or renovation to the display site, government regulation, public catastrophe, an act of God or any similar reason, the PSF shall determine that the conference or any part thereof may not be held, the PSF may cancel the conference or any part thereof. In that event, the PSF shall determine and refund to Sponsor its proportionate share of the balance of the aggregate display fees received which remain after deducting all expenses incurred by the PSF.\r\n\r\n\r\n#### SPONSOR CANCELLATION\r\n\r\nExcept as provided under the cancellation policy above, all payments made to the PSF under this application shall bedeemed fully earned and non-refundable in consideration for expenses incurred by the PSF and the PSF's lost or deferred opportunity to provide display space to others.\r\n\r\n\r\n#### SPONSOR CONDUCT\r\n\r\nSponsor and all of its representatives shall conduct themselves at all times in accordance with highest standards of decorum and good taste. The PSF reserves the right to eject from the conference any Sponsor or representative violating those standards.\r\n\r\n\r\n#### AGREEMENT TO TERMS, CONDITIONS AND RULES\r\n\r\nSponsor agrees to observe and abide by the foregoing terms and conditions and by such additional terms, conditions and rules made by the PSF from time to time for the efficient and safe operation of the conference. This application represents the entire agreement between Sponsor and the PSF concerning the subject matter of this application. The PSF is not making any warranties or other agreements except as set forth above. Any amendment to this contract must be in writing signed by the PSF. The rights of the PSF under this agreement shall not be deemed waived except as specifically stated in writing and signed by an officer of the PSF. If any term of this agreement shall be declared invalid or unenforceable, the remainder of the agreement shall continue in full force and effect. This agreement shall be binding upon the heirs, successors and assigns of Sponsor subject to the terms of this agreement regarding assignment.", 
        "status": 2, 
        "updated": "2012-11-02T17:09:58.940", 
        "title": "Sponsorship Terms and Conditions", 
        "body_fr": "", 
        "created": "2012-11-02T17:08:30.922", 
        "publish_date": "2012-11-02T17:08:30.922", 
        "path": "sponsor/terms/"
    }
},
{
    "pk": 61, 
    "model": "cms.page", 
    "fields": {
        "body": "Coming soon!", 
        "status": 2, 
        "updated": "2013-06-27T01:14:55.881", 
        "title": "Carpooling", 
        "body_fr": "", 
        "created": "2012-11-06T13:40:20.453", 
        "publish_date": "2012-11-06T13:40:20", 
        "path": "community/carpooling/"
    }
},
{
    "pk": 62, 
    "model": "cms.page", 
    "fields": {
        "body": "Coming soon!", 
        "status": 2, 
        "updated": "2013-06-26T23:42:08.939", 
        "title": "Open Spaces", 
        "body_fr": "", 
        "created": "2012-12-11T08:50:07.250", 
        "publish_date": "2012-12-11T08:50:07.250", 
        "path": "community/openspaces/"
    }
},
{
    "pk": 70, 
    "model": "cms.page", 
    "fields": {
        "body": "Coming soon!", 
        "status": 2, 
        "updated": "2013-06-26T23:56:13.988", 
        "title": "PyLadies @ PyCon!", 
        "body_fr": "", 
        "created": "2013-01-28T09:06:07.600", 
        "publish_date": "2013-01-28T09:06:07.600", 
        "path": "events/pyladieslunch/"
    }
},
{
    "pk": 79, 
    "model": "cms.page", 
    "fields": {
        "body": "Coming soon!", 
        "status": 2, 
        "updated": "2013-06-26T23:42:21.833", 
        "title": "Opening Reception", 
        "body_fr": "", 
        "created": "2013-02-18T13:08:41.321", 
        "publish_date": "2013-02-18T13:04:21", 
        "path": "events/reception/"
    }
},
{
    "pk": 80, 
    "model": "cms.page", 
    "fields": {
        "body": "### [This page has moved (click to go there)](/2013/about/volunteers/)", 
        "status": 2, 
        "updated": "2013-02-18T16:34:20.911", 
        "title": "Volunteering On-Site", 
        "body_fr": "", 
        "created": "2013-02-18T16:34:20.908", 
        "publish_date": "2013-02-18T16:34:20.908", 
        "path": "community/volunteer/"
    }
},
{
    "pk": 83, 
    "model": "cms.page", 
    "fields": {
        "body": "<h1 class=\"shift\">Session Staff</h1>\r\n\r\nWe need volunteers to support each session and keep them on track. The duties are simple yet vital to the success of the conference. You\u2019ll help keep an eye on the clock, make sure everyone is in the right place, give the audience a voice, and get a front seat.\r\n\r\nThere are two roles: [**Session Chairs**](#chairs) and [**Session Runners**](#runners). Each needs to be present for the full session.  A session is the group of talks in between breaks (usually 2-3 talks).\r\n\r\n### **Orientation Meeting**\r\n\r\nThere is a speaker and volunteer orientation, Thursday evening, at 8:00pm, after the swag bag stuffing party, in the Green Room. If you are unable to attend the meeting, that is fine. Instead please stop by the Green Room, preferably in the morning between 7:00am and 9:00am. The Green Room is located in the 212 meeting room on the second floor above registration.\r\n\r\n### [**SESSION CHAIRS**](#chairs) {#chairs}\r\n\r\nSession Chairs take charge of the session. You start by getting on stage to introduce the speaker. Keep the intro simple -- something like their name, where they\u2019re from, and the talk title.  Then head back and close the doors to keep it quiet. You watch the clock and let the speaker know when it\u2019s time to stop for questions. If there are multiple questions, you juggle who gets the microphone, pass it around, then let the speaker know when it\u2019s time to wrap it all up. After that, help them disconnect the microphone equipment and make any last announcements (open spaces, BoF, etc).\r\n\r\n### [**SESSION RUNNERS**](#runners) {#runners}\r\n\r\nSession Runners are the shepherds of the session. You start in the elusive Green Room fifteen minutes before each talk and help the speaker get ready. The first step is a test run of the speaker\u2019s laptop on the projector to make sure they can walk up and get started immediately. After everything is alright, you'll show the speaker where to upload their slides -- attendees like a copy for later, and everyone following along with the videos online does too. Five minutes before talk time, the **runner** and speaker head to the session and get situated. Assuming everything gets connected and ready to roll, the runner hands it off to the chair to do their introduction (tip off the chair on pronunciation, and any other requests from the speaker, as needed).\r\n\r\n### Sign Up!\r\n\r\nAre you willing to help? If so, signing up is as easy as viewing the [Conference Schedule](/2013/schedule/talks/) and signing up an open time slot.\r\n\r\nFirst login to the site, then find a time slot, then click the blue S in one of the talk slots for the session.\r\n<center>\r\n![Session Staff Signup](http://i.imgur.com/d4E0PWy.png)\r\n</center>\r\n\r\n\r\n\r\n\r\n", 
        "status": 2, 
        "updated": "2013-03-09T10:29:35.531", 
        "title": "Session Staff", 
        "body_fr": "", 
        "created": "2013-02-22T13:19:38.970", 
        "publish_date": "2013-02-22T13:19:38.970", 
        "path": "about/volunteers/sessionstaff/"
    }
},
{
    "pk": 125, 
    "model": "cms.page", 
    "fields": {
        "body": "## Quick List: Where to Get Help at PyCon ##\r\n\r\n* <p class=\"alert alert-info\"> Required: [Speaker Orientation](#speaker_orientation) - Thursday 8PM.</p>\r\n* Go to the [conference green room](#greenroom).\r\n* Speak with your [session chair](#chair).\r\n* Ask a member of the [PyCon staff](https://us.pycon.org/2013/about/staff/).\r\n* Contact <pycon-organizers@python.org>.\r\n\r\nFor more details, read on...\r\n\r\nHere's some quick-links into this page:\r\n\r\n* [Speaker Orientation](#speaker_orientation)\r\n* [Preparation Advice](#prep)\r\n* [About Slides](#slides)\r\n* [What to Bring](#what_to_bring)\r\n* [Audio-Visual](#audio_visual)\r\n* [Finding Staff](#chair)\r\n* [Practice Space / Green Room](#greenroom)\r\n* [Speaking Advice](#speaking_advice)\r\n* [About The Audience](#audience)\r\n* [Responding to Questions](#qa)\r\n* [Other Resources](#other_resources)\r\n\r\n![Speaking](https://sourceforge.net/blog/communityhub/uploads/2012/03/pycon-600x450.jpg \"From the page: https://sourceforge.net/blog/sourceforge-at-pycon/\")\r\n\r\n## Speaker Orientation ## {#speaker_orientation}\r\n\r\n* When:   Thursday, 8 PM  \r\n* Where:  [Green Room](#greenroom) (Terrace 200 area - up the escalator from Registration)\r\n\r\nAll speakers need to receive an orientation. Even if you have presented at PyCon in the past, the procedures have changed, and important information will be discussed. Also an introduction for first time speakers will immediately follow the orientation.\r\n\r\nIf you are unable to attend the main orientation, that is fine. Instead stop by the Green Room, preferably in the morning between 7:00am and 9:00am, and the Session Staff will give you a personal orientation. \r\n\r\nPlanned activities are:\r\n\r\n* introduction to the session staff\r\n* a review of the session procedures\r\n* a review of what to do in emergencies\r\n* a demonstration of using the conference AV equipment\r\n* a visit to the [green room](#greenroom) (at the end of the meeting)\r\n\r\n\r\n## Preparation Advice ## {#prep}\r\n\r\nFor a 30-minute slot, you have 25 minutes to talk plus 5 minutes for questions. 45-minute slots mean you have 40 minutes to talk and 5 minutes for questions. Time your talk accordingly.  If in doubt, err on the side of not talking long enough.\r\n\r\n### Practice, practice, practice ###\r\n\r\nGiving a talk is not a writing problem or a design problem.  It is a performance problem.  If you are a new speaker, you should probably spend more time practicing your presentation than you spend writing and designing the slides.  It may be worth going to a local interest group or something similar to practice your talk in front of a small audience.\r\n\r\nPractice! Go through your talk at least twice just to yourself. You\u2019ll find yourself much more confident if you know the talk well enough not to worry about forgetting it or what you will say next. It just flows better and you\u2019ll feel much more relaxed.\r\n\r\n* Video yourself (even just for part of your talk) and see yourself \u201cin action\u201d as others see you.\r\n\r\n### Slides ### {#slides}\r\n\r\nSome tips on getting your slides as ship-shape as possible:\r\n\r\n#### Resolution, fonts, colors ####\r\n\r\n* Presentations/laptop res should be **1024x768** (best \"safe\" resolution for video capture equipment and projectors).\r\n* Use **large fonts**, both in presentations and technical demos.\r\n* Use more slides with less code per slide in order to increase your font size.\r\n* Use a white or other light background color with **high contrast** dark text.\r\n* Be sure to test your slides out in the [green room](#greenroom).\r\n* The most important thing about slides is that the audience needs to be able to read them, even the people waaaay at the back.\r\n\r\n#### Content ####\r\n\r\n* The slides are primarily to support your talk.\r\n* Slides should not be too \u201cbusy\u201d. Keep them short, effectively as reminders what to say.\r\n* Use pictures to reinforce concepts.\r\n* Use diagrams to explain the architecture of the thing you are describing.\r\n* Avoid live demos like the plague (pre-recorded sessions should be fine).\r\n* If you are funny, use it. Good, geeky tech jokes == good.\r\n* Gender references and sexual/racy refs are right out. Don\u2019t. Just don\u2019t.\r\n\r\n#### Time per slide ####\r\n\r\n* Plan on spending absolutely no more than 60 seconds on any slide.\r\n* Conversely, only a few seconds for a slide may be too little.\r\n* Above all, try to be consistent about how long you spend on each slide. The audience will respond well to consistency.\r\n\r\n#### publishing your slides ####\r\n\r\nPyCon does not have a published volume of proceedings, but the slides and other materials for talks are often made available on-line.  Consider uploading the presentation to the conference talk proposal system or to a page linked from your talk\u2019s page on the PyCon site. This gives the audience more information in choosing which talks to attend, and people can refer to the slides if they miss something during your talk.\r\n\r\nConsider giving the audience a URL for your slides at the beginning of your talk.\r\n\r\n## At the Conference ##\r\n\r\n**IMPORTANT**: Take the time to stop by the [green room](#greenroom) at some point **prior** to your talk.  You can practice there with the AV equipment.  More importantly, even if you don\u2019t want to practice, be sure your laptop and any other equipment are compatible with the conference AV by trying them out in the green room.\r\n\r\n### what to bring ### {#what_to_bring}\r\n\r\n* Your own VGA dongle (see below).\r\n* Your presentation on a thumb drive, in several formats (just in case).\r\n* A print copy of your speakers notes, if you have any (just in case).\r\n* Your laptop.  If you don\u2019t have one or have any trouble with yours, please contact the conference AV team before your talk.\r\n* Your calm, wonderful self.\r\n\r\n### Before your talk ###\r\n\r\n* Make sure you got a good night sleep.\r\n* Come to your talk sober.\r\n* Eat food that makes you feel physically better.\r\n* Remove any large objects from your pockets (trust us).\r\n* The backdrops are generally black so don\u2019t wear dark clothes.\r\n\r\n### Just before your talk ###\r\n\r\n* Be in the room a few minutes early if you can, and chat to people already in the room as you prepare.\r\n* Introduce yourself to your session chairperson no later than the break before your talk. Once the presentations start the chair will be focused on managing the session.\r\n* Remove your conference lanyard, so it doesn\u2019t get in the way\r\n* Turn off everything you can (phone, wifi, apps on laptop, popup notifications).\r\n* Empty your hands.\r\n\r\n### Audio-visual ### {#audio_visual}\r\n\r\n* **VGA output only**.  Mac owners, make sure you have your appropriate VGA dongle before your talk.\r\n* Once more, the recommended resolution for your slides is **1024x768**.\r\n* If your presentation uses sound, let the AV team know directly before your talk.\r\n* If you don't get a clip-on microphone and your talk relies on you typing and speaking at the same time, ask for a clip-on mic.\r\n* If you are using a handheld microphone, speak in a clear & loud voice, with the microphone situated close to your mouth.  Please do *not* tap the microphone or use it as a pointing device.\r\n* If a higher slide resolution (like 1280x1024) is important for your talk, be sure to test your resolution against the projector in the greenroom.\r\n* If your talk requires other accommodations, be sure to speak with your session chair.\r\n\r\n## Conference Staff ## {#chair}\r\n\r\nThe conference staff will be all over the place.  However, when in doubt, head to the registration desk if you need someone.\r\n\r\n### Session Chairs ###\r\n\r\nPyCon talks are arranged in groups of two or three, called sessions.  ([Look at the schedule](/2012/schedule/)).  Session chairs help run the session, introduce speakers, call time, and help run the room for a short period of time.\r\n\r\nThese session chairs can help if you have any last minute issues.  Please make them aware of any changes or accommodations for your talk (AV, etc.), even though you will have addressed those things with the appropriate people already.\r\n\r\n## The Conference Greenroom ## {#greenroom}\r\n\r\nThe conference has a room set aside that may be used for practicing, testing your slides with the projector, or just cooling down before your talk.  Take advantage of it.\r\n\r\nThe green room is in the same circle of rooms where Open Spaces will be held this week.  You can check your program for the site map, or have a look at the [Open Spaces page](/2013/community/openspaces/).    If you take the escalators behind Registration Desk, and turn 90 degrees left when you get to the top, this area is at about 10 o'clock.\r\n\r\n## Speaking Advice ## {#speaking_advice}\r\n\r\n**DOs and DON\u2019Ts during**\r\n\r\n**DON\u2019T** move around.\r\n\r\nStand still. See [this blog post](http://therealkatie.net/blog/2011/sep/19/tip-speakers/).\r\n\r\n**DO** take the podium...then move to the side.\r\n\r\nMake sure the audience can see you. This is a good thing. We like seeing the whole person. Once you\u2019re out there, stand still. Don\u2019t sway. Try not to lean. Keep your hand movements to, maybe, one every five minutes. This works really well if you\u2019re actually calm and well-rested.\r\n\r\nIf you\u2019re tired, stay behind the podium and grab it. This isn\u2019t the best thing in the world, as it weakens your visual presence, but it also won\u2019t be distracting your audience.\r\n\r\n**DO** speak loudly!\r\n\r\nThis naturally makes you slow down and enunciate your words more clearly. It also makes you seem and feel more confident. It\u2019s very hard to listen to a talk, even from a very knowledgeable person, who is talking too quietly and mumbling words. It\u2019s amazing what effect it has on your confidence too.\r\n\r\n**DON\u2019T** just read the slides.\r\n\r\nPeople came to hear what you have to say.  What you should be doing is using the slides to remind yourself of your next point. Think of them as notes for your speech, not the speech itself.\r\n\r\n**DO** remember about the microphone...\r\n\r\n...regardless of whether it\u2019s attached to your lapel or is on the podium in front of you. Some speakers will turn to point at the display and talk away from the microphone; be sure to point and then turn back.\r\n\r\n**DON\u2019T** depend on the wireless.\r\n\r\nOver 1500 attendees, a handful of access points, your talk, and your friend Murphy.  Do the math.  <wink>\r\n\r\n![Keynote Perspective](http://swiftstack.com/images/posts/pycon-paul-graham.png \"From the post: http://swiftstack.com/blog/2012/03/12/pycon-2012-review-my-favorite-talks/\")\r\n\r\n### About the audience ### {#audience}\r\n\r\nUnlike some academic conferences, PyCon is not an adversarial environment\u2013you\u2019re not going to be attacked afterwards.  This community is particularly friendly and forgiving if you are sincere and make your best effort.\r\n\r\nWhen you present at PyCon you have to realize a huge portion of people will be on their laptops, staring at their screens. This does **not** mean they are not listening, but it can be disconcerting as you won\u2019t be able to use the audience to easily judge how engaging you are being.  Said one past speaker:\r\n\r\n> I have presented and thought I sucked and then later have tell people they loved my presentation, even with essentially no one laughing at my jokes.\r\n\r\nLook around at your audience and pay attention to their body language.  Check that the audience is hearing you (\u201cCan you hear me at the back?\u201d) and understanding you (\u201cDoes that make sense to everyone?\u201d; \u201cAre there any questions about that?\u201d).\r\n\r\nIt takes people about 10 seconds to realize you have asked a question, so if you ask if people are understanding you need to wait that long for it to be effective, else just always assume that someone will speak up if you are being confusing.\r\n\r\nDon\u2019t forget to invite your audiance to a BoF or Open Space followup! The part of your audience which is passionate (or has become passionate due to your presentation) are encouraged to continue the conversation, and you the presenter are a key part of that.\r\n\r\nFinally, encourage the audience to fill all available seats, rather than standing/sitting in the aisles or by the door.\r\n\r\n### The magical time for questions ###  {#qa}\r\n\r\nDuring the Q&A portion of the talk, always repeat any questions that were asked without a microphone - otherwise many people in the audience won\u2019t hear the question.\r\n\r\nConsider finishing your talk early for extra question time. Then prepare some bonus material in case people run out of questions.  Said one veteran:\r\n\r\n> Another suggestion, reasonably specific to PyCon: leave plenty of time for questions. The PyCon audience is unusually engaged, and often the Q&A is the best part of the talk (both as a speaker and attendee).\r\n\r\n### Responding to questions ###\r\n\r\nHave a prepped response for when you just don\u2019t know an answer. It\u2019s okay to say \u2018I haven\u2019t run into that\u2019 or \u2018I\u2019m not familiar with that\u2019. It\u2019s **not** okay to bumble and fake it.\r\n\r\nSome scenarios:\r\n\r\n* Someone will ask you a tough question that you can\u2019t answer on the spot.\r\n\r\nResponse: Just ask them to catch you after the talk.\r\n\r\n*  Someone asks on the mic a very specific question that is really only helpful to them.\r\n\r\nResponse: Ask them to talk to you after so you can get to more questions that are helpful to the whole audience.\r\n\r\n* There may be that one smart aleck who tries to point out some bad design decision or mistake or something that is really not important or your fault.\r\n\r\nResponse: Feel free to answer them succinctly to get them off the microphone.\r\n\r\n### After your talk ###\r\n\r\nBe nice to people who come up to you after a talk. You never know who is that new person who comes up to you, and you might regret it later. Be nice to them and you\u2019ll find out. Try to find time to talk to everyone, even if for just a minute each.\r\n\r\nIf anyone has more questions after your talk, feel free to keep it up in the hallway.  You never know who might join in on the conversation.  If you have a crowd, *consider* finding an \"open space\" room.\r\n\r\nAbove all, take a deep breath and savor the moment.  You did it!\r\n\r\n### Handling nervousness ###\r\n\r\nRemember, they\u2019re more scared of you than you are of them!\r\n\r\nYou shouldn\u2019t get all worried about \u201cbeing remembered for a bad talk\u201d. The honest truth of the matter is that almost nobody is going to remember much about the actual presentation of your talk. So, don\u2019t sweat it.\r\n\r\nIf you\u2019re nervous, thinking that if you screw up that you\u2019ll forever ruin your reputation in the community due to fidgeting a tiny bit too much? Chill out. We\u2019re all still working on our talks.\r\n\r\nTake a deep breath and relax. One veteran said, \u201cI\u2019ve yet to see a talk where someone was booed off the stage, and I\u2019ve seen some horrific talks.\u201d\r\n\r\nIf you are nervous, there\u2019s nothing wrong with admitting that. The information you present is your talk\u2019s primary value. PyCon audiences are very forgiving.\r\n\r\nTake time to yourself before you speak. Deep breathing is always good preparation. Your nervousness will be less apparent than you suppose.\r\n\r\nAnd again, the best remedy for nervousness is to practice, practice, practice.\r\n\r\n## Other Resources ## {#other_resources}\r\n\r\nThis page is derived from [Advice For PyCon Speakers](http://ref.rtfd.org/speakers).\r\n\r\n* <http://therealkatie.net/blog/2011/sep/19/tip-speakers/>\r\n* <http://nedbatchelder.com/text/presentationtips.html>\r\n* <http://nedbatchelder.com/blog/201002/25_minutes_is_a_bitch.html>\r\n* <http://nedbatchelder.com/blog/201102/pycon_presentations_hollywood_style.html>\r\n* <http://web.archive.org/web/20100212084133/http://us.pycon.org/TX2007/HelpForSpeakers>\r\n* <http://pydanny.blogspot.com/2011/02/my-tips-for-speaking.html>\r\n* <http://dalecarnegielesson.blogspot.com/2011/06/12-ways-to-minimize-fear-and-anxiety.html>\r\n* <http://perl.plover.com/yak/presentation/>\r\n* <http://web.archive.org/web/20060628122618/http://www.sage.org/presentation/>\r\n* <http://pages.cs.wisc.edu/~markhill/conference-talk.html>\r\n* <http://solarsail.hcs.harvard.edu/~krstic/08-2005-giving-talks.pdf>\r\n* <http://web.archive.org/web/20110204154428/http://ite.org/meetcon/speech.asp>\r\n* <http://shop.oreilly.com/product/9780596802004.do>\r\n* <http://martinfowler.com/bliki/PresentationSmells.html>\r\n\r\n----------------------------\r\n\r\nMost of the information on this page came from generous members of the Python community.", 
        "status": 2, 
        "updated": "2013-03-09T16:01:06.925", 
        "title": "Resources for PyCon Speakers", 
        "body_fr": "", 
        "created": "2013-03-09T10:46:33.047", 
        "publish_date": "2013-03-09T10:46:33.047", 
        "path": "speaking/resources/"
    }
},
{
    "pk": 128, 
    "model": "cms.page", 
    "fields": {
        "body": "## Proposal resources\r\n\r\nWe want **you** to submit a proposal to PyCon! The program committee is always available to help you put together a proposal. Here's a list of information and advice to help you out.\r\n\r\n#### General advice\r\n\r\n- <a href=\"http://us.pycon.org/2016/speaking/proposal_advice\">Proposal Advice</a> on how to structure your PyCon talk, tutorial, or conference proposal. \r\n- [Speak Up!](http://speakup.io/) is a cross-community project that provides a friendly place to help people give great talks. They have a fantastic list of [resources](http://speakup.io/resources.html). \r\n\r\n#### Posters\r\n\r\n- <a href=\"https://us.pycon.org/2016/posters/\">Poster Session Information</a>\r\n- <a href=\"https://us.pycon.org/2016/posters/faq\">Poster FAQ</a>\r\n\r\n#### Tutorials\r\n\r\n- <a href=\"https://us.pycon.org/2016/speakers/tutorials/instructors/\">Tutorial Information For Instructors</a>\r\n- <a href=\"https://us.pycon.org/2016/speakers/tutorials/proposals/\">How to Submit a Tutorial Proposal</a>\r\n- <a href=\"http://us.pycon.org/2016/tutorials/suggested_topics/\">Suggested Topics</a>\r\n\r\n#### Talks\r\n\r\n- <a href=\"https://us.pycon.org/2016/speaking/proposal_advice/samples/SpacePug/\">Example PyCon talk proposal: SpacePug</a>\r\n\r\n### Articles\r\n\r\n- [Pro Tips for Conference Talks](http://craigkerstiens.com/2012/06/19/pro-tips-for-conference-talks/) - an excellent write up / advice by Craig Kerstiens of Heroku\r\n- [OSCON Call for Proposals](http://www.oscon.com/oscon2011/public/cfp/144) - the same guidelines and tips for OSCON talks apply for PyCon talks.\r\n- [http://www.doughellmann.com/articles/how-tos/review-conference-proposal/index.html](http://www.doughellmann.com/articles/how-tos/review-conference-proposal/index.html) - a good write up by Doug Hellmann on what he looks for when reviewing PyCon talks as part of the Program Committee", 
        "status": 2, 
        "updated": "2013-10-15T19:14:08.185", 
        "title": " Proposal Resources", 
        "body_fr": "# Conseils et directives pour des propositions\r\n\r\nNous d\u00e9sirons que **vous** nous soumettiez une proposition pour Pycon ! Les membres du comit\u00e9 de programme sont toujours disponible pour vous aider \u00e0 r\u00e9diger votre proposition. Voici une liste de conseils pour vous aider dans cette t\u00e2che.\r\n\r\n### Conseils g\u00e9n\u00e9raux\r\n\r\n* [Comment structurer votre pr\u00e9sentation, tutoriel ou votre conf\u00e9rence](http://us.pycon.org/2016/speaking/proposal_advice)\r\n* [Speak Up!](http://speakup.io/) est un projet inter-communautaire et accueillant pour venir en aide aux pr\u00e9sentateurs potentiels. Ils offrent des conseils et du mentorat ainsi qu'une liste non-n\u00e9gligeable de [conseils](http://speakup.io/resources.html).\r\n\r\n### Affiches\r\n\r\n* [Informations g\u00e9n\u00e9rales concernant les affiches](https://us.pycon.org/2016/posters/)\r\n* [Foire aux questions sur les affiches](https://us.pycon.org/2016/posters/faq)\r\n\r\n### Tutoriels\r\n\r\n* [Informations pour les tuteurs](https://us.pycon.org/2016/speakers/tutorials/instructors/)\r\n* [Comment soumettre une proposition de tutoriel](https://us.pycon.org/2016/speakers/tutorials/proposals/)\r\n* [Suggestion de sujets](http://us.pycon.org/2016/tutorials/suggested_topics/)\r\n\r\n### Pr\u00e9sentations\r\n\r\n* [Exemple de pr\u00e9sentation: SpacePug](https://us.pycon.org/2016/speaking/proposal_advice/samples/SpacePug/)\r\n\r\n## Liens utiles\r\n\r\n* [Conseils de pro pour des pr\u00e9sentations \u00e0 des conf\u00e9rences](http://craigkerstiens.com/2012/06/19/pro-tips-for-conference-talks/) - des conseils tr\u00e8s pratiques de la part de Craig Kerstiens d'Heroku\r\n* [Demande de proposition d'OSCON](http://www.oscon.com/oscon2011/public/cfp/144) - Les directives et conseils pour les pr\u00e9sentations d'OSCON s'appliquent \u00e9galement aux pr\u00e9sentations de PyCon\r\n* [Un billet de Doug Hellman](http://www.doughellmann.com/articles/how-tos/review-conference-proposal/index.html) sur ce qu'il recherche lorsqu'il r\u00e9vise une proposition en tant que membre du comit\u00e9 de programme.\r\n", 
        "created": "2013-07-01T21:06:53.854", 
        "publish_date": "2013-07-01T21:03:36", 
        "path": "speaking/proposal-resources/"
    }
},
{
    "pk": 129, 
    "model": "cms.page", 
    "fields": {
        "body": "# How to Submit a Lightning Talk Proposal\r\n\r\nFirst, sign up for a new account or log in to your account.\r\nOnce you are logged in, proceed to your account dashboard and create a speaker profile.\r\nAt this point, you can submit lightning talk proposals. Fill in the fields as follows:\r\n\r\n## Title*\r\n\r\nGive your lightning talk a descriptive title for the audience.\r\n\r\n## Description*\r\n\r\nA high-level description of the lightning talk, limited to 400 characters.\r\n\r\n## Additional Notes\r\n\r\nAny additional notes for the program committee to make a decision: past talks experience, links to projects, etc. These notes will not be made public.\r\n\r\n## Additional Requirements\r\n\r\nAny specific needs, e.g. A/V needs, multiple microphones, audio out, etc.\r\n\r\n## Slide Deck\r\n\r\nIf you have given this presentation before or a similar, feel free to upload those slides for the program committee to review in the context of your proposal(s).\r\n\r\nJust before you give your talk, be sure to circle back and upload your slides so that we can post them online in addition to the video of your talk.\r\n\r\n(*) denotes required fields", 
        "status": 2, 
        "updated": "2013-10-15T19:12:41.038", 
        "title": "Submitting  a Lightning Talk", 
        "body_fr": "# Comment soumettre une proposition pour une courte pr\u00e9sentation\r\n\r\n* Commencez tout d'abord par cr\u00e9er un nouveau compte si vous n'en n'avez pas d\u00e9j\u00e0 un\r\n* Connectez-vous et rendez vous dans le panneau d'administration de votre compte\r\n* Cr\u00e9ez ensuite un profile de pr\u00e9sentateur\r\n* \u00c0 partir de ce moment, vous pouvez faire une proposition pour une courte pr\u00e9sentation\r\n\r\nVoici une petite explication des champs du formulaire:\r\n\r\n### Titre *\r\n\r\nDonnez un titre qui d\u00e9crit bien votre pr\u00e9sentation.\r\n\r\n### Description *\r\n\r\nUne description sommaire limit\u00e9e \u00e0 400 caract\u00e8res\r\n\r\n### Notes additionnelles\r\n\r\nDes notes concernant votre exp\u00e9rience par le pass\u00e9 pour des pr\u00e9sentation ou des projets. Ils aideront le comit\u00e9 de programme \u00e0 prendre une d\u00e9cision. Ces notes ne seront pas publiques.\r\n\r\n### Demandes additionnelles\r\n\r\nUne liste de besoins particuliers pour votre pr\u00e9sentation. ex: besoins audio/vid\u00e9os, microphones multiples, sortie audio, etc.\r\n\r\n### Diapositives\r\n\r\nSi vous avez d\u00e9j\u00e0 donn\u00e9 la pr\u00e9sentation que vous proposez, vous pouvez nous soumettre vos diapositives. Le comit\u00e9 de la programmation le r\u00e9visera dans le contexte de votre proposition.\r\n\r\nAvant de faire votre proposition, assurez-vous de r\u00e9viser vos diapositives et de nous les envoyer \u00e0 nouveau pour que nous puissions les mettre en ligne en plus de l'enregistrement vid\u00e9o de la pr\u00e9sentation.\r\n\r\n(*) Champs obligatoires", 
        "created": "2013-07-28T22:23:16.163", 
        "publish_date": "2013-07-28T22:23:16", 
        "path": "speakers/lightning-talks/proposals/"
    }
}
]