ACM International Conference Proceedings Series Policy (ICPS)
Reviewed April 2018
The ACM International Conference Proceeding Series (ICPS) provides a mechanism to publish the contents of conferences, technical symposia and workshops and thereby increase their visibility among the international computing community. The goal of this program is to enable conferences and workshops to cost effectively produce proceedings which provide maximum dissemination of the material through electronic channels, specifically, the ACM Digital Library.
Conferences that are not sponsored by an ACM SIG or another unit of ACM may publish their proceedings within ICPS.
Conferences that are in-cooperation with an ACM SIG must apply to ICPS in order to get published in the ACM Digital Library.
The ICPS Editorial Board reviews all applications to publish a volume in ACM's ICPS.
The ACM Author Rights and Publishing Policy will apply to the proceedings. The proceedings will appear in the ACM Digital Library.
For a full description and to apply see ACM's International Conference Proceedings Series.
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.
ACM Queue’s “Research for Practice” consistently 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 of RfP is by Anna Wiedemann, Nicole Forsgren, Manuel Wiesche, Heiko Gewald, and Helmut Krcmar. Titled “The DevOps Phenomenon,” this RfP gives an overview of stories from across the industry about software organizations overcoming the early hurdles of adopting DevOps practices, and coming out on the other side with tighter integration between their software and operations teams, faster delivery times for new software features, and achieving a higher level 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.