How to Create and Kickoff a Special Interest Group (SIG)

Proposing a SIG

As explained in the Bytecode Alliance Technical Steering Committee charter, any member of the Bytecode Alliance can propose the creation of an Interest Group.

• Write a proposal to create the SIG, clearly identifing its scope and goals, and list the member(s) supporting its creation. It is helpful to also have the proposal suggest willing Chairpersons for the SIG.
• Submit the proposal as a pull request to the SIGs directory of the governance repository of the Bytecode Allicance GitHub organization with a request for members to comment to be added as a supporting member to the proposal. TSC has the approval authority for the SIG. For an example, see the SIG-docs pull request.
• The TSC will consider the proposal and make a decision in a reasonable timeframe. It may adopt the proposal as made, but it can also modify the proposal if it believes it necessary. If approved the TSC will formally appoint one or more Chairs, who should follow the steps below to establish the SIG.

Establishing a SIG

Bytecode Alliance SIGs operate transparently and in full public view, open to participation by all. Approved SIGs therefore require a variety of resources to support their operation. For help with any of these contact David Bryant, Bytecode Alliance Executive Director, at [e-mail]

• Create a Google Group for the SIG within the Bytecode Alliance Google Workspace, allowing easy communication and sharing of materials among SIG members
• Create a subfolder for the SIG in the SIGs folder of the Bytecode Alliance governance repository
  • Add the approved proposal for the SIG to its subfolder, making sure the stated scope, goals, and members are up to date.
  • Update the README in the overall SIGs subfolder to include the new SIG with its Chair(s).
• Ensure SIG Chairs are added to the sig-admin Google Group to get admin information and access, such as in organizing Zoom meetings, access meeting recordings, update the Bytecode Alliance public calendar, etc.
• Create a channel for the SIG on the Bytecode Alliance Zulip server
• Add SIG Chairs as maintainers to the Bytecode Alliance meetings repository so they can manage a subfolder there for the SIG's meeting agenda, notes, presentations, etc.
  • Create the subfolder for the SIG, and add a README that summarizes general information about attending SIG meetings.
  • Update the README in the meetings repo to include the new SIG. As soon as the SIG Chair(s) are appointed please identify them in the repo README as well.
  • Add meeting agegnda and notes to the subfolder as meetings are planned and occur, typically organized by year.
• Add SIG meetings to the Bytecode Alliance public calendar. Include important details on joining the meeting or a link to where those details may be found.
• Announce the new SIG on Zulip in #general

Running SIG Meetings

The following are minimum requirements of running a SIG:

• All meetings should be public
• Attendance and notes should be taken at all meetings
• Meetings should be recorded if practical and uploaded to Bytecode Alliance YouTube in a new channel for the SIG. Note, check "No it is not made for kids" when uploaded.
• Meeting notes should publicly available and easy to find, either by including them in the SIG's subfolder in the meetings repo or, if elsewhere, directly linked to from within that subfolder.

The Bytecode Alliance maintains a Zoom account to enable video meeting support and recording for all its SIGs.

Co-chair onboarding

• Add to sig-admins Google Group
• Add to the Bytecode Alliance 1Password Team account so can access:
  • SIG Admin Zoom credentials to manage video meetings and meeting recordings
  • YouTube credentials to upload videos
  • Public Events calendar to schedule and maintain SIG meetings