PyColorado (http://pycolorado.org) is a regional Python conference held annually that brings together the community of Python users and developers in the Front Range region of the Rocky Mountains.
In 2019, PyColorado is a 4-day conference that runs from September 6th - 9th in Denver, Colorado:
- CFP Opens: March 4, 2019
- CFP Closes: May 16, 2019
- CFP Notifications: June 17, 2019
- Schedule Announced: June 24, 2019
- Workshops: September 6, 2019
- Main Conference: September 7-8, 2019
- Sprints: September 9, 2019
Call For Proposals
Welcome! Thank you for your interest in speaking at PyColorado 2019! We look forward to reviewing your talk proposal.
This is a community conference so we are not looking for product and/or vendor sales pitches.
First Time Submitting?
Everyone is encouraged to submit a proposal. We are looking for speakers of all different speaking and Python experience levels, from first-timers to experienced veterans.
Try not to feel intimidated—no topic is too small or too big. Share your ideas and your work, get to know and collaborate with the community. You do NOT need to be a Python expert, chief architect or seasoned developer evangelist to submit a proposal.
Experienced mentors can help you edit and provide feedback on your proposal. We have office hours from 6pm to 7pm MT every Wednesday in the
#cfp-mentorship channel on the PyColorado Slack. You can also email email@example.com to be connected with a mentor.
Suggested Topics and Themes
We love compelling case studies, inspiring success and failure stories, tools and libraries, beginner topics, deep dives, and advanced features. Whatever you feel is relevant for our audience.
- Python fundamentals
- Web development
- Data science
- Libraries and tools
- Python community
- User experience
- Software design or architecture
- Engineering philosophy
- Professional development
- Something that isn’t specifically Python
…and anything else we might not have thought of!
- Talks: 30 to 45 minutes long, maximum of 2 presenters
- CFP Opens: Monday, March 4, 2019
- CFP Closes: Thursday, May 16, 2019
- CFP Notifications: Monday, June 17, 2019
Make as many submissions as you’d like!
Length: 30 to 45 minutes
What gets you excited about Python development lately? What cool art did you build? What’s something you wish someone had told you years ago? What interesting problem have you solved recently? What has been the slowest or most frustrating thing you’ve had to learn over the past few years, and could you put together a talk that would assist in that process for the next Pythonista who tackles the same problem?
If your submission is accepted, we will cover your ticket to PyColorado.
Be sure to answer some basic questions in your submission:
- WHO is the intended audience for your talk?
- WHAT are you going to be talking about and WHAT will people learn from your talk?
- WHY is your talk important/interesting/useful? Explain why people would want to attend your talk.
- HOW will you be delivering your talk?
Your submission must include the following sections:
- Title: To appear prominently in the schedule.
- Abstract: High-level, to-the-point description of your talk, limited to 250 characters. Your abstract is the cornerstone of your submission. This is your chance to sell your talk to the program committee, so do your best to highlight the problem/contribution/work that you are addressing in your talk. If your talk is accepted, this will be displayed on the conference website and some marketing materials.
- Description: An in-depth explanation of your talk, read only by reviewers. Tell us about your talk. A basic structure, content overview, and main content points would be great. The description should contain an outline of your talk (preferably with estimated timings for each section of your talk, but not required), and anything else you think would be relevant for reviewers to take into consideration.
Please do not include any personally identifiable information in these three fields; maintaining anonymity here helps us reduce implicit bias while reviewing submissions.