conext-artifact-evaluationUse when converting an accepted ACM CoNEXT paper's package into optional ACM reproducibility badges via the CoNEXT reproducibility committee — from the badge opt-in due before submission, to the one-page artifact description due within a week of acceptance, to the Available / Functional / Reusable /
conext-author-responseUse when drafting ACM CoNEXT author responses, covering the initial-review rebuttal and — distinctively — the one-shot "major" revision response letter that must stay double-anonymous, map every "minimum necessary change" to a concrete tracked edit, and survive a single re-review by the original rev
conext-camera-readyUse when preparing the camera-ready of an accepted ACM CoNEXT paper for its assigned PACMNET issue — systematically de-anonymizing, completing PACMNET journal metadata and ACM rights/CCS/keywords, permanentizing artifact and DOI links, applying any shepherd-required changes, and passing ACM producti
conext-experimentsUse when designing or auditing the evaluation of an ACM CoNEXT paper — matching evidence to claim shape with real testbeds and deployments, honest and tuned baselines, measurement statistics and uncertainty, trace and config provenance, and contamination-aware ablations for ML-for-networking work.
conext-related-workUse when writing the related-work and positioning of an ACM CoNEXT paper — covering the networking literature lanes (SIGCOMM, NSDI, IMC, SIGMETRICS, MobiCom, CCR), delta-first positioning against the venue's own recent programs, and keeping self-citations double-anonymous.
conext-reproducibilityUse when building the reproducibility story for an ACM CoNEXT paper — pinned traces and configs, a runnable artifact, an honest data-availability posture, and the one-page artifact description the CoNEXT reproducibility committee needs — remembering that the ACM badge opt-in is due before the submis
conext-review-processUse when reasoning about how an ACM CoNEXT submission is evaluated, covering double-anonymous review, the two-round TPC process with online discussion and a TPC meeting, the Accept / Reject / one-shot "major" revision decision categories, the journal-style revise-and-resubmit re-read by the original
conext-submissionUse when auditing an ACM CoNEXT submission for HotCRP readiness, covering the choice between the December and June cycles, the mandatory paper-registration step, the ACM acmart page budget (long ≤16 + ≤4 appendix; short ≤10 + ≤2 appendix), double-anonymous review, the reproducibility badge opt-in du
conext-supplementaryUse when deciding what goes in the ACM CoNEXT main body versus the appendix budget versus the artifact — splitting content by decision-criticality so nothing a reviewer needs to accept the paper hides in an appendix or repository, within the acmart limits (long ≤4 appendix pages, short ≤2).
conext-topic-selectionUse when deciding whether a networking project belongs at ACM CoNEXT or should be routed to SIGCOMM, NSDI, IMC, SIGMETRICS, MobiCom, or HotNets, and when using CoNEXT's two-cycles-per-year calendar and PACMNET journal-style fit to choose the venue and the cycle by contribution shape and evidence mat
conext-workflowUse when planning an ACM CoNEXT campaign backward from a deadline, covering the choice between the December and June submission cycles, the mandatory registration step, the one-shot major-revision window, the reproducibility badge opt-in due at submission, PACMNET camera-ready, and presentation — al
conext-writing-styleUse when shaping the prose and structure of an ACM CoNEXT paper — leading with the networking problem and deployment context, tying every claim to a measurement on the real target platform, arguing limitations rather than reciting them, and holding the acmart page budget for long (≤16) and short (≤1