ACM SGB Meeting Agenda, March 21, 2014

SIG Governing Board

Friday, March 21, 2014

8:30 am - 4:00 pm

Chicago, Hilton O'Hare

Room: International West & Center

WIRELESS ACCESS (case sensitive):

Network Name: Hilton Meeting Rms

Access Code: AFCOHARE

8:30 am - 9:00 am
Continental Breakfast
9:00 am - 9:05 am
1.0 Welcome, Introductions (Cerf, Altman, Madden)
9:05 am - 9:50 am
2.0 Report from the ACM CEO (White) Report
9:50 am - 10:10 am 3.0 ACM Europe (Gagliardi)
10:10 am - 10:25 am
Break
10:25 am - 11:00 am 4.0 Report on ACM Books Program (Ozsu)
11:00 am - 11:25 am 5.0 Research Highlights CACM (Morrisett) Report
11:25 am - 11:45 am 6.0 ICPS Program (Perrott)
11:45 am - 12:00 pm 7.0 Publications Activities (Konstan)
12:00 pm - 12:45 pm  8.0 Viability Reviews Recommendations
8.1SIGACCESS SlidesViabilityReach
8.2 SIGACT SlidesViabilityReach
8.3 SIGAda SlidesViabilityReach 
1:15 pm - 2:00 pm Viability Reviews Continued
8.4 SIGCAS SlidesViabilityReach
8.5 SIGCSE SlidesViabilityReach
8.6 SIGDA SlidesViabilityReach
2:00 pm - 2:15 pm 9.0 SIGLOG Proposal to Charter (Shankar) ProposalBudgetSlides
2:15 pm - 2:45 pm 10.0 DL App Demo (Graves)
10.0.1 Android App                                      10.0.2 iPhone App
2:45 pm - 2:55 pm Break
2:55 pm - 3:10 pm 11.0 Webinar Programs (Tracz) Report
3:10 pm - 3:30 pm 12.0 SGB EC Administrative Reports                          
12.1 SGB EC Update (Altman) Report
12.1.1 Survey Results from the last SGB MeetingM
12.1.2 Retreat
12.1.3 CCS/NSA Issue
12.1.4 History Committee Report
12.2 SGB Elections (Hanson) Report
12.3 Full Inclusion Task Force Report (Harper) Slides
3:30 pm - 4:00 pm 13.0 Best Practices Relationship with Steering Committees (Van der Veer) Report
 

ACM Case Studies

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.

The DevOps Phenomenon

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.