Updated January 22, 2018
The form of reviewing for most ACM journals and transactions, as well as for some magazines, is single-blind peer review. The "Roles and Responsibilities in ACM Publishing" policy assures that ACM will maintain the anonymity of reviewers. Editors and administrators of ACM publications must keep the identities of all reviewers of particular manuscripts hidden from authors, other reviewers, and the public. To facilitate this, reviewers access and perform their review of the text via a manuscript submission system, and their identities are not released. Identities of reviewers may be divulged to members of a publication's Editorial Board or to ACM staff as needed to solicit expert advice in special circumstances. In such cases, identities of a reviewer may also be made known to other reviewers of the same manuscript, provided that the consent of all affected reviewers is obtained. Reviewers must also maintain the confidentiality of reviewer identities, as well as the reviews themselves, that are communicated to them at any time.
An exception to the anonymity policy is made in the case of review of conference submissions by a program committee. It is permissible to make reviews and the identity of reviewers visible to the entire program committee, provided that all committee members and solicited reviewers are notified in advance of this practice. (A further exception occurs when a program committee member is also an author. Names of reviewers can never be disclosed to the author.) ACM is opposed to any attempt by authors to determine their reviewer's identities, and will not engage in any speculation regarding this.
This policy does not prevent the simple listing of all reviewers of a particular volume or proceedings without reference to particular manuscripts for the purpose of acknowledgement, or the appearance of reviewers names in a composite database for use by the editors.
Created November 19, 2003
ACM Queue’s “Research for Practice” serves up expert-curated guides to the best of computing research, and relates these breakthroughs to the challenges that software engineers face every day. This installment, “The DevOps Phenomenon” by Anna Wiedemann, Nicole Forsgren, Manuel Wiesche, Heiko Gewald and Helmut Krcmar, gives an overview of stories from across the industry about software organizations overcoming early hurdles of adopting DevOps practices, and coming out on the other side with tighter integration between software and operations teams, faster delivery times for new software features, and achieving higher levels of stability.
Written by leading domain experts for software engineers, ACM Case Studies provide an in-depth look at how software teams overcome specific challenges by implementing new technologies, adopting new practices, or a combination of both. Often through first-hand accounts, these pieces explore what the challenges were, the tools and techniques that were used to combat them, and the solution that was achieved.
Why I Belong to ACM
Hear from Bryan Cantrill, vice president of engineering at Joyent, Ben Fried chief information officer at Google, and Theo Schlossnagle, OmniTI founder on why they are members of ACM.