ACM SGB Meeting Materials September 20-21, 2003
(1) SIGDA puts together a compendium to capture and archive research contributions that take place at their conferences. SIGDA uses leverage by stating if ACM doesn't do it, IEEE will and if IEEE doesn't do it, ACM will. SIGDA's compendium was presented to ACM and other SIGs with positive feedback.
(2) SIGMOD did a version of the compendium, but found it to be more costly than anticipated.
(3) SIGARCH is doing a compendium as well. The challenge is gathering outside copyright information. The data is more available now and if utilize ACM's data, it is already scanable and includes it accurately.
(4) SIGMICRO allows authors to rebuttal paper reviews. SIGMICRO had an incident when someone gave an obnoxious review and the Program Chair did not notice it and sent it to the author. That particular review was discarded and other reviews were counted. Software is available through Kemal Ebcioglu.
(5) SIGARCH states that we must be observant with the Program Committee because with additional activities can be difficult. Also, just as there is a page limit on papers, there should also be a page limit on rebuttals. Long rebuttal reviews makes the process harder to run.
(6) SIGCHI feels that more precise guidelines should be given to the authors and the Program Committee regarding the rebuttal reviews. This may be more work, but the outcome is better.
(7) SIGPLAN feels that depending on the percentage of papers receive; Program Chairs should not have the need to read every paper.
(8) Be cautious when entering a co-sponsored agreement with other organizers. SIGOPS recent USENIX agreement caused quite concern.
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” 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, “The DevOps Phenomenon” by Anna Wiedemann, Nicole Forsgren, Manuel Wiesche, Heiko Gewald and Helmut Krcmar, gives an overview of stories from across the industry about software organizations overcoming early hurdles of adopting DevOps practices, and coming out on the other side with tighter integration between software and operations teams, faster delivery times for new software features, and achieving higher levels of stability.
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.