How to Propose a Talk?

We'd like to encourage you to complete the entire form to help reviewers better understand your proposal. The fields include title, category, duration, language, abstract, python level, objective, detailed description (optional), outline (optional), supplementary (optional), recording release, first time speaker or not, slide link (optional), referral policy, prefer event time, and living in Taiwan or not.

Some of the fields are for proposal reviewers only, so there is no need to worry about spoilers, including objectives, outline, and supplementary.

The abstract or detailed description should answer all of the following questions:
Who is the intended audience?
What should they know before the talk?
Is there any special domain knowledge required?
What will they get after my talk?

Avoid infomercials. Try not to focus on selling your products or introduce how to use them in your talk. However, we do welcome talks about how your company solved a problem previously or how your open source project can be useful to the attendees.
Don’t assume that everyone in the review committee knows who you are. Always submit a complete proposal with all the information that you are able to provide. Avoiding plagiarism. We welcome all forms of sharing, but it should be clear which sections are original and which are citations from previous work.

It is very important for you to choose an appropriate Python level for your talk. The acceptance of your talk correlates with the specified Python level and your targeted audience.
If your talk is designed for Python beginners and you are sharing about your Python learning experience and how you solved some tricky issues you face, then it is a good proposal with content suitable for the right audience group. It will not be a good idea to share about how to inspect Python’s memory usage and GC systems together in a talk for beginners learning Python.
Talks that have mismatched audience groups (like topics above) are easy for the committee to decide. However, most topics lie somewhere in between and it will be hard for the committee to decide. Therefore, do have a look at the following description to help you find the right audience level for your talk.

People who have little to no Python knowledge. One can expect them to have basic knowledge about Python syntax and control flow (e.g. if-else, for loops; functions), but the audience will not understand every module in stdlib, nor the concepts of tricky variables visible scope and OOP (and MRO inheritance).

Sharing your experience learning Python, or how you lead a community are suitable for an audience at this level. Generally, a talk about non-stdlib Python packages, such as pandas or Django, is not suitable for novices, unless they are able to learn and master all the concepts from just your talk alone.

The possible applications are more diverse than novice talks. Intermediate talks are for those who have learned how Python works and wish to know more about how it can be used in various different tasks. Suitable talk topics include setting up web frameworks, working with databases, monitoring web traffic, auto trading in the stock market, and so on.

From our past experience, around half of the talks will fall into this category. Note that we may contact you to adjust your talk for the novice or experienced audience groups based on your proposal.

People coming to experienced talks already have a good proficiency in Python (or programming in general).

The main difference between intermediate and experienced talks is that experienced talks assume more domain knowledge about the talk topic. For example, talks about performance optimization and the internals of how a module works should be at this level.