forked from openkylin/docs
Merge branch 'master' of gitee.com:delong1998/docs
This commit is contained in:
commit
8cc7db3542
|
|
@ -15,7 +15,7 @@ The new generation of UKUI 4.0 desktop environment is installed by default, whic
|
|||
|
||||
|
||||
## Rich application ecosystem
|
||||
In addition to a variety of self-developed applications such as video, music and housekeeping, the openKylin software store also provides users with thousands of three-party mainstream software such as wps, WeChat, QQ and Kugou music, which meet the needs of users for daily office, life entertainment, Internet access, production activities and other multi-scene applications.
|
||||
In addition to a variety of self-developed applications such as video, music and housekeeping, the openKylin software store also provides users with thousands of three-party mainstream software such as WPS, WeChat, QQ and Kugou music, which meet the needs of users for daily office, life entertainment, Internet access, production activities and other multi-scene applications.
|
||||
|
||||
|
||||
|
||||
|
|
@ -30,7 +30,7 @@ openKylin OS is pre-installed with multi-terminal collaboration tools by default
|
|||
|
||||
|
||||
## KMRE Mobile Compatible Operating Environment
|
||||
openKylin OS supports KMRE mobile compatible runtime environment, which can realize the AA (Android+ARM) ecosystem compatible runtime in openKylin OS!
|
||||
openKylin OS supports KMRE mobile-compatible runtime environment, which can realize the AA (Android+ARM) ecosystem-compatible runtime in openKylin OS!
|
||||
|
||||
|
||||
|
||||
|
|
@ -40,12 +40,12 @@ VirtIO-GPU is a GPU virtualization technology, but because the technology does n
|
|||
|
||||
|
||||
## openKylin Self-Developed Developer Kit
|
||||
The openKylin Self-Developed Developer Kit (hereinafter referred to as OpenSDK) is dedicated to providing a secure, reliable, fast and stable developer interface for ecological construction and software development on the openKylin operating system. openSDK currently focuses on three major modules, including the Application Support SDK, System Capability SDK, and Basic Development SDK, while fully considering At the same time, the compatibility of OpenSDK is fully considered. The OpenSDK SIG group has completed the development of OpenSDK V2.0, which provides a safer, more reliable, faster and more stable development interface for the community developers and greatly improves the development efficiency!
|
||||
The openKylin Self-Developed Developer Kit (hereinafter referred to as OpenSDK) is dedicated to providing a secure, reliable, fast and stable developer interface for ecological construction and software development on the openKylin operating system. openSDK currently focuses on three major modules, including the Application Support SDK, System Capability SDK, and Basic Development SDK, while fully considering At the same time, the compatibility of OpenSDK is fully considered. The OpenSDK SIG group has completed the development of OpenSDK V2.0, which provides a safer, more reliable, faster and more stable development interface for the community developers and greatly improves development efficiency!
|
||||
|
||||
|
||||
|
||||
## openKylin Virtual Keyboard
|
||||
openKylin virtual keyboard is a good, easy-to-use and stable virtual keyboard in tablet mode, developed by InputMethod SIG group in the lead. During the development period InputMethod SIG group also worked deeply with Fcitx5 authors to add basic virtual keyboard support mechanism to Fcitx5 input method framework!
|
||||
openKylin virtual keyboard is a good, easy-to-use and stable virtual keyboard in tablet mode, developed by InputMethod SIG group in the lead. During the development period,InputMethod SIG group also worked deeply with Fcitx5 authors to add basic virtual keyboard support mechanism to Fcitx5 input method framework!
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -21,24 +21,23 @@ After the topics are collected, the SIG Maintainer will arrange the meeting agen
|
|||
|
||||
The meeting will be hosted by each SIG Maintainer, and the meeting will be started according to the pre-defined meeting agenda. During the meeting, attention should be paid to time control to ensure that all the topics already on the meeting agenda will be given the corresponding discussion time. Each participant needs to fill in his or her name and Gitee_ID as required in the participant part of the meeting topic collection file, and the topic will be regarded as automatically abandoned if he or she is not present and no substitute participant is designated.
|
||||
|
||||
The discussion of each topic can be divided into the following stages.
|
||||
The discussion of each topic can be divided into the following stages:
|
||||
|
||||
1. Presentation: The topic is presented by the topic sponsor, and the rest of the audience is not allowed to interrupt during the presentation phase.
|
||||
1. Topic presentation: The topic sponsor will present the topic, and the rest of the audience will not be allowed to interrupt during the presentation stage.
|
||||
|
||||
2. Discussion: The participants will discuss the topic accordingly, all participants can participate in the discussion, and the moderator is responsible for recording the views and key opinions of all parties.
|
||||
2. Discussion: Each participant will discuss the topic accordingly, and all participants can participate in the discussion, and the moderator will be responsible for recording the views and key opinions of each party.
|
||||
|
||||
3. Summary: After reaching a consensus, the moderator will output the conclusion of the topic according to the consensus. If no consensus is reached on the spot, a specific time for another discussion should be negotiated.
|
||||
3. Summary: After consensus is reached, the moderator outputs the conclusion of the topic based on the consensus. If no consensus is reached on the spot, a specific time for another discussion should be negotiated.
|
||||
|
||||
After all the topics are discussed, the SIG Maintainer team will prioritize and divide the topics according to the discussion of each topic and the actual situation of the SIG group.
|
||||
After all the topics are discussed, the SIG Maintainer team will prioritize and divide the topics according to the discussion of each topic and the actual situation of SIG group.
|
||||
|
||||
### Meeting Minutes
|
||||
|
||||
The person in charge of each SIG group will compile and complete the meeting minutes within three days after the meeting, and release the minutes publicly on the corresponding meeting collection directory on gitee, the mailing list of this SIG, Release SIG and other related SIGs, so that developers and users can understand the work planning and arrangement of each SIG, and the meeting minutes need to contain the following contents.
|
||||
The person in charge of each SIG group will compile and complete the minutes of the meeting within three days after the meeting, and release the minutes publicly on the corresponding meeting collection directory on gitee, the mailing list of this SIG, Release SIG and other related SIGs, so that developers and users can understand the work planning and arrangement of each SIG, and the minutes need to contain the following contents.
|
||||
|
||||
1. all the topics discussed and the conclusions of the topics
|
||||
|
||||
2. the person in charge of each work and the time frame
|
||||
1. all the topics that were discussed and the conclusions of the topic
|
||||
|
||||
2. the person in charge of each task and the duration of their work plan
|
||||
......
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
# SIG owner co-option or withdrawal
|
||||
## SIG owner co-option specification
|
||||
# SIG group Owner co-option, revocation specification
|
||||
## SIG group Owner co-option specification
|
||||
### Co-opted candidates
|
||||
SIG owners shall be elected from SIG group maintainers.
|
||||
SIG group Owners shall be elected from SIG group Maintainers.
|
||||
|
||||
### Submit application
|
||||
Applicants are required to complete the submission of application materials at least three days before the SIG meeting, and the application materials template is as follows. After writing, complete the submission of application materials and issue declaration by replying to the next SIG meeting issue collection email.
|
||||
### Submit an application
|
||||
Applicants are required to complete the submission of application materials at least three days before the SIG meeting, and the application materials template is as follows. After writing, complete the submission of application materials and issue declaration by replying to the next SIG meeting issue a collection email.
|
||||
```
|
||||
I. Basic information.
|
||||
1, Applicant: name (email address)
|
||||
|
|
@ -19,14 +19,14 @@ II. the main contributions to the SIG group listed.
|
|||
All SIG Owners and maintainers will vote on the application. The vote will be divided into affirmative, negative and abstaining votes, either directly at the meeting or by email after the meeting. The application can be approved only if two-thirds or more votes are cast. The voting result must be reported to the technical committee, which has the right to veto the election result within the SIG group.
|
||||
|
||||
|
||||
## SIG owner withdrawal specification
|
||||
### Principles of withdrawal
|
||||
* SIG group owners have low activity and participation for a long period of time, including but not limited to: not participating in regular SIG group meetings, SIG group decisions, SIG group activities, etc. for a long period of time (more than six months).
|
||||
* SIG group owner has limited ability to lead the SIG group to accomplish the set goals and work plan, which affects the development of SIG group and community.
|
||||
* SIG group owners are unable to continue their duties as SIG group owners due to personal or other reasons.
|
||||
* Other circumstances that require the revocation of the SIG group owner as deemed by the core members of the SIG group or the technical committee.
|
||||
## SIG group Owner revocation specification
|
||||
### Principles of Revocation
|
||||
* SIG group Owners have a low level of activity and participation for a long period of time, including but not limited to: not participating in regular SIG group meetings, SIG group decisions, SIG group activities, etc. for a long period of time (more than 6 months).
|
||||
* SIG group Owner has limited ability to lead the SIG group to accomplish the set goals and work plan, which affects the development of SIG group and community.
|
||||
* SIG group Owners are unable to continue their duties as SIG group Owners due to personal or other reasons.
|
||||
* Other circumstances that require the revocation of the SIG group Owner as deemed by the core members of the SIG group or the technical committee.
|
||||
|
||||
### Submit application
|
||||
### Submit an application
|
||||
The application for revocation of SIG group Owner should be submitted by other core SIG group personnel (other Owners, Maintainer), the Owner himself or a member of the Technical Committee, with specific reasons for revocation, and the application for revocation should be completed by replying to the issue collection email and issue declaration at least three days before the next SIG group meeting.
|
||||
|
||||
### Voting
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
## SIG Name
|
||||
> SIG naming specification.
|
||||
> 1. SIG name with full spelling, only one word is capitalized; each word with multiple words is capitalized and no hyphen in between, for example: Release, BootAndInstall, etc..
|
||||
> 2. special nouns or SIG names that must be abbreviated are all capitalized, for example: RISC-V, QA, etc..
|
||||
## SIG Group Name
|
||||
> SIG naming convention.
|
||||
> 1. full spelling of SIG name, only one word is capitalized; multiple words are capitalized with no hyphen in between, e.g., Release, BootAndInstall, etc...
|
||||
> 2. special nouns or SIG names that must be abbreviated are all capitalized, e.g., RISC-V, QA, etc...
|
||||
> 3. SIG naming shall not infringe on the legitimate rights and interests of any third party (including but not limited to unauthorized use of third party trademarks, trade names, logos, etc.).
|
||||
> 4. The community has the final right to review the naming of SIG.
|
||||
> 4. the community has the final right to review the naming of SIG.
|
||||
|
||||
SIG Group Introduction
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue