Chapter Membership Requirements

The ACM Bylaws specify the membership requirements for Professional and student chapters:

Chapter Management

Each ACM General Interest chapter must have a minimum of three officers at all times; a Chair, Vice-Chair, and Treasurer. The bylaws received by all chapters contain valuable information as to the individual duties all officers should execute; all amendments to the bylaws must receive approval by the ACM Chief Operating Officer. These approvals must be obtained before any amendment may be distributed for a vote to the members of the chapters.

The officers of a chapter will be elected and vacant offices filled as provided in its bylaws. All officers in student chapters must be ACM members. All officers in professional chapters must be ACM Members."

As chapters are subsidiaries of the ACM and share the non-profit status thereof, membership is required for indemnification against damage and loss:

BYLAW 16: INDEMNIFCIATION

"The Association shall indemnify any person who was or is a party to any threatened, pending or completed action, suit or proceeding, whether civil, criminal, administrative or investigative, by reason of the fact that the person is or was a member of the Council or an officer of the Association."

Chapter Members

In addition to the chapter officers, chapters must consist of chapter members. To be considered active and viable by ACM, chapters must have a minimum of 10 members. Non-officer members are not required to have ACM membership, but ACM must be notified of all active chapter members by adding them through the chapter's web account. Chapters that fail to meet this minimum membership requirement jeopardize their status with the Association.

Additional Requirements

Student chapters must have a faculty sponsor. This sponsor must have ACM Professional Membership.
Officers of SIG chapters must have both ACM and the respective SIG membership.

For Practitioners

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.

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.