SIG Center
Meeting Guide

Introduction

The openFuyao open-source community organizes development and version release activities based on special interest groups (SIGs). Its main technical products are delivered in the openFuyao community releases, with four versions each year in March, June, September, and December. After each version release, the openFuyao open-source community holds development planning meetings for the next version within each SIG. Each meeting lasts for half a day to one day and aims to discuss the plans, work items, task assignments, and priorities of each SIG for the next six months. The openFuyao open-source community provides venues and technical support for the planning meetings of each SIG.

Type

Single-SIG Meeting
Meeting held within a single SIG. These meetings are organized by the SIG maintainer, whose responsibilities include collecting topics, arranging agendas, chairing discussions, and providing meeting minutes.
Working Group Meeting
Collaborative meeting held across SIGs. The maintainers of involved SIGs need to contact the version planning meeting organizer in advance by email or other means to arrange the venue and organize the meeting, including collecting topics, arranging the agenda, chairing discussions, and providing the meeting minutes.

Organizing Meetings

Created with Pixso.
Collecting Requirements
Each SIG should begin collecting requirements for the next version in due course. The maintainer of each SIG creates a meeting collection directory on openFuyao Etherpad (in the recommended format: SIG name-Version name (for example, 24.09)-Planning) to collect requirements and plans for the version planning meeting, and sends the directory to the SIG version planning meeting organizer of the openFuyao open-source community.
  1. Anyone can propose requirements at SIG release meetings. You can fill in the topics in the Etherpad shared file of each SIG meeting as required. Generally, the following information is required:

    Requirement proposer

    Requirement description

    Online address for issue feedback

    Existing technical solutions or PRs

    Existing discussion minutes

  2. After requirements are collected, SIG maintainers specify the meeting agenda based on requirement factors such as type, technical difficulty, workload, and meeting time. The meeting agenda must be released in the Etherpad shared file and community mailing list at least three days before the meeting, so that participants can learn about the meeting agenda.
Created with Pixso.
Holding Meetings
Meetings are held by the version planning owner of each SIG according to the predefined meeting agenda. During the meeting, time management is required to ensure that all requirements in the meeting agenda can be discussed. Each participant needs to enter their name and GitCode ID in the attendees section of Etherpad. If a participant is absent and has not designated a representative, the requirement is deemed to be automatically withdrawn.
  1. The discussion of each topic can be divided into the following phases:

    Requirement presentation: The requirement proposer states the requirement, including requirement objectives, requirement sources, proposed technical solutions, and previous discussions and results. Other attendees should not interrupt during this phase.

    Discussion: All attendees discuss the requirement. The host records the opinions of all parties and key opinions.

    Conclusion: Once consensus is reached, the host outputs the conclusion of the topic based on the consensus. If no consensus is reached, the specific time for the next discussion should be negotiated.

  2. After all topics are discussed, the SIG maintainer team prioritizes and assigns tasks based on the discussion results and SIG situation. Contributors claim tasks for task assignment.
Created with Pixso.
Providing Meeting Minutes
The version planning owner of each SIG shall complete the meeting minutes within one week after the meeting and release the meeting minutes on Etherpad and SIG, and in the TC and release-management SIG mailing lists. The meeting minutes must contain the following information:
  1. All topics discussed and their conclusions
  2. Owners of each task in the next version
  3. Work priority of the next version