forked from openkylin/docs
moshengren
Gitee
commit
df80d65815
|
|
@ -0,0 +1,64 @@
|
|||
# How to join SIG
|
||||
**Application**.
|
||||
1. Sign the CLA https://cla.openkylin.top/
|
||||
2. Check the SIG of interest through the SIG list https://www.openkylin.top/join/sig-cn.html and directly enter the link to the SIG project for code contribution, or subscribe to the mailing list https://mailweb.openkylin.top, participate in SIG meetings https://www.openkylin.top/sig/meeting-cn.html and so on, to participate in the technical discussion and community maintenance of the corresponding SIG project.
|
||||
3. Join the developer exchange group (CLA backend management actively pull you into the group)
|
||||
|
||||
**Become a maintainer condition (recommended to)**.
|
||||
Benefits: When developers meet the following two or more conditions, they can apply for SIG group and become a group maintainer:
|
||||
|
||||
1.Submit five or more valid commissions.
|
||||
2.Raise five or more valid issues.
|
||||
3.Fix five or more issues.
|
||||
4.Actively participate in SIG meetings and make constructive suggestions in the meetings.
|
||||
|
||||
# How to apply Or withdraw SIG
|
||||
|
||||
## Individual / Corporate Application
|
||||
|
||||
**Application**.
|
||||
After all SIG members [sign personal cla](https://cla.openkylin.top), please follow these steps to execute the request.
|
||||
1. Fork the project [openKylin / community](https://gitee.com/openkylin/community) under your Gitee by the relevant proposer. Create your own new SIG directory in the sig directory under your Gitee project, and follow the [SIG Group Charter Template](https://gitee.com/openkylin/docs/blob/master/SIG%E7%AE%A1%E7%90%86%E6%8C%87%E5%8D%97/SIG%E7%BB%84%E7%AB%A0%E7%A8%8B%E6%A8%A1%E7%89%88.md) and create the corresponding `README.md` under your Gitee project, and complete the new SIG charter;
|
||||
2. In the SIG directory you just created, create the sig.yaml file according to the [sig.yaml template](https://gitee.com/openkylin/community/blob/master/sig/README.md), and complete the sig.yaml file;
|
||||
3. After completing the above two steps, commit the above changes to Gitee and submit a PR request to the [openKylin / community](https://gitee.com/openkylin/community) project to create a SIG group, fill out the relevant information, the technical committee will review the relevant information in advance and further communicate at the next The technical committee will review the information in advance and communicate further at the next regular meeting.
|
||||
|
||||
**Review**: The Technical Committee participants will communicate with the proposer and review and comment on the SIG related business scope and maintenance objectives.
|
||||
|
||||
**Approval**: After the Technical Committee has passed the review, the corresponding mailing list will be created for the SIG group you applied for, and official confirmation information and the mailing list account will be sent by email to the email address you bound when you signed the CLA, and the person in charge of the infrastructure SIG group will complete the creation of the corresponding SIG group warehouse and permission processing.
|
||||
|
||||
**Operation**: SIG is officially operated, and the group members communicate through mailing list and group meeting. At the early stage of the operation of a new SIG group, a member of the technical committee can be appointed as the mentor of the SIG group to guide the SIG group to ensure that the SIG group quickly gets on the right track.
|
||||
|
||||
|
||||
## Corporate Application
|
||||
|
||||
**Application**.
|
||||
After the person in charge of the business [sign the business cla](https://cla.openkylin.top) and ask the relevant business employees of that business [sign the employee cla](https://cla.openkylin.top), then please follow the steps below to execute the application.
|
||||
1. Fork the project [openKylin / community](https://gitee.com/openkylin/community) under your Gitee by the relevant proposer. And create your own new SIG directory in the sig directory under your Gitee project, and follow the [SIG Group Charter Template](https://gitee.com/openkylin/docs/blob/master/SIG%E7%AE%A1%E7%90%86%E6%8C%87%E5%8D%97/) SIG%E7%BB%84%E7%AB%A0%E7%A8%8B%E6%A8%A1%E7%89%88.md) and create the corresponding `README.md` under your Gitee project, and complete the new SIG charter;
|
||||
2. In the SIG directory you just created, create the sig.yaml file according to the [sig.yaml template](https://gitee.com/openkylin/community/blob/master/sig/README.md) and fill out the sig.yaml file;
|
||||
3. After completing the above two steps, commit the above changes to Gitee and submit a PR request to the [openKylin / community](https://gitee.com/openkylin/community) project to create a SIG group. The technical committee will review the information in advance and communicate further at the next regular meeting.
|
||||
|
||||
**Review**: The Technical Committee participants will communicate with the person in charge and review and comment on the SIG related business scope and maintenance objectives.
|
||||
|
||||
**Approval**: After the Technical Committee has passed the review, the corresponding mailing list will be created for the SIG group you applied for, and the official confirmation information and mailing list account will be sent by email to the email address you bound when you signed the cla, and the person in charge of the infrastructure SIG group will complete the creation of the corresponding SIG group warehouse and permission processing.
|
||||
|
||||
**Operation**: SIG is officially operated, and the group members communicate through mailing list and group meeting. At the initial stage of the operation of a new SIG group, a member of the technical committee can be appointed as the mentor of the SIG group to provide guidance for the SIG group to ensure that the SIG group quickly gets on the right track.
|
||||
|
||||
## Withdrawal of SIG
|
||||
### Principles of Withdrawal
|
||||
The following circumstances can occur when the SIG owner or the technical committee member submits a request to cancel the SIG group.
|
||||
|
||||
* The SIG group has been very inactive for a long time and cannot maintain daily operation. Including but not limited to the existence of: long time (more than 6 months) has not held regular meetings, never participated in the community SIG group related activities (including release), has not been responsible for the repository or the repository responsible for a long time no code updates, can not respond to the community feedback issues in a timely manner and other inactive phenomenon.
|
||||
* SIG group is responsible for an important module or technical direction in the openKylin release, but the current work cannot meet the requirements of the openKylin release for that module or technical direction, which hinders the release and technical development of the openKylin release.
|
||||
* the SIG group's goal planning, technical direction, etc. overlap with another SIG group.
|
||||
* Other circumstances that the Technical Committee considers necessary to abolish the SIG group.
|
||||
|
||||
### Withdrawal Process
|
||||
#### Submit a withdrawal request
|
||||
SIG group revocation requests should be submitted by the SIG group Owner or technical committee member in the following manner.
|
||||
1. Fork the project [openKylin / community](https://gitee.com/openkylin/community) to your Gitee. and delete the directory corresponding to that SIG group in the [community/sig](https://gitee.com/openkylin/community/sig) directory.
|
||||
2. After completing the above steps, commit the changes to Gitee and submit a PR request to the [openKylin / community](https://gitee.com/openkylin/community) project to remove the SIG group. After filling out the relevant information (detailed reasons for removing the SIG group), the technical committee will advance The technical committee will review the information and discuss and vote on the issue at the next regular meeting.
|
||||
|
||||
#### Discuss and vote
|
||||
The SIG withdrawal application shall be discussed and decided by voting at the regular meeting of the Technical Committee. AAll members of the Technical Committee are required to participate in the voting, which is divided into affirmative votes, negative votes, and abstentions, and can be voted directly at the regular meeting or in response to an email vote after the meeting. Two-thirds or more of the members must vote in favor of the application in order for it to be approved. The voting results are publicized via the mailing list.
|
||||
|
||||
When the SIG group is withdrawn, the packages under the name of the SIG group that need to be maintained will be temporarily divided into the Packaging SIG group and publicized through the mailing list, and these packages can be claimed and maintained by other SIG groups or other new SIG groups established.
|
||||
|
|
@ -0,0 +1,31 @@
|
|||
## Introduction
|
||||
|
||||
The openKylin community is a free and open community. In order to ensure the openness and transparency of the community work, to strengthen the communication between the community contributors, enthusiasts and maintainers of the openKylin OS distribution, to expand the influence of the openKylin community, and to attract more Linux enthusiasts to join the openKylin community, we hope to establish a SIG group to organize and coordinate the various matters in the community work, and to make the openKylin community an active open source community for the Linux OS.
|
||||
|
||||
## Principles
|
||||
|
||||
1. all SIG groups in the openKylin community are open for anyone and any organization to participate.
|
||||
2. The `README.md` file of the SIG contains information about the SIG to which the project belongs, communication methods, members and contact information. We welcome you to actively participate in the communication within the SIG through the contact information mentioned in the `README.md` file, including the mailing list, open meetings, etc.
|
||||
3. Each SIG group is composed of project leader (Owner) and core maintainer (Maintainer), and major decisions within the group must be decided by all members with more than 2/3 votes and reported to the Technical Committee.
|
||||
4. Each SIG group can have its own mailing list, community, etc., and its own contribution strategy, but it must have its own SIG charter.
|
||||
5. The types of matters responsible between SIGs in the community are not allowed to cross over, and it is necessary to keep the types of matters isolated between the groups.
|
||||
6. The meetings within each SIG need to be held regularly.
|
||||
|
||||
## Organizational Structure
|
||||
|
||||
The openKylin community currently has the following SIG groups:
|
||||
|
||||
- Architecture
|
||||
- Infrastructure
|
||||
- Versions
|
||||
- Kernel
|
||||
- Security
|
||||
- Compatibility
|
||||
- DE
|
||||
- QA
|
||||
- HTML5
|
||||
- RISC-V
|
||||
- Input Method
|
||||
- ...
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,29 @@
|
|||
# How to change information of SIG
|
||||
|
||||
## Change of SIG name
|
||||
|
||||
1. SIG group submits a request to change the name PR, pay attention to the changes to cover all the places on gitee where the SIG group name is displayed to avoid inconsistent SIG group names. Generally involve: community/sig/xxxx directory name, the name field in sig.yaml file
|
||||
The SIG group name in the README.md file.
|
||||
2. the administrator reviews whether it conforms to the SIG group naming specification, etc.
|
||||
3. the administrator notifies the community operators to modify the SIG group names in the openKylin website and mailing list, etc.
|
||||
|
||||
|
||||
SIG group naming specification
|
||||
1. the SIG name with full spelling, the initial letter is capitalized if there is only one word; for multiple words, the initial letter of each word is capitalized and no hyphen is added in between, for example: Release, BootAndInstall, etc..
|
||||
2. special nouns or SIG names that must be abbreviated are capitalized, for example: RISC-V, QA, etc.
|
||||
3. the SIG naming shall not infringe upon the legitimate rights and interests of any third party (including but not limited to the unauthorized use of third party trademarks, trade names, logos, etc.).
|
||||
4. the community has the final right to review the SIG naming.
|
||||
|
||||
|
||||
## Change of team members/membership privileges
|
||||
* If you have a member change request after the SIG group is created, please follow these steps to execute the request.
|
||||
1. Fork the project [openKylin / community](https://gitee.com/openkylin/community) to your Gitee project by the relevant proponent. Modify the `README.md` in the corresponding SIG group's directory under your Gitee project according to the changes;
|
||||
2. Complete the changes to the sig.yaml file in the corresponding SIG group directory;
|
||||
3. After completing the above two steps, submit the above changes to Gitee and submit a PR request to the [openKylin / community](https://gitee.com/openkylin/community) project for SIG group membership changes (if new members are added, the new members will need to sign a cla first). After filling in the relevant information, the technical committee will review the relevant information in advance and communicate further at the next regular meeting.
|
||||
|
||||
|
||||
## Change of maintenance package list
|
||||
* If you have a package list update request after the SIG group is created, please execute the request as follows.
|
||||
1. Fork the project [openKylin / community](https://gitee.com/openkylin/community) under your Gitee by the relevant proposer. Modify the `README.md` in the SIG group directory under your Gitee project according to the changes;
|
||||
2. Complete the changes to the sig.yaml file in the corresponding SIG group directory;
|
||||
3. After completing the above two steps, commit the above changes to Gitee and submit a PR request to the [openKylin / community](https://gitee.com/openkylin/community) project for changes to the SIG group package list, fill out the relevant information, the technical committee will review the information in advance and The technical committee will review the information in advance and communicate further at the next regular meeting.
|
||||
|
|
@ -0,0 +1,62 @@
|
|||
## openKylin sig-xxx 1.0 plan
|
||||
|
||||
\---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
This document is for the openKylin sig-xxx 1.0 issue collection, meeting date: xx/xx/xxxx
|
||||
|
||||
|
||||
|
||||
Participants
|
||||
|
||||
\---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
|
||||
|
||||
Please fill in participant information at
|
||||
|
||||
|
||||
|
||||
|
||||
Name (gitee_ID)
|
||||
|
||||
|
||||
|
||||
Meeting schedule
|
||||
|
||||
\---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
|
||||
|
||||
9:30pm ~ 9:45pm: Topic 1
|
||||
|
||||
9:45pm ~ 10:00pm: Topic 2
|
||||
|
||||
...
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Topics:
|
||||
|
||||
\---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Please fill in the content of the topic you want to submit, including the topic sponsor, a brief description of the topic, an online address for issue feedback, existing technical proposals or PR, existing discussion notes, etc.
|
||||
|
||||
(No priority and order of priority for all issues in the issue declaration stage, after the completion of requirements collection by the SIG group version planning leader and all maintainers in accordance with the specific circumstances of all collected requirements (type, technical difficulty, workload, etc.), according to the meeting schedule to specify the meeting agenda, the meeting schedule will be announced three days before the work session)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
1. Example: Topic 1 (Proposer):
|
||||
|
||||
- You should need to write clear details of the proposed topic, including but not limited to: xxx,xxx
|
||||
|
||||
- User scenario: who is using it in what scenario and how
|
||||
|
||||
- Related issues: issue_link1, issue_link2, issue_link3
|
||||
|
||||
- Previous discussions or technical solutions pre-research: xxx xxx xxx
|
||||
Loading…
Reference in New Issue