The deadline is August 15, and no one knows the instructions. Not the workshop organizers, not the authors refreshing OpenReview every few hours, and apparently not the people running the conference either. A researcher posted this exact frustration to the machine learning community, and the response has been a chorus of shared bewilderment. Some workshops have quietly enabled camera-ready PDF uploads, but the copyright form and LaTeX source files remain a mystery. This is not a minor hiccup. It is a pattern, and it is one we have seen before in other high-stakes, high-pressure environments.
Think about the Neurosurgery Match Requirements Highlight Growing Pressure on Medical Students. In that story, the pressure is on students to submit materials with no clear timeline, while the stakes are their careers. Here, the pressure is on researchers to finalize their work for a major computer vision workshop, and the stakes are their professional reputations and the integrity of the scientific record. The common thread is a system that demands compliance before it provides clarity. It is not that the conference organizers are malicious; it is that they are treating the people who make the event worthwhile as an afterthought. The same way medical students are told to "just wait" for instructions that should have been published months ago, researchers are being told to "just wait" for a form that takes five minutes to draft.
What makes this particularly frustrating is that it is entirely avoidable. The Navigating AI/ML Job Requirements: A Shift in Expected Skills piece highlighted how AI roles are becoming a confusing mix of software engineering and research, and the same blurriness is happening here. The conference wants the papers, the organizers want the credit, and the authors are left guessing what they actually need to do. This is not about a lack of technical expertise; it is about a lack of operational discipline. If you can build a system that accepts submissions, you can build a system that tells people the terms of acceptance.
Our take is simple: this is a leadership failure, not a logistical one. The researchers are not the problem. They are the ones doing the work, and they deserve better than a vague "check back later." If we ran this publication, we would tell the conference organizers to publish the camera-ready instructions immediately, even if it means a rough draft. Clarity is a form of respect. And to the researcher who posted this, we would say this: you are not alone, and you are not being unreasonable. You are asking for the bare minimum. The Unidentified Individual's Data Leaks Spark Debate on Online Anonymity piece reminds us that when people feel left in the dark, they start to fill the gaps with speculation and frustration. The same applies here.
The concrete point to watch is not the August 15 deadline itself. It is what happens the day after. Will the conference issue a blanket extension for those who missed the upload window, or will it hold people to a timeline it never clearly communicated? That answer will tell you everything about whether this is an organization worth submitting to again.