Merge branch 'master' of https://github.com/kubesphere/community into s2i_trigger

README.md

@@ -10,8 +10,8 @@ Before you start contributing, read our [Code of Conduct](code-of-conduct.md) an
 
 ## Special Interest Group
 
-Through SIGs, the KubeSphere community members collaborate and contribute to topics of long-term interest for KubeSphere and its community. Generally, SIGs can be either vertically focused on particular components and features, or span multiple functional and technical domains. There are some SIGs in KubeSphere community. Please read [KubeSphere Special Interest Group](sigs.md) for details.
+Through SIGs, the KubeSphere community members collaborate and contribute to topics of long-term interest for KubeSphere and its community. Generally, SIGs can be either vertically focused on particular components and features, or span multiple functional and technical domains. There are some SIGs in KubeSphere community. Please read [KubeSphere Special Interest Group](sigs.md) for details. Each SIG may have several subprojects to work on. For instance, SIG observability has four subprojects, i.e., Logging, Monitoring, Alerting and Notification.
 
 ## Working Group
 
-Working Group (WG) facilitates discussions and work on short-lived, concrete topics that either result from the work of SIG groups or the community members initiate directly. Each SIG can propose a new WG based on the detailed requirements and issues.
+Working Group (WG) facilitates discussions and work on cross-SIGs. For example, we may create a WG for the design of multi-tenancy monitoring across the SIG observability and the SIG multi-tenancy. Each SIG can propose a new WG based on the detailed requirements and issues.

ROLES.md

