2015 ACM SIG Elections
The 2015 ACM SIG Elections are being conducted by Election Services Corporation (ESC) for the Special Interest Groups SIGACCESS, SIGACT, SIGAPP, SIGBED, SIGBio, SIGCHI, SIGDA, SIGecom, SIGEVO, ACM SIGGRAPH, SIGITE, SIGMETRICS, SIGMIS, SIGOPS, SIGPLAN, SIGSOFT, and SIGWEB.
On 2 April 2015, members of the following SIGs (who were in good standing as of 12 March 2015) were sent voting information from ESC: SIGACCESS, SIGACT, SIGAPP, SIGBED, SIGBio and SIGITE.
On 13 April 2015, members of the following SIGs (who were in good standing as of 24 March 2015) were sent voting information from ESC: SIGecom, SIGEVO, ACM SIGGRAPH, SIGMETRICS, SIGMIS, and SIGOPS.
On 30 April 2015, members of the following SIGs (who were in good standing as of 9 April 2015) were sent voting information from ESC: SIGCHI, SIGDA, SIGPLAN, SIGSOFT, and SIGWEB.
If you have not received email from Election Services Corporation, please contact.
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.
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.
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.