Formerly: Focus Groups (FGs)

1. Introduction

This document serves as a starter kit for Software Special Interest Groups and provides some general guidelines for someone starting up a new SIG or interested in joining SIG.

  • SIG can be created as needed when shared interest arises around a specific topic
    • Examples: research new software stacks, new technologies, tech training, improve knowledge in a certain area, areas for future proposal development
  • Anyone can join SIG based on expertise and interest
  • SIG activity frequency and activity formats are decided by SIG members
    • SIG can choose to meet once every week or two to share updates, or just chat on Slack, all depends on the SIG member's collective agreements
    • You can pick topics that overlap with work you are already doing or will be doing on a project
    • You can also choose a new topic that you are interested in learning more about it
  • Low pressure - choose SIG based on your own passions and goals
  • Members of the SIG choose:
    • A lead in charge of organizing the team and reporting back to the Software Working Group
    • No set time frame is required - large topics can have long-term groups
    • No concrete deliverables are required - goals or milestones are encouraged

2. What is a Special Interest Group?

When like-minded folks share a project, they have the time to pursue new areas and help cross-train each other. This is especially nice if the project's research areas are aligned with topics that need more discussion. 

SIGs serve as a mechanism to bring together folks who don’t share a project but share a common interest in a topic that could benefit NCSA, SD, or the projects within.

A small amount of funding may be available upon request to further these interests.

3. Incentives

Why do this as a SIG and not just meet separately?

  • SIG leader will share updates with SD members
  • Leveraging past / present knowledge from other SD members
  • Additional publicity and recruitment options
  • Opportunity to present findings to larger SD
  • Chance to elevate and showcase your project

4. For new SIGs:

Step 1. Choose a Topic

Some topics may emerge naturally through SD discussions:

  • “I wish I knew more about _____”
  • “I’d like to get together to discuss using ____ across projects”
  • “I think ____ would be a really good technology for us to learn and leverage”
  • “We would like to start training more experts using ____”

Please add your topic to the running SWG Topics spreadsheet to keep track of it. You may also find existing SIGs that match your interest there. You can find Special Interest Group topics by filtering the "Category" column to "Special Interest Group":

Step 2. Create a Slack Channel + Wiki Page

  • Once you have a topic of interest, please create a Slack channel or utilize the existing Slack channel for group communication.
    • If you want to know if your SIG has an existing Slack channel or not, please ask software working group members for help
  • Create a wiki page under this parent - this page can be the one-stop place for any outputs
    • e.g. documentation, meeting notes, reports, etc

Step 3. Advertise

  • It will be good to advertise the group within the Software Directorate or sometimes at the NCSA level, depending on the scope of the topic.
    • It is recommended to announce the start of the group in at least #announce , #ncsa-discussion, and #sd-general Slack channels.
  • If any help is needed, please reach out to Lisa Yanello or the Special Interest Groups Activity Leads.

5. Group Activities

  • It is recommended to have a Slack channel or some other dedicated communication platform for the Special Interest Group.
  • Live meetings are encouraged as well, if there is enough to share updates regularly
  • The Special Interest Group members need to communicate with each other to make decisions and share updates within the group.
  • Many tasks and explorations may be completed offline and wouldn't require a meeting.
  • Document meeting notes/action items and follows up as appropriate

6. Outputs / Goals

Goals are not required upfront and can be decided by the group as the discussion progresses

If the group produces significant outputs or other discoveries, it is recommended to present their work/findings in a relevant platform like Software Directorate lightning talks or Software Seminar

  • Hands-on session/tutorial
  • Round table discussion
  • Future proposal or project idea
  • Lightning talks at SD or NCSA all-hands meeting
  • Presentation at upcoming Software Seminar or conference 

7. Examples

Some examples of previous groups can be found here in the Active or Archived sections.

  • No labels