Production and Distribution Schedule


  1. Editor sends newsletter with a submission cover sheet (sample follows) to appropriate SIG Staff Liaison at ACM headquarters.
  2. Headquarters checks for completeness and scans nontechnical material. Headquarters determines the print run. Headquarters may supply fillers (house ads, calls for papers, etc.) to secure appropriate page count.
    Corrections, if any, are made and if necessary, the editor or chair is contacted. Some problems that can occur include misnumbered pages, volumes, and issues, poor quality copy, and missing or incorrect information regarding ACM. The newsletter is held until all problems are resolved and the newsletter is complete. (0.5-2 WEEKS)
  3. The newsletter is sent to the printer. The front and inside covers of some newsletters are typeset at the printer. ACM headquarters proofs what the printer has typeset. (0-.5 WEEK)
  4. The printer then photographs, prints and binds the newsletter. (2.5 WEEKS)
  5. One week prior to scheduled mail date, membership and subscriber mailing labels are run at ACM and sent to printer. ACM prepares separate labels for mailing the "hot off the press" copies to editors and chairs.
  6. Issues are mailed via:
    Third class bulk mail within the U.S. (4 WEEKS) or
    Second class bulk mail within the U.S. (1-3 WEEKS)*

U.S. Surface mail to foreign addresses

Foreign freight surface, where overseas members have paid an extra fee for the faster delivery

Air printed matter, where overseas members have paid an extra fee for aster delivery

*Eleven SIGs currently have been approved by the U.S. Post Office for second class mailing privileges. This mail status provides quicker, less expensive service. Please see "Postage" in Section V. Budgeting for further information.

SIG Editors Manual
Updated November 1993

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.

Volunteer with SocialCoder

You can use your technical skills for social good and offer volunteer support on software development projects to organizations who could not otherwise afford it. SocialCoder connects volunteer programmers/software developers with registered charities and helps match them to suitable projects based on their skills, experience, and the causes they care about. Learn more about ACM’s new partnership with SocialCoder, and how you can get involved.

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.