Most community activities are organized into a variety of Special Interest Group (SIG).
KubeSphere SIGs are organizations responsible for the design and implementation of some relatively large architectural aspects of the overall KubeSphere project. SIGs operate with a fair amount of autonomy within the broader scope of the project.
Generally, SIGs focus on specific technologies and features. For example, the storage SIG primarily focuses on design, integration and development for the Kubernetes-based storage within KubeSphere.
Leads are responsible for running a SIG. Running the group involves a few activities:
-
Meetings. Prepare the agenda and run the regular SIG meetings. Ensure the meetings are recorded, and properly archived on YouTube.
-
Operation. Operate the related Slack channel and GitHub issue, make sure the questions and proposals are answered in time.
-
Notes. Ensure that meeting notes are kept up to date. Provide a link to the recorded meeting in the notes. The lead may delegate note-taking duties.
-
Roadmap. Establish and maintain a roadmap for the SIG outlining the areas of focus for the SIG over the next three months.
The community design process is done in open way. SIGs should communicate primarily through the public tools, through design documents in the SIG’s folder, through GitHub issues, and GitHub PRs. Avoid private emails or messages when possible.
In general, SIGs operate in a highly cooperative environment. The members of a SIG discuss designs in the open and take input from the community at large when making technical choices. The SIG leads are ultimately responsible for setting the direction of the SIG and making the technical choices affecting the SIG.
The SIGs at present are:
Other than the sig channels, we have several general channels.
- users #kubesphere-users
- contributors #contributors
- general #general
There are several non-English channels for local communities.
- Chinese #community-china
- Turkish #turkiye-toplulugu-genel