Code
EN
SIG
Meeting Guide

Meeting Introduction

The MindSpore community organizes development and community work based on special interest groups (SIGs). SIGs hold one or two regular meetings every month to discuss the progress, requirements, tasks, and priorities of SIGs.

Regular SIG meetings comply with the open source and openness principles. The discussion processes such as topic collection, technical discussion, and meeting minutes are open to the public.

Meeting Types

Meetings of a Single SIG
The meetings of a single SIG are organized by the SIG maintainer, including collecting topics, arranging agendas, chairing discussions, and outputting meeting minutes.
Meetings of a Working Group
The working group (across SIGs) holds meetings for collaboration. If two or more SIGs plan to hold a meeting together, SIG maintainers need to communicate with each other in advance to determine an organizer to coordinate the meeting, including but not limited to collecting topics, arranging agendas, chairing discussions, and outputting meeting minutes.

Meeting Organization

Requirement Collection

Each SIG regularly starts a meeting to collect requirements and understand the progress three to five days in advance. The maintainer of each SIG creates a meeting collection directory (in the recommended format: SIG name-meetings) on the MindSpore Etherpad platform at https://etherpad.mindspore.cn to collect developer requirements and plans, and sends the meeting directory to all members of the SIG. (Reference template: https://etherpad.mindspore.cn/p/sig-xx-meetings)

  • Anyone can raise requirements at SIG meetings. You can fill in the topics in the Etherpad file of each SIG meeting as required. Generally, the following information is required:

    • Requester
    • Requirement description
    • Online address for issue feedback (if any)
    • Existing technical solutions or PRs (if any)
    • Existing discussion minutes (if any)

  • After requirements are collected, the meeting organizer of the SIG specifies the meeting agenda based on the collected requirements (such as the type, technical difficulty, and workload) and meeting time. The meeting schedule must be released on the Etherpad shared file and community mailing list two to three days before the meeting, so that participants can learn about the meeting agenda.

Holding Meetings

Meetings are held by the meeting organizer or owner of each SIG according to the predefined meeting agenda. During the meeting, time control is required to ensure that all requirements in the meeting agenda can be discussed. Each participant needs to enter their name and Gitee ID in the attendees section of Etherpad. If a participant is absent and no proxy is designated, the requirement is deemed to be automatically abandoned.

  • The discussion of each topic can be divided into the following phases:

    1. Requirement statement: The requirement initiator states the requirement, including requirement objectives, requirement sources, proposed technical solutions, and previous discussions and results. Other listeners are not allowed to interrupt the requirement statement phase.
    2. Discussion: All participants discuss the requirement. The host records the opinions of all parties and key opinions.
    3. Conclusion: After a 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.

  • 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.

Meeting Minutes

The meeting host of each SIG shall complete the meeting minutes within one week after the meeting and release the meeting minutes on Etherpad and SIG, dev, and TC mailing lists. The meeting minutes must include but not limited to the following information: