Role of Newsletter Editor
The primary responsibility of the SIG newsletter editor is to oversee the publication of the periodic SIG newsletter. This involves everything from establishing acceptance criteria for materials to be published in the newsletter to production of the electronic materials to be submitted to headquarters for production and fulfillment to the members. Since this is one of the key benefits that members see for the dues dollar, it is important that the publication of the newsletter meet their expectations in terms of content, appearance, and timely delivery. Because the importance of the SIG newsletter as a communication vehicle with the membership, close working relationships with the other members of the SIG Executive Committee is valuable. Specific duties include:
- Develop resources for editorial support;
- Develop resources for production support;
- Establish reasonable schedule for newsletter production with Headquarters SIG Publications Program Coordinator;
- Provide electronic copy to ACM headquarters
- Get readership feedback on current policies and newsletter directions on a regular basis; and
- Coordinate with other SIG officers on member communication through the newsletter.
This description appears in the SIG Officer Manual, as part of Item 2.2 Officer Responsibilities.
SIG Editors Manual
Date Revised July 1993
ACM Queue’s “Research for Practice” is your number one resource for keeping up with emerging developments in the world of theory and applying them to the challenges you face on a daily basis. In this installment, Dan Crankshaw and Joey Gonzalez provide an overview of machine learning server systems. What happens when we wish to actually deploy a machine learning model to production, and how do we serve predictions with high accuracy and high computational efficiency? Dan and Joey’s curated research selection presents cutting-edge techniques spanning database-level integration, video processing, and prediction middleware. Given the explosion of interest in machine learning and its increasing impact on seemingly every application vertical, it's possible that systems such as these will become as commonplace as relational databases are today.
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.