I understand planning is hard, but it’s counterproductive for #Python conferences to run CfPs before #PyConUS2023 has sent out talk acceptances.

ESPECIALLY ppl who spend extraordinary amount of time on talk preparations make it dependent on it whether they write a talk at all.

This way you’re optimizing your schedule for ppl who get paid to give talks vs ppl reporting from the figurative trenches.

@hynek I don't understand the issue. Is it that people will prepare a talk only for PyCon and if they get a different talk accepted in a local con then they have to prepare two talks?

@pganssle I guess you don’t spend 200+ hours preparing a talk then? The value of a talk for me is being able to transform it into social capital and later being invited to small confs that pay for my travel. But maybe that’s all a thing of the past anyway in 2020+ and the trade-off is broken for ppl like me.

@hynek I actually, non-rhetorically, don't understand the problem or the relevance of the amount of time spent on talks.

For me PyCon US is usually the "capstone performance" of my talk, not the debut - and that's not usually my choice, so whether or not PyCon accepts my talk this year has no real bearing on other conferences from this year, since usually a talk gets rejected once or twice from PyCon US before I actually give it. A lot of investment in the talk makes me *less* sensitive to the timing of when I give it, not more.