Outstanding Chapter Community Service Submissions

Thank you to our panel of judges for agreeing to help us out!

We hope that this set up will allow for a smooth and efficient judging process. Following each list of submissions is the rubric for judging that specific category. If you have any questions or concerns throughout this process, please do not hesitate to contact Sunita Jaswal, local_activities@hq.acm.org.

Listed below is a brief description of what we expect, followed by each chapters' submission.

Outstanding Chapter Community Service - 11 Chapter Submissions

Chapters should apply to the Outstanding Chapter Community Service category if they have made significant contributions to their communities through one major service project or a series of smaller projects. They should tell us about each project, who it served, and how many people participated. They should include why this project was of interest to their chapter.

ABES ACM Student Chapter

Ain Shams University ACM Student Chapter

Bharati Vidyapeeth's College of Engineering ACM Student Chapter

BITS Pilani-Rajasthan ACM Student Chapter

Michigan State University ACM-W Student Chapter

North American University ACM Student Chapter

PSUT ACM Student Chapter

Temple ACM Chapter

University of Cincinnati ACM-W Student Chapter

University of Virginia ACM-W Student Chapter

UPES ACM Student Chapter

Outstanding Chapter Community Service Scoring Rubric

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.