In January 2011 Sorel Reisman the first time introduced Special Technical Communities (STCs) to the public: «By the end of 2011, we’ll have launched pilot Special Technical Communities in social networking, could computing, education, software engineering, and green computing.» [1]

In June 2011 Dejan Milojicic and Phil Laplante provide an in-depth review of STCs and an overview of existing (pilot) STCs [2]. STCs offer a new engagement model for IEEE CS members and the much broader computer practitioner world to collaborate for their individual and mutual benefit and to advance technical topics to the benefit of the profession. STCs are intended go beyond traditional membership and activities and open new outlets for the membership to create and distribute intellectual property (IP). They will create new revenue-generating opportunities, new products, and services and enrich professional activities (e.g., newsletters, sharing of best practices). Finally, STCs will help strengthen governance by allowing all members to feel closer to decision-making processes through the dynamic organizational structure.

The principles behind an STC can be summarized as follows.

• Elasticity: STCs will be easy to create, grow, contract, and retire as member needs warrant; comprised of CS and IEEE members and non-members with a shared interest; and with different levels of engagement: news feeds, blogging, information exchanges, reviews, newsletters, virtual conferences, etc. 
• Self-service: STCs will require little or no staff support; use up-to-date technology, integrate with social networking tools, such as blogs, twikis, alerts, portals and allow for personalization and presence (e.g., in Facebook, LinkedIn, Twitter).
• Customization: STCs will integrate into CS existing IP and contribute to it; they will promote publications, technical councils, education, chapters and standards in a holistic manner. They will further link to other organization and services relevant to the underlying STC.