...
- 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 from the Center can be part of a SIG based on expertise and interest
- Meet once every week or two to share updates, or just chat on Slack
- 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 and subscribe to a Slack channel to learn more about it
- Low pressure - choose your own topics and goals
- Members of the SIG choose:
- A lead in charge of organizing the team and reporting back to the FGSoftware 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
...
This document serves as a starter kit for Software Special Interest Groups , and to provide provides some general guidelines for someone starting up a new SIG.
...
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 of the project are aligned with topics that need more discussion.
SIGs serve as a mechanism to bring together folks who don’t share a project , but who do share a common interest in a topic that could be beneficial to benefit NCSA, SD, or the projects within.
...
Why do this as a SIG and not just meet separately?
- Written updates are shared with SD during bi-weekly meetings
- 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
...
- 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 regularly 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 follow follows up as appropriate
Outputs / Goals
Goals are not required up front, upfront and can be decided by the group as the discussion progresses
If the group produces significant outputs or other discoveries are produced by the group, it is recommended to present their work/findings in a relevant platform like Software Directorate lightning talks or Software Seminar
...
Some examples of previous groups can be found here in the Active or Archived sectionshere.