Proposing a Tutorial
<blockquote class="callout"> Thank you, everyone who proposed a tutorial for PyCon 2017! <br><br> This Call for Proposals is <b>now closed</b>. <br><br> Here is the remaining timeline: <ul> <li>November 30 — Our Call For Proposals closed. <li>February — We send acceptance and rejection emails. <li>February — The schedule is posted here on the web site. <li>May 17–18 — The tutorials are all presented at PyCon 2017. <li>June — All tutorials that were recorded should appear online. </blockquote> Tutorial proposals are due this year on **30 November**. To learn the mechanics of submitting a proposal, visit the [main Speaking page](https://us.pycon.org/2017/speaking/). Do you think that you would be able to assemble 3 hours of material and lead a classroom full of PyCon attendees through learning a new skill, library, or technology? Then you might want to apply to be one of our tutorial instructors for PyCon 2017! **PyCon 2017 tutorials will be held May 17-18 at the Oregon Convention Center.** As you think about your experiences, skills, and knowledge, here are some links that might help you get started in thinking about the expertise that you could bring for the benefit of the conference: - <a href="https://us.pycon.org/2016/speaking/tutorials/topics/">Possible tutorial topics</a> - <a href="http://us.pycon.org/2015/schedule/tutorials/">PyCon 2015 Tutorials</a> - <a href="http://us.pycon.org/2014/schedule/tutorials/">PyCon 2014 Tutorials</a> - <a href="http://us.pycon.org/2013/schedule/tutorials/">PyCon 2013 Tutorials</a> - <a href="http://us.pycon.org/2012/schedule/">PyCon 2012 Tutorials</a> <p><a data-flickr-embed="true" href="https://www.flickr.com/photos/mikepirnat/13997682270/in/album-72157644656495851/" title="IMG_0794.jpg"><img src="https://farm3.staticflickr.com/2905/13997682270_d34bb03835.jpg" width="500" height="375" alt="IMG_0794.jpg"></a><script async src="//embedr.flickr.com/assets/client-code.js" charset="utf-8"></script></p> ## What information to submit 1. First, <a href="/2017/account/signup/">sign up for a new account</a> or <a href="/2017/account/login/">log in</a> to your account. 2. Once you are logged in; proceed to your <a href="/2017/dashboard/">account dashboard</a> and create a speaker profile. 3. At this point, you can submit tutorials, fill in the fields as follows: ## Title Give your tutorial a name that accurately describes the tutorial's focus to potential students. ## Description A high-level description of the tutorial, limited to 400 characters. ## Abstract Try to include the following to help participants decide if the tutorial is a good match for them: - What the tutorial aims to teach students. - Prerequisites for the tutorial, i.e., what students should know or be able to do before the tutorial. As an example, one past tutorial's prerequisites were *"Students should have at least intermediate-level Python and SQL and have some experience using an ORM."* - Prerequisites for their laptop (assuming one is required). Note that these prerequisites serve two purposes: 1. They may help the potential student understand more precisely what you plan to teach. 2. They help ensure students arrive with the software they need to take the tutorial. If possible, finalize these prerequisites and submit them with your proposal. However, we realize the prerequisites may change as you prepare to teach your tutorial, and in a few cases the prerequisites will be complex enough that they'll need their own page on instructions. We're working on how best to communicate to students in both cases. - 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. ## Audience Level At what level of Python and other topic-specific experience or expertise is the tutorial aiming for? We realize this may be too narrow for a tutorial, for example if the tutorial is aimed at Experienced programmers but Novices to Python, but give it your best shot. If this field doesn't work well, be sure to include a note in the Additional Notes section, and you may also wish to add to your Description or Abstract. ## Additional Notes This is the one section that is for the reviewers' benefit only and will not be published in the PyCon guide. In this section, you should include information that you think would be helpful to assist reviewers in deciding which tutorials to accept, based on both the subject being taught and the ability of the teacher. The following information should be included: - Any explanation or fleshing out of the public fields that would help reviewers. - Intended audience: more than just novice/intermediate/etc. Reviewers need to know what level of Python experience is targeted and also what level(s) of domain-specific expertise is targeted, for example networking, SQL, database, etc. - Tutorial format: lab, lecture, workshop, etc. However, don't just pick a label, describe what will happen during the tutorial. - Interest in tutorial assistants: We're considering making tutorial assistants available to instructors. These would be volunteers with Python experience who will provide one-on-one help during the tutorial when students are working on exercises. If we do this, would you be interested and if so how many students per assistant would you want? - Preferences or requirements with respect to class size or scheduling. - Outline: of the tutorial content for reviewers. - Previous experience: tell us what experience you have in the subject, in activities such as teaching or public speaking, or anything else that would help us understand and gauge your abilities as a tutorial presenter. Ideal would be a link to a video. - Biography: You'll be asked to enter your biography when you register on this site and that information will be made public. Here, you may wish to include more information for reviewers to complement information about your Previous Experience. ## Miscellaneous Notes About Proposals and Tutorials Here are some notes about the proposal, selection, and delivery process for tutorials. - There will be some duplication of information between the public information contained in the Description and Abstract, and the Additional Notes which only reviewers will read. That duplicate information is for two different audiences so if you just copy and paste between them neither will likely be served well. A better strategy, if you don't want to write two versions, is to reference the public version (Description and Abstract) in the Additional Notes for reviewers and then expound on it. - The tutorial selection process attempts to choose a good variety of tutorial topics and levels that will be in demand, i.e., it doesn't just select the best proposals! - The selection process has also tended to prefer Python-related topics over more general software development tools or practices that aren't Python-specific. - Tutorials are subject to cancellation if enrollment is low. In the past the cancellation criterion has been less than 10 students registered. ## Questions or Suggestions If you have questions about any of this, or suggestions, please contact us at: <a href="mailto:email@example.com?subject=Question/Suggestion about Tutorial Proposal">firstname.lastname@example.org</a>.