ACM SGB Meeting Materials Agenda, February 11, 2008
SIG Governing Board
Monday, February 11th, 2008
8:30 am - 4:00 pm
| 8:30 am - 9:00 am | Continental Breakfast | ||
| 9:00 am - 9:20 am | 1.0 | Welcome | |
| 1.1 | Welcome, Introductions (Konstan, Hanson) | ||
| 1.2 | History Committee Introductions and Update (Hall, Wise) | ||
| 9:20 am - 9:35 am | 2.0 | Opening Remarks from Stu Feldman | |
| 9:35 am - 10:15 am | 3.0 | Report from the ACM CEO (White) | |
| 10:15 am - 10:45 am | 4.0 | SIGDOC Program Review (Mehlenbacher): Viability Slides | |
| 10:45 am - 11:00 am | Break | ||
| 11:00am - 12:00 pm | 5.0 | SIGAPL Program Review (Walker, LaRocque): Slides | |
| 12:00 pm - 12:30 pm | 6.0 | Education Board Report (McGettrick): Activity Sheet | |
| 12:30 pm - 1:00 pm | 7.0 | CACM Update (Vardi) | |
| 1:00 pm - 2:00 pm | Lunch | ||
| 2:00 pm - 2:30 pm | 8.0 | SGB EC Administrative Report (Konstan) | |
| 8.1 | New SIG Slides | ||
| 8.2 | Other | ||
| 2:30 pm - 3:00 pm | 9.0 | CSTA Report and Discussion(Stephenson): Slides | |
| 3:00 pm - 3:15 pm | Break | ||
| 3:15 pm - 4:00 pm | 10.0 | Best Practices Session | |
| 10.1 | PC Meetings | ||
| 10.2 | Other Items |
Publish with ACM
ACM's prestigious conferences and journals are seeking top-quality papers in all areas of computing and IT. It is now easier than ever to find the most appropriate venue for your research and publish with ACM.
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” 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.
