====== New SIGs ======

===== Expectations =====

When starting a SIG, we expect:

  - You should have concrete goals for your SIG, and a timeframe for hitting them 
    - Even if that goal is just "learn X" or "talk about Y", try to find a target of some kind
  - Your SIG should meet at least once every two weeks
  - You should be prepared to run your SIG for at least a full academic year

===== How to create a new SIG =====

  - Get a bunch of people together to show that people are interested in your proposed SIG.
     - At least 4, but the more the better
  - Talk to an ACM officer about starting the SIG
  - Write a proposal document and email it to the officers' mailing list. Include the following information:
      - Goals and milestones for the next year
      - A plan for your first few meetings
      - What resources you want to request from the ACM
  - Bring the topic of starting a new SIG up at the next ACM or ACM council meeting, **after** completing the previous steps
  - Once you get your SIG approved, get SIG leader level access to ACM systems and services
  - Have the webmaster add your SIG's page on the website to the official active SIGs list, and have a Slack admin create a channel for your SIG
  - Put together a presentation of no more than 2 PowerPoint slides, and present them at the next GBM

===== National SIGs =====

Currently, none of our SIGs are formal chapters of the national ACM-SIGs. The full list of ACM-SIGs can be found [[https://www.acm.org/special-interest-groups/sigs-by-knowledge-area|here]]. The [[https://www.acm.org/chapters/students/how-to-start-a-sig-student-chapter|process of becoming an ACM-SIG chapter]] is significantly more involved, and involves registering as a separate financial entity. It's probably more trouble than it's worth. Still, let an officer know if you're interested.