p62978453
/
docs
forked from openkylin/docs
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

删除文件 SIG管理指南/SIG Group Charter.md

This commit is contained in:
pangjunjie1 2023-04-03 08:54:51 +00:00 committed by Gitee
parent 81df9f4e6b
commit 46bc3a1935
No known key found for this signature in database
GPG Key ID: 173E9B9CA92EEF8F
1 changed files with 0 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
SIG管理指南/SIG Group Charter.md
View File

@ -1,39 +0,0 @@
---
title: 01-SIG Group Charter
description:
published: true
date: 2022-06-23T06:11:31.972Z
tags:
editor: markdown
dateCreated: 2022-03-11T03:16:31.536Z
---
## Background
The openKylin community is a free and open community. In order to ensure the openness and transparency of community work, strengthen the communication between contributors, enthusiasts and maintainers of the openKylin operating system release version in the community, expand the influence of the openKylin community, and attract more Linux Enthusiasts join the openKylin community. We hope to organize and coordinate various affairs in the community work in the form of establishing a SIG group, and make the openKylin community an active Linux operating system open source community.
## Principle
1. All SIG groups in the openKylin community are open, and anyone and any organization can participate.
2. The SIG's `README.md` file contains information about the SIG to which the project belongs, communication methods, members and contact information, etc. We welcome everyone to actively participate in the communication within the SIG through the contact methods mentioned in the `README.md` file, including mailing lists, public meetings, etc.
3. Each SIG group is composed of the project leader (Owner) and the core maintainer (Maintainer). Major decisions in the group must be voted by all members with more than 2/3 of the votes and reported to the technical committee.
4. Each SIG group can have its own mailing list, community, etc., and can also have its own contribution strategy, but must have its own SIG charter.
5. The transaction types responsible for each SIG group in the community are not allowed to overlap, and the transaction types between groups need to be kept isolated.
6. Meetings within each SIG group need to be held regularly.
## Organization
The openKylin community currently has the following SIG groups:
- Architecture
- Infrastructure
- Version
- Kernel
- Security
- Compatibility
- DE
- QA
- HTML5
- RISC-V
- Input method