SIG Governing Board Motions - FY'99
Motion: Move to approve the minutes of the February'98 SIG Chairs Meeting.
Motion: Move that the SGB formally express interest in pursuing the IFIP proposal presented by Joe Turner and work on implementation.
Motion: Move to endorse the SIGLINK name change to SIGWEB and forward to ACM EC for approval.
Motion: Move to recommend that the SGB EC further review the viability of SIGCAPH.
Motion: Move that SIGARCH retain their status as a multi-service SIG.
Motion: Move that SIGMICRO retain their status as a conference SIG.
Motion: Move that SIGPLAN retain their status as a multi-service SIG.
Motion: Decertify SIG3C as an active ACM SIG and refer to SGBEC for discussion and decision on how to compensate and serve current SIG3C members.
Furuta, L. Johnson
Motion: Move that SIGAda retain their status as a multi-service SIG with a program review in two years.
Motion: Move that SIGCPR retain their status as a multi-service SIG.
Motion: Move to refer SIGBIO status to the SGB EC for discussion and decision.
Cuningham, L. Johnson
Motion: Move that the viability of SIGAPL be referred to the SGB EC for discussion and decision.
Motion: Move that SIGSIM retain their status as a conference SIG.
Motion: Move that SIGWEB retain their status as a multi-service SIG.
Motion: Move that the SGB EC constitute a committee to provide recommendations on what the SGB should do with regard to conference management software.
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.
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.