PyColorado 2019

Denver, CO - September 06, 2019, September 07, 2019, September 08, 2019

https://pycolorado.org
Tags: Python, Web development, Data science, Devops, Machine learning, Testing, Django, Flask, Api, Big data

CFP closes at  May 10, 2019 00:05 UTC
  (Local)

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:

Key Dates

  • CFP Opens: March 4, 2019
  • CFP Closes: May 9, 2019
  • CFP Notifications: June 10, 2019
  • Schedule Announced: June 17, 2019
  • Workshops: September 6, 2019
  • Main Conference: September 7-8, 2019
  • Sprints: September 9, 2019

CFP Description

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.

More information about the event can be found at http://pycolorado.org. Reach out at hello@pycolorado.org or on Slack (http://slack.pycolorado.org) for help.

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 hello@pycolorado.org 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.

Some ideas:

  • Python fundamentals
  • Web development
  • Data science
  • Libraries and tools
  • Python community
  • Testing
  • DevOps
  • Performance
  • Security
  • User experience
  • Software design or architecture
  • Engineering philosophy
  • Professional development
  • Ethics
  • Something that isn’t specifically Python

…and anything else we might not have thought of!

Submission Formats

  • Talks: 30 to 45 minutes long, maximum of 2 presenters
  • Lightning talks: 5 minutes long, maximum of 1 presenter
  • Workshops ~3 hours long, in-depth + hands-on presentation, 1 to 4 presenters

CFP Schedule

  • CFP Opens: Monday, March 4, 2019
  • CFP Closes: Thursday, May 9, 2019
  • CFP Notifications: Monday, June 10, 2019

Make as many submissions as you’d like!

Workshop Schedule

September 6th, 2019:

workshop schedule

Talks

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:

  1. WHO is the intended audience for your talk?
  2. WHAT are you going to be talking about and WHAT will people learn from your talk?
  3. WHY is your talk important/interesting/useful? Explain why people would want to attend your talk.
  4. HOW will you be delivering your talk?

Your submission must include the following sections:

  1. Title: To appear prominently in the schedule.
  2. 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.
  3. 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.

Samples:

  1. The AST and Me
  2. Python 2 to 3: How to Upgrade and What Features to Start Using

Lightning Talks

Length: 5 minutes

Your submission must include the same sections as a regular talk, minus the description.

If your submission is accepted, please note that you will still need to purchase a ticket to PyColorado.

Workshops

Length: ~3 hours

Workshops offer a unique opportunity to provide an in-depth education on a topic or theme relevant to research or practice. We’re open to all kinds of ideas. Workshops can be targeted at any experience level, just be sure to indicate clearly what you expect your students to already know or have experience within your proposal.

If your submission is accepted, we will cover your ticket to PyColorado and you will be compensated (based on the percentage of tickets sold).

Be sure to answer some basic questions in your submission:

  1. WHO is the intended audience for your workshops?
  2. WHAT are you going to be teaching and WHAT will people learn from your workshop?
  3. WHY is your workshop important/interesting/useful? Explain why people would want to attend your workshop.
  4. HOW will you be delivering your workshop?

Your submission must include the following sections:

  1. Title: To appear prominently in the schedule. Should accurately describe the workshop’s focus to potential students.
  2. Abstract: High-level, to-the-point description of your workshop, limited to 350 characters. Your abstract is the cornerstone of your submission. This is your chance to sell your workshop to the program committee, so do your best to highlight the problem/contribution/work that you are addressing in your workshop. If your workshop is accepted, this will be displayed on the conference website and some marketing materials. Be sure to address what your workshop aims to teach students, prerequisites for the workshop (what students should know beforehand), prerequisites for their laptop (what students should have installed, whether there are any required libraries, which version of Python is required).
  3. Description: An in-depth explanation of your workshop, read only by reviewers. Tell us about your workshop. A basic structure, content overview, and main content points would be great. The description should contain an outline of your workshop (preferably with estimated timings for each section of your workshop, 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.

Sample submissions:

  1. Going Serverless with OpenFaaS, Kubernetes, and Python
  2. Django deployment workshop

Attendees (3)

Speak at PyColorado 2019!
View Code of Conduct