Chapter Publications

Reviewed April 2018

 

ACM's SIG professional and student chapters continue to grow at a healthy pace annually. Most SIGs and chapters produce their own publications for their members: be they newsletters, conference proceedings, and forums/notices, among others.

While the ACM Publications Board is responsible for the overall ACM Publications Program, the Board has delegated oversight responsibility to the ACM SIGs for publication of SIG-sponsored proceedings and SIG newsletters. The SIGs make their own policies within the overarching framework set by the Publications Board.

Chapters may publish newsletters for their constituents, the titles of which should not include terms that are used to identify other publication genres (e.g., Transactions, Journal). Titles (or subtitles) of a chapter newsletter are typically of the form "Newsletter of the {ACM Chapter Name}." In addition to the "Newsletter" moniker, terms like "Bulletin," "Forum," "News," "Notes," "Notices," "Pointers," and "Exchanges" can be employed. Frequency of these newsletters are the discretion of the chapter leaders.

Chapters are required to include the standardized ACM Chapter logo on all newsletter covers and on Chapter homepages.

Any questions about starting up a chapter publication should be directed to: Cynthia Ryan, Associate Director of Membership, ryanc@hq.acm.org.
 

The DevOps Phenomenon

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.

ACM Case Studies

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.