HOW TO START A SPECIAL INTEREST GROUP (SIG)

Process for Starting a SIG

Prior to submitting a formal proposal to the SIG Governing Board Executive Committee (SGB EC) it is mandatory that proposers provide some preliminary information on the potential SIG.

After SGB EC reviews the information, it will determine what the next steps are for the development process.

In some cases, a formal proposal will be requested and in others, proposers may be asked to work within an existing SIG for a period of time to determine the level of interest for the new specialty.

Preliminary Information Instructions

To get started, the following preliminary information / outline of the anticipated activities envisioned for the group should be sent to  Donna Cappo.

The SGB EC will find it most helpful if your outline includes:

  1. Primary focus of this special interest group with as much detail as possible
  2. Primary audience/primary need to be served
  3. Initial activity to be undertaken by the group (publication, conferences, workshop, etc.)
  4. Overlap issues with other ACM SIGS
  5. Listing of the core group of volunteer leaders that would lead the SIG

Please feel free to contact Donna Cappo if you have any questions.

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.

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.

The DevOps Phenomenon

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.