ACM Policy Award
How to Nominate
The ACM Policy Award honors the contributions of an individual, or a small group, who has had a significant impact on the formation or execution of public policy related to computing. It may recognize establishment of an innovative educational or advisory program in policy, the development of technology policy organizations or resources, or other notable policy activities affecting the computing community and/or the general public. The biennial award is presented at the June ACM Awards Banquet in even-numbered years. It is accompanied by a prize of $10,000 plus travel expenses to the banquet.
January 15, 2020 - End of Day, Anywhere on Earth (AoE), UTC -12
The achievement cited must represent a major policy innovation or a significant ongoing engagement that has had broad influence on computing policy.
Nominations will be reviewed for the quality and impact of the individual’s personal contributions. If a small group is being nominated, the information must spell out why these particular individuals should be recognized.
Nominations for the ACM Policy Award should be submitted using the online nomination form. Submitted materials should explain the contribution in terms understandable to a non-specialist. Each nomination involves several components:
- Name, address, phone number, and email address of the nominator (person making the nomination). The most appropriate person to submit a nomination would be a recognized member of the community who is not from the same organization as the candidate and who can address the candidate's impact on the broader community.
- Name, address, and email address of the candidate (person being nominated). It is ACM's policy not to tell candidates who has nominated or endorsed them.
- Suggested citation if the candidate is selected. This should be a concise statement (maximum of 25 words) describing the policy achievement and the contribution of the individual(s) being recognized. Note that the final wording for awardees will be at the discretion of the Award Committee.
- Nomination statement (500-1000 words in length) addressing why the candidate should receive this award. This should spell out what policy achievements are being recognized, what the implications are for the computing community and general public, and why this particular individual/group merits recognition for the contributions.
- Copy of the candidate's CV, listing publications, patents, honors, service contributions, etc.
- Supporting letters from at least 2, and not more than 4, endorsers. Endorsers should be chosen to represent a range of perspectives and institutions and provide additional insights or evidence of the candidate's impact. Each letter must include the name, address, and telephone number of the endorser, and should focus on the accomplishments to which that endorser can attest and place in context. The nominator should collect the letters and bundle them for submission.
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.
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.