@@ -0,0 +1,40 @@
+# KubeSphere Community Roles
+
+This document defines a set of roles for the community individuals to join. and describes the requirements, responsibilities and privileges of each role to join or stay in.
+
+## Contributor
+
+You need to satisfy the following requirements to become a contributor.
+
+- Anyone who has at least one non-trivial PR merged into any project under [KubeSphere organization](https://github.com/kubesphere) becomes a contributor.
+
+You are also encouraged to help the community in the following ways since it is important for you to become a KubeSphere member.
+
+- Answer questions from the community users in GitHub issues, forum or any communication channels.
+- Help test the project or report bugs.
+- Write blogs or technical documents including source code analysis to help users better understand and use KubeSphere.
+- Help improve KubeSphere user guide.
+
+## Member
+
+You need to have notable contribution to the project to become a member of KubeSphere community. 
+
+- Active contribution to the project.
+- Nominated by the current member of the project and approved by the lead of the project.
+- Help review PR from other contributors.
+
+## Owner / Lead
+
+A lead is also the member of the project who is an experienced and active reviewer of the project. 
+
+- Significant contribution to the project.
+- Domain expert of any area of the project.
+- Nominated by the current member and approved by TOC.
+
+As a lead, you have the following responsibilities.
+
+- Review PR from other contributors.
+- Approve PR
+- Triage issues, set labels on issues.
+- Manage code repository and related resources.
+- Run SIG and working group.

TOC.md

@@ -26,4 +26,4 @@ Avatar | Name | GitHub Account
 
 ## Meetings
 
-The KubeSphere technical committee meets bi-weekly on every other Tuesday mornings. The meeting notes are open to public.
+The KubeSphere technical committee meets bi-weekly on every other Tuesday mornings. The [meeting notes](https://docs.google.com/document/d/1O8YQYKynTVOs9AMoaBRBT1mdUsxtLKAer9pTwjlrod0/edit#) are open to public.

contribution/design/README.md

@@ -1,3 +0,0 @@
-# Design Documentation
-
-This is the design documentation for each SIG.

contribution/design/sig-observability/README.md

@@ -1,3 +0,0 @@
-# Design Documentation
-
-This is the design documentation for observability SIG.

developer-guide/concepts-and-designs/README.md

@@ -8,19 +8,19 @@ Concepts and Designs help you to learn and understand the KubeSphere and the lan
 
 ## DevOps
 
-- [KubeSphere DevOps Pipeline Overview](sig-devops/devops-pipeline-overview.md): explains the architecture and key components of KubeSphere pipeline.
-- [KubeSphere S2I and B2I overview](sig-devops/s2i_b2i_overview.md): explains the workflow and principle of KubeSphere S2I (Source-to-Image) and B2I (Binary-to-Image).
+- [KubeSphere DevOps Pipeline Overview](../../sig-devops/concepts-and-designs/devops-pipeline-overview.md): explains the architecture and key components of KubeSphere pipeline.
+- [KubeSphere S2I and B2I overview](../../sig-devops/concepts-and-designs/s2i-b2i-overview.md): explains the workflow and principle of KubeSphere S2I (Source-to-Image) and B2I (Binary-to-Image).
 
 ## Observability
 
 ### KubeSphere Monitoring
 
-- [Overview](sig-observability/kubesphere-monitoring.md#Overview): explains the architecture and key components behind the monitoring system.
-- [Setup](sig-observability/kubesphere-monitoring.md#Setup): introduces manifests related to Prometheus setup.
+- [Overview](../../sig-observability/concepts-and-designs/kubesphere-monitoring.md#Overview): explains the architecture and key components behind the monitoring system.
+- [Setup](../../sig-observability/concepts-and-designs/kubesphere-monitoring.md#Setup): introduces manifests related to Prometheus setup.
 
 ### KubeSphere Logging
 
-- [Overview](sig-observability/kubesphere-logging.md#Overview): explains the architecture and key components behind the logging system.
-- [Log Collection and Forward](sig-observability/kubesphere-logging.md#Log-Collection-and-Forward): introduces logging agent and the sidecar-based solution for collecting application logs on disk.
-- [Log Store and Management](sig-observability/kubesphere-logging.md#Log-Store-and-Management): introduces long-term log storage and management.
-- [Log Search, Export and Visualization](sig-observability/kubesphere-logging.md#Log-Search,-Export-and-Visualization): introduces log query and reporting.
+- [Overview](../../sig-observability/concepts-and-designs/kubesphere-logging.md#Overview): explains the architecture and key components behind the logging system.
+- [Log Collection and Forward](../../sig-observability/concepts-and-designs/kubesphere-logging.md#Log-Collection-and-Forward): introduces logging agent and the sidecar-based solution for collecting application logs on disk.
+- [Log Store and Management](../../sig-observability/concepts-and-designs/kubesphere-logging.md#Log-Store-and-Management): introduces long-term log storage and management.
+- [Log Search, Export and Visualization](../../sig-observability/concepts-and-designs/kubesphere-logging.md#Log-Search,-Export-and-Visualization): introduces log query and reporting.

sig-apps/README.md

@@ -0,0 +1,15 @@
+# Apps Special Interest Group
+
+The Apps SIG is to develop most common applications to use in [App Store](../sig-appstore) of KubeSphere. The app is based on Helm and the code repo is [helm-charts](https://github.com/kubesphere/helm-charts/).
+
+## Members
+
+- Hongliang Wang ([@hlwanghl](https://github.com/hlwanghl)), Lead
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/1nRAK2U9flkz-8z7bT2-T_0VneW3w1fx1fJtB5Bu3JyU/)
+
+## Contact
+
+- Slack [#sig-apps](https://kubesphere.slack.com/messages/sig-apps)

sig-appstore/README.md

@@ -0,0 +1,15 @@
+# App Store Special Interest Group
+
+The App Store SIG is to develop an application store platform running on KubeSphere. It is based on the open source [OpenPitrix](https://github.com/openpitrix/openpitrix) project.
+
+## Members
+
+- Zhengyi Lai ([@zheng1](https://github.com/zheng1)), Lead
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/1FYxeQOiwN3jL6EPeIA71iB3gXZfNf-PhSufVaywFbxI/)
+
+## Contact
+
+- Slack [#sig-appstore](https://kubesphere.slack.com/messages/sig-appstore)

sig-architecture/README.md

@@ -0,0 +1,18 @@
+# Architecture Special Interest Group
+
+The architecture SIG is to evolve the architecture of KubeSphere. For example, there is going to be a fundamental change in terms of architecture for KubeSphere 4.0.
+
+## Members
+
+- Lu Liu ([@leoendless](https://github.com/leoendless)), Lead
+- Benjamin Huo ([@benjaminhuo](https://github.com/benjaminhuo)), Lead
+- Dan Ma ([@Ma-Dan](https://github.com/Ma-Dan)), Member
+- Ray Zhou ([@rayzhou2017](https://github.com/rayzhou2017)), Member
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/1lqL0c6SpxLxRbwVk870-9HDeGIwVodSRJV-Uh4hPemQ/)
+
+## Contact
+
+- Slack [#sig-architecture](https://kubesphere.slack.com/messages/sig-architecture)

sig-console/README.md

@@ -0,0 +1,17 @@
+# Console Special Interest Group
+
+The console SIG is the community place to develop the frontend of KubeSphere with the code repository at [KubeSphere console](https://github.com/kubesphere/console).
+
+## Members
+
+- Lu Liu ([@leoendless](https://github.com/leoendless)), Lead
+- Edisonchen ([@justahole](https://github.com/justahole)), Logging, Monitoring & Storage
+- wickyang ([liyefox](https://github.com/liyefox)), Network
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/1a2RHltQm3armW4Jf7m1aYFTjdvlqiuW5hW2-KBeLqi0/)
+
+## Contact
+
+- Slack [#sig-console](https://kubesphere.slack.com/messages/sig-console)

sig-devops/README.md

@@ -0,0 +1,16 @@
+# DevOps Special Interest Group
+
+The DevOps SIG is to design and implement the DevOps functionalities including pipeline, S2I and B2I running on KubeSphere.
+
+## Members
+
+- Jeff Zhang ([@zryfish](https://github.com/zryfish)), Lead
+- Shaowen Chen ([@shaowenchen](https://github.com/shaowenchen)), Member
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/1ZORl7ZhRlZxKXFle2LGPRJqXzlr6EDhu2A7qzjybfro/)
+
+## Contact
+
+- Slack [#sig-devops](https://kubesphere.slack.com/messages/sig-devops)

sig-devops/concepts-and-designs/jenkins-plugin.md

@@ -0,0 +1,64 @@
+# KubeSphere Jenkins Plugin
+
+As we all know,KubeSphere uses Jenkins as the CI / CD engine by default.
+Using Jenkins is like building Lego bricks. It is a combination of Jenkins plugins.
+KubeSphere also has its own Jenkins Plugin to extend the capabilities of the CI / CD engine.
+At present, we will use a Jenkins Plugin to complete multiple extension functions (the traditional method may build multiple Plugins). 
+This is because each version of KubeSphere is bundled with a specific version of Plugin, 
+so there will be no conflict between plugins. Using this method also makes it easier to install and maintain plugins.
+The plugin is currently maintained in [Jenkins github org](https://github.com/jenkinsci/kubesphere-extension-plugin).
+
+## Main functions
+
+Next we will explain the several functions that the plugin currently provides.
+
+### Custom ContainerFilter
+
+[ContainerFilter](https://jenkins.io/doc/developer/extensions/blueocean-rest-impl/) is an ExtensionPoint of Jenkins BlueOcean Plugin.
+
+KubeSphere extends this extension point to implement a specific filter in Jenkins to filter the BlueOcean API's response.
+
+
+### KubeSphere ApiToken Authenticator 
+
+[BasicHeaderAuthenticator](https://jenkins.io/doc/developer/extensions/jenkins-core/#basicheaderauthenticator) is an ExtensionPoint of Jenkins Core.
+
+This extension point allows us to implement our own authentication logic, not just using user systems such as ldap.
+
+When a user accesses the DevOps part of the KubeSphere interface, the user calls Jenkins' API (for example, triggering a build).
+At this point, KubeSphere needs a way to access Jenkins as a user.  
+
+This extension implements such functionality. When accessing the Jenkins API, users can use KubeSphere's API token for authentication.
+
+
+### KubeSphere Notification
+
+KubeSphereNotification implements multiple extension points within the Jenkins Core for event notification.
+
+Both notification methods and event types are extensible.
+Currently we have implemented a Webhook notification method, with the following event types:
+
+```markdown
+- jenkins.job.started (Events are triggered when the pipeline started)
+- jenkins.job.completed (Events are triggered when the pipeline completed)
+- jenkins.job.finalized (Events are triggered when the pipeline finalized)
+- jenkins.job.input.started (Events are triggered when the pipeline input step started)
+- jenkins.job.input.proceeded (Events are triggered when the pipeline input step proceeded)
+- jenkins.job.input.aborted (Events are triggered when the pipeline input step aborted)
+```
+
+For more detailed information we recommend you read the documentation of the plugin.
+
+## Configure the plugin
+
+Currently, the two most popular Jenkins plugin configuration methods are [Groovy Script](https://wiki.jenkins.io/display/JENKINS/Post-initialization+script) and 
+[CasC Plugin](https://github.com/jenkinsci/configuration-as-code-plugin). 
+We recommend use CasC to configure plugins. Therefore, the configuration method of CasC is implemented in our plugins.
+Detailed information can refer to the documentation of the plugin.
+
+## Plugin release
+
+The way plugins are published is no different from regular Jenkins plugins.
+You can read the official Jenkins plugin [release documentation](https://jenkins.io/doc/developer/publishing/releasing/) to publish KubeSphere Jenkins plugin.
+
+

sig-docs/README.md

@@ -0,0 +1,15 @@
+# Docs Special Interest Group
+
+The Docs SIG is to develop and maintain the documents related to KubeSphere including website, user guide, forum and so on.
+
+## Members
+
+- Pengfei Zhou ([@FeynmanZhou](https://github.com/FeynmanZhou)), Lead
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/1tyB2RDJFmfwFfO2ok9dH7ttZRICDiaogSI12Ajz9CD0/)
+
+## Contact
+
+- Slack [#sig-docs](https://kubesphere.slack.com/messages/sig-docs)

sig-installation/README.md

@@ -0,0 +1,16 @@
+# Installation Special Interest Group
+
+The Installation SIG is to develop KubeSphere installer for a variety of environment and options such as all-in-one, multi-node, install on existing K8s cluster. The code repository is hosted at [ks-installer](https://github.com/kubesphere/ks-installer).
+
+## Members
+
+- Feng Guo ([@pixiake](https://github.com/pixiake)), Lead
+- Lin Li ([@Forest-L](https://github.com/Forest-L)), Member
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/1sXMKViZ5cchbaBajRZiJsaSdMAQ1GpmDKCcq3UwT3Vg/)
+
+## Contact
+
+- Slack [#sig-installation](https://kubesphere.slack.com/messages/sig-installation)

sig-microservice/README.md

@@ -0,0 +1,15 @@
+# Microservice Special Interest Group
+
+The Microservice SIG is to design and develop microservice management capabilities for KubeSphere.
+
+## Members
+
+- Jeff Zhang ([@zryfish](https://github.com/zryfish)), Lead
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/1eAAbdIxJwFgNjkU9xvQ8SrezW7pHgPryzOAPjZYjvFg/)
+
+## Contact
+
+- Slack [#sig-microservice](https://kubesphere.slack.com/messages/sig-microservice)

sig-multicluster/README.md

@@ -0,0 +1,15 @@
+# Multi-cluster Special Interest Group
+
+The Multi-cluster SIG is to design and develop the management for multiple K8s clusters in KubeSphere.
+
+## Members
+
+- Jeff Zhang ([@zryfish](https://github.com/zryfish)), Lead
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/1P0NaJbAYTK4BnMazJcrc4he-sh2YpZNvG1rkPQrNhpY/)
+
+## Contact
+
+- Slack [#sig-multicluster](https://kubesphere.slack.com/messages/sig-multicluster)

sig-multitenancy/README.md

@@ -0,0 +1,15 @@
+# Multi-tenancy Special Interest Group
+
+The Multi-tenancy SIG is to design and develop the resource and identity management of KubeSphere in terms of tenancy.
+
+## Members
+
+- Hongming Wan ([@wansir]((https://github.com/wansir))), Lead
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/1Ewf30_Z6mlIxpJH-qF96c_mx96UaQtLi-fCf6m1r_yg/)
+
+## Contact
+
+- Slack [#sig-multitenancy](https://kubesphere.slack.com/messages/sig-multitenancy)

sig-network/README.md

@@ -0,0 +1,15 @@
+# Network Special Interest Group
+
+The Network SIG is to design and develop network-related capabilities for KubeSphere such as CNI, SDN, the bare metal load balancer [Porter](https://github.com/kubesphere/porter).
+
+## Members
+
+- Zhengyi Lai ([@zheng1](https://github.com/zheng1)), Lead
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/12KTd1xBSYPBTbn4WTvN4iTPoDg1skU-bbbcoNt_RAPE/)
+
+## Contact
+
+- Slack [#sig-network](https://kubesphere.slack.com/messages/sig-network)

sig-observability/README.md

@@ -0,0 +1,16 @@
+# Release Special Interest Group
+
+The Release SIG is to make plan and approve the release of each KubeSphere version.
+
+## Members
+
+- Calvin Yu ([@calvinyv](https://github.com/calvinyv)), Lead
+- Ray Zhou ([@rayzhou2017](https://github.com/rayzhou2017)), Lead
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/1IzkvpZlkc_4hKTyvWWyTfLgPFTWGaowOEAfh0li9qZQ/)
+
+## Contact
+
+- Slack [#sig-release](https://kubesphere.slack.com/messages/sig-release)

sig-release/README.md

@@ -0,0 +1,16 @@
+# Observability Special Interest Group
+
+The Observability SIG is to design and implement the observability features for KubeSphere including monitoring, alerting, notification and logging.
+
+## Members
+
+- Benjamin Huo ([@benjaminhuo](https://github.com/benjaminhuo)), Lead
+- Dan Ma ([@Ma-Dan](https://github.com/Ma-Dan)), Member
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/18SOB2NRQWS-Qad4oebzIjtQzUG831PFvQtvN5tBwNrM/)
+
+## Contact
+
+- Slack [#sig-observability](https://kubesphere.slack.com/messages/sig-observability)

sig-storage/README.md

@@ -0,0 +1,16 @@
+# Storage Special Interest Group
+
+The Storage SIG is to design and implement KubeSphere storage service such as CSI plugins.
+
+## Members
+
+- Xin Wang ([@wnxn](https://github.com/wnxn)), Lead
+- Min Zhang ([@min-zh](https://github.com/min-zh)), Member
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/171DjRH8CDkubc_fl8tO1tN-kpdPwek-G819FQt6EhV0/)
+
+## Contact
+
+- Slack [#sig-storage](https://kubesphere.slack.com/messages/sig-storage)

sig-testing/README.md

@@ -0,0 +1,15 @@
+# Testing Special Interest Group
+
+The Testing SIG is to make plan for testing KubeSphere versions.
+
+## Members
+
+- Yaping Liu ([@liuyp2018](https://github.com/liuyp2018)), Lead
+
+## Meetings
+
+[Meeting notes](https://docs.google.com/document/d/191w4_ePxBSEklZjKTSiYw7XwDH9_gCIVOt6cKkTvqYc/)
+
+## Contact
+
+- Slack [#sig-testing](https://kubesphere.slack.com/messages/sig-testing)

sigs.md

@@ -1,6 +1,6 @@
 # KubeSphere Special Interest Groups
 
-Most community activities are organized into a variety of Special Interest Group (SIGs).
+Most community activities are organized into a variety of Special Interest Group (SIG).
 
 ## Why Special Interest Groups
 
@@ -22,7 +22,7 @@ Leads are responsible for running a SIG. Running the group involves a few activi
 
 ### Be Open
 
-The community design process is done in the open. 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.
+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.
 
 ### Make Decisions
 
@@ -30,10 +30,22 @@ In general, SIGs operate in a highly cooperative environment. The members of a S
 
 ## SIGs
 
-The current SIGs are:
+The SIGs at present are:
 
-| Group | Lead | Name | Design Docs |  Slack Channel | To do (GitHub Issues) | Description
-|-------|-------------|-------|---------------|--------------|-------------------- | -----
-| Observability | <img width="30px" src="https://avatars2.githubusercontent.com/u/18525465?s=96&v=4">| [Benjamin Huo](https://github.com/benjaminhuo) | [Design documentation](./contribution/design/sig-observability) | [#observability](https://kubesphere.slack.com/archives/CLHL8R1C7) | [Tasks & Issues](https://github.com/kubesphere/kubesphere/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Fmonitoring+) | Logging, Monitoring, Alerting, Notification |
-
-> Please add your information in the table above.
+| Group | Lead |  Slack Channel | Meeting Notes | Description |
+|-------|-------------|-------|--------------|--------------------|
+| [Apps](./sig-apps/) | [Hongliang Wang](https://github.com/hlwanghl) | [#sig-apps](https://kubesphere.slack.com/messages/sig-apps) | [Notes](https://docs.google.com/document/d/1nRAK2U9flkz-8z7bT2-T_0VneW3w1fx1fJtB5Bu3JyU/) | App charts for the built-in App Store |
+| [App Store](./sig-appstore) | [Zhengyi Lai](https://github.com/zheng1) | [#sig-appstore](https://kubesphere.slack.com/messages/sig-appstore) | [Notes](https://docs.google.com/document/d/1FYxeQOiwN3jL6EPeIA71iB3gXZfNf-PhSufVaywFbxI/) | App Store, App template management |
+| [Architecture](./sig-architecture) | [Lu Liu](https://github.com/leoendless), [Benjamin Huo](https://github.com/benjaminhuo) | [#sig-architecture](https://kubesphere.slack.com/messages/sig-architecture) | [Notes](https://docs.google.com/document/d/1lqL0c6SpxLxRbwVk870-9HDeGIwVodSRJV-Uh4hPemQ/) | system architecture |
+| [Console](./sig-console) | [Lu Liu](https://github.com/leoendless) | [#sig-console](https://kubesphere.slack.com/messages/sig-console) | [Notes](https://docs.google.com/document/d/1a2RHltQm3armW4Jf7m1aYFTjdvlqiuW5hW2-KBeLqi0/) | dashboard |
+| [DevOps](./sig-devops) | [Jeff Zhang](https://github.com/zryfish) | [#sig-devops](https://kubesphere.slack.com/messages/sig-devops) | [Notes](https://docs.google.com/document/d/1ZORl7ZhRlZxKXFle2LGPRJqXzlr6EDhu2A7qzjybfro/) | pipeline, s2i, b2i, image registry |
+| [Docs](./sig-docs) | [Pengfei Zhou](https://github.com/FeynmanZhou) | [#sig-docs](https://kubesphere.slack.com/messages/sig-docs) | [Notes](https://docs.google.com/document/d/1tyB2RDJFmfwFfO2ok9dH7ttZRICDiaogSI12Ajz9CD0/) | User docs, kubesphere.io |
+| [Installation](./sig-installation) | [Feng Guo](https://github.com/pixiake) | [#sig-installation](https://kubesphere.slack.com/messages/sig-installation) | [Notes](https://docs.google.com/document/d/1sXMKViZ5cchbaBajRZiJsaSdMAQ1GpmDKCcq3UwT3Vg/) | KubeSphere installer and deployment |
+| [Microservice management](./sig-microservice) | [Jeff Zhang](https://github.com/zryfish) | [#sig-microservice](https://kubesphere.slack.com/messages/sig-microservice) | [Notes](https://docs.google.com/document/d/1eAAbdIxJwFgNjkU9xvQ8SrezW7pHgPryzOAPjZYjvFg/) | architecture, microservice governance |
+| [Multi-cluster](./sig-multicluster) | [Jeff Zhang](https://github.com/zryfish) | [#sig-multicluster](https://kubesphere.slack.com/messages/sig-multicluster) | [Notes](https://docs.google.com/document/d/1P0NaJbAYTK4BnMazJcrc4he-sh2YpZNvG1rkPQrNhpY/) | multi-cluster management |
+| [Multi-tenancy](./sig-multitenancy) | [Hongming Wan](https://github.com/wansir) | [#sig-multitenancy](https://kubesphere.slack.com/messages/sig-multitenancy) | [Notes](https://docs.google.com/document/d/1Ewf30_Z6mlIxpJH-qF96c_mx96UaQtLi-fCf6m1r_yg/) | workspace, IAM |
+| [Network](./sig-network) | [Zhengyi Lai](https://github.com/zheng1) | [#sig-network](https://kubesphere.slack.com/messages/sig-network) | [Notes](https://docs.google.com/document/d/12KTd1xBSYPBTbn4WTvN4iTPoDg1skU-bbbcoNt_RAPE/) | network policy, CNI plugins, SDN |
+| [Observability](sig-observability) | [Benjamin Huo](https://github.com/benjaminhuo) | [#sig-observability](https://kubesphere.slack.com/messages/sig-observability) | [Notes](https://docs.google.com/document/d/18SOB2NRQWS-Qad4oebzIjtQzUG831PFvQtvN5tBwNrM/) | Logging, Monitoring, Alerting, Notification |
+| [Release](./sig-release) | [Calvin Yu](https://github.com/calvinyv) | [#sig-release](https://kubesphere.slack.com/messages/sig-release) | [Notes](https://docs.google.com/document/d/1IzkvpZlkc_4hKTyvWWyTfLgPFTWGaowOEAfh0li9qZQ/) | release of each version |
+| [Storage](./sig-storage) | [Xin Wang](https://github.com/wnxn) | [#sig-storage](https://kubesphere.slack.com/messages/sig-storage) | [Notes](https://docs.google.com/document/d/171DjRH8CDkubc_fl8tO1tN-kpdPwek-G819FQt6EhV0/) | CSI plugins |
+| [Testing](./sig-testing) | [Yaping Liu](https://github.com/liuyp2018) | [#sig-testing](https://kubesphere.slack.com/messages/sig-testing) | [Notes](https://docs.google.com/document/d/191w4_ePxBSEklZjKTSiYw7XwDH9_gCIVOt6cKkTvqYc/) | test, release |