ACM SGB Meeting Materials Agenda, September 20, 2010

SIG Governing Board
Monday, September 20, 2010
8:30 am – 4:00 pm
Location: Financial Ballrooms I & II
 
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
4.1 SIGARCH (Burger) Slides Program Review Reach Awards DL Revenue 
4.3 SIGCOMM (Schulzrinne) Slides Program Review Reach Awards DL Revenue 
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
4.5 SIGITE (Stockman) Slides Program Review Reach DL Revenue
4.6 SIGMETRICS (Williamson) Slides Program Review Reach Awards DL Revenue 
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)

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.

Publish your work

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.