提交 eccd88df 编写于 作者: S SimonLi

Merge branch 'master' of https://gitee.com/kkup180/community

* 'master' of https://gitee.com/kkup180/community: (32 commits)
  !566 add drivers_interface repository * add drivers_interface repository
  Description:[meeting] update MoM of PMC meeting on 20211125 Bug: NA Test: It could be normally readable
  !565 Add exfat-utils repos for kernel-sig * Add exfat-utils for kernel-sig
  !564 添加开源仓openh264  Add new thirdparty software openh264
  !547 新增 sig-crossplatformui 组信息 * feat: add sig-cross
  !554 sig robotics doc init * sig robotics doc init
  !552 sig-release中增加维护committer * xiezhiwei3@huawei.com
  update zh/committer.md. Signed-off-by: renwei <renwei8@huawei.com>
  !541 增加 commiter Merge pull request !541 from xuchangzhou/master
  !529 sig-print PR申请 * eric:add info for sig-print
  !544 update MoM of PMC meeting * Description:[meeting] update recently MoM of PMC meeting on 20211109
  新建EGL和openGLES仓
  dy200 device and vendor project name modify
  !532 sig孵化准出申请,涉及third_party_nghttp2以及communication_netstack * sig孵化准出申请,涉及third_party_nghttp2以及communication_netstack
  add rockchip device/vendor owner
  add sig-test file Signed-off-by: NicoYam <renxiang11@huawei.com>
  add sig-test file Signed-off-by: NicoYam <renxiang11@huawei.com>
  add sig-test file Signed-off-by: NicoYam <renxiang11@huawei.com>
  add sig-test file Signed-off-by: NicoYam <renxiang11@huawei.com>
  add sig-test file
  ...
# PMC 例会 2021-11-09
## 参会人员 (Attendance):
| 姓名 | 账号 |
| :----: | :----: |
| 董金光 |[@dongjinguang](https://gitee.com/dongjinguang) |
| 任革林 | [@im-off-this-week](https://gitee.com/im-off-this-week) |
| 强波 | [@huawei_qiangbo](https://gitee.com/huawei_qiangbo) |
| 鲜余强 | [@klooer](https://gitee.com/klooer) |
| 余枝强 | [@yuzhiqiang101](https://gitee.com/yuzhiqiang101) |
| 梁克雷 | [@xzmu](https://gitee.com/xzmu) |
| 黄明龙 | [@minglonghuang](https://gitee.com/minglonghuang) |
| 李家欣 | [@ninalijiaxin](https://gitee.com/ninalijiaxin) |
| 丁勇 | [@ding-yong](https://gitee.com/ding-yong) |
| 邢文华 | [@xhuazi](https://gitee.com/xhuazi) |
| 高涵一 | [@gaohanyi1982](https://gitee.com/gaohanyi1982) |
| 王意明 | [@youthdragon](https://gitee.com/youthdragon) |
| 议题相关人员 | 议题相关人员|
| | |
## 议题(Agenda):
1. PMC etherpad 议题列表 [No10~16](https://etherpad.openharmony.cn/p/pmc)
## 会议纪要(Minute of Meeting):
| 议题编号 | 议题名称 |会议纪要 |
| :----: | :----: | :----: |
| No10 | 社区开发板流水线资源部署 | 同意采取主线CI流水线+ 三方流水线门禁分摊CI门禁资源支撑开发板OpenHarmony 社区主线 |
| No11 | 社区开发板、芯片孵化准出到主线标准 | 1. 开发板采取device soc/board架构解耦 <br> 2. 开发板进主线满足PCS最小集且能通过XTS测试认证 <br> 3. 由李开龙整理输出开发板准出标准文档 |
| No12 | 社区编程规范刷新评审 | 1. 按照评审意见刷新编程规范指导文档 <br> 2. DFX日志输出规范、补充HDF编码规范、新增C语言实现面向对象的规范等遗留问题 |
| No13 | Devboard开发板准出规范 | 1. 同议题No11 <br> 2. 参见No11 结论3 |
| No14 | taro sig设立申请 | 1. sig命名建议不体现taro具体名称,修改更通用快应用、小程序转换的SIG命名 <br> 2. 同意新建快应用、小程序的转换工具的SIG |
| No15 | vulnerability sig成立 | 遗留:待安工治理工作组的策略再安排评审 |
| No16 | 申请成立 物联感知网 SIG | 1. 同意创建物联网感知SIG <br> 2. 建议该SIG聚焦物联场景通信感知、增强等能力 <br> 3. 需要补充对应领域的测试贡献|
| | | |
# PMC 例会 2021-11-09
## 参会人员 (Attendance):
| 姓名 | 账号 |
| :----: | :----: |
| 董金光 |[@dongjinguang](https://gitee.com/dongjinguang) |
| 任革林 | [@im-off-this-week](https://gitee.com/im-off-this-week) |
| 强波 | [@huawei_qiangbo](https://gitee.com/huawei_qiangbo) |
| 鲜余强 | [@klooer](https://gitee.com/klooer) |
| 余枝强 | [@yuzhiqiang101](https://gitee.com/yuzhiqiang101) |
| 梁克雷 | [@xzmu](https://gitee.com/xzmu) |
| 黄明龙 | [@minglonghuang](https://gitee.com/minglonghuang) |
| 李家欣 | [@ninalijiaxin](https://gitee.com/ninalijiaxin) |
| 赵文华 | [@shidi_snow](https://gitee.com/shidi_snow) |
| 邢文华 | [@xhuazi](https://gitee.com/xhuazi) |
| 高涵一 | [@gaohanyi1982](https://gitee.com/gaohanyi1982) |
| 万承臻 | [@wanchengzhen](https://gitee.com/wanchengzhen) |
| 议题相关人员 | 议题相关人员|
| | |
## 议题(Agenda):
1. PMC etherpad 议题列表 [No17~19](https://etherpad.openharmony.cn/p/pmc)
## 会议纪要(Minute of Meeting):
| 议题编号 | 议题名称 |会议纪要 |
| :----: | :----: | :----: |
| No17 | 申请辞去API SIG Leader工作 | 同意,后续API SIG由强波 来担任|
| No18 | 在开源社区提供C,C++ API参考 | 1. 需要在社区补齐XTS范围内的C、C++接口参考(POSIX标准类接口不提供) <br> 2. HDI部分暂未稳定,暂不提供 |
| No19 | 申请成立 LTS维护 SIG | 1. 遗留问题: 补充业界多仓管理的开源项目,不同分支的代码漏洞、需求管理的策略-- 责任人: 钟小明 <br> 2. 共同参与release-sig一起工作,针对当前存在的问题和优化策略补充完善,一起参与到releasesig的运作中来 |
| | | |
# OpenHarmony LTS版本路标管理已迁移至[SIG_Release](https://gitee.com/openharmony/release-management/blob/master/openharmony-1.0.1%20LTS%20RoadMap.md)进行维护
# OpenHarmony LTS版本路标管理已迁移至[SIG_Release](https://gitee.com/openharmony/release-management/blob/master/OpenHarmony-LTS-RoadMap.md)进行维护
......@@ -15,7 +15,7 @@ English | [简体中文](./guidance_for_incubation_project_graduation_cn.md)
| PMC| Huang Minglong| [minglonghuang](https://gitee.com/minglonghuang) |
| Architecture SIG| Ren Gelin| [im-off-this-week](https://gitee.com/im-off-this-week) |
| Security SIG| Zhang Adong|[zhangadong](https://gitee.com/zhangadong) |
| Test SIG| Nie Xin|[nie-x](https://gitee.com/nie-x) |
| Test SIG| Gao Hanyi | [gaohanyi1982](https://gitee.com/1982) |
| Test SIG| Wang Juntao| [wangjuntao](https://gitee.com/buranfanchen) |
| Infrastructure SIG| Wang Yiming| [youthdragon](https://gitee.com/youthdragon) |
| API SIG | Zhang Yongzhi| [zhangyongzhi](https://gitee.com/karl-z)|
......
......@@ -15,7 +15,7 @@ SIG孵化项目毕业评审组织
| PMC | 黄明龙 | [minglonghuang](https://gitee.com/minglonghuang) |
| 架构 SIG | 任革林 | [im-off-this-week](https://gitee.com/im-off-this-week) |
| 安全 | 张阿东 |[zhangadong](https://gitee.com/zhangadong) |
| 测试 SIG | 聂欣 |[nie-x](https://gitee.com/nie-x) |
| 测试 SIG | 高涵一 |[gaohanyi1982](https://gitee.com/gaohanyi1982) |
| 测试 SIG | 王俊涛 | [wangjuntao](https://gitee.com/buranfanchen) |
| 基础设施SIG | 王意明 | [youthdragon](https://gitee.com/youthdragon) |
| API SIG | 张勇智 | [zhangyognzhi](https://gitee.com/karl-z) |
......
### 缺陷来源
分两种:社区开发者提交的需求和测试sig在测试过程发现的缺陷提交的issue。
<br>
整体出来过程如下图:
# 缺陷类Issue处理指导
![图片说明](http://image.huawei.com/tiny-lts/v1/images/f81aa437fe1f4f18531aa956ead45a00_1035x656.png@900-0-90-f.png)
### 缺陷的创建
## 缺陷来源
社区开发者提交的需求和测试sig在测试过程发现的缺陷提交的issue。
流程如下图:
![图片说明](figures/issue.png)
## 缺陷的创建
[规则 1]:所有缺陷创建按照模板提交
**【模块名_概率】简要描述:**
......@@ -31,7 +33,7 @@
- 1. Log、截图、多媒体文件等,所有和问题有关的信息:
### 缺陷审核
## 缺陷审核
- [规则 1]:缺陷审核责任人:测试提交缺陷由测试sig组织确认和审核,社区开发者提交缺陷由sig组组织确认和审核<br>
- [规则 2]:issue各字段需要确保正确,正确的issue字段是度量的基础,在审核环节需要刷新issue的状态,issue的优先级、指定issue责任人<br>
- [规则 3]:如果经过审核和提交人达成一致,明确是非问题的,可以直接关闭,状态为“已取消”<br>
......@@ -39,7 +41,7 @@
- [规则 5]:如果经过审核和提交人达成一致,明确是问题,但是版本不解决,当前可以直接关闭,状态为“挂起”<br>
- [规则 6]:如果经过审核和提交人无法达成一致,此类缺陷提交到联合sig组,组织技术评审,按照评审结论执行,或解决或挂起<br>
### 缺陷的修改
## 缺陷的修改
- [规则 1]:缺陷修改描述清楚问题发生原因和定位过程。<br>
- [规则 2]:先定位后修改,原因分析需填写原因分析和修改方案,如有设计文档,按需附上设计文档,指导后续的测试设计和验证。<br>
- [规则 3]:测试用例设计,白盒自动化用例要做到代码逻辑全覆盖,手工测试用例要做到修改场景上的覆盖。建议:如果修改代码量在50行以下,设计测试用例不少于5条;50行及以上,测试用例在代码行的10%以上;<br>
......
......@@ -25,6 +25,7 @@
### 需求类issue各字段的要求
- issue状态字段是跟踪管理issue重要的信息,需要在处理issue环节及时更新
| 状态字段 | 负责人 | 描述 |
| ------------ | ------------ | ------------ |
| 待办 | 提交者 | 任何开发者都可以提交需求到社区,初始状态为待办 |
......
# OpenHarmony 代码门禁质量要求、活动定义及实践介绍
# OpenHarmony代码门禁质量要求、活动定义及实践介绍
代码门禁的使用场景:当开发者完成一个issue(Feature、Task、Bug),准备提交PR合入开源主干,在代码合入主干前,会触发代码检视、代码门禁流水线,其中代码门禁负责检查待合入PR新增或者修改的所有文件是否达到质量要求。达到质量要求才允许合入开源主干;否则该PR需要开发者修订检查出来的问题,继续重复提交PR动作。
注意:代码门禁的触发以issue为单位,支持一个Issue下面挂多个PR的情况,原因是研发中存在一个Issue单需要多人联合开发场景,或者说多个PR存在关联关系,为了避免代码门禁的重复构建或者PR间的相互依赖,需要以Issue为单位多PR提交后,再触发代码门禁执行。
代码门禁的活动定义及实践:代码门禁活动主要分为流水线触发(码云触发流水线执行:webhook模式)、代码下载、构建、部署、测试几个步骤,可参考图-1;其中主要的检查项包含:编译检查、静态/安全/开源检查、敏感词/copyright扫描、部署、冒烟测试、功能测试;因为OpenHarmony涉及多型号开发板验证,为了提升门禁执行效率,使用了基于提交PR识别的精准构建和精准测试。门禁检查结果可以通过码云提交PR的评论区查看(参考图-2)或者直接访问Http://ci.openharmony.cn查看结果(参考图-3)。
**代码门禁的使用场景**:当开发者完成一个issue(Feature、Task、Bug),准备提交PR合入开源主干,在代码合入主干前,会触发代码检视、代码门禁流水线,其中代码门禁负责检查待合入PR新增或者修改的所有文件是否达到质量要求。达到质量要求才允许合入开源主干;否则该PR需要开发者修订检查出来的问题,继续重复提交PR动作。
注意:代码门禁的触发以issue为单位,支持一个Issue下面挂多个PR的情况,原因是研发中存在一个Issue单需要多人联合开发场景,或者说多个PR存在关联关系,为了避免代码门禁的重复构建或者PR间的相互依赖,需要以Issue为单位多PR提交后,再触发代码门禁执行。
## 代码门禁活动定义
**代码门禁的活动定义及实践**
代码门禁活动主要分为流水线触发(码云触发流水线执行:webhook模式)、代码下载、构建、部署、测试几个步骤,如下图所示。
图-1:代码门禁的主要活动和实践
![图一](figures/p1.png)
其中主要的检查项包含:编译检查、静态/安全/开源检查、敏感词/copyright扫描、部署、冒烟测试、功能测试。由于OpenHarmony涉及多型号开发板验证,为了提升门禁执行效率,基于提交PR识别精准构建和精准测试。
门禁检查结果可以通过码云提交PR的评论区查看(参考图-2)或者直接访问Http://ci.openharmony.cn查看结果(参考图-3)。
图-2:在码云评论区可以直接查看代码门禁执行结果
![图-2](figures/p2.png)
图-3:OpenHarmony的Ci门户网站,可以直接访问Http://Ci.openharmony.cn ;查看代码门禁、每日版本构建的详细情况。可点击每笔记录,查看详情。
可以直接访问Http://Ci.openharmony.cn ,查看代码门禁、每日版本构建的详细情况。可点击每笔记录,查看详情。
![图-3](figures/P3.png)
图-3:OpenHarmony的Ci门户网站
![图-3](figures/p3.png)
# 代码门禁的质量要求:包含检查项、规范、及操作指南
代码门禁的质量要求:涉及的PR提交代码等文件必须通过各项检查,才允许代码合入主干。
当前门禁检查项包含:编译告警(涉及多型号开发板及模拟器)、构建规范检查(鸿蒙构建规范)、CodeCheck(静态/安全/开源检查、敏感词/copyright扫描)、部署(烧录)、测试(冒烟测试和功能测试)4个部分,下面具体来说明每个部分的检查项及要求。
## 代码门禁的质量要求:包含检查项、规范、及操作指南
代码门禁的质量要求:涉及的PR提交代码等文件必须通过各项检查,才允许代码合入主干。
当前门禁检查项包含:编译告警(涉及多型号开发板及模拟器)、构建规范检查(OpenHarmony构建规范)、CodeCheck(静态/安全/开源检查、敏感词/copyright扫描)、部署(烧录)、测试(冒烟测试和功能测试)4个部分,下面具体来说明每个部分的检查项及要求。
## 编译告警 <a name="section20979554791"></a>
### 编译告警 <a name="section20979554791"></a>
编译告警主要用于检查代码下载是否Ready(基线代码下载、PR代码获取)、编译环境是否Ready(prebuilds编译依赖工具、lfs二进制工具、node_modules、nodejs、build/lite等)、编译是否通过(全量编译、增量编译、缓存是否OK)、编译选项检查是否最优;
编译选项检查主要是针对C/C++语言编译选项或系统配置的检查,检查规范涉及语言选项、警告选项、安全选项、总体选项、代码生成选项、架构选项、优化选项、编译宏等。
参考 [Openharmony 编译选项规范](Openharmony_Compile_Rule.md)
参考 [OpenHarmony编译规范](编译规范.md)
## 构建规范检查 <a name="section20979554791"></a>
### 构建规范检查 <a name="section20979554791"></a>
为指导OpenHarmony的社区开发者开展构建工作,提升构建系统的可重复性、可维护性,提高构建质量,构建规范工作组分析总结了各种典型的构建问题,提炼相应的构建规则和建议,制订了规范,用于保障构建脚本的存放目录、文件格式、编写内容符合要求。
为指导OpenHarmony的社区开发者开展构建工作,提升构建系统的可重复性、可维护性,提高构建质量,构建规范工作组分析总结了各种典型的构建问题,提炼相应的构建规则和建议,制订了规范,用于保障构建脚本的存放目录、文件格式、编写内容符合要求。
具体规范参考[Openharmony 构建规范](Openharmony_Build_Rule.md)
具体规范参考《OpenHarmony构建规范 》
## CodeCheck检查 & 屏蔽
### CodeCheck检查 & 屏蔽
#### CodeCheck检查
CodeCheck支持静态扫描、安全扫描、代码度量、开源合规、敏感词扫描、Copyright等检查服务。对于检测问题存在争议,需要和Committer确认,是否为问题或者工具告警在当前代码上下文为非问题。Committer确认问题不用修改,可直接在Ci门户网站登录,系统会提供屏蔽功能,允许Committer屏蔽该问题,以保障该问题不再重复检测出现。
CodeCheck支持静态扫描、安全扫描、代码度量、开源合规、敏感词扫描、Copyright等检查服务。对于检测问题存在争议,需要和Committer确认,是否为问题或者工具告警在当前代码上下文为非问题。Committer确认问题不用修改,可直接在Ci门户网站登录,系统会提供屏蔽功能,允许Committer屏蔽该问题,以保障该问题不再重复检测出现。
##### 工具及服务使用
CI门户:选择任意一个PR的CodeCheck检查结果(包括“通过”、“不通过"、“失败”,若结果为“失败”表示未获取到扫描结果,即不支持查看),进入到代码检查结果查看页面。具体如下。
1、选择任意一个代码门禁CI流水线执行记录,进入详情查看页面
![](figures/P4.png)
CI门户:选择任意一个PR的CodeCheck检查结果(包括“通过”、“不通过"、“失败”,若结果为“失败”表示未获取到扫描结果,即不支持查看),进入到代码检查结果查看页面。具体如下。
1、选择任意一个代码门禁CI流水线执行记录,进入详情查看页面
![](figures/p4.png)
2、点击CodeCheck检查结果,例如:”不通过“,进入代码检查详情页面
![](figures/P5.png)
2、点击CodeCheck检查结果,例如:”不通过“,进入代码检查详情页面
![](figures/p5.png)
码云:从码云选择提交的PR(对应仓库下的Pull Requests),或从CI门户上选择任意一个PR进入详情后点击合入请求即跳转码云对应的PR,根据评论中start build的时间找到对应的合入记录,即可查看CodeCheck检查返回的结果。具体如下。
说明:从Gitee码云选择提交的PR(对应仓库下的Pull Requests),或从CI门户上选择任意一个PR进入详情后点击合入请求即跳转Gitee码云对应的PR,根据评论中start build的时间找到对应的合入记录,即可查看CodeCheck检查返回的结果。具体如下。
1、选择任意一个PR的合入请求即可跳转码云对应的PR,如下
码云入口:
![](figures/P6.png)
Gitee码云入口:
![](figures/p6.png)
CI门户入口:
![](figures/P7.png)
![](figures/p7.png)
2、根据评论中start build的时间找到对应的合入记录,即可查看CodeCheck检查返回的结果
2、根据评论中start build的时间找到对应的合入记录,即可查看CodeCheck检查返回的结果
![](figures/P2.png)
![](figures/p2.png)
##### 静态扫描
支持通用&安全编程规范集成;支持C/C++、JAVA、JS
具体规则参考 [Openharmony 通用编码规范](https://gitee.com/openharmony/docs/blob/master/zh-cn/contribute/%E8%B4%A1%E7%8C%AE%E4%BB%A3%E7%A0%81.md)
支持通用&安全编程规范集成;支持C/C++、JS、Java
具体规则参考 [OpenHarmony 通用编码规范](https://gitee.com/openharmony/docs/blob/master/zh-cn/contribute/%E8%B4%A1%E7%8C%AE%E4%BB%A3%E7%A0%81.md)
##### 安全扫描
支持C/C++、Java、JS语言安全编程规范的检查。
具体规则参考[Openharmony 安全编码规范](https://gitee.com/openharmony/docs/blob/master/zh-cn/contribute/%E8%B4%A1%E7%8C%AE%E4%BB%A3%E7%A0%81.md)
支持C/C++、JS、Java语言安全编程规范的检查。
具体规则参考[OpenHarmony 安全编码规范](https://gitee.com/openharmony/docs/blob/master/zh-cn/contribute/%E8%B4%A1%E7%8C%AE%E4%BB%A3%E7%A0%81.md)
##### 代码度量
支持单仓代码检查;支持代码行、重复率、重复文件数、函数数、圈复杂度总数统计和展示。
......@@ -89,50 +98,52 @@ CI门户入口:
#### 屏蔽指导
屏蔽操作主要针对一般以及上问题级别,未登录或者非代码仓的commiter用户无操作权限。当前的主要规则如下(黄区网络暂时无法屏蔽代码问题):
1、未解决问题可以修改为已忽略问题;
2、已忽略问题可以修改为未解决问题;
3、未解决问题和已忽略问题都无法修改已解决问题
屏蔽操作主要针对一般以及上问题级别,未登录或者非代码仓的committer用户无操作权限。当前的主要规则如下(黄区网络暂时无法屏蔽代码问题):
1. 未解决问题可以修改为已忽略问题。
2. 已忽略问题可以修改为未解决问题。
3. 未解决问题和已忽略问题都无法修改已解决问题。
##### 单个问题状态修改
根据过滤器查出出来的结果,选择问题,下拉菜单点击"已忽略"即可。
![](figures/P8.png)
根据过滤器查看结果,选择问题,下拉菜单点击"已忽略"即可。
![](figures/p8.png)
##### 批量操作问题修改
选择要修改的问题后点击 "批量操作",设置修改后的问题状态为"已忽略",然后“确认”即可。
![](figures/P9.png)
![](figures/p9.png)
![](figures/P10.png)
![](figures/p10.png)
## 部署升级及测试
门禁流水线测试涉及的测试活动主要有部署升级、冒烟测试、功能测试、API看护测试。精准测试是对功能测试及API看护测试用例挑选后的精确测试,具体如下:
门禁流水线测试涉及的测试活动主要有部署升级、冒烟测试、功能测试、API看护测试。精准测试是对功能测试及API看护测试用例挑选后的精确测试,具体如下:
#### 冒烟测试
冒烟测试是在软件开发过程中的一种针对软件版本包的快速基本功能验证策略,是对软件基本功能进行确认验证的手段,并非对软件版本包的深入测试。冒烟测试的对象是每一个新编译的需要正式测试的软件版本,关注的是阻塞型缺陷。
门禁冒烟测试用例是选择功能测试用例中level 0的用例,主要保障版本可以正常开关机,主功能可用,覆盖多种设备形态。
冒烟测试是在软件开发过程中的一种针对软件版本包的快速基本功能验证策略,是对软件基本功能进行确认验证的手段,并非对软件版本包的深入测试。冒烟测试的对象是每一个新编译的需要正式测试的软件版本,关注的是阻塞型缺陷。
门禁冒烟测试用例是选择功能测试用例中level 0的用例,主要保障版本可以正常开关机,主功能可用,覆盖多种设备形态。
#### 功能测试
功能测试是对产品的各功能模块进行验证,包含全量测试用例中level 0~5的用例。根据功能用例覆盖结果,测试产品是否达到各模块功能的质量要求。
功能测试是对产品的各功能模块进行验证,包含全量测试用例中level 0~5的用例。根据功能用例覆盖结果,测试产品是否达到各模块功能的质量要求。
#### API看护测试
根据代码仓与api头文件的关联关系,通过识别所提交的代码对代码仓头文件的修改,触发对应形态下自身代码仓的XTS用例的执行。
根据代码仓与api头文件的关联关系,通过识别所提交的代码对代码仓头文件的修改,触发对应形态下自身代码仓的XTS用例的执行。
#### 优化:精准构建&精准测试
根据代码仓与设备形态之间的关联关系,通过识别所提交的代码对代码仓文件的修改,触发对应形态下所修改的代码仓的TDD level0用例的执行。
根据代码仓与设备形态之间的关联关系,通过识别所提交的代码对代码仓文件的修改,触发对应形态下所修改的代码仓的TDD level0用例的执行。
#### 代码门禁测试用例上线规则
##### 门禁问题提单
1、门禁用例问题第一时间转给第一责任人,经分析后,由第一责任人继续往下分解
门禁用例问题第一时间转给第一责任人,经分析后,由第一责任人继续往下分解。
##### 门禁响应时间
1、TDD 用例上线门禁后,定位出用例导致的测试失败,需要两小时内闭环
TDD 用例上线门禁后,定位出用例导致的测试失败,需要两小时内闭环。
##### 门禁用例下线
1、用例问题两小时未解决的,需对应的责任田即时下线,不影响后续的门禁
用例问题两小时未解决的,需对应的责任田即时下线,不影响后续的门禁。
##### 门禁用例上线
1、用例重新上线或者新用例上线,需要责任人提供两天以上的稳定报告并知会我们(门禁看护人),
2、流水线这边压测48小时后才可重新上线
\ No newline at end of file
1. 用例重新上线或者新用例上线,需要责任人提供两天以上的稳定报告并知会我们(门禁看护人)。
2. 流水线这边压测48小时后才可重新上线。
\ No newline at end of file
# Openharmony 编译规范
# OpenHarmony编译规范
## 目的和范围
Openharmony 编译规范用于指导开发者规范地编写和修改编译相关的源码、脚本和工具,保证编译过程正确,可信,可重复和高效。
OpenHarmony编译规范用于指导开发者规范地编写和修改编译相关的源码、脚本和工具,保证编译过程正确,可信,可重复和高效。
## 术语
### 编译框架
Openharmony的编译系统就是用来构建Openharmony操作系统的一组软件,主要由模块编译模板,配置框架、发布框架组成。
OpenHarmony的编译系统就是用来构建OpenHarmony操作系统的一组软件,主要由模块编译模板,配置框架、发布框架组成。
Openharmony的编译系统主要由GN语言和python编写完成,通常GN用于描述编译过程和依赖关系,python用于执行特定的编译目标
OpenHarmony的编译系统主要由GN(Generate Ninja)语言和Python编写完成,通常GN用于描述编译过程和依赖关系,Python用于执行特定的编译目标
本文主要描述GN的相关编写要求
本文主要描述GN的相关编写要求
### GN
GN : Generate Ninja, 开源的编译工具,使用.gn文件定义和描述编译过程,并生成最终的编译过程清单,即ninja文件
GN : Generate Ninja, 开源的编译工具,使用.gn文件定义和描述编译过程,并生成最终的编译过程清单,即ninja文件
### Ninja
Ninja: 开源的编译执行工具,高效执行ninja文件描述的编译过程清单
Ninja: 开源的编译执行工具,高效执行ninja文件描述的编译过程清单
## GN 编写规范
......@@ -29,13 +29,13 @@ Ninja: 开源的编译执行工具,高效执行ninja文件描述的编译过
**禁止** :在gn中调用外部编译工具编译软件模块。
**反例** :在gn中使用action调用automake和Make来编译三方组件。
**要求** :需要将外部组件移植成gn的编译形式,避免编译过程对环境产生不必要的依赖,而且可获得编译框架提供的公共能力,包括不限于:安全编译选项,ASAN等。
**例外** :Linux Kernel 编译框架实际完成的用户态程序编译,内核完全可以在编译框架之外完成独立编译。某些平台实现为了实现一键编译,使用gn将内核编译加在编译过程中,是可以接 受的
**例外** :Linux Kernel 编译框架实际完成的用户态程序编译,内核完全可以在编译框架之外完成独立编译。某些平台实现为了实现一键编译,使用gn将内核编译加在编译过程中,是可以接受的。
### 规则1.2
**禁止** :禁止在模块的gn文件中,再次添加编译系统已经添加的安全编译选项。
**反例** :在模块的编译添加 `` -fstack-protector-strong``
**要求** :对于全局已经添加的默认选项,模块开发者应当知晓,不需要为了满足内外部规则再次添加
**要求** :对于全局已经添加的默认选项,模块开发者应当知晓,不需要为了满足内外部规则再次添加
| 编译选项 | 编译参数 | 默认值 |
|--|--|--|
......@@ -44,27 +44,27 @@ Ninja: 开源的编译执行工具,高效执行ninja文件描述的编译过
### 规则1.3
**禁止** :在gn中添加和默认编译选项相反的编译选项
**反例** :在自研模块中添加 ``-wno-unused`` 以消除编译告警
**要求** :默认的编译选项代表了系统的默认能力,自研模块有特殊情况需要去掉部分能力,必须有足有的理由
**例外** :移植三方组件,或者使用因为三方组件时,可根据三方组件的要求覆盖默认的编译选项
**禁止** :在gn中添加和默认编译选项相反的编译选项
**反例** :在自研模块中添加 ``-wno-unused`` 以消除编译告警
**要求** :默认的编译选项代表了系统的默认能力,自研模块有特殊情况需要去掉部分能力,必须有足有的理由
**例外** :移植三方组件,或者使用因为三方组件时,可根据三方组件的要求覆盖默认的编译选项
### 规则 2.1
**要求** :使用gn format 对添加或者修改的gn文件进行格式化,满足格式和排版的需求
**要求** :使用gn format 对添加或者修改的gn文件进行格式化,满足格式和排版的需求
### 规则 2.2
**建议** :编写action时,使用python而不是shell
**说明** : python 环境更容易保持统一,可以比较容易的多重操作系统上运行,并且扩展性可读性可测试更好
**建议** :编写action时,使用Python而不是shell。
**说明** : Python 环境更容易保持统一,可以比较容易的多重操作系统上运行,并且扩展性可读性可测试更好。
### 规则 2.3
**规则**:禁止在gn和ninja执行过程修改源码目录的内容
**说明**:包括但不限于给源码目录打patch,向源码目录中拷贝,在源码目录中执行编译,在源码目录生成中间文件等
**规则**:禁止在gn和ninja执行过程修改源码目录的内容
**说明**:包括但不限于给源码目录打patch,向源码目录中拷贝,在源码目录中执行编译,在源码目录生成中间文件等
### 规则 2.4
**规则**:编译脚本的编码格式设置为utf-8,换行符设置为unix格式
**反例** :在windows上编写脚本后,使用了中文注释并保存为本地编码
**规则**:编译脚本的编码格式设置为utf-8,换行符设置为unix格式
**反例** :在windows上编写脚本后,使用了中文注释并保存为本地编码
......@@ -30,7 +30,7 @@ Basic Software Services includes the following sub-systems:
|HiviewDFX|[hiviewdfx_hilog_lite](https://gitee.com/openharmony/hiviewdfx_hilog_lite)|base/hiviewdfx/hilog_lite|[stesen](https://gitee.com/stesen)|
|HiviewDFX|[hiviewdfx_hiview_lite](https://gitee.com/openharmony/hiviewdfx_hiview_lite)|base/hiviewdfx/hiview_lite|[stesen](https://gitee.com/stesen)|
|HiviewDFX|[third_party_curl](https://gitee.com/openharmony/third_party_curl)|third_party/curl|[stesen](https://gitee.com/stesen)|
|HiviewDFX|[third_party_nghttp2](https://gitee.com/openharmony-sig/third_party_nghttp2)|third_party/nghttp2|[zhuwenchao](https://gitee.com/xautosoft)|
|HiviewDFX|[third_party_nghttp2](https://gitee.com/openharmony/third_party_nghttp2)|third_party/nghttp2|[zhuwenchao](https://gitee.com/xautosoft)|
|HiviewDFX|[hiviewdfx_faultloggerd](https://gitee.com/openharmony/hiviewdfx_faultloggerd)|base/hiviewdfx/faultloggerd|[maplestorys](https://gitee.com/maplestorys)|
|HiviewDFX|[hiviewdfx_hiappevent](https://gitee.com/openharmony/hiviewdfx_hiappevent)|base/hiviewdfx/hiappevent|[stesen](https://gitee.com/stesen)|
|HiviewDFX|[hiviewdfx_hilog](https://gitee.com/openharmony/hiviewdfx_hilog)|base/hiviewdfx/hilog|[stesen](https://gitee.com/stesen)|
......@@ -63,6 +63,7 @@ Basic Software Services includes the following sub-systems:
|Notification|[notification_ces_standard](https://gitee.com/openharmony/notification_ces_standard)|base/notification/ces_standard|[autumn330](https://gitee.com/autumn330)|
|Notification|[notification_ans_standard](https://gitee.com/openharmony/notification_ans_standard)|base/notification/ans_standard|[autumn330](https://gitee.com/autumn330)|
|Account|[account_os_account](https://gitee.com/openharmony/account_os_account)|base/account/os_account|[verystone](https://gitee.com/verystone)|
|Account|[account_app_account](https://gitee.com/openharmony-sig/account_app_account)|base/account/app_account|[verystone](https://gitee.com/verystone)|
|ResourceSchedule|[resourceschedule_workscheduler](https://gitee.com/openharmony-sig/resourceschedule_workscheduler)|foundation/resourceschedule/workscheduler|[hujun211](https://gitee.com/hujun211)|
|ResourceSchedule|[resourceschedule_backgroundtaskmanager](https://gitee.com/openharmony-sig/resourceschedule_backgroundtaskmanager)|foundation/resourceschedule/backgroundtaskmanager|[FrankJone](https://gitee.com/FrankJone)|
|accessibility|[accessibility](https://gitee.com/openharmony-sig/accessibility)|base/accessibility|[xueyulong](https://gitee.com/ylsnow)|
......
......@@ -30,7 +30,7 @@
|DFX子系统|[hiviewdfx_hilog_lite](https://gitee.com/openharmony/hiviewdfx_hilog_lite)|base/hiviewdfx/hilog_lite|[stesen](https://gitee.com/stesen)|
|DFX子系统|[hiviewdfx_hiview_lite](https://gitee.com/openharmony/hiviewdfx_hiview_lite)|base/hiviewdfx/hiview_lite|[stesen](https://gitee.com/stesen)|
|DFX子系统|[third_party_curl](https://gitee.com/openharmony/third_party_curl)|third_party/curl|[stesen](https://gitee.com/stesen)|
|DFX子系统|[third_party_nghttp2](https://gitee.com/openharmony-sig/third_party_nghttp2)|third_party/nghttp2|[zhuwenchao](https://gitee.com/xautosoft)|
|DFX子系统|[third_party_nghttp2](https://gitee.com/openharmony/third_party_nghttp2)|third_party/nghttp2|[zhuwenchao](https://gitee.com/xautosoft)|
|DFX子系统|[hiviewdfx_faultloggerd](https://gitee.com/openharmony/hiviewdfx_faultloggerd)|base/hiviewdfx/faultloggerd|[maplestorys](https://gitee.com/maplestorys)|
|DFX子系统|[hiviewdfx_hiappevent](https://gitee.com/openharmony/hiviewdfx_hiappevent)|base/hiviewdfx/hiappevent|[stesen](https://gitee.com/stesen)|
|DFX子系统|[hiviewdfx_hilog](https://gitee.com/openharmony/hiviewdfx_hilog)|base/hiviewdfx/hilog|[stesen](https://gitee.com/stesen)|
......@@ -63,6 +63,7 @@
|事件通知子系统|[notification_ces_standard](https://gitee.com/openharmony/notification_ces_standard)|base/notification/ces_standard|[autumn330](https://gitee.com/autumn330)|
|事件通知子系统|[notification_ans_standard](https://gitee.com/openharmony/notification_ans_standard)|base/notification/ans_standard|[autumn330](https://gitee.com/autumn330)|
|账号子系统|[account_os_account](https://gitee.com/openharmony/account_os_account)|base/account/os_account|[verystone](https://gitee.com/verystone)|
|账号子系统|[account_app_account](https://gitee.com/openharmony-sig/account_app_account)|base/account/app_account|[verystone](https://gitee.com/verystone)|
|资源调度子系统|[resourceschedule_workscheduler](https://gitee.com/openharmony-sig/resourceschedule_workscheduler)|foundation/resourceschedule/workscheduler|[hujun211](https://gitee.com/hujun211)|
|资源调度子系统|[resourceschedule_backgroundtaskmanager](https://gitee.com/openharmony-sig/resourceschedule_backgroundtaskmanager)|foundation/resourceschedule/backgroundtaskmanager|[FrankJone](https://gitee.com/FrankJone)|
|无障碍软件服务子系统|[accessibility](https://gitee.com/openharmony-sig/accessibility)|base/accessibility|[xueyulong](https://gitee.com/ylsnow)|
......
{
"Leader": [
{
"gitee_id": "o2team",
"gitee_email": "o2labs@163.com"
}
],
"Committers": [
{
"gitee_id": "baosiqing",
"gitee_email": "baosiqing@jd.com"
},
{
"gitee_id": "medivhcai",
"gitee_email": "caishuai6@jd.com"
},
{
"gitee_id": "chenjj68",
"gitee_email": "chenjiajian@jd.com"
},
{
"gitee_id": "advancedcat",
"gitee_email": "hongxin@jd.com"
},
{
"gitee_id": "hawleyhuo",
"gitee_email": "huozhongyi@jd.com"
},
{
"gitee_id": "evernoteHW",
"gitee_email": "huwei161@jd.com"
},
{
"gitee_id": "JSZabc",
"gitee_email": "jiangshangze@jd.com"
},
{
"gitee_id": "showeb",
"gitee_email": "bin.liu@jd.com"
},
{
"gitee_id": "lumeiling3",
"gitee_email": "lumeiling@jd.com"
},
{
"gitee_id": "xiaojianshang",
"gitee_email": "shangxiaojian@jd.com"
},
{
"gitee_id": "tangjiao11",
"gitee_email": "tangjiao11@jd.com"
},
{
"gitee_id": "xuanzebin",
"gitee_email": "xuanzebin3@jd.com"
},
{
"gitee_id": "shuairuofukua",
"gitee_email": "xueshuai@jd.com"
}
]
}
\ No newline at end of file
# SIG-CROSS-PLATFORM-UI
SIG-CROSS-PLATFORM-UI
English | [简体中文](./sig_crossplatformui_cn.md)
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
CrossPlatformUI SIG aims to reduce the cost and difficulty of OpenHarmony UI layer development, so that OpenHarmony can reuse the massive development ecology and application ecology of Web side and small program side, and improve the efficiency of cross-platform development.
On the one hand, the CrossPlatformUI SIG extends various UI development paradigms for OpenHarmony, allowing developers to use technology stacks familiar with the front end (including programming frameworks such as React and Vue; Build tools such as Webpack, Vite) to develop OpenHarmony applications. The CrossPlatformUI SIG, on the other hand, enables applets and H5 applications to run directly on OpenHarmony, as well as a vast library of front-end ecosystem tools.
### work scope
- Cross-platform core adaptation
Develop and maintain a cross-platform adaptation core, including the ability to expand the UI paradigm for OpenHarmony and adapt Web applications and various applets to OpenHarmony.
- Component library, API library
Develop and encapsulate cross-platform component libraries and API libraries.
- Ecological expansion
Including the development of OpenHarmony compatible UI library and various ecological tools library, etc.
Actively cooperate with communities, universities and relevant customers.
### The repository
- project name:
- [https://gitee.com/o2team/Taro](https://gitee.com/o2team/Taro)
## SIG Members
### Leader
- [Taro](https://gitee.com/o2team/Taro)
### Committers
- [baosiqing](https://gitee.com/baosiqing)
- [medivhcai](https://gitee.com/medivhcai)
- [chenjj68](https://gitee.com/chenjj68)
- [advancedcat](https://gitee.com/advancedcat)
- [hawleyhuo](https://gitee.com/hawleyhuo)
- [evernoteHW](https://gitee.com/evernoteHW)
- [JSZabc](https://gitee.com/JSZabc)
- [showeb](https://gitee.com/showeb)
- [lumeiling3](https://gitee.com/lumeiling3)
- [xiaojianshang](https://gitee.com/xiaojianshang)
- [tangjiao11](https://gitee.com/tangjiao11)
- [xuanzebin](https://gitee.com/xuanzebin)
- [shuairuofukua](https://gitee.com/shuairuofukua)
### Meetings
- Meeting time:Every fortnight Thursday 17:00-18:00
- Meeting application: [OpenHarmony Taro Meeting Proposal](https://etherpad.openharmony.cn/p/taro%E8%AE%AE%E9%A2%98%E7%94%B3%E6%8A%A5)
- Meeting link: Tencent meeting
- Meeting notification: [Subscribe to](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/taro/meetings)
### Contact (optional)
- Mailing list:taro@jd.com
- Wechat group:
![](https://img13.360buyimg.com/ling/jfs/t1/199829/17/18179/761565/619df07aE2f32e9ba/2b328bf44471a1ab.png)
\ No newline at end of file
# SIG-CROSS-PLATFORM-UI
跨平台前端框架(crossplatform-jsframework)兴趣小组
简体中文 | [English](./sig_crossplatformui.md)
说明:本SIG的内容遵循OpenHarmony的PMC管理章程 [README](/zh/pmc.md) 中描述的约定。
## SIG组工作目标和范围
### 工作目标
CrossPlatformUI SIG 致力于降低 OpenHarmony UI 层的上手成本和开发难度,让 OpenHarmony 能够复用 Web 端和小程序端海量的开发生态和应用生态,提升跨平台开发的效率。
一方面 CrossPlatformUI SIG 为 OpenHarmony 扩展各类 UI 开发范式,让开发者能使用前端熟悉的技术栈(包括编程框架,如:React、Vue;构建工具,如:Webpack、Vite)去开发 OpenHarmony 应用。另一方面,CrossPlatformUI SIG 让小程序、H5 应用能够直接运行在 OpenHarmony 平台,也让海量的前端生态工具库能直接在 OpenHarmony 平台上使用。
### 工作范围
- 跨平台适配核心
开发和维护跨平台适配核心,包括为 OpenHarmony 拓展 UI 范式,让 Web 应用和各类小程序应用适配 OpenHarmony 的能力。
- 组件库、API 库
开发封装跨平台的组件库和 API 库。
- 生态拓展
包括开发适配 OpenHarmony 的 UI 库和各类生态工具库等。
积极与社区、高校和相关客户展开合作。
## 代码仓
- 代码仓地址:
- [https://gitee.com/o2team/Taro](https://gitee.com/o2team/Taro)
## SIG组成员
### Leader
- [Taro](https://gitee.com/o2team/Taro)
### Committers列表
- [baosiqing](https://gitee.com/baosiqing)
- [medivhcai](https://gitee.com/medivhcai)
- [chenjj68](https://gitee.com/chenjj68)
- [advancedcat](https://gitee.com/advancedcat)
- [hawleyhuo](https://gitee.com/hawleyhuo)
- [evernoteHW](https://gitee.com/evernoteHW)
- [JSZabc](https://gitee.com/JSZabc)
- [showeb](https://gitee.com/showeb)
- [lumeiling3](https://gitee.com/lumeiling3)
- [xiaojianshang](https://gitee.com/xiaojianshang)
- [tangjiao11](https://gitee.com/tangjiao11)
- [xuanzebin](https://gitee.com/xuanzebin)
- [shuairuofukua](https://gitee.com/shuairuofukua)
### 会议
- 会议时间:每双周周四 17:00-18:00
- 会议申报:[OpenHarmony Taro Meeting Proposal](https://etherpad.openharmony.cn/p/taro%E8%AE%AE%E9%A2%98%E7%94%B3%E6%8A%A5)
- 会议链接: 腾讯会议
- 会议通知: 请[订阅](https://lists.openatom.io/postorius/lists/dev.openharmony.io)邮件列表 dev@openharmony.io 获取会议链接
- 会议纪要: [归档链接地址](https://gitee.com/openharmony-sig/sig-content/tree/master/taro/meetings)
### 联系方式
- 邮件列表:taro@jd.com
- 微信群:
![](https://img13.360buyimg.com/ling/jfs/t1/199829/17/18179/761565/619df07aE2f32e9ba/2b328bf44471a1ab.png)
......@@ -9,12 +9,13 @@ Note: The content of this SIG follows the convention described in OpenHarmony's
### Driving related
### The repository
### The repository
- project name:
- drivers_framework: https://gitee.com/openharmony/drivers_framework
- drivers_peripheral: https://gitee.com/openharmony/drivers_peripheral
- drivers_adapter: https://gitee.com/openharmony/drivers_adapter
- drivers_adapter_khdf_linux: https://gitee.com/openharmony/drivers_adapter_khdf_linux
- drivers_interface:https://gitee.com/openharmony-sig/drivers_interface
## SIG Members
......@@ -31,7 +32,7 @@ Note: The content of this SIG follows the convention described in OpenHarmony's
- Meeting time: BiWeek Wednesday 16:00
- Meeting application: [SIG-Driver application](https://shimo.im/sheets/36GKhpvrXd8TcQHY)
- meeting link:Tencent meeting or other meeting
- Meeting notification: [Subscribe to](https://lists.openatom.io/postorius/lists/sig_driver.openharmony.io) mailing list for the
- Meeting notification: [Subscribe to](https://lists.openatom.io/postorius/lists/sig_driver.openharmony.io) mailing list for the
- Meeting Summary:To view the minutes of past meetings, please click this [link](https://gitee.com/openharmony-sig/sig-content/tree/master/driver/meetings)
### Contact (optional)
......
......@@ -17,6 +17,7 @@
- drivers_peripheral:https://gitee.com/openharmony/drivers_peripheral
- drivers_adapter:https://gitee.com/openharmony/drivers_adapter
- drivers_adapter_khdf_linux:https://gitee.com/openharmony/drivers_adapter_khdf_linux
- drivers_interface:https://gitee.com/openharmony-sig/drivers_interface
## SIG组成员
......
......@@ -29,9 +29,10 @@ OpenHarmony Graphics and Multimedia related design and review.
- third_party_libsnd:https://gitee.com/openharmony/third_party_libsnd
- third_party_pulseaudio:https://gitee.com/openharmony/third_party_pulseaudio
- third_party_ffmpeg:https://gitee.com/openharmony/third_party_ffmpeg
- third_party_libsoup:https://gitee.com/openharmony-sig/third_party_libsoup
- third_party_libpsl:https://gitee.com/openharmony-sig/third_party_libpsl
- third_party_gettext:https://gitee.com/openharmony-sig/third_party_gettext
- third_party_libsoup:https://gitee.com/openharmony/third_party_libsoup
- third_party_libpsl:https://gitee.com/openharmony/third_party_libpsl
- third_party_gettext:https://gitee.com/openharmony/third_party_gettext
- third_party_openh264:https://gitee.com/openharmony-sig/third_party_openh264
- graphic_standard:https://gitee.com/openharmony/graphic_standard
- graphic_surface:https://gitee.com/openharmony/graphic_surface
- graphic_ui:https://gitee.com/openharmony/graphic_ui
......@@ -43,6 +44,8 @@ OpenHarmony Graphics and Multimedia related design and review.
- third_party_wayland_standard:https://gitee.com/openharmony/third_party_wayland_standard
- third_party_libdrm:https://gitee.com/openharmony/third_party_libdrm
- third_party_pixman:https://gitee.com/openharmony/third_party_pixman
- third_party_egl:https://gitee.com/openharmony/third_party_egl
- third_party_opengles:https://gitee.com/openharmony/third_party_opengles
## SIG Members
......
......@@ -29,9 +29,10 @@ OpenHarmony 图形和媒体管理。
- third_party_libsnd:https://gitee.com/openharmony/third_party_libsnd
- third_party_pulseaudio:https://gitee.com/openharmony/third_party_pulseaudio
- third_party_ffmpeg:https://gitee.com/openharmony/third_party_ffmpeg
- third_party_libsoup:https://gitee.com/openharmony-sig/third_party_libsoup
- third_party_libpsl:https://gitee.com/openharmony-sig/third_party_libpsl
- third_party_gettext:https://gitee.com/openharmony-sig/third_party_gettext
- third_party_libsoup:https://gitee.com/openharmony/third_party_libsoup
- third_party_libpsl:https://gitee.com/openharmony/third_party_libpsl
- third_party_gettext:https://gitee.com/openharmony/third_party_gettext
- third_party_openh264:https://gitee.com/openharmony-sig/third_party_openh264
- graphic_standard:https://gitee.com/openharmony/graphic_standard
- graphic_surface:https://gitee.com/openharmony/graphic_surface
- graphic_ui:https://gitee.com/openharmony/graphic_ui
......@@ -43,6 +44,8 @@ OpenHarmony 图形和媒体管理。
- third_party_wayland_standard:https://gitee.com/openharmony/third_party_wayland_standard
- third_party_libdrm:https://gitee.com/openharmony/third_party_libdrm
- third_party_pixman:https://gitee.com/openharmony/third_party_pixman
- third_party_egl:https://gitee.com/openharmony/third_party_egl
- third_party_opengles:https://gitee.com/openharmony/third_party_opengles
## SIG组成员
......
......@@ -27,6 +27,7 @@ File system related open source software used by OpenHarmony lite equipment, inc
- repository14 name:https://gitee.com/openharmony-sig/third_party_fsck_msdos
- repository15 name:https://gitee.com/openharmony-sig/third_party_gptfdisk
- repository16 name:https://gitee.com/openharmony-sig/third_party_newfs_msdos
- repository17 name:https://gitee.com/openharmony-sig/third_party_exfat-utils
## SIG Members
......
......@@ -27,6 +27,7 @@
- repository14名称:https://gitee.com/openharmony-sig/third_party_fsck_msdos
- repository15名称:https://gitee.com/openharmony-sig/third_party_gptfdisk
- repository16名称:https://gitee.com/openharmony-sig/third_party_newfs_msdos
- repository17名称:https://gitee.com/openharmony-sig/third_party_exfat-utils
## SIG组成员
......
......@@ -21,6 +21,7 @@ Note: The content of this SIG follows the convention described in OpenHarmony's
- project name:
- https://gitee.com/openharmony-sig/knowledge
- https://gitee.com/openharmony-sig/knowledge_demo_smart_home
- https://gitee.com/openharmony-sig/knowledge_demo_temp
- https://gitee.com/openharmony-sig/online_event
## SIG Members
......
......@@ -21,6 +21,7 @@
- 代码仓地址:
- https://gitee.com/openharmony-sig/knowledge
- https://gitee.com/openharmony-sig/knowledge_demo_smart_home
- https://gitee.com/openharmony-sig/knowledge_demo_temp
- https://gitee.com/openharmony-sig/online_event
## SIG组成员
......
{
"Leader": [
{
"gitee_id": "eric.li",
"gitee_email": "eric.li@urovo.com"
}
],
"Committers": [
{
"gitee_id": "eric.li",
"gitee_email": "eric.li@urovo.com"
},
{
"gitee_id": "stur.guan",
"gitee_email": "stur.guan@urovo.com"
},
{
"gitee_id": "jorway.ou",
"gitee_email": "jorway.ou@urovo.com"
},
{
"gitee_id": "litao33",
"gitee_email": "litao33@huawei.com"
}
]
}
\ No newline at end of file
# SIG-Print
English | [简体中文](./sig_print_cn.md)
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
Print SIG aims to develop print function for OpenHarmony, expand and improve the ability for industry intelligent terminal and other devices. It can be expected that Print SIG will provide API for printable apps northwards to make application development easier, and establish standardized communication mode for built-in thermal printer, USB printer, Bluetooth printer, WiFi printer and other different interface devices southwards, unfreezing the limitations of plug-in style from print equipment vendors.
### work scope
1) Function realization and maintenance of printing service, and providing unified APIs for application.
2) Requirements of portability and compatibility, and providing a compatible solution for printers with different interfaces.
3) Providing a printable application demo
4) Negotiate and cooperate with printer manufacturers, promoting the process of OpenHarmony's southbound interface standardization
### The repository
- project name:
- print-sig:https://gitee.com/openharmony-sig/print
- print:https://gitee.com/openharmony/print
## SIG Members
### Leader
- @eric072(https://gitee.com/eric072)
### Committers
- @eric072(https://gitee.com/eric072)
- @Sturmegezhutz(https://gitee.com/Sturmegezhutz)
- @jorway_ou(https://gitee.com/jorway_ou)
- @litao33(https://gitee.com/litao33)
### Meetings
- Meeting time:BiWeek Friday 9:30-10:30
- Meeting application: https://etherpad.openharmony.cn/p/sig-print
- Meeting link: Welink Meeting or Others
- Meeting notification: [Subscribe to] (https://lists.openatom.io/hyperkitty/list/sig-print@openharmony.io/) mailing list dev@openharmony.io for the meeting link
- Meeting-Minutes: [Archive link address](https://gitee.com/openharmony-sig/sig-content)
### Contact (optional)
- eric.li@urovo.com
- stur.guan@urovo.com
- Mailing list:dev@openharmony.io
- Zulip group:https://zulip.openharmony.cn
- Wechat group:SIG-Print
# SIG-print
简体中文 | [English](./sig_print.md)
说明:本SIG的内容遵循OpenHarmony的PMC管理章程 [README](/zh/pmc.md)中描述的约定。
## SIG组工作目标和范围
### 工作目标
Print SIG旨在为OpenHarmony开发打印服务功能,进一步拓展及完善OpenHarmony在行业智能终端及其他打印设备的基本能力。北向方面,为打印类应用提供统一的框架接口,降低应用开发难度。南向方面,为内置热敏打印机、USB打印机、蓝牙打印机、WiFi打印机等不同的接口方式提供标准化的通讯方式,解决打印设备供应商的插件化支持的限制。
### 工作范围
1)打印服务的功能实现及维护,为应用开发提供统一的API。
2)移植性以及兼容性需求。为不同接口方式的打印机提供一套兼容方案。
3)提供打印应用示例demo
4)积极与打印机厂商进行洽谈合作,推动OpenHarmony打印业务南向接口的标准化进程。
## 代码仓
- 代码仓地址:
- print-sig:https://gitee.com/openharmony-sig/print
- print:https://gitee.com/openharmony/print
## SIG组成员
### Leader
- @eric072(https://gitee.com/eric072)
### Committers列表
- @eric072(https://gitee.com/eric072)
- @Sturmegezhutz(https://gitee.com/Sturmegezhutz)
- @jorway_ou(https://gitee.com/jorway_ou)
- @litao33(https://gitee.com/litao33)
### 会议
- 会议时间:双周例会,周5上午9:30-10:30
- 会议申报:https://etherpad.openharmony.cn/p/sig-print
- 会议链接: Welink或其他会议
- 会议通知: 请[订阅](https://lists.openatom.io/hyperkitty/list/sig-print@openharmony.io/)邮件列表 dev@openharmony.io 获取会议链接
- 会议纪要: [归档链接地址](https://gitee.com/openharmony-sig/sig-content)
### 联系方式(可选)
- eric.li@urovo.com
- stur.guan@urovo.com
- 邮件列表:dev@openharmony.io
- Zulip群组:https://zulip.openharmony.cn
- 微信群:SIG-Print
......@@ -9,6 +9,10 @@
{
"gitee_id": "aiyongfu",
"gitee_email": "aiyongfu@huawei.com"
}
{
"gitee_id": "shermanzhong",
"gitee_email": "sherman.zhong@huawei.com"
}
]
}
\ No newline at end of file
......@@ -28,6 +28,7 @@ Note: The content of this SIG follows the convention described in OpenHarmony's
### Committers
- @[aiyongfu](https://gitee.com/aiyongfu)
- @[zhongxiaoming](https://gitee.com/shermanzhong)
### Meetings
- Meeting time:Biweekly Friday afternoon 16:30
......
......@@ -27,7 +27,7 @@
### Committers列表
- @[aiyongfu](https://gitee.com/aiyongfu)
- @[zhongxiaoming](https://gitee.com/shermanzhong)
### 会议
- 会议时间:双周周五 16:30
......
{
"Leader": [
{
"gitee_id": "sunmingang",
"gitee_email": "sunmingang@jd.com"
}
{
"gitee_id": "ricther",
"gitee_email": "liuxu6@jd.com"
}
{
"gitee_id": "shangchunpeng",
"gitee_email": "shangchunpeng@jd.com"
}
],
"Committers": [
{
"gitee_id": "leaforever",
"gitee_email": "lipengfeng1@jd.com"
}
{
"gitee_id": "tongkedong",
"gitee_email": "tongkedong@jd.com"
}
{
"gitee_id": "songguoku",
"gitee_email": "songguoku@jd.com"
}
{
"gitee_id": "kun",
"gitee_email": "shenkun9@jd.com"
}
{
"gitee_id": "sunzuxin",
"gitee_email": "sunzuxin@jd.com"
}
{
"gitee_id": "zhangjie",
"gitee_email": "zhangjie589@jd.com"
}
]
}
\ No newline at end of file
# SIG-ROBOTICS
English | [简体中文](./sig_robotics_cn.md)
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 & work scope
Robotic sub-systems based on OpenHarmony that support technical architectures, application-layer interface standards, and communication protocols of robots such as AGVs, AMRs, and RGVs. Formulating architecture design principles, evolution processes, evaluation procedures, etc., and absorbing and developing related functional modules.
### The repository
- project name:
## SIG Members
### Leader
- @[sunmingang](https://gitee.com/sunmingang)
- @[ricther](https://gitee.com/ricther)
- @[shangchunpeng](https://gitee.com/shangchunpeng)
### Committers
- @[leaforever](https://gitee.com/leaforever)
- @[tongkedong](https://gitee.com/tongkedong)
- @[songguoku](https://gitee.com/songguoku)
- @[kun](https://gitee.com/kun)
- @[sunzuxin](https://gitee.com/sunzuxin)
- @[zhangjie](https://gitee.com/zhangjie)
### Meetings
- Meeting time: BiWeek Wednesday 20:00
- Meeting application: [SIG-robotics application](https://etherpad.openharmony.cn/p/sig-robotics)
- meeting link:Tencent meeting or other meeting
- Meeting notification: [Subscribe to](dev@openharmony.io) mailing list for the
- Meeting Summary:To view the minutes of past meetings, please click this [link](https://gitee.com/openharmony-sig/sig-content/tree/master/robotics/meetings)
### Contact (optional)
- Mailing list:sig_robotics@openharmony.io
- Zulip group:https://zulip.openharmony.cn/#narrow/stream/57-robotics_sig/topic/stream.20events/near/10338
- Wechat group:xxx
# SIG-ROBOTICS
简体中文 | [English](./sig_robotics.md)
说明:本SIG的内容遵循OpenHarmony的PMC管理章程 [README](/zh/pmc.md)中描述的约定。
## SIG组工作目标和范围
### 工作目标和工作范围
基于OpenHarmony,打造机器人子系统, 设计可支持AGV、AMR、RGV等移动机器人的技术架构、应用层接口标准、通讯协议。制定架构设计原则、演进流程、评审流程等,吸纳和开发相关功能模块。
## 代码仓
- 代码仓地址:
## SIG组成员
### Leader
- @[sunmingang](https://gitee.com/sunmingang)
- @[ricther](https://gitee.com/ricther)
- @[shangchunpeng](https://gitee.com/shangchunpeng)
### Committers列表
- @[leaforever](https://gitee.com/leaforever)
- @[tongkedong](https://gitee.com/tongkedong)
- @[songguoku](https://gitee.com/songguoku)
- @[kun](https://gitee.com/kun)
- @[sunzuxin](https://gitee.com/sunzuxin)
- @[zhangjie](https://gitee.com/zhangjie)
### 会议
- 会议时间:双周例会,周三晚上20:00
- 会议申报:[SIG-robotics会议申报](https://etherpad.openharmony.cn/p/sig-robotics)
- 会议链接:腾讯会议或其他会议
- 会议通知: 请[订阅](dev@openharmony.io)邮件列表获取会议链接
- 会议纪要:查看往期会议纪要,请点此[链接](https://gitee.com/openharmony-sig/sig-content/tree/master/robotics/meetings)
### 联系方式(可选)
- 邮件列表:sig_robotics@openharmony.io
- Zulip群组:https://zulip.openharmony.cn/#narrow/stream/57-robotics_sig/topic/stream.20events/near/10338
- 微信群:xxx
......@@ -33,6 +33,34 @@
{
"gitee_id": "sunjunxiong",
"gitee_email": "sunjunxiong@huawei.com"
}
},
{
"gitee_id": "quantumshark",
"gitee_email": "yanghuaiyi1@huawei.com"
},
{
"gitee_id": "qano",
"gitee_email": "nimaosen1@huawei.com"
},
{
"gitee_id": "sjtu_sp",
"gitee_email": "supeng13@huawei.com"
},
{
"gitee_id": "zeng_lingyi",
"gitee_email": "zenglingchang@huawei.com"
},
{
"gitee_id": "zhuchengfeng1",
"gitee_email": "zhuchengfeng1@huawei.com"
},
{
"gitee_id": "yangpeng85",
"gitee_email": "yangpeng85@huawei.com"
},
{
"gitee_id": "xuchangzhou",
"gitee_email": "xuzhangzhou@huawei.com"
}
]
}
\ No newline at end of file
......@@ -41,6 +41,13 @@ Defines and builds OpenHarmony system applications, applies for and implements i
- @lv-zhongwei(https://gitee.com/lv-zhongwei)
- @hosphoto(https://gitee.com/hosphoto)
- @sunjunxiong(https://gitee.com/sunjunxiong)
- @quantumshark(https://gitee.com/quantumshark)
- @qano(https://gitee.com/qano)
- @sjtu_sp(https://gitee.com/sjtu_sp)
- @zeng_lingyi(https://gitee.com/zeng_lingyi)
- @zhuchengfeng1(https://gitee.com/zhuchengfeng1)
- @yangpeng85(https://gitee.com/yangpeng85)
- @xuchangzhou(https://gitee.com/xuchangzhou)
### Meetings
- Meeting time:monthly meeting
......
......@@ -41,6 +41,13 @@
- @lv-zhongwei(https://gitee.com/lv-zhongwei)
- @hosphoto(https://gitee.com/hosphoto)
- @sunjunxiong(https://gitee.com/sunjunxiong)
- @quantumshark(https://gitee.com/quantumshark)
- @qano(https://gitee.com/qano)
- @sjtu_sp(https://gitee.com/sjtu_sp)
- @zeng_lingyi(https://gitee.com/zeng_lingyi)
- @zhuchengfeng1(https://gitee.com/zhuchengfeng1)
- @yangpeng85(https://gitee.com/yangpeng85)
- @xuchangzhou(https://gitee.com/xuchangzhou)
### 会议
- 会议时间:月度例会
......
......@@ -26,7 +26,7 @@ Note: The content of this SIG follows the convention described in OpenHarmony's
- cellular_data:https://gitee.com/openharmony/telephony_cellular_data
- data_storage:https://gitee.com/openharmony/telephony_data_storage
- netmanager_standard:https://gitee.com/openharmony/communication_netmanager_standard
- netstack:https://gitee.com/openharmony-sig/communication_netstack
- netstack:https://gitee.com/openharmony/communication_netstack
## SIG Members
......
......@@ -27,7 +27,7 @@
- 数据业务:https://gitee.com/openharmony/telephony_cellular_data
- 数据存储:https://gitee.com/openharmony/telephony_data_storage
- 网络管理:https://gitee.com/openharmony/communication_netmanager_standard
- 网络协议栈:https://gitee.com/openharmony-sig/communication_netstack
- 网络协议栈:https://gitee.com/openharmony/communication_netstack
## SIG组成员
......
{
"Leader": [
{
"gitee_id": "gaohanyi1982",
"gitee_email": "gaohanyi@huawei.com"
}
],
"Committers": [
{
"gitee_id": "wangjuntao",
"gitee_email": "wangjuntao.wang@huawei.com"
},
{
"gitee_id": "Nicoyam",
"gitee_email": "renxiang11@huawei.com"
}
]
}
\ No newline at end of file
# SIG-Test
English | [简体中文](./sig_test_cn.md)
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
​ Improve the developer self-test capability of OpenHarmony, provide a variety of test types including unit test and performance test, and improve the ease of use of TDD framework.
### work scope
- Maintaining TDD self-test framework.
- Improving the test types in TDD self-test framework and provide developer self-test capability in OpenHarmony.
## The repository
- project name:
- https://gitee.com/openharmony-sig/third_party_benchmark
## SIG Members
### Leader
- [gaohanyi1982](https://gitee.com/gaohanyi1982)
### Committers
- [wangjuntao](https://gitee.com/buranfanchen)
- [NicoYam](https://gitee.com/nicoyam)
### Meetings
- Meeting time:Biweekly,detail time undetermined
- Meeting application:[OpenHarmony SIG-Test Meeting Proposal](https://etherpad.openharmony.cn/p/sig-test)
- Meeting link: Welink or other meeting
- Meeting notification: [Subscribe to ](https://lists.openatom.io/postorius/lists/dev.openharmony.io) mailing list dev@openharmony.io for the meeting link
- Meeting Summary: [link](https://gitee.com/openharmony-sig/sig-content)
### Contact (optional)
- Mailing list:dev@openharmony.io
- Zulip group:https://zulip.openharmony.cn
# SIG-Test
简体中文 | [English](./sig_test.md)
说明:本SIG的内容遵循OpenHarmony的PMC管理章程 [README](/zh/pmc.md)中描述的约定。
## SIG组工作目标和范围
### 工作目标
​ 完善OpenHarmony开发自测试能力,提供包括单元测试、性能测试等在内的多种测试类型,提升TDD框架易用性。
### 工作范围
- 维护TDD开发自测试框架
- 完善TDD开发自测试框架中测试类型,为OpenHarmony提供开发自测试能力
## 代码仓
- 代码仓地址:
- https://gitee.com/openharmony-sig/third_party_benchmark
## SIG组成员
### Leader
- [gaohanyi1982](https://gitee.com/gaohanyi1982)
### Committers列表
- [wangjuntao](https://gitee.com/buranfanchen)
- [NicoYam](https://gitee.com/nicoyam)
### 会议
- 会议时间:双周例会,待定
- 会议申报:[OpenHarmony SIG-Test Meeting Proposal](https://etherpad.openharmony.cn/p/sig-test)
- 会议链接: Welink或其他会议
- 会议通知: 会议通知: 请[订阅](https://lists.openatom.io/postorius/lists/dev.openharmony.io)邮件列表 dev@openharmony.io 获取会议链接
- 会议纪要: [归档链接地址](https://gitee.com/openharmony-sig/sig-content)
### 联系方式(可选)
- 邮件列表:dev@openharmony.io
- Zulip群组:https://zulip.openharmony.cn
......@@ -17,7 +17,8 @@
"https://gitee.com/openharmony-sig/third_party_ntfs-3g",
"https://gitee.com/openharmony-sig/third_party_fsck_msdos",
"https://gitee.com/openharmony-sig/third_party_gptfdisk",
"https://gitee.com/openharmony-sig/third_party_newfs_msdos"],
"https://gitee.com/openharmony-sig/third_party_newfs_msdos",
"https://gitee.com/openharmony-sig/third_party_exfat-utils"],
"project-path":["third_party/littlefs",
"third_party/e2fsprogs",
"kernel/linux/build",
......@@ -33,18 +34,21 @@
"third_party/ntfs-3g",
"third_party/fsck_msdos",
"third_party/gptfdisk",
"third_party/newfs_msdos"]
"third_party/newfs_msdos",
"third_party/exfat-utils"]
},
{
"sig-name":"sig-driver",
"projects":["https://gitee.com/openharmony/drivers_framework",
"https://gitee.com/openharmony/drivers_peripheral",
"https://gitee.com/openharmony/drivers_adapter",
"https://gitee.com/openharmony/drivers_adapter_khdf_linux"],
"https://gitee.com/openharmony/drivers_adapter_khdf_linux",
"https://gitee.com/openharmony-sig/drivers_interface"],
"project-path":["drivers/framework",
"drivers/peripheral",
"drivers/adapter",
"drivers/adapter/khdf/linux"]
"drivers/adapter/khdf/linux",
"drivers/interface"]
},
{
"sig-name":"sig-devboard",
......@@ -276,7 +280,7 @@
},
{
"sig-name":"sig-telephony",
"projects":"https://gitee.com/openharmony-sig/communication_netstack",
"projects":"https://gitee.com/openharmony/communication_netstack",
"project-path":"foundation/communication/netstack"
},
{
......@@ -358,7 +362,8 @@
"https://gitee.com/openharmony/notification_ces_standard",
"https://gitee.com/openharmony/notification_ans_standard",
"https://gitee.com/openharmony/account_os_account",
"https://gitee.com/openharmony-sig/third_party_nghttp2",
"https://gitee.com/openharmony-sig/account_app_account",
"https://gitee.com/openharmony/third_party_nghttp2",
"https://gitee.com/openharmony-sig/resourceschedule_workscheduler",
"https://gitee.com/openharmony-sig/resourceschedule_backgroundtaskmanager",
"https://gitee.com/openharmony-sig/accessibility"
......@@ -401,6 +406,7 @@
"base/notification/ces_standard",
"base/notification/ans_standard",
"base/account/os_account",
"base/account/app_account",
"foundation/resourceschedule/workscheduler",
"foundation/resourceschedule/backgroundtaskmanager",
"base/accessibility"
......@@ -425,9 +431,10 @@
"https://gitee.com/openharmony/third_party_libsnd",
"https://gitee.com/openharmony/third_party_pulseaudio",
"https://gitee.com/openharmony/third_party_ffmpeg",
"https://gitee.com/openharmony-sig/third_party_libsoup",
"https://gitee.com/openharmony-sig/third_party_libpsl",
"https://gitee.com/openharmony-sig/third_party_gettext",
"https://gitee.com/openharmony/third_party_libsoup",
"https://gitee.com/openharmony/third_party_libpsl",
"https://gitee.com/openharmony/third_party_gettext",
"https://gitee.com/openharmony-sig/third_party_openh264",
"https://gitee.com/openharmony/graphic_standard",
"https://gitee.com/openharmony/graphic_surface",
"https://gitee.com/openharmony/graphic_ui",
......@@ -438,7 +445,9 @@
"https://gitee.com/openharmony/third_party_wayland-protocols_standard",
"https://gitee.com/openharmony/third_party_wayland_standard",
"https://gitee.com/openharmony/third_party_libdrm",
"https://gitee.com/openharmony/third_party_pixman"
"https://gitee.com/openharmony/third_party_pixman",
"https://gitee.com/openharmony/third_party_egl",
"https://gitee.com/openharmony/third_party_opengles"
],
"project-path":[
"foundation/multimedia/media_standard",
......@@ -460,6 +469,7 @@
"third_party/libsoup",
"third_party/libpsl",
"third_party/gettext",
"third_party/openh264",
"foundation/graphic/standard",
"foundation/graphic/surface",
"foundation/graphic/ui",
......@@ -470,7 +480,9 @@
"third_party/wayland-protocols_standard",
"third_party/wayland_standard",
"third_party/libdrm",
"third_party/pixman"
"third_party/pixman",
"third_party/EGL",
"third_party/openGLES"
]
},
{
......@@ -562,6 +574,15 @@
"third_party/parse5",
"third_party/glfw"
]
},
{
"sig-name": "sig-test",
"projects": [
"https://gitee.com/openharmony-sig/third_party_benchmark"
],
"project-path": [
"third_party/benchmark"
]
},
{
"sig-name": "sig-knowlege",
......@@ -569,6 +590,7 @@
"https://gitee.com/openharmony-sig/knowledge"
"https://gitee.com/openharmony-sig/online_event",
"https://gitee.com/openharmony-sig/knowledge_demo_smart_home"
"https://gitee.com/openharmony-sig/knowledge_demo_temp"
],
"project-path":[
"NONE"
......@@ -582,6 +604,12 @@
],
"project-path": [
]
}
},
{
"sig-name":"sig-crossplatformui",
"projects":[],
"project-path": [
]
}
]
}
......@@ -4,7 +4,7 @@
|2|SIG_API|SIG_API|[zhangyongzhi](https://gitee.com/karl-z)|NA|
|3|SIG_Security|SIG_Security|[yangyongjie](yongjie.yan@huawei.com)|L1S_Security <br> L1S_BIOMETRICS|
|4|SIG_CompileRuntime|SIG_CompileRuntime|[huanghuijin](https://gitee.com/huanghuijin) <br> [wangxing](https://gitee.com/wangxing-hw)|L1S_CCRuntime <br> L1S_Build <br> L1S_UTILS|
|5|SIG_Test|SIG_Test|[niexin](https://gitee.com/nie-x) <br> [wangjuntao](https://gitee.com/buranfanchen)|L1S_Test|
|5|SIG_Test|SIG_Test|[gaohanyi](https://gitee.com/gaohanyi1982) <br> [wangjuntao](https://gitee.com/buranfanchen)|L1S_Test|
|6|SIG_DistributedHardwareManagement|SIG_HardwareMgr|[ligang](william.ligang@huawei.com) <br> [houpengfei](https://gitee.com/hhh2)|L1S_MSDP <br> L1S_PowerMgr <br> L1S_Sensors <br> L1S_USB <br> L1s_DistributedHardware <br> |
|7|SIG_BasicSoftwareService|SIG_BasicSoftwareService|[zhangxiaotian](https://gitee.com/handyohos) <br> [liyu](https://gitee.com/ericlee)|L1S_DistributedSchedule <br> L1S_ResourceSchedule <br> L1S_StartUp <br> L1S_Notification <br> L1S_HiviewDFX <br> L1S_Update <br> L1S_Account <br> L1S_BarrierFree <br> L1S_MiscServices|
|8|SIG_Kernel|SIG_Kernel|[lijiaxin](nina.lijiaxin@huawei.com) <br> [wangmihu](https://gitee.com/wangmihu2008)|L1S_Kernel|
......
......@@ -297,6 +297,15 @@
|295|communication_netstack|foundation/communication/netstack|https://gitee.com/xautosoft|zhuwenchao@huawei.com|https://gitee.com/clevercong|lichunlin2@huawei.com|SIG-Telephony|
|296|device_soc_hisilicon|device/soc/hisilicon|https://gitee.com/northking-super|chenxin100@huawei.com|https://gitee.com/hisi_zk <br> https://gitee.com/Aaron_lv|hisi.zhaokai@hisilicon.com <br> lvyong7@huawei.com|SIG_Devboard|
|297|device_board_hisilicon|device/board/hisilicon|https://gitee.com/northking-super|chenxin100@huawei.com|https://gitee.com/hisi_zk <br> https://gitee.com/Aaron_lv|hisi.zhaokai@hisilicon.com <br> lvyong7@huawei.com|SIG_Devboard|
|298|security_selinux|base/security/selinux|https://gitee.com/shell_way|qinfd@superred.com.cn|https://gitee.com/freenull|xieb@superred.com.cn|SIG_SELinux|
|299|third_party_selinux|third_party/selinux|https://gitee.com/shell_way|qinfd@superred.com.cn|https://gitee.com/freenull|xieb@superred.com.cn|SIG_SELinux|
|300|third_party_pcre2|third_party/pcre2|https://gitee.com/shell_way|qinfd@superred.com.cn|https://gitee.com/freenull|xieb@superred.com.cn|SIG_SELinux|
|298|security_selinux|base/security/selinux|https://gitee.com/shell_way|qinfd@superred.com.cn|https://gitee.com/freenull <br> https://gitee.com/hu-huifeng <br> https://gitee.com/jiang-xiaofeng|xieb@superred.com.cn <br> huhuifeng@huawei.com <br> jiangxiaofeng8@huawei.com|SIG_SELinux|
|299|third_party_selinux|third_party/selinux|https://gitee.com/shell_way|qinfd@superred.com.cn|https://gitee.com/freenull <br> https://gitee.com/hu-huifeng <br> https://gitee.com/jiang-xiaofeng|xieb@superred.com.cn <br> huhuifeng@huawei.com <br> jiangxiaofeng8@huawei.com|SIG_SELinux|
|300|third_party_pcre2|third_party/pcre2|https://gitee.com/shell_way|qinfd@superred.com.cn|https://gitee.com/freenull <br> https://gitee.com/hu-huifeng <br> https://gitee.com/jiang-xiaofeng|xieb@superred.com.cn <br> huhuifeng@huawei.com <br> jiangxiaofeng8@huawei.com|SIG_SELinux|
|301|account_app_account|base/account/app_account|https://gitee.com/verystone|xudaqing@huawei.com| | |SIG_BasicSoftwareService|
|302|third_party_benchmark|third_party/benchmark|https://gitee.com/gaohanyi1982|gaohanyi@huawei.com| https://gitee.com/buranfanchen | wangjuntao.wang@huawei.com |SIG_Test|
|303|device_hihope|device/hihope|https://gitee.com/leonard_shi|shi_lei1@hoperun.com| | |SIG_Devboard|
|304|vendor_hihope|vendor/hihope|https://gitee.com/leonard_shi|shi_lei1@hoperun.com| | |SIG_Devboard|
|305|third_party_egl|third_party/EGL|https://gitee.com/lijj01|lijunjie29@huawei.com| | |SIG_GraphicsandMedia|
|306|third_party_opengles|third_party/openGLES|https://gitee.com/lijj01|lijunjie29@huawei.com| | |SIG_GraphicsandMedia|
|307|third_party_openh264|third_party/openh264|https://gitee.com/zhu-mingliang|zhumingliang@huawei.com| | |SIG_GraphicsandMedia|
|308|third_party_exfat-utils|third_party/exfat_utils|https://gitee.com/zhangzhiwi|weizhi.zhang@huawei.com|https://gitee.com/easy-to-see|salient.yijian@huawei.com|SIG_Kernel|
|309|drivers_interface|drivers/interface|https://gitee.com/zianed|houxuanzhe@huawei.com|https://gitee.com/Kevin-Lau|liufeihu@huawei.com|SIG_DriverFramework|
\ No newline at end of file
......@@ -29,7 +29,7 @@
| 赵文华 | [@shidi_snow](https://gitee.com/shidi_snow) | PMC成员 | 驱动框架SIG |
| 丁勇 | [@ding-yong](https://gitee.com/ding-yong) | PMC成员 | 社区产品规划 |
| 邢文华 | [@xhuazi](https://gitee.com/xhuazi) | PMC成员 | QA-SIG |
| 聂 欣 | [@nie-x](https://gitee.com/nie-x) | PMC成员 | 测试SIG |
| 高涵一 | [@gaohanyi1982](https://gitee.com/gaohanyi1982) | PMC成员 | 测试SIG |
| 王意明 | [@youthdragon](https://gitee.com/youthdragon) | PMC成员 | 基础设施SIG |
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册