OSDI Skills
A 12-skill depth pack for OSDI submissions: venue fit, HotCRP submission audits, the no-rebuttal review process, USENIX open-access camera-ready, sysartifacts artifact evaluation, systems reproducibility, page-budget planning, writing style, related work, evaluation design, and cycle management. Grounded in the official OSDI '26 CFP, Call for Artifacts, and USENIX policy pages checked on 2026-07-0
Skills in this plugin
10- ▌ Osdi Submission · brycewang-stanfordUse when running the final pre-upload audit of an OSDI submission on HotCRP — the December registration and full-paper deadlines at 2:59 pm PST, the 12-page/no-appendix check, institution-level double-blind rules, the renamed-system requirement, track choice, and the eight-submission author cap.
- ▌ Osdi Experiments · brycewang-stanfordUse when designing or auditing the evaluation of an OSDI submission — choosing mature baselines and realistic workloads, structuring the section around research questions, measuring scalability and tail behavior, quantifying the design's costs, and fitting the evidence into the 12-page reviewed body.
- ▌ Osdi Camera Ready · brycewang-stanfordUse when converting an OSDI acceptance into the published paper — the June final-paper deadline, expansion to 14 pages plus appendices, the two-page Artifact Appendix, de-anonymization and restored acknowledgments, USENIX open-access publication from day one, and presenter obligations in Seattle.
- ▌ Osdi Related Work · brycewang-stanfordUse when positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes, verifying venues through USENIX's free open-access proceedings and dblp, and citing your own precursors without breaking the renamed-system anonymity rule.
- ▌ Osdi Supplementary · brycewang-stanfordUse when deciding where OSDI content lives given the no-appendix submission rule — triaging material between the 12-page reviewed body, the 14-page-plus-appendices final paper, and the public artifact, since OSDI (unlike appendix-friendly venues) reviews nothing outside the body.
- ▌ Osdi Writing Style · brycewang-stanfordUse when drafting or revising an OSDI paper's prose and structure — building the pain → abstraction → mechanism → measurement narrative, fitting it into the 12-page reviewed body with no appendix escape hatch, and writing for a PC told to down-rank padded papers and given no rebuttal to clarify with.
- ▌ Osdi Review Process · brycewang-stanfordUse when reasoning about how an OSDI paper is reviewed and decided — the double-blind HotCRP PC pipeline with no author-response period, the two tracks, conditional acceptance with heavyweight shepherding, co-chair recusal, notification timing, and the Jay Lepreau Best Paper lineage.
- ▌ Osdi Reproducibility · brycewang-stanfordUse when building reproducibility into an OSDI systems project — recording hardware, configuration, workload, and measurement provenance while experiments run, keeping paper and artifact from drifting apart, and setting up for the post-acceptance sysartifacts evaluation and open-access scrutiny.
- ▌ Osdi Topic Selection · brycewang-stanfordUse when deciding whether a systems project fits OSDI, choosing between its Research and Operational Systems tracks, or routing the work to SOSP, NSDI, FAST, EuroSys, or the post-USENIX ATC instead — applying the built-and-measured test before a December deadline is spent on a misfit.
- ▌ Osdi Artifact Evaluation · brycewang-stanfordUse when preparing an OSDI artifact for sysartifacts-run evaluation — the post-acceptance timeline, the 2026 narrowing to a single Artifacts Available badge, Zenodo-grade permanent archiving, the AE-committee runbook, and the two-page Artifact Appendix that documents the result.