PyBeach is a general Python conference serving the wide variety of people who use the Python programming language. It is a welcoming, volunteer-run, community-driven event with the mission to educate and connect its attendees to one another, and promote Python within the local technology community. The conference is made possible by the fiscal sponsorship of the Python Software Foundation.
PyBeach 2020 will be a one-day, single-track event, with a main talks track, open source sprints, “hallway track” space, and an expo hall. It will be hosted on Saturday, February 29, 2020, at Toolbox LA. The expected attendance is around 225 professionals, enthusiasts, and students, mostly local to the greater Los Angeles area and the rest of Southern California.
Talk length is 30 minutes, with no Q&A. If you’re open to audience interaction about your talk, we suggest you encourage that people stop you in the hallway, find you on Twitter, send you an email, or the like.
The CFP review process is anonymized from submission until rating. The program committee may then take other factors into consideration to ensure a diverse selection of both talks and speakers that can honestly represent our community.
First-time speakers are as welcome as those with long speaking resumes. If you’d like help with your proposal or talk, we’d be happy to give you feedback and help guide you along.
If you have any questions, please reach out to us at email@example.com.
Subject Matter and Talk Level
PyBeach is a Python conference, so talks should cover subjects of interest to the Python community. While this may predominantly indicate specificity to Python, topics of open source software, technology in general, community, industry, et al. are also appropriate.
Additionally, as the conference is a general Python one, we’re looking for a variety of both levels (from beginner to intermediate to advanced) and subjects (general Python, web, data, ops, testing, documentation, accessibility, teamwork, etc.).
Keep in mind that this is a single-track conference, so your talk will be seen by beginners, veterans, and everyone in between. Not every talk has to appeal to everyone, but broader coverage is likely better.
Note: keep in mind that your talk submission should be anonymous—please refrain from adding any identifying information to talk-specific fields.
With the above in mind, we welcome as much detail as you can provide about your talk. The bare minimum for a submission to be considered involves:
- Title: make it snazzy! It’s the main thing that gets attendees to read the rest of your write-up to decide whether to watch you present.
- Elevator Pitch: a brief explanation of your talk, to be included on the schedule page.
- Description: a more detailed abstract of your talk, to be shown on the talk page.
Optionally you may also provide:
- Notes: anything else you’d like to tell us about your talk or yourself that we can use to evaluate your proposal.
- Tags: keywords relevant to your talk.
Information about you as a presenter will be kept anonymous during the review process:
- Name: your preferred name as you’d like it to appear in the program.
- URL: your preferred web presence, e.g., blog or portfolio. [optional]
- Organization or Affiliation: any affiliation you’d like to publicize, e.g., an open source project you participate in or your employer. [optional]
- Twitter Handle: [optional]
- Shirt Size: we’d like to thank all our speakers with a conference t-shirt.
- Bio: short blurb about yourself as a Python community member, professional, and person.