ICSME Camera Ready
Use this after acceptance. ICSME research papers publish in IEEE Xplore, so the camera-ready is
an IEEE production step. There is no revision round, so the camera-ready is where you fold in the
changes the reviews and your author response committed to — faithfully, without strengthening claims
the PC did not evaluate. Reopen the current IEEE author instructions, the decision email, and the
ROSE-Festival and registration pages before advising.
Camera-ready audit
- De-anonymize completely: restore the author block, affiliations, acknowledgements, funding,
the real tool and repository names, and the real subject-system names that double-anonymity forced
you to hide or genericize.
- Apply the final format: the IEEEtran two-column conference template, within the page budget
(2026: 10 + 2 references), with any camera-ready allowance the acceptance letter states.
- Complete IEEE metadata and rights: title/abstract, author order and affiliations, the IEEE
copyright / eCopyright form, and the correct IEEE copyright notice on the first page. Add ORCID and
index terms/keywords as the template requires.
- Integrate reviewer-required and author-response changes faithfully — the clarifications and
additions you committed to in the rebuttal — without expanding the claim beyond what was evaluated.
- Permanentize open science: replace every anonymized artifact link with a public, licensed,
DOI-issuing archive, and update the data-availability statement to point at it.
- Confirm registration and presentation obligations; at least one author registers and presents.
De-anonymization sweep
| Anonymized at submission |
Restore at camera-ready |
Watch for |
| Author block, affiliations, ORCID |
Full, correctly ordered |
Wrong author order breaks the IEEE Xplore citation |
| Tool / system name |
Real name throughout text, figures, artifact |
A leftover placeholder name in a caption |
| Own subject-system name (genericized) |
Real system name where accurate |
A generic descriptor surviving next to a real one |
| Acknowledgements, funding |
Restored |
Grant numbers required by funders |
| Self-citations (third person) |
Natural first-person where it aids clarity |
Over-correcting and double-citing |
| Artifact link |
Public archive DOI |
The old anonymized URL surviving in a footnote |
IEEE Xplore production checks
[Template] IEEEtran two-column conference, current revision; no manual margin/font edits
[Metadata] title, abstract, authors+affiliations+ORCID, index terms all entered and matching PDF
[Rights] IEEE eCopyright completed; correct copyright notice on the first page
[References] complete, consistent; DOIs where available; within the 2 reference pages
[Figures] vector where possible; readable in two-column print; captions self-contained
[PDF] IEEE PDF-eXpress / compliance check passed if required by the current instructions
[Links] every data-availability and artifact link resolves from a logged-out browser
Worked example: folding in an author-response commitment
In the rebuttal you told the PC the held-out-system result was already in Table 3 and promised to
make the construct-validity threat explicit. Camera-ready move: keep Table 3, add one bounding
sentence to the threats section making the proxy limitation explicit, restore the real tool and
system names in that table, and point the data-availability statement at the now-public artifact —
without expanding the claim the PC accepted. Because there was no revision round, the camera-ready is
the first and only place these promised edits actually land.
Artifact / ROSE handoff
The camera-ready and the ROSE-Festival artifact evaluation are separate deadlines (the artifact
track is shared with SCAM and VISSOFT). Do not wait for the badge result to finalize the paper, but
make the data-availability statement consistent with the IEEE badges you pursue (Open Research
Object at minimum; Research Object Reviewed if the track grants it). Add any badge acknowledgement
only per the current instructions.
Hedged logistics
- Page allowances, IEEE rights-form mechanics, keyword/index-term requirements, and the exact
camera-ready date change each cycle; confirm against the decision email and current IEEE
instructions rather than a prior year. The ICSME 2026 camera-ready date is 待核实 on the access
date.
Output format
[Camera-ready status] ready / needs fixes / blocked
[De-anonymization] author block / tool name / own-system name / acks / links restored? yes/no
[IEEE metadata] eCopyright / index terms / ORCID complete? yes/no
[Response-change map] <committed change -> final edit, no scope creep>
[Open science] anonymized links replaced by DOI archive? yes/no
[Remaining owner] <person -> task>
1---2name: icsme-camera-ready3description: Use when preparing an accepted IEEE ICSME paper for its IEEE Xplore camera-ready, covering de-anonymization, the IEEEtran two-column format and page budget, the IEEE eCopyright form, integrating the reviewer-required and author-response changes without scope creep, permanentizing data-availability links, and the ROSE-Festival artifact handoff.4---56# ICSME Camera Ready78Use this after acceptance. ICSME research papers publish in **IEEE Xplore**, so the camera-ready is9an IEEE production step. There is **no revision round**, so the camera-ready is where you fold in the10changes the reviews and your author response committed to — faithfully, without strengthening claims11the PC did not evaluate. Reopen the current IEEE author instructions, the decision email, and the12ROSE-Festival and registration pages before advising.1314## Camera-ready audit1516- **De-anonymize completely:** restore the author block, affiliations, acknowledgements, funding,17 the real tool and repository names, and the real subject-system names that double-anonymity forced18 you to hide or genericize.19- **Apply the final format:** the IEEEtran two-column conference template, within the page budget20 (2026: 10 + 2 references), with any camera-ready allowance the acceptance letter states.21- **Complete IEEE metadata and rights:** title/abstract, author order and affiliations, the IEEE22 copyright / eCopyright form, and the correct IEEE copyright notice on the first page. Add ORCID and23 index terms/keywords as the template requires.24- **Integrate reviewer-required and author-response changes** faithfully — the clarifications and25 additions you committed to in the rebuttal — without expanding the claim beyond what was evaluated.26- **Permanentize open science:** replace every anonymized artifact link with a public, licensed,27 DOI-issuing archive, and update the data-availability statement to point at it.28- **Confirm registration and presentation** obligations; at least one author registers and presents.2930## De-anonymization sweep3132| Anonymized at submission | Restore at camera-ready | Watch for |33|---|---|---|34| Author block, affiliations, ORCID | Full, correctly ordered | Wrong author order breaks the IEEE Xplore citation |35| Tool / system name | Real name throughout text, figures, artifact | A leftover placeholder name in a caption |36| Own subject-system name (genericized) | Real system name where accurate | A generic descriptor surviving next to a real one |37| Acknowledgements, funding | Restored | Grant numbers required by funders |38| Self-citations (third person) | Natural first-person where it aids clarity | Over-correcting and double-citing |39| Artifact link | Public archive DOI | The old anonymized URL surviving in a footnote |4041## IEEE Xplore production checks4243```text44[Template] IEEEtran two-column conference, current revision; no manual margin/font edits45[Metadata] title, abstract, authors+affiliations+ORCID, index terms all entered and matching PDF46[Rights] IEEE eCopyright completed; correct copyright notice on the first page47[References] complete, consistent; DOIs where available; within the 2 reference pages48[Figures] vector where possible; readable in two-column print; captions self-contained49[PDF] IEEE PDF-eXpress / compliance check passed if required by the current instructions50[Links] every data-availability and artifact link resolves from a logged-out browser51```5253## Worked example: folding in an author-response commitment5455In the rebuttal you told the PC the held-out-system result was already in Table 3 and promised to56make the construct-validity threat explicit. Camera-ready move: keep Table 3, add one bounding57sentence to the threats section making the proxy limitation explicit, restore the real tool and58system names in that table, and point the data-availability statement at the now-public artifact —59without expanding the claim the PC accepted. Because there was no revision round, the camera-ready is60the first and only place these promised edits actually land.6162## Artifact / ROSE handoff6364The camera-ready and the ROSE-Festival artifact evaluation are separate deadlines (the artifact65track is shared with SCAM and VISSOFT). Do not wait for the badge result to finalize the paper, but66make the data-availability statement consistent with the IEEE badges you pursue (Open Research67Object at minimum; Research Object Reviewed if the track grants it). Add any badge acknowledgement68only per the current instructions.6970## Hedged logistics7172- Page allowances, IEEE rights-form mechanics, keyword/index-term requirements, and the exact73 camera-ready date change each cycle; confirm against the decision email and current IEEE74 instructions rather than a prior year. The ICSME 2026 camera-ready date is **待核实** on the access75 date.7677## Output format7879```text80[Camera-ready status] ready / needs fixes / blocked81[De-anonymization] author block / tool name / own-system name / acks / links restored? yes/no82[IEEE metadata] eCopyright / index terms / ORCID complete? yes/no83[Response-change map] <committed change -> final edit, no scope creep>84[Open science] anonymized links replaced by DOI archive? yes/no85[Remaining owner] <person -> task>86```
brycewang-stanford