Student Chapters: Getting Started
A Student chapter serves as a gateway to forums, panel discussions, and symposia that further a student's professional development. Preparation and presentation of technical reports and papers and cooperative efforts on research projects allow students to test their technical expertise.
* Entries made during the application process may be saved and completed at a later time by visiting the URL sent to the chapter email address.
Step 1: Enter chapter name, chapter email address, chapter type, and chapter sub-type.
Step 2: Enter the names of the individuals to serve as Chair, Vice Chair and Treasurer. These individuals must be ACM Student Members. In addition, a Faculty Sponsor with an ACM Professional Membership is required.
Step 3: Enter chapter contact information (postal address and phone number).
Step 4: Enter the names of at least ten (10) individuals willing to carry out the chapter's mission and participate in activities. A CSV file (comma-separated values) containing the last name, middle initial, first name, and email addresses of these members will be required through the automated chartering application.
Example: "Doe","John","firstname.lastname@example.org"You may enter each member name individually.
Once the completed application is submitted, it will be reviewed by the Local Activities Manager within 5-7 business days.
FOR UNITED STATES CHAPTERS: The IRS requires chapters operating in the United States to have an Employer Identification Number (EIN). The EIN will serve as proof of a chapter’s nonprofit status and allow ACM to include the chapter in our annual group filing with the IRS. ACM will request an EIN on your behalf which you will receive upon chartering.
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.
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.
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.