CFP checklist
Our aim here is to improve the speaker's CFP(Call for Proposal) so that we can make the process easy for the final selection committee.
- Feedback should be welcoming and constructive
- Be kind. No passive-aggressive feedback
- CoC(Code of Conduct) also applies to organizers and volunteers
-
The title and description don't look like a sales talk
- Speakers can discuss their interesting open-source libraries or projects but ensure they are not promoting their business.
- Note: They can talk about how they solved a business problem or scaled a business with the help of Python.
-
The title matches the description
- The title should reflect whatever the speaker has conveyed in the description.
-
The topic can be covered within the given time
- If you feel the talk cannot be covered in the stipulated time, let the speaker know to cut/narrow down the contents
-
The description is elaborate enough
-
The topic is ethical
- Any part of the topic should not be an infringement of privacy or other rights
-
No selling ice to the Eskimos
- Everyone in the conference knows why we use Python. If the proposal states the obvious, politely mention the speaker and suggest what they could change.
-
If the above items are checked. Request the speaker to upload the slides for the talk
- The slides need not be complete. A skeleton or an approximate idea is enough
-
2 minutes video pitch about the talk
