SIG Governing Board-Executive Committee Motions - FY'02
Motion: Move that the SGB accept the proposal that the SIGs finance the development of the Guide, in exchange for making the Guide free to all and enabling SIG-specific enhancements to the Guide.
That the SGB EC constitute a group to work with HQ and the ACM EC to agree on the details. (11/20/01)
Motion: Move to endorse exception to ACM policy and allow SIGGRAPH to sole source their Web Programming Services. This is a one-time only exception.
Motion: Move to endorse a waiver to current policy and allow a two-year extension to ACM SIGGRAPH's contract with Freeman Decorating. SIGGRAPH leadership is encouraged to exchange this extension for clear benefit to the conference.
Motion: Move to endorse policy modification on the RFP process bringing the threshold to $75,000 for conferences with budgets in excess of $1M.
Motion: Move to endorse a change in policy on the length of contracts for 3 to 5 years for conferences with budgets in excess of $1M.
Motion: The SGB EC approves the budgets of SIGCAPH, SIGDOC, SIGMICRO, SIGSAC and SIGecomm for FY'03. All Chairs for these SIGs will be required to submit an outline by June 1st indicating their plans to bring the SIG out of financial trouble.
Motion: Move that SIGART be converted to a conference SIG as directed by the SIG Operating Rules.
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” 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.