PyCon AU call for proposals
We’d love you to present at PyCon AU 2024!
Our call for proposals is open until Sunday the 21st of July, 2024.
We’re looking for talks on everything Python, open source, and tech-related. If it would be of interest to someone, anyone, in the Python community, it’s of interest to us!
The PyCon AU call for proposals (CFP) is open from June 1, 2024 until the end of Sunday 21 July, 2024, anywhere on earth. You can submit to the main conference and specialist tracks through the same process.
You can submit your proposal through our online portal, Pretalx:
Submit to the PyCon AU CFP!
If you can’t afford to attend PyCon AU or don’t have an employer that will sponsor your travel, please submit anyway! PyCon AU will have a financial aid program to assist attendees who otherwise couldn’t make it to the conference, and we will prioritise speakers in that process.
We welcome submissions from everybody, including from those:
- Who have never given a conference talk before,
- Who are new to Python,
- Who have built interesting things in Python,
- Who have broken interesting things with Python,
- Who have helped build Python, and
- Who have expertise to share with our community from fields outside of Python (and outside of technology).
Our CFP process also encompasses submissions to the Specialist Tracks (Education, Scientific Python, and DevOops), so you can submit your talk to the main conference and the Specialist Tracks with one click.
To submit your proposal to one or more of the Specialist Tracks, please tag it with the track names of your choice, which are provided for you in the screens that follow. You can select more than one!
If you have questions about the CFP process, you can reach us at program@pycon.org.au.
Specialist Tracks
This year we have three specialist tracks you can submit to, in addition to the main conference! Specialist tracks are independently run events held on the first day of PyCon AU: Scientific Python, Education, and DevOops.
NEW: Academic Abstract Submission
Are you an academic researcher or otherwise very excited about the prospect of publishing your work as a peer-reviewed paper? If so, read on. (If not, you can ignore this whole section and learn more about talk slots and timing, below.)
This year, PyCon AU is partnering with the Journal of Open Source Software (JOSS) to publish academic papers in association with PyCon AU submissions.
Academic abstract submission will not increase your chances of having your talk selected for presentation at PyCon AU. This is intended as a way for participants to further engage with the conference and build their academic track record. If your proposal is accepted as part of the PyCon AU program, we will work with you to handle the JOSS submission, and upon acceptance it will become part of a new PyCon AU collection.
Your academic abstract submission must fulfil basic requirements for publication in JOSS:
- Your submission must describe open source software (as defined by OSI)
- Your software must have an obvious research application
- You must be a major contributor to the software
Additionally, any submissions must comply with the PyCon AU Code of Conduct, as with their accompanying presentation.
For this academic submission, you must provide:
- A title
- Authors names and affiliations of all authors
- Academic abstract text itself, up to 500 words.
You do not have to worry about adding references at this stage (although a few key references might help us evaluate the work - we may not have a reviewer on hand who works in your field).
If your proposal moves forward, members of the PyCon AU academic program committee will work with you to develop your academic abstract submission into a JOSS paper that complies with the journal standards.
We will also help with review and editorial tasks to speed up the progress of your submission.
Our goal is to have all PyCon AU papers published by the time the conference kicks off, but obviously this is subject to many factors.
Please make sure you provide the names and academic affiliations for all authors on the submission. This is important for us to evaluate conflicts of interest and maintain the integrity of the review process.
Talk slots and timing
Talk slots are 30 minutes, with the exception of Deep Dive talks (as discussed in the next section).
If you choose to take questions, the time allocated for that will be part of your allotted time.
We are open to other formats beyond slide-based talks. If you have an idea for a panel, a live coding exercise, a guided tour of your programming environment, or anything else that you think might interest the Python community, feel free to pitch it!
Deep Dives
Sometimes 30 minutes isn’t enough to get into the real meat of something. If you’ve got a topic you feel requires more detail than would fit in our standard talk slot, you can ask for a Deep Dive slot.
Our expectation for these is that presentations in these slots will be highly technical, highly detailed, or both. They should move beyond basic introductions and leave their audience with a much deeper understanding of the topic at hand. They may also assume an audience with an existing familiarity with the subject.
Examples of possible Deep Dive talks include (but are not limited to):
- “What comes after the tutorial?” talks - walkthroughs how to solve complex, real world problems with Python
- “Internals” talks - detailed walkthroughs of the internal architecture of a well known project, describing how it is architected to provide the clean external interface for users
- “Professional skills” talks - taking your skills as a team-based software developer to the next level
- “Theory” talks - explainers of the mathematical or conceptual underpinnings of a subject domain
Proposals for Deep Dive presentations will be very rigorously assessed so please include plenty of information as to what the extra time will be used for.
Presenting your talk online
PyCon AU 2024 is a face to face conference. We are committed to making the event as safe as we can, including measures above and beyond the legally required minimums, and including a mask wearing requirement; please see our Covid-19 information for more detail.
However, if you need to avoid face to face events, for example due to being immunocompromised or unwell, please let us know as part of the submission process. We can provide facilities for delivering your talk via a live video stream or as a pre-recorded video.
Please note that because of the labour involved in ensuring the high A/V quality our attendees expect, our ability to offer remote presentation slots is limited. Because of this, we may prioritise online presenters who live in or near Australia and can’t attend for health or disability reasons, over presenters that live far overseas and are near a more suitable regional PyCon.
Anonymity
Our submission process is anonymous. This means our first-round reviewers will not know anything about your identity while assessing your proposal. Please avoid including identifying information like your name or your pronouns (he/she/they) anywhere in your abstract or description so that our reviewers can assess your talk by itself. If you add such details, please be advised that our CFP curators will edit all identifying information from your submissions before the reviewing process begins.
Make sure to read our anonymity guidelines before your final submission! This FAQ contains important tips on what “anonymous” looks like, and provides information on our review process.
Benefits
Proposals which are accepted will receive one free ticket to PyCon AU 2024, or, if multiple speakers are listed for an accepted talk, two tickets.
You are welcome to propose a talk with more than two speakers, but please be aware that if it is accepted, only two complimentary tickets will be allocated.
If you can’t afford to attend PyCon AU or don’t have an employer that will sponsor your travel, please submit anyway! PyCon AU will have a financial aid program to assist attendees who otherwise couldn’t make it to the conference, and we will prioritise speakers in that process.
Speaker expectations
All speakers will be expected to have read the conference’s code of conduct and adhere to it.
Speaker slide contents and spoken material should be appropriate for a professional audience, including people of many different backgrounds. Sexual language and imagery is not appropriate, nor is language or imagery that denigrates or demeans people based on race, gender, religion, sexual orientation, physical appearance, disability, or body size.
Mentors and feedback
If you’ve never presented at a conference before and think you might like to try it, we want to hear from you!
In order to support speakers, we will offer mentorship and feedback to those who would like it. The list of mentors is coming soon, but you can request mentorship by contacting program@pycon.org.au and we’ll put you in touch with a mentor as soon as we can.
Similarly, if you would like feedback on your proposal, contact us once your proposal is submitted and one of our mentors will reply with feedback.
CFP review and selection process
Phase one: reviewing of anonymised proposal contents
During this phase, the PyCon AU proposal reviewers will review and score each proposal solely on the merits of its contents, without any identifying information or other knowledge about the speaker(s) proposing the talk.
Proposal reviewers come from the following groups:
- PyCon AU core organisers
- PyCon AU specialist track organisers
- Selected members of the Python, FOSS, and Australian tech community
Any members of the aforementioned groups who are acting as PyCon AU CFP mentors, reviewing CFP submissions for identifying information, or who are answering questions at the program email address are disqualified from reviewing proposals in phase one, as through these activities they are likely to gain knowledge of the personal details of some people who have submitted talk proposals.
Phase two: identity-aware ranking and curation
Once reviewing is finished, all proposals will be de-anonymised.
PyCon AU proposal reviewers are then joined by the remaining members of the PyCon AU core organising team in order to curate the program. This group will use the reviewed proposals, in conjunction with speaker profiles, to rank and organise a program that meets our goals for diversity of speakers and topics.
Once curation is complete, we then start to notify speakers, allowing for speakers to decline if required, until we fill our entire conference schedule, including identifying several backup speakers. Emails are generally sent via Pretalx, and the status of each submission will eventually be updated in Pretalx too.
We anticipate all CFP submitters to hear back about their submissions within one month of the CFP close, and before the schedule is released publicly.
Anonymity guidelines
PyCon AU aims to curate a diverse and interesting lineup of talks. In order to review talk proposals with as little bias as is humanly possible, we have made our proposal review process anonymous.
This may be different to the processes you have seen at other conferences, so we have created this FAQ for you. If you have questions that aren’t answered here, you can email program@pycon.org.au
Put any and all personally-identifiable information in the “Profile” section of your submission. This is where we want it to be!
If we identify that you have included information that identifies you, the organisers will edit your proposal before the review process begins. We can’t guarantee it will sound exactly how you intended it, so we encourage you to make very sure that you have removed identifying information before you submit your talk proposal to us.
How do I write a proposal that doesn’t identify me?
The basic guiding principle is to give only the information about yourself that is relevant to the talk.
This means:
- Don’t include your name, your pronouns (he/she/they), or other references to your gender (“this guy”, “her work”)
- Don’t include links to your website, or videos of you giving the talk
- Don’t mention your affiliation with your employer or your project, unless it directly relates to the talk:
Here’s an example where identifying your affiliations is relevant to the talk:
This talk will explore the ways that the Dog Patting Corp team used Python to make their work patting dogs easier.
Here’s an example where identifying your affiliations is not relevant to the talk:
The speaker, who is a Lead Canine Appreciator for Dog Patting Corp, will explore how to build a home automation system using MicroPython.
How do I tell you about myself and why I am the best person to give this talk… without identifying myself?
There is plenty you can say about your work without including your name, references to your gender, or other links. You can accomplish this even without referring to your employer’s name or affiliation with a project.
Things we want to hear about:
- why you are passionate about this topic
- research or work you have already done on this topic
- research or work you are planning to do on this topic
- what you’re interested in
- what kinds of industries you are (or have been) involved in
- what kind of experience you are bringing to this topic
e.g.
I have worked in the dog patting industry for several years and am particularly interested in the problems of how to pat extremely fluffy dogs. I have also worked on patting short-haired dogs. This experience gives me a unique perspective on the problem of dog patting, which I am looking forward to sharing with the audience.
I am also passionate about the history of dog patting, and have both attended and run several workshops on the cultural legacy of being nice to our canine companions.”
Another example:
I started dog patting this year. I have a lot of thoughts about effective ways to teach dog patting to beginners, and I am enthusiastic about making other people’s journeys into the world of patting dogs more enjoyable and accessible.
Can I still identify myself as a [insert gender/minority/attribute here]?
tl;dr: This information belongs in the “Profile” section of your submission.
During the first phase of our review process, the PyCon AU reviewers will not know anything about your identity. Reviewers will use only the talk topic and the details provided in the abstract and notes to rate your talk.
Once all proposals have been rated and reviewed, we will de-anonymise all talks. This means that the information you provided in your “Profile” will become visible to the PyCon AU organisers, and we can begin the work of selecting talks, and putting together the beginnings of the conference schedule. You are welcome to provide demographic information in this section.
Additionally, we provide financial aid to ensure people from a wide variety of backgrounds are able to attend PyCon AU. The financial assistance application process is separate to the CFP review process, and you may provide information about your background and circumstances there as well. See more about financial assistance.
What about my “Profile”?
tl;dr: Put any identifying information in the “Profile” section of your submission! This is where we want it to be.
Our system will hide the information you provide in your “Profile” section from PyCon AU organisers until we choose to de-anonymise it. De-anonymisation is a one-time process that will apply to all submissions at the same time. We will trigger this once the review process has been completed.
This means that the information you provided in your Profile will become visible to the PyCon AU organisers, and we can begin the work of selecting talks, and putting together the beginnings of the conference schedule. You are welcome to provide demographic information in this section.
Information in your Pretalx “Profile” can include:
- Your name
- A free-text biography
- An avatar (or Gravatar)
I didn’t have to do this for [other conference]. Why do I have to do this for PyCon AU?
All conferences will have different processes for reviewing talks based on the needs of their communities. This process is the way that PyCon AU believes is the most likely to reduce bias in the rating and reviewing of talk submissions.
PyCon AU takes our commitment to anonymous reviews very seriously. This means that non-reviewing members of the PyCon AU organising team will check incoming proposals to make sure they do not have identifying information, and remove identifying information before the review process begins if they discover anything that needs changing.
Oh no! I already submitted something that identifies me! What should I do?
tl;dr: Until the CFP closes, you can edit your submissions. You will be able to remove identifying information from your proposal until this time.
You are also welcome to make tweaks and changes to your proposal up until the CFP is closed. This gives you a chance to polish submissions based on feedback, and to remove identifying information if you notice it there.
If you notice we have already edited your proposal to remove identifying information, feel free to make further edits so it reads the way you would like it to. Please note that if you add additional identifying information during an edit, it will be removed again.
I have removed all the identifying info, but my talk title/topic is pretty unique and could identify me. What should I do?
We have reviewers who are both frequent and infrequent conference reviewers and attendees. We will be asking any reviewers who recognise your talk by title or abstract to refrain from reviewing your proposal.
This will give other reviewers the chance to review your proposal without prior knowledge of you or your talk.
I have a different question.
Great! You can email it to program@pycon.org.au.
Content warnings
If your talk contains content that you think might be sensitive, distressing or traumatic to some people (even if most people will be fine with it) please add a content warning in the dedicated field in Pretalx.
Content warnings aren’t a moral judgement on your talk, and they won’t restrict who is able to watch it. In fact, the opposite is true - for some of your audience members, if they know something they find distressing is coming up, they’ll be better able to handle it than if it’s a surprise. That lets them look after their mental health and better engage with and learn from your talk!
Here are some examples of content warnings:
This talk contains extensive discussion of the COVID-19 pandemic throughout.
or
This talk contains images and brief mentions of bushfires and other natural disasters.
Content warnings don’t exempt you from the code of conduct. They exist to warn audiences of things that comply with the code of conduct, but might be distressing anyway.