ACM's Policies and Procedures
ACM's policies and procedures promoting standards of conduct for the computing field, addressing the following areas:
ACM Constitution
Code of Ethics
- ACM Code of Ethics and Professional Conduct
- Using the ACM Code of Ethics
- Software Engineering Code of Ethics and Professional Practice (includes multiple language translations)
Elections
Privacy
Harassment
Social Media
Anti-Spam
Awards
Publications
- Roles and Responsibilities in ACM Publishing
- ACM Policy and Procedures on Plagiarism
- ACM Policy on Reviewer Anonymity
- Copyright Policy
- Fax or Electronic Copyright Forms Policy
- Viability Review Process for ACM Publications
- Including Ancillary Material in Digital Library
- Editor-in-Chief Appointment Policy
- Policy for Appeals - Manuscript Handling
- Policy on Retention of Paper Files
- Publishing Non-SIG Conference Proceedings
- Terms of Usage - Digital Library
- Access to non Digital Library Subscribers Policy
- Turing Award printed in CACM Policy
- Quality of Refereed Electronic Publications
- Recording Publication Dates for Electronic-Only Publications
- Conflict of Interest Policy for Papers Authored by ACM Editors-in-Chief
- Joint-Publishing Agreements for Track I Publications
- ACM-Branded Facility Policy
- Policy on Pre-Publication Evaluation
- ACM Policy on Prior Publication and Simultaneous Submissions
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.
The DevOps Phenomenon
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.
