How to Minimize Production Time
- Communicate to SIG Staff Liaison your schedule for sending the newsletter to headquarters.
- Check that ACM Conference/Symposia that are announced have been approved by the SIG Governing Board or are marked as "approval pending."
- Ensure that the editorial content is accurate and complete.
- Exclude all advertisements in the SIG newsletters that are not paid advertisements. See Section IV. Advertising Procedures and Policies.
- Provide copy for covers and spine.
- Send electronic material and submission cover sheet filled out in detail to the appropriate SIG Staff Liaison at headquarters. The more details you attend to, the less time it will take headquarters to process and prepare your newsletter for final production. See "Production Pointers" to follow.
The following can delay production:
poor quality copy
pages that require typesetting
oversized image areas, requiring reduction to print
missing footlines and running heads
incorrect volume and/or issue number
SIG Editors Manual
Updated November 1993
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.
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.