Policy on Authorship
Anyone listed as Author on an ACM paper must meet all the following criteria:
- they have made substantial intellectual contributions to some components of the original work described in the paper; and
- they have participated in drafting and/or revision of the paper; and
- they are aware that the paper has been submitted for publication; and
- they agree to be held accountable for any issues relating to correctness or integrity of the work.
Other contributors may be acknowledged at the end of the paper, before the bibliography, with explicitly described roles, preferably using the roles found in the CASRAI Contributor Roles Taxonomy at http://casrai.org/CRediT.
Approved January 2016
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.
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.