ACM SGB Meeting Materials Agenda, September 20, 2010
Monday, September 20, 2010
8:30 am – 4:00 pm
| 8:30 am – 9:00 am | Continental Breakfast |
| 9:00 am – 9:30 am |
1.0 Welcome
1.1 Welcome, Introductions (Hanson, Sears)
1.2 Welcome, ACM President (Chesnais)
|
| 9:30 am – 10:15 am |
2.0 Report from the ACM CEO (White)
|
| 10:15 am – 10:30 am |
Break
|
| 10:30 am – 11:15 am |
3.0 SIG Proposals
3.1 Process (van de Veer)
3.2 Special Interest Group on Bioinformatics
3.3 Special Interest Group on Health Informatics
|
| 11:15 am – 12:00 am |
4.0 Viability Reviews
|
| 12:00 am – 1:00 pm | Lunch |
| 1:00 pm – 1:20 pm | 5.0 Distinguished Speakers Program Update (Molly Stevens) |
| 1:20 pm – 1:50 pm |
6.0 Publications Advisor Report (Konstan)
|
| 1:50 pm – 2:20 pm |
4.0 Viability Reviews Cont’d
|
| 2:20 pm – 2:30 pm | Break |
| 2:30 pm – 3:15 pm |
7.0 VAT Discussion (Martin Pinsonnault)
|
| 3:15 pm – 3:30 pm |
8.0 SGB EC Administrative Report (Hanson)
|
| 3:30 pm – 4:00 pm |
Best Practices Session (All)
|
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.
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.
