oopsla-camera-ready
Use when converting an accepted OOPSLA paper into its PACMPL journal article — final acmsmall formatting within the 25-page revision cap, de-anonymization and Data-Availability Statement updates, ACM open-access and rights steps, hitting the OOPSLA1 (April) or OOPSLA2 (October) issue, and planning the SPLASH talk.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-camera-ready --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# OOPSLA Camera-Ready An accepted OOPSLA paper does not go into "conference proceedings" — it becomes a journal article in PACMPL (Proceedings of the ACM on Programming Languages), Gold Open Access, in the issue matching its acceptance round: Round 1 acceptances of the 2026 volume appeared as **Vol. 10, Issue OOPSLA1** (published no earlier than April 1, 2026); Round 2 acceptances form **Issue OOPSLA2** (no earlier than October 1, 2026). The talk then happens at SPLASH — for 2026, Oakland, with OOPSLA sessions October 5–7. Production deadlines arrive by email from ACM/the chairs and were not publicly posted at verification time (待核实): treat the acceptance letter as the calendar. ## What changes between acceptance and print | Item | Submission state | Published-article state | | --- | --- | --- | | Class options | `acmsmall,screen,review,anonymous` | `acmsmall,screen` per production instructions | | Authors | Hidden | Full names, affiliations, ORCIDs, CCS concepts | | Acknowledgments | Absent | Funders, grant numbers, contributors | | Data-Availability Statement | Anonymized archive | Real archive — ideally the DOI-stamped Zenodo deposit from artifact evaluation | | Citations to you
- What changes between acceptance and print
- Reviewer-commitment reconciliation
- ACM production specifics to expect
- Talk planning is part of camera-ready
- Output format
What does the oopsla-camera-ready skill do?
Use when converting an accepted OOPSLA paper into its PACMPL journal article — final acmsmall formatting within the 25-page revision cap, de-anonymization and Data-Availability Statement updates, ACM open-access and rights steps, hitting the OOPSLA1 (April) or OOPSLA2 (October) issue, and planning the SPLASH talk.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-camera-ready --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.