We seem to have two different ways people need to organize, and only one term for them.

1. A broad group of people looking to add or affect technical change in the project in some way. This group more closely adheres to the Wikipedia definition of a SIG as a "community within a larger organization with a shared interest in advancing a ... technology where members cooperate to affect or to produce solutions... and may communicate, meet, and organize..."

2. A focused group of people working on a functional area of the project, who create processes and get things done. These might be called "teams" or something similar. There is a project history with that, the "Core Team" was used to describe the central group of people creating processes/`tools, and getting things done.

I'm thinking of this from a community architect perspective. Right now it's confusing how the one term fills two things. A SIG is "bring your own technology to integrate with CentOS" and also "the way we to contribute with skills to the project." It looks like a pretty high bar for someone who wants to help write some documentation or operate some infrastructure.

The intention is for potential contributors to more clearly see how they can get involved.

The actions here would be:

• Agree there is a distinction.
• Write up the distinction into the wiki/SpecialInterestGroup page.
• Add a wiki page that describes what a team is, how to form one, how to join one.
• Have groups look at themselves as they exist or are chartering, and be(come) the thing they really are.

OR

• Decide it's not worth worrying about.