Hatchery Program

<blockquote class="callout"> This Call for Proposals is <b>now open</b>. <br><br> Submit proposals to <a href="mailto:pycon-hatchery@python.org">pycon-hatchery@python.org</a> by <b>January 3, 2018 <a href="https://www.timeanddate.com/time/zones/aoe">AOE</a></b> <br><br> Here is the remaining timeline: <ul> <li>October 24, 2017 — Our Call For Proposals opens. <li>January 3, 2018 — Call For Proposals closes. <li>February 2018 — Accepted Hatchery proposals are announced. </blockquote> The PyCon Hatchery Program is an effort to establish a path for introduction of new tracks, summits, demos, etc which share and fulfill the mission of the Python Software Foundation into PyCon’s schedule. For 2018 this program will be run as a trial with the intent to build the program out and formalize it for 2019 and moving forward. Beginning this year, we have assigned one room equipped similarly to other PyCon events for the hatchery program. It will take place Friday, May 11 through Sunday, May 13 2018. Proposals for the hatchery program will be accepted through **January 3, 2018** [AoE](https://www.timeanddate.com/time/zones/aoe) and will be reviewed by an ad-hoc group of the Conference Chair, three PSF Board of Directors, and two community volunteers. After a review process, we plan to announce accepted proposals early in February 2018. ## Time expectations for content Proposals should be for either half or full day’s worth of content, meaning they should fill time slots similarly to PyCon Conference talks. You can see the 2017 schedule [here](https://us.pycon.org/2017/schedule/talks/) to use as a guideline for 2018 as they will be similar. Note that Sunday is a shorter content day so if you wish to propose specifically for that day, please mark so in your proposal ## CFP & review process The criteria for acceptance will be based on the following guidelines: - Is the proposal well organized and detailed? - Proposals should be representative of the effort, thought, and ongoing work that will be necessary to organize, sustain, and grow the proposed event. - Does the program track coincide with the PSF’s mission? - Our goal is to support topics that are relevant to our community. Additionally, the track content being proposed should help us enforce the PSF's mission of diversity, inclusivity, and foster the growth of Python. - Does the program adhere to PyCon’s Code of Conduct? - PyCon is a professional setting where everyone should feel welcome and safe. We expect all proposals to keep the Code of Conduct in mind. - Does the proposer have any experience organizing events/putting talk programs together? - While not strictly a requirement, having previous experience in organizing among the proposing party will be considered in the overall application. - Is the target audience underrepresented or is the subject about underrepresented topics within the tech community? - As we strive to improve the diversity of PyCon overall, priority for this program will be given to proposals that bring new viewpoints and additional representation to the conference. - Does the proposed track pertain to a topic that has enough content on it to form a continued “spin-off” event at PyCon? - While not strictly a requirement, the time and resources which will be furnished by the PSF, PyCon staff, and PyCon volunteers to support these programs are best served by sustainable proposals. Ephemeral programs are welcome and will generally be given lower priority. A few examples of types of topics that are suitable for the program (not a complete list): - PyLadies talk track - Foreign language talk track - Scientific data summit ## What are we asking in the application? - Who is the organizing team or individual - Do you (or the team) have experience organizing conferences, workshops, tutorials, meetups? - Do you have experience putting together a talk program? - What subject are you proposing? - What is your (or the team’s) experience/involvement with the subject? - Can you list some of the subject subtopics that will be given during the track? Do you have presenters in mind for the track? If so, who are they? If not, what is your plan of outreach to get presenters? - What will the audience gain from attending your track? - What will be the actionable take away from the proposed track? How will you get Pythonistas more involved in the subject beyond the conference and how do you plan on proposing this actionable to the attendees? - How do you see this subject evolving into a spin-off event at PyCon going forward? Submit your proposals to <mailto:pycon-hatchery@python.org> by **January 3, 2018 [AoE](https://www.timeanddate.com/time/zones/aoe)**