Skip to content

C
Community

OpenHarmony / Community
9 个月 前同步成功

通知 53
Star 210
Fork 5
C
Community

前往新版Gitcode，体验更适合开发者的 AI 搜索 >>

提交 6044e138 编写于 作者: J jinguang
浏览文件
操作

!1439 [fix] uniform sig's name and content 

* Description:[fix] uniform sig's name and content
上级 424b682a
展开全部 隐藏空白更改
内联 并排
Showing with 915 addition and 915 deletion
README.md
浏览文件 @ 6044e138
# OpenHarmony Community
欢迎来到OpenHarmony社区！
简体中文 | [English](./README-EN.md)
简体中文 | [English](./README_EN.md)
## 介绍
Community仓库用于管理OpenHarmony社区治理、开发者贡献指南、开发者贡献协议、社区交流等内容。
......
sig/README.md
浏览文件 @ 6044e138
......@@ -18,7 +18,7 @@
### 2.提交申请
SIG发起人参照[SIG章程模板]创建SIG提案初稿，以附件形式发送给dev@openharmony.io，邮件标题为：
- **SIG-Charter-Proposal-SIG XXX+简要介绍**，如`SIG-Charter-Proposal-SIG Test+OpenHarmony开发自测试能力构建`。
- **sig_Charter-Proposal-SIG XXX+简要介绍**，如`sig_Charter-Proposal-SIG Test+OpenHarmony开发自测试能力构建`。
### 3.PMC评审提案
- SIG发起人接受PMC问询，对SIG提案进行必要的说明，并根据PMC的指导意见修改提案，通过原申请邮件与PMC进行沟通，直至PMC无疑问；
......@@ -28,14 +28,14 @@ SIG发起人参照[SIG章程模板]创建SIG提案初稿，以附件形式发送
### 4.提交PR
SIG发起人收到PMC评审反馈、确认SIG提案通过后，执行以下操作：
- fork OpenHarmony社区仓库到本地，在`OpenHarmony/community/sig`仓库内新建SIG文件夹，文件夹名称为“sig-XXX”；
- 创建该SIG的`README.md`、`OWNERS.md`文档，文档格式请参考[其他SIG](https://gitee.com/openharmony/community/tree/master/sig)，如sig-driver的[README.md](https://gitee.com/openharmony/community/blob/master/sig/sig-driver/sig_driver_cn.md)及[OWNERS.md](https://gitee.com/openharmony/community/blob/master/sig/sig-driver/OWNERS)。
- fork OpenHarmony社区仓库到本地，在`OpenHarmony/community/sig`仓库内新建SIG文件夹，文件夹名称为“sig_XXX”；
- 创建该SIG的`README.md`、`OWNERS.md`文档，文档格式请参考[其他SIG](https://gitee.com/openharmony/community/tree/master/sig)，如sig_driver的[README.md](https://gitee.com/openharmony/community/blob/master/sig/sig_driver/sig_driver_cn.md)及[OWNERS.md](https://gitee.com/openharmony/community/blob/master/sig/sig_driver/OWNERS)。
- 更新`sigs.json`文档，参考以下样例：
**sigs.json 文件格式**
| 字段 | 说明 |
|:---|:---|
| sig-name | SIG名称 |
| sig_name | SIG名称 |
| projects| gitee仓名 |
| project-path | OpenHarmony下的归档路径，若不涉及回合OpenHarmony填写NONE |
......@@ -43,12 +43,12 @@ SIG发起人收到PMC评审反馈、确认SIG提案通过后，执行以下操
```
"sigs-List":[
{
"sig-name":"sig-python",
"sig_name":"sig_python",
"projects":"https://gitee.com/openharmony-sig/python",
"project-path":"python/"
},
{
"sig-name ":"sig-updates",
"sig_name ":"sig_updates",
"projects":["https://gitee.com/openharmony/startup_appspawn_lite", "https://gitee.com/openharmony/startup_bootstrap_lite"]
"project-path":["base/startup/appspawn_lite", "base/startup/bootstrap_lite"]
},
......@@ -113,7 +113,7 @@ Committer负责代码审核、主干代码合入及特性设计方案审核和
#### 1.会议组织
- SIG需定期召开例行会议，每双周至少半小时，由SIG Leader主持；
- 会议议程提前在邮件列表及官网进行公布；
- 会议纪要及时发布并保存在`OpenHarmony/community/sig/sig-XXX/meeting-minutes`内。
- 会议纪要及时发布并保存在`OpenHarmony/community/sig/sig_XXX/meeting-minutes`内。
#### 2.社区共建
- SIG Leader至少两个月一次，在PMC例会汇报SIG工作进展，并基于PMC指导意见改进工作；
......@@ -214,7 +214,7 @@ SIG信息记录统一归档在OpenHarmony/community仓库的sig目录内：
### sigs.json 文件格式
| 字段 | 说明 |
|:---|:---|
| sig-name | SIG名称 |
| sig_name | SIG名称 |
| projects| gitee仓名 |
| project-path | OpenHarmony下的归档路径，若不涉及回合OpenHarmony填写NONE |
......@@ -222,12 +222,12 @@ SIG信息记录统一归档在OpenHarmony/community仓库的sig目录内：
```
"sigs-List":[
{
"sig-name":"sig-python",
"sig_name":"sig_python",
"projects":"https://gitee.com/openharmony-sig/python",
"project-path":"python/"
},
{
"sig-name":"sig-updates",
"sig_name":"sig_updates",
"projects":["https://gitee.com/openharmony/startup_appspawn_lite", "https://gitee.com/openharmony/startup_bootstrap_lite"],
"project-path":["base/startup/appspawn_lite", "base/startup/bootstrap_lite"]
},
......
sig/README-EN.md → sig/README_EN.md
浏览文件 @ 6044e138
......@@ -6,11 +6,11 @@ Under the guidance of the Project Management Committee (PMC), a special interest
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:
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:
-Create background information for the SIG
-Create the business scope of the SIG
-Create business goals for the SIG
2. The SIG leader sends the SIG proposal via an email with the title [New-SIG-Proposal-XXX] to dev@openharmony.io.
2. The SIG leader sends the SIG proposal via an email with the title [New-sig_Proposal-XXX] to dev@openharmony.io.
3. Wait for the PMC or the corresponding field SIG, Committer to approve the proposal, the proposer could filed agenda collection on [PMC](https://docs.qingque.cn/s/home/eZQB8yRFQfEFeAxk_6JKZEE0q?identityId=1tbICPd8j3s), PMC will periodic organization review meeting for the proposal. The proposer could go to the [Community](https://gitee.com/openharmony/community) repository to create a Pull Request to create a new SIG after passing the review and perfecting it in accordance with the review comments.
-**Important**: If you need to apply for a new warehouse in the SIG, please report the issue of new parts to the [Architecture SIG](https://shimo.im/sheets/StzhuFkEk38enrnl/MODOC).
......@@ -20,7 +20,7 @@ This repository stores information about all the SIGs in the OpenHarmony communi
## Operating and Maintaining an SIG
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.
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.
......@@ -44,7 +44,7 @@ SIG data is stored in the **sig** directory of the **OpenHarmony/community** rep
### sigs.json File
| Field | Description |
|:---|:---|
| sig-name | SIG name |
| sig_name | SIG name |
| projects| Gitee repository name |
| project-path | Archive path of the OpenHarmony project. Enter **NONE** if the code of the SIG does not need to be incorporated into the master code of OpenHarmony. |
......@@ -52,12 +52,12 @@ SIG data is stored in the **sig** directory of the **OpenHarmony/community** rep
```
"sigs-List":[
{
"sig-name":"sig-python",
"sig_name":"sig_python",
"projects":"https://gitee.com/openharmony-sig/python",
"project-path":"python/"
},
{
"sig-name":"sig-updates",
"sig_name":"sig_updates",
"projects":["https://gitee.com/openharmony/startup_appspawn_lite", "https://gitee.com/openharmony/startup_bootstrap_lite"],
"project-path":["base/startup/appspawn_lite", "base/startup/bootstrap_lite"]
},
......
sig/sig-ai-framework/sig-ai-framework.md → sig/sig_ai_framework/sig_ai_framework.md
浏览文件 @ 6044e138
# SIG-AI-Framework
# sig_AI_Framework
English | [简体中文](./sig-ai-framework_cn.md)
English | [简体中文](./sig_ai_framework_cn.md)
Note: The content of this SIG follows the convention described in OpenHarmony's PMC Management Charter [README](/zh/pmc.md).
......@@ -27,7 +27,7 @@ Neural Network Runtime is an important bridge between On-Device inference framew
- AI Subsystem Architecture
![figures/ai-framework-arch-en.png](figures/ai-framework-arch-en.png)
![figures/ai_framework_arch_en.png](figures/ai_framework_arch_en.png)
### The repository
| Component Name | Component Functionality Description | Component repository name |
......
sig/sig-ai-framework/sig-ai-framework_cn.md → sig/sig_ai_framework/sig_ai_framework_cn.md
浏览文件 @ 6044e138
# SIG-AI-Framework
# sig_AI_Framework
简体中文 | [English](./sig-ai-framework.md)
简体中文 | [English](./sig_ai_framework.md)
说明：本SIG的内容遵循OpenHarmony的PMC管理章程 [README](/zh/pmc.md)中描述的约定。
......@@ -27,7 +27,7 @@ AI原子能力/服务接口分为能力和服务接口，能力接口是对AI模
- AI子系统架构
![figures/ai-framework-arch.png](figures/ai-framework-arch.png)
![figures/ai_framework_arch.png](figures/ai_framework_arch.png)
## 代码仓
| 部件名称 | 部件功能描述 | 部件仓名称 |
......
sig/sig-ai_framework_integration/sig_ai_framework_integration.md → sig/sig_ai_framework_integration/sig_ai_framework_integration.md
浏览文件 @ 6044e138
......@@ -29,9 +29,9 @@ Integrates current state of art high quality open sourced AI inference framework
### Meetings
- Meeting time：time：Biweek Tuesday 19:00, UTC+8
- Meeting application: Refer to the method of [PMC meeting](https://gitee.com/dongjinguang/community/blob/master/zh/pmc.md#pmc%E4%BC%9A%E8%AE%AE%E9%93%BE%E6%8E%A5) to provide the shimo sharing document weblink, convenient for SIG-related people to apply for the topic.
- Meeting application: Refer to the method of [PMC meeting](https://gitee.com/dongjinguang/community/blob/master/zh/pmc.md#pmc%E4%BC%9A%E8%AE%AE%E9%93%BE%E6%8E%A5) to provide the shimo sharing document weblink, convenient for sig_related people to apply for the topic.
- Meeting link: Welink Meeting or Others
- Meeting notification: [Subscribe](https://lists.openatom.io/postorius/lists/sig-ai_framework_integration.openharmony.io/) mailing list [sig-ai_framework_integration@openharmony.i]() for the meeting link
- Meeting notification: [Subscribe](https://lists.openatom.io/postorius/lists/sig_ai_framework_integration.openharmony.io/) mailing list [sig_ai_framework_integration@openharmony.i]() for the meeting link
- Meeting-Minutes: [Archive link address](https://gitee.com/openharmony-sig/sig-content/tree/master/ai_framework_integration/meetings)
### Contact (optional)
......
sig/sig-ai_framework_integration/sig-ai_framework_integration_cn.md → sig/sig_ai_framework_integration/sig_ai_framework_integration_cn.md
浏览文件 @ 6044e138
......@@ -33,8 +33,8 @@
- 会议申报：[AI 推理框架集成 Meeting Proposal]()
- 会议方式: 腾讯会议
- 会议通知: 请[订阅](https://lists.openatom.io/postorius/lists/sig-ai_framework_integration.openharmony.io/)邮件列表 sig-ai_framework_integration@openharmony.io 获取会议链接
- 会议纪要: [归档链接地址](https://gitee.com/openharmony-sig/sig-content/tree/master/ai_framework_integration/meetings)
- 会议通知: 请[订阅](https://lists.openatom.io/postorius/lists/sig_ai_framework_integration.openharmony.io/)邮件列表 sig_ai_framework_integration@openharmony.io 获取会议链接
- 会议纪要: [归档链接地址](https://gitee.com/openharmony-sig/sig_content/tree/master/ai_framework_integration/meetings)
### 联系方式(可选)
......
sig/sig-api/sig-api.md → sig/sig_api/sig_api.md
浏览文件 @ 6044e138
# SIG_API
English | [简体中文](./sig-api_cn.md)
English | [简体中文](./sig_api_cn.md)
Note: The content of this SIG follows the convention described in OpenHarmony's PMC Management Charter [README](/zh/pmc.md).
......
sig/sig-api/sig-api_cn.md → sig/sig_api/sig_api_cn.md
浏览文件 @ 6044e138
# SIG_API
简体中文 | [English](./sig-api.md)
简体中文 | [English](./sig_api.md)
说明：本SIG的内容遵循OpenHarmony的PMC管理章程 [README](/zh/pmc.md)中描述的约定。
......
sig/sig-appframework/sig-appframework_cn.md → sig/sig_appframework/sig_appframework_cn.md
浏览文件 @ 6044e138
# SIG_ApplicationFramework
简体中文 | [English](./sig-appframework_cn.md)
简体中文 | [English](./sig_appframework_cn.md)
说明：本SIG的内容遵循OpenHarmony的PMC管理章程 [README](/zh/pmc.md)中描述的约定。
......@@ -13,7 +13,7 @@ ApplicationFramework相关的设计评审、提交评审、《OpenHarmony Applic
ApplicationFramework SIG技术栈范围全景图如下图所示：
![ApplicationFramework SIG技术栈范围全景图](figures/appframework-overview.png)
![ApplicationFramework SIG技术栈范围全景图](figures/appframework_overview.png)
## 代码仓
| 部件名称 | 部件功能描述 | 部件仓名称 |
......
sig/sig-basicsoftwareservice/sig-basicsoftwareservice.md → sig/sig_basicsoftwareservice/sig_basicsoftwareservice.md
浏览文件 @ 6044e138
# SIG_BasicSoftwareService
English | [简体中文](./sig-basicsoftwareservice_cn.md)
English | [简体中文](./sig_basicsoftwareservice_cn.md)
Note: The content of this SIG follows the convention described in OpenHarmony's PMC Management Charter [README](/zh/pmc.md).
......@@ -89,7 +89,7 @@ Basic Software Services includes the following sub-systems:
### Meetings
- Meeting time: Wednesday at 14:00 o'clock, biweekly
- Meeting proposal: [OpenHarmony SIG-BasicSoftware Meeting Proposal](https://etherpad.openharmony.cn/p/sig-basicsoftware)
- Meeting proposal: [OpenHarmony sig_BasicSoftware Meeting Proposal](https://etherpad.openharmony.cn/p/sig_basicsoftware)
- Meeting link: Welink
### Contact (optional)
......
sig/sig-basicsoftwareservice/sig-basicsoftwareservice_cn.md → sig/sig_basicsoftwareservice/sig_basicsoftwareservice_cn.md
浏览文件 @ 6044e138
# SIG_BasicSoftwareService
简体中文 | [English](./sig-basicsoftwareservice.md)
简体中文 | [English](./sig_basicsoftwareservice.md)
说明：本SIG的内容遵循OpenHarmony的PMC管理章程 [README](/zh/pmc.md)中描述的约定。
......@@ -10,7 +10,7 @@
BasicSoftwareService SIG技术栈范围全景图如下图所示：
![image-20220722232522588](./images/overview-zh.png)
![image-20220722232522588](./images/overview_zh.png)
### 工作范围
基础软件服务主要包括以下几个子系统：
......@@ -107,7 +107,7 @@ BasicSoftwareService SIG技术栈范围全景图如下图所示：
### 会议
- 会议时间: 双周三 14:00
- 会议申报: [OpenHarmony SIG-BasicSoftware Meeting Proposal](https://etherpad.openharmony.cn/p/sig-basicsoftware)
- 会议申报: [OpenHarmony sig_BasicSoftware Meeting Proposal](https://etherpad.openharmony.cn/p/sig_basicsoftware)
- 会议链接: Welink
### 联系方式(可选)
......
sig/sig-blockchain/sig_blockchain_cn.md → sig/sig_blockchain/sig_blockchain_cn.md
浏览文件 @ 6044e138
# SIG_BlockChain
简体中文 | [English](./sig_blockchain.md)
说明：本SIG的内容遵循OpenHarmony的PMC管理章程 [README](https://gitee.com/openharmony/community/blob/master/zh/pmc.md)中描述的约定。
## SIG组工作目标和范围
### 工作目标
致力于探索物联网 + 区块链方向，打造「安全可信」物联网操作系统，为OpenHarmony OS用户提供原生、友好、通用化的“上链”能力，满足用户在数据隐私服务，设备安全服务，身份保护服务的需求，打造物链网系统生态场景（碳中和、车生态、智慧城市、智慧社区、智能家居），构建万物互联场景下数字化可信基石。
### 业务范围
- OpenHarmony数据上链功能以及兼容性需求
提供OpenHarmony数据上链功能，深度定制可适配OpenHarmony的数据上链组件
- 样例工程
创建物联网 + 区块链样例工程，给其他厂商做参考
- 生态拓展
积极与物联网设备厂商进行洽谈合作，推动物链网应用场景落地，推广物链网操作系统生态。探索OpenHarmony + Blockchain在碳中和、车生态场景下的应用。
## SIG相关代码仓及描述
交付件形式：源码、文档等
- block_chain:https://gitee.com/openharmony-sig/security_block_chain
## SIG组成员
### Leader
- [shangxuan_hz](https://gitee.com/shangxuan_hz)
### Committers列表
- [haisong2](https://gitee.com/haisong2)
- [Lee](https://gitee.com/www.lee.com)
- [platformdepartment](https://gitee.com/platformdepartment)
- [lingfengbao](https://gitee.com/lingfengbao)
- [max_mars](https://gitee.com/max_mars)
- [jiafeicheng](https://gitee.com/15335180944)
- [xkwang1228](https://gitee.com/xkwang1228)
- [jerryma0912](https://gitee.com/jerryma0912)
- [painterq](https://gitee.com/painterq)
### 会议
- 会议时间：双周例会，周二下午16:00（暂定）
- 会议链接：https://meeting.tencent.com/s/653ACaiONpYZ
### 联系方式(可选)
- 邮件列表：
- zulip群组：https://zulip.openharmony.cn
- 微信群：
# SIG_BlockChain
简体中文 | [English](./sig_blockchain.md)
说明：本SIG的内容遵循OpenHarmony的PMC管理章程 [README](https://gitee.com/openharmony/community/blob/master/zh/pmc.md)中描述的约定。
## SIG组工作目标和范围
### 工作目标
致力于探索物联网 + 区块链方向，打造「安全可信」物联网操作系统，为OpenHarmony OS用户提供原生、友好、通用化的“上链”能力，满足用户在数据隐私服务，设备安全服务，身份保护服务的需求，打造物链网系统生态场景（碳中和、车生态、智慧城市、智慧社区、智能家居），构建万物互联场景下数字化可信基石。
### 业务范围
- OpenHarmony数据上链功能以及兼容性需求
提供OpenHarmony数据上链功能，深度定制可适配OpenHarmony的数据上链组件
- 样例工程
创建物联网 + 区块链样例工程，给其他厂商做参考
- 生态拓展
积极与物联网设备厂商进行洽谈合作，推动物链网应用场景落地，推广物链网操作系统生态。探索OpenHarmony + Blockchain在碳中和、车生态场景下的应用。
## SIG相关代码仓及描述
交付件形式：源码、文档等
- block_chain:https://gitee.com/openharmony-sig/security_block_chain
## SIG组成员
### Leader
- [shangxuan_hz](https://gitee.com/shangxuan_hz)
### Committers列表
- [haisong2](https://gitee.com/haisong2)
- [Lee](https://gitee.com/www.lee.com)
- [platformdepartment](https://gitee.com/platformdepartment)
- [lingfengbao](https://gitee.com/lingfengbao)
- [max_mars](https://gitee.com/max_mars)
- [jiafeicheng](https://gitee.com/15335180944)
- [xkwang1228](https://gitee.com/xkwang1228)
- [jerryma0912](https://gitee.com/jerryma0912)
- [painterq](https://gitee.com/painterq)
### 会议
- 会议时间：双周例会，周二下午16:00（暂定）
- 会议链接：https://meeting.tencent.com/s/653ACaiONpYZ
### 联系方式(可选)
- 邮件列表：
- zulip群组：https://zulip.openharmony.cn
- 微信群：
sig/sig_list.toml
浏览文件 @ 6044e138
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或