A Practical Guide to the Responsibilities of ACM Chapters
ACM fosters growth in the computing community through its support of more than 950 professional, student and local Special Interest Group chapters worldwide. These chapters establish a local presence for ACM in international cities large and small and seek to disseminate knowledge and advance the field of computing by sponsoring state-of-the-art seminars on pressing issues in information technology, conducting volunteer training workshops, hosting lectures by highly regarded computer professionals, and more.
Through its sponsorship of chapters, ACM facilitates the exchange of ideas among members from all backgrounds and from all facets of computing, from academia to research to business and industry. The list below lays out items that comprise the nuts and bolts of the responsibilities chapters face in many areas, including finance, membership, and conferences. Please click on any item to learn more.
- Financial Responsibilities and Reporting Requirements - Chapter's Relationship to the IRS
- Responsibilities of Chapter Officers
- Membership Requirements
- Chapter Meetings
- Chapter-Sponsored Conferences
- Chapter Events Form
- Conference TMRF (.doc) and budget spreadsheet (.xls)
- Certificates of Insurance
- Chapter Outreach and Communication
- Member Recruitment
- ACM Headquarters Support for Chapters
- Chapter Publications
- Certificate of Completion
- Corporate Sponsorship
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.
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.