| contact@openharmony.io <imgwidth=150/> | Public mailing list <imgwidth=100/> | Public mailing list of the OpenHarmony community. You can send a signed CLA to this mailing list. <imgwidth=200/> |
| dev@openharmony.io <imgwidth=150/>| Development mailing list <imgwidth=100/> | Mailing list for discussing development issues in the OpenHarmony community. Any developer can [subscribe to](https://lists.openatom.io/postorius/lists/dev.openharmony.io) this mailing list. <imgwidth=200/> |
| cicd@openharmony.io <imgwidth=150/> | CI mailing list <imgwidth=100/> | Mailing list for continuous integration and continuous delivery (CI/CD) of the OpenHarmomny community. Any developer can [subscribe to](https://lists.openatom.io/postorius/lists/cicd.openharmony.io) this mailing list. <imgwidth=200/> |
| cicd@openharmony.io <imgwidth=150/> | CI mailing list <imgwidth=100/> | Mailing list for continuous integration and continuous delivery (CI/CD) of the OpenHarmony community. Any developer can [subscribe to](https://lists.openatom.io/postorius/lists/cicd.openharmony.io) this mailing list. <imgwidth=200/> |
| pmc@openharmony.io <imgwidth=150/>| PMC mailing list <imgwidth=100/> | Mailing list for PMC discussion. PMC members can [subscribe to](https://lists.openatom.io/postorius/lists/pmc.openharmony.io/) this mailing list. <imgwidth=200/> |
| scy@openharmony.io <imgwidth=150/> | Mailing list for security issues <imgwidth=100/> | Mailing list for reporting OpenHarmony security issues. <imgwidth=200/> |
| scy-priv@openharmony.io <imgwidth=150/>| Security group mailing list <imgwidth=100/> | Mailing list for discussing how to handle security issues. Security group members can [subscribe to](https://lists.openatom.io/postorius/lists/scy-priv.openharmony.io/) this mailing list. <imgwidth=200/> |
Under the guidance of the Project Management Committee (PMC), a special interest group (SIG) designs the architecture, develops open capabilities, and performs maintenance for innovative projects in a specific domain.
This repository stores information about all the SIGs in the OpenHamony community.
This repository stores information about all the SIGs in the OpenHarmony community.
## Applying for Creating an SIG
1. Seek two or three developers in the community who have the same interest or objectives as you and elect a leader for this SIG. Create an SIG proposal based on the [SIG creation template](sig-template/sig_template.md), The proposal includes the following elements:
...
...
@@ -20,7 +20,7 @@ This repository stores information about all the SIGs in the OpenHamony communit
## Operating and Maintaining an SIG
1. The SIG leader forks the **OpenHamony/community** release, creates a folder and names it with the SIG name in the **sig** directory, creates an SIG profile in the created folder based on the [SIG template](sig-template/), and submits pull requests (PRs) for incorporating modifications of the SIG profile into the master code of OpenHarmony.
1. The SIG leader forks the **OpenHarmony/community** release, creates a folder and names it with the SIG name in the **sig** directory, creates an SIG profile in the created folder based on the [SIG template](sig-template/), and submits pull requests (PRs) for incorporating modifications of the SIG profile into the master code of OpenHarmony.
2. SIG incubation projects are stored in the [OpenHarmony-SIG](https://gitee.com/openharmony-sig) organization. The code of incubation projects that meet graduation requirements can be incorporated into the master code of OpenHarmony.
...
...
@@ -34,8 +34,8 @@ This repository stores information about all the SIGs in the OpenHamony communit
3. After the PMC approves the graduation application, you can incorporate the code of the incubation project into the master code of OpenHarmony.
### How SIG Data Is Stored and Managed
SIG data is stored in the **sig** directory of the **OpenHamony/community** repository. The **sig_***xxx***.md**/**sig_***xxx***_cn.md** file is a template that contains the objectives and work scope of this SIG, repositories managed by the SIG and their descriptions, and SIG meetings and members. A backup of the maintainer/committer information of the SIG is stored in the **OWNER** file and can be automatically obtained by a tool. The names and directory structures of the repositories managed by each SIG are stored in the **sigs.json** file.
1. The **sigs.json** file in the **sig** directory of the **OpenHarmony/community** repository is used to manage all the SIGs visible to the PMC.
SIG data is stored in the **sig** directory of the **OpenHarmony/community** repository. The **sig_***xxx***.md**/**sig_***xxx***_cn.md** file is a template that contains the objectives and work scope of this SIG, repositories managed by the SIG and their descriptions, and SIG meetings and members. A backup of the maintainer/committer information of the SIG is stored in the **OWNER** file and can be automatically obtained by a tool. The names and directory structures of the repositories managed by each SIG are stored in the **sigs.json** file.
1. The **sigs.json** file in the **sig** directory of the **OpenHarmony/community** repository is used to manage all the SIGs visible to the PMC.
2. The PMC modifies and maintains SIGs. Maintainers submit PRs for modifying SIGs, and the PMC reviews the PRs and incorporates the modifications into the master code of OpenHarmony.
3. The **sig_***xxx***.md**/**sig_***xxx***_cn.md** file in the **sig** directory stores SIG data. In this file, the basic SIG information is empty and needs to be specified during SIG creation.
4. The **OWNER** file in the **sig** directory stores information about the maintainer of the SIG.
...
...
@@ -57,8 +57,8 @@ SIG data is stored in the **sig** directory of the **OpenHamony/community** repo
3. SIG Leader及Committer负责对应SIG的运营及维护，会议纪要和资料统一参考sig-template目录下的[meetings](https://gitee.com/openharmony-sig/sig-content)和[docs](https://gitee.com/openharmony-sig/sig-content)模版进行归档。
4. SIG Leader定期在PMC项目管理委员会汇报SIG孵化项目及SIG运营进展，PMC基于SIG运作情况给出指导建议。
- Meeting notification: [Subscribe to](https://lists.openatom.io/postorius/lists/dev.openharmony.io) mailing list dev@openharmony.io for the meeting link
- The evelopment and maintenance of compilation framework and its efficiency improvement. Supporting compilation of multiple products and components.
- The development and maintenance of compilation framework and its efficiency improvement. Supporting compilation of multiple products and components.
- Support JS/TS language compilation and runtime, and create high-performance JS/TS virtual machines. Provide basic JSAPI capabilities, including multi-threading capabilities, encoding and decoding string capabilities, and URL parsing capabilities.
- Support C/C++ compilation, debuging based on Clang/LLVM.
- Provide basic libarary supoort such as musl and evolution of related abilities.
- Support C/C++ compilation, debugging based on Clang/LLVM.
- Provide basic library support such as musl and evolution of related abilities.
### work scope
- Design, review, and make decisions on the architecture of the language compilation and runtime.
@@ -21,7 +21,7 @@ SIG will work with partners to establish and improve corresponding data collecti
**Set the benchmark**
Innovate Oh education application scenarios and build demonstration benchmark projects based on Oh root technology; Promote the development of industrial hongmenghua with demonstration effect.
Innovate Oh education application scenarios and build demonstration benchmark projects based on Oh root technology; Promote the development of industrial in an OpenHarmony-based way with demonstration effect.
- Meeting notification: [Subscribe](https://lists.openatom.io/postorius/lists/dev.openharmony.io/) mailing list dev@openharmony.io for the meeting link
- Meeting-Minutes: [Archive link address](https://gitee.com/openharmony-sig/sig-content/tree/master/assist_tools/meetings)
- Meeting-Minutes: [Archive link address](https://gitee.com/openharmony-sig/sig-content/tree/master/napi_generator/meetings)
### Contact (optional)
- Mailing list：dev@openharmony.io
- Zulip group：https://zulip.openharmony.cn subscript to sig_napi_generator stream
Note: The content of this SIG follows the convention described in OpenHarmony's PMC Management Charter [README](/zh/pmc.md).
## SIG group work objectives and scope
### work goals
Secure Element (SE) is a secure chip that is by design protected from unauthorized access and used to run a limited set of applications, as well as store confidential and cryptographic data. This SIG provides a unified secure chip management framework and specifications for OpenHarmony. In addition, the SIG also supports standard advanced security system security service deployment of secure chips and promotes the development of the OpenHarmony secure chip ecosystem.
### work scope
- Provide standard advanced security services deployed in secure chips, such as password authentication, key management, secure storage, and anti-rollback services.
- Build the OpenHarmony secure chip ecosystem alliance, support technical communication among secure chip vendors, and jointly develop secure chip specifications.
- Provide a unified secure chip management framework and is responsible for secure chip architecture maintenance, technical solution review, and ecosystem cooperation.
- Meeting notification: [Subscribe to] (https://lists.openatom.io/postorius/lists/sig-secure_element.openharmony.io) mailing list sig-secure_element@openharmony.io for the meeting link
- Meeting-Minutes: [Archive link address](https://gitee.com/openharmony-sig/sig-content)
| dev@openharmony.io <imgwidth=120/>| Mailing list <imgwidth=100/> | OpenHarmony community development discussion mailing list, any community development related topics can be discussed in the mailing list. Any developer can [subscribe](https://lists.openatom.io/postorius/lists/dev.openharmony.io)。<imgwidth=200/>|
| sig-secure_element@openharmony.io <imgwidth=120/>| Sig-SecureElement Mailing list <imgwidth=100/> | OpenHarmony community SIG-SecureElement discussion mailing list, any technical topics and implementation related to the secure chip management framework can be discussed in the mailing list. Any developer can [subscribe](https://lists.openatom.io/postorius/lists/sig-secure_element.openharmony.io/)。<imgwidth=200/>|
| zulip platform <imgwidth=120/>| Sig-SecureElement zulip platform <imgwidth=100/> | OpenHarmony community SIG-SecureElement discussion platform, any technical topics and implementation related to the secure chip management framework can be discussed in the platform. Any developer can [follow](https://zulip.openharmony.cn/#narrow/stream/60-secure_element_sig/)。<imgwidth=200/>|
