Star112
32
代码
代码
Issues1
Pull Requests1
项目讨论
Wiki
分析
Star112
32
已合并
[fix] fixed the invalid link #1441
dong_jinguang创建于 2023年4月23日
[fix] fixed the invalid link #1441
已合并
dong_jinguang创建于 2023年4月23日
从refs/pull/1441/head合入到master
共 9 个文件变更+22-115
Mmeeting-notes/2021-04-13.md+2-2
@@ -22,7 +22,7 @@ TOP projects:
22sig-kernel [@wangmihu](https://gitee.com/wangmihu2008)22sig-kernel [@wangmihu](https://gitee.com/wangmihu2008)
23sig-Test [@gaohanyi](https://gitee.com/gaohanyi1982) 23sig-Test [@gaohanyi](https://gitee.com/gaohanyi1982)
24sig-Compiler-and-build [@wangxing](https://gitee.com/wangxing-hw)24sig-Compiler-and-build [@wangxing](https://gitee.com/wangxing-hw)
25-sig-hisi-vendor [@yuanwenhong](https://gitee.com/yuan.w.hong)25+sig-hisi-vendor [@yuanwenhong](https://gitee.com/yuanwhong)
26sig-softbus [@xuyongpan](https://gitee.com/Xuyongpan)26sig-softbus [@xuyongpan](https://gitee.com/Xuyongpan)
277. A total of 75 issues will be created after March 2021, of which 57 have not designated responsible persons;277. A total of 75 issues will be created after March 2021, of which 57 have not designated responsible persons;
28TOP projects: 28TOP projects:
@@ -34,7 +34,7 @@ sig-Test [@gaohanyi](https://gitee.com/gaohanyi1982)
34Topic2: Standardize the use of CMSIS on L0-Provide support for the M core to add other IoT kernel OS34Topic2: Standardize the use of CMSIS on L0-Provide support for the M core to add other IoT kernel OS
351. Standardize CMSIS invocation based on the original OpenHarmony to facilitate access of other kernels in the community. Correct improper CMSIS test suites in test cases and non-standard CMSIS in LiteOS. Owner: [@wangmihu](https://gitee.com/wangmihu2008)351. Standardize CMSIS invocation based on the original OpenHarmony to facilitate access of other kernels in the community. Correct improper CMSIS test suites in test cases and non-standard CMSIS in LiteOS. Owner: [@wangmihu](https://gitee.com/wangmihu2008)
362. Each L0 subsystem is decoupled from the LiteOS and accesses the kernel through the CMSIS interface. Owner: [@wangmihu](https://gitee.com/wangmihu2008)362. Each L0 subsystem is decoupled from the LiteOS and accesses the kernel through the CMSIS interface. Owner: [@wangmihu](https://gitee.com/wangmihu2008)
37-3. Establish a SIG group to provide APIs at the compatibility layer for migrating other IoT kernel OS to OpenHarmony. owner: [@liangkelei](https://gitee.com/kevenlikai)37+3. Establish a SIG group to provide APIs at the compatibility layer for migrating other IoT kernel OS to OpenHarmony. owner: [@liangkelei](https://gitee.com/xzmu)
38 38 
39Topic3: Added KV-database management subsystem:39Topic3: Added KV-database management subsystem:
401. Agree to establish sig-database and provides the local database capability. The distributed capability is added to connect to 1+8+N devices in future.401. Agree to establish sig-database and provides the local database capability. The distributed capability is added to connect to 1+8+N devices in future.
Mmeeting-notes/2021-04-26.md+1-1
@@ -32,7 +32,7 @@ Topic 4: Review of OpenHamony security requirements (secure coding specification
32Topic 5: sig-devboard progress report32Topic 5: sig-devboard progress report
331. Agree to the proposal of creating repository stm32l4r9i_disco under sig-devboard; owner: [@likailong](https://gitee.com/kkup180)331. Agree to the proposal of creating repository stm32l4r9i_disco under sig-devboard; owner: [@likailong](https://gitee.com/kkup180)
342. Ask Liang Kelei and Liu Jianyu to support the development of sig-devboard. owner: [@liangkelei](https://gitee.com/xzmu)342. Ask Liang Kelei and Liu Jianyu to support the development of sig-devboard. owner: [@liangkelei](https://gitee.com/xzmu)
35-3. Periodically update devboard sig's routine operation discussions and meeting minutes to [@sig-board](https://gitee.com/openharmony/community/tree/master/sig/sig-devboard/meeting.md). owner: [@likailong](https://gitee.com/kkup180)35+3. Periodically update devboard sig's routine operation discussions and meeting minutes to [@sig-board](https://gitee.com/openharmony-sig/sig-content/tree/master/devboard/meetings). owner: [@likailong](https://gitee.com/kkup180)
36 36 
37Topic 6: Decision for the proposal of sig-OTA37Topic 6: Decision for the proposal of sig-OTA
381. Postponed to the next PMC meeting. owner: [@Jianyu](https://gitee.com/L97229) [@zhangxiaotian](https://gitee.com/handyohos)381. Postponed to the next PMC meeting. owner: [@Jianyu](https://gitee.com/L97229) [@zhangxiaotian](https://gitee.com/handyohos)
Mmeeting-notes/2021-05-26.md+1-1
@@ -19,7 +19,7 @@ Topic 2: Proposal for OpenBlock SIG
19Topic 3: devboard-sig repository refactoring19Topic 3: devboard-sig repository refactoring
201. The devboard repository creation rule is defined as [device/xxx], xxx is the soc/vendor name, and the special devboard is incubated in OpenHarmony-SIG.201. The devboard repository creation rule is defined as [device/xxx], xxx is the soc/vendor name, and the special devboard is incubated in OpenHarmony-SIG.
212. Current hisi device repository is device_hisilicon_xxx. It is recommended that those hisi repository could be merged into one warehouse device_hisilicon. owner: [yuanwenhong](https://gitee.com/yuan.w.hong)212. Current hisi device repository is device_hisilicon_xxx. It is recommended that those hisi repository could be merged into one warehouse device_hisilicon. owner: [yuanwenhong](https://gitee.com/yuan.w.hong)
22-3. The third_party software repository in device directory, recommended those repository move to first folder of third_party directory. owner: [yuanwenhong](https://gitee.com/yuan.w.hong)22+3. The third_party software repository in device directory, recommended those repository move to first folder of third_party directory. owner: [yuanwenhong](https://gitee.com/yuanwhong)
23device_hisilicon_third_party_uboot -> third_party_uboot23device_hisilicon_third_party_uboot -> third_party_uboot
24device_hisilicon_third_party_ffmpeg -> third_party_ffmpeg24device_hisilicon_third_party_ffmpeg -> third_party_ffmpeg
254. The special device/xxx repository should be maintained by the SOC vendor or devboard manufacturer.254. The special device/xxx repository should be maintained by the SOC vendor or devboard manufacturer.
Dmeeting-notes/docs/assets/xxboard.md+0-83
@@ -1,83 +0,0 @@
1-# 开发板名称
2-## 介绍
3- 
4-文字描述开发板的功能，面向场景，主要支持的特性能力。
5- 
6-提供开发板外观图片。
7- 
8-底板图片。
9- 
10-功能框图及介绍。
11- 
12-**图片名称以开发板名称命名。*
13- 
14-参考文档：https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/quick-start/oem_minitinier_des_3861.md
15- 
16-********
17-## 开发板规格
18- 
19-开发板模组规格清单，硬件规格列表。
20- 
21-## 约束和限制（可选）
22- 
23-如果开发板在某些功能、特性、规格等使用上，有一定的约束和建议，需要明确说明。
24- 
25-********
26- 
27- 
28-## 关键特性
29-支持的OpenHarmony关键特性列表。
30- 
31-## 引脚定义
32-介绍单板的管脚定义等，描述单板I/O引脚，PIN，以及如何配置PIN、如何使用PIN连接外部组件。
33- 
34-## 搭建开发环境
35- 
36-### 系统要求
37- 
38-描述开发板对OpenHarmony系统依赖、软、硬件环境系统依赖。
39- 
40-### 工具要求
41- 
42-提供从哪里下载开发板编译调试工具链。
43- 
44-### 搭建过程
45- 
46-介绍环境搭建详细步骤。
47- 
48-## 编译调试
49- 
50-### 编译
51- 
52-如何在此开发板上使用OpenHarmony，以及如何在此单板上刷新OpenHarmony二进制文件及设备。
53- 
54-### 烧录
55- 
56-介绍如何烧录参考步骤。
57- 
58-### 运行
59- 
60-如何判断开发板正常点亮、运行、输出正常。
61- 
62- 
63-### 调试
64- 
65-如何调试开发板常见报错等。
66- 
67-## 首个示例
68- 
69-基于此开发板给出一个快速上手的示例，运行效果，或者给出demo示例源码链接。
70- 
71-## 参考资源
72- 
73-给出更多详细参考文档、sample示例、FAQ等内容链接。
74- 
75-## 联系（可选）
76- 
77-提供支持或者商务等联系合作方式。
78- 
79-## 感谢（可选）
80- 
81-致谢做出突出贡献的三方开发者。
82- 
83-**********
Mrfcs/yyyymmdd-rfc-template.md+3-2
@@ -1,6 +1,7 @@
1- Start Date: (fill me in with today's date, DD-MM-YYYY)1- Start Date: (fill me in with today's date, DD-MM-YYYY)
2-- RFC(request for comments) PR: [repository name/rfcs#pr number](https://gitee.com/openharmony/repositroy-name/pulls/xxxx)2+- RFC(request for comments) PR: repository name and pr number
3-- Issue: [repository name/issue number](https://gitee.com/openharmony/repository-name/issues/xxxxxx)3+- Issue: repository name/issue number
4+ 
4# (RFC title goes here)5# (RFC title goes here)
5 6 
6## Summary7## Summary
Mrfcs/yyyymmdd-rfc-template_cn.md+2-2
@@ -1,6 +1,6 @@
1- 创建时间: (按照创建时间填写, 日-月-年)1- 创建时间: (按照创建时间填写, 日-月-年)
2-- RFC（请求评论） PR: [代码仓名称/rfc#pr number](https://gitee.com/openharmony/repositroy-name/pulls/xxxx)2+- RFC（请求评论） PR: 代码仓名称/rfc#pr number
3-- Issue: [代码仓名称/issue number](https://gitee.com/openharmony/repository-name/issues/xxxxxx)3+- Issue: 代码仓名称/issue number
4 4 
5#（RFC 标题）5#（RFC 标题）
6 6 
Mtodo/00-社区ToDoList & 如何参与.md+1-1
@@ -18,7 +18,7 @@
18 18 
19步骤四、**需求澄清&方案确认**：issue责任人对需求有任何疑问，或者需要交流方案，建议在issue下方进行评论，并@committer，仓committer收到消息后会进行回复；19步骤四、**需求澄清&方案确认**：issue责任人对需求有任何疑问，或者需要交流方案，建议在issue下方进行评论，并@committer，仓committer收到消息后会进行回复；
20 20 
21-步骤五、**开发与提交代码**：责任人和社区通过跟踪[issue](https://gitee.com/openharmony/community/blob/master/sig/sig-QA/issue%EF%BC%88%E9%9C%80%E6%B1%82%E7%B1%BB%EF%BC%89%E5%A4%84%E7%90%86%E6%8C%87%E5%AF%BC.md)来进行互动，开发完成后，提交PR[上传代码](https://gitee.com/openharmony/docs/blob/master/zh-cn/contribute/%E8%B4%A1%E7%8C%AE%E6%B5%81%E7%A8%8B.md),并把PR和对应的任务issue进行关联。21+步骤五、**开发与提交代码**：责任人和社区通过跟踪[issue](https://gitee.com/openharmony/community/blob/master/sig/sig_qa/issue%EF%BC%88%E9%9C%80%E6%B1%82%E7%B1%BB%EF%BC%89%E5%A4%84%E7%90%86%E6%8C%87%E5%AF%BC.md)来进行互动，开发完成后，提交PR[上传代码](https://gitee.com/openharmony/docs/blob/master/zh-cn/contribute/%E8%B4%A1%E7%8C%AE%E6%B5%81%E7%A8%8B.md),并把PR和对应的任务issue进行关联。
22 22 
23 23 
24 24 
Mzh/sig_governance.md+12-23
@@ -31,20 +31,20 @@ git clone https://gitee.com/YOURGITEE/community
31 31 
32cd ./community/sig32cd ./community/sig
33 33 
34-cp -r sig-template sig-YOURSIGNAME34+cp -r sig_template sig_YOURSIGNAME
35 35 
36-cd sig-YOURSIGNAME36+cd sig_YOURSIGNAME
37 37 
38```38```
39 39 
40**2、完成新SIG章程的填写**40**2、完成新SIG章程的填写**
41 41 
42-为便于更好的理解和填写[SIG申请模板](./../../../sig/sig-template/sig_template_cn.md)里的内容，建议先阅读[建议书和要求](./repository-governance.md)，完成新SIG的申请填写。42+为便于更好的理解和填写[SIG申请模板](./../../../sig/sig_template/sig_template_cn.md)里的内容，建议先阅读[建议书和要求](./sig_governance.md)，完成新SIG的申请填写。
43 43 
44```44```
45-mv sig-template_cn.md sig_YOURSIGNAME_cn.md45+mv sig_template_cn.md sig_YOURSIGNAME_cn.md
46 46 
47-mv sig-template.md sig_YOURSIGNAME.md47+mv sig_template.md sig_YOURSIGNAME.md
48 48 
49vi sig_YOURSIGNAME_cn.md49vi sig_YOURSIGNAME_cn.md
50 50 
@@ -64,18 +64,11 @@ vi OWNERS
64**4、完成新SIG的Repository的配置**64**4、完成新SIG的Repository的配置**
65 65 
66- 如果您的项目在OpenHarmony社区新增子模块，请提交PR至[manifest仓](https://gitee.com/openharmony/manifest)，在其中按照格式把你的项目添加进来，其中PR提交中必须包含如下说明信息：66- 如果您的项目在OpenHarmony社区新增子模块，请提交PR至[manifest仓](https://gitee.com/openharmony/manifest)，在其中按照格式把你的项目添加进来，其中PR提交中必须包含如下说明信息：
67- 1. 新增仓路径：xxx67+ 1. 新增仓路径：kernel_liteos_a
68- 2. 新增仓库名：https://gitee.com/openharmony/xxx68+ 2. 新增仓库名：https://gitee.com/openharmony/kernel_liteos_a
69 3. 新增仓库描述：为什么需要在OpenHarmony里创建一个这样的新仓，业务功能描述69 3. 新增仓库描述：为什么需要在OpenHarmony里创建一个这样的新仓，业务功能描述
70- 4. committer：70+ 4. committer owner刷新：zh/committer.md
71- name1<email1 address> [[@gitee_id1](https://gitee.com/gitee_id1)]71+ 5. docs刷新: 如果涉及资料刷新，需要提供对应的描述链接
72- name1<email1 address> [[@gitee_id1](https://gitee.com/gitee_id1)]
73- 5. docs: 如果涉及资料刷新，需要提供对应的描述链接
74-```
75- git clone https://gitee.com/openharmony/manifest
76- cd ./community
77- vi ./default.xml
78-```
79 72 
80- 如果不是以上的情况，请单击[sigs.json](/sig/sigs.json)，并按照内部的格式在文件的最后把您的SIG添加进来73- 如果不是以上的情况，请单击[sigs.json](/sig/sigs.json)，并按照内部的格式在文件的最后把您的SIG添加进来
81 74 
@@ -124,11 +117,7 @@ PMC将通过合并Pull Request的方式来批准您的申请
124 1. 删除仓路径：xxx117 1. 删除仓路径：xxx
125 2. 删除仓库名：https://gitee.com/openharmony/xxx118 2. 删除仓库名：https://gitee.com/openharmony/xxx
126 3. 删除仓库描述：为什么需要在OpenHarmony里删除这个仓，删除后的影响是什么119 3. 删除仓库描述：为什么需要在OpenHarmony里删除这个仓，删除后的影响是什么
127- ```120+
128- git clone https://gitee.com/openharmony/manifest
129- cd ./community
130- vi ./default.xml
131- ```
132 121 
133**2、在sig文件夹的sig.yaml内添加新项目的repository信息或删除相关信息**122**2、在sig文件夹的sig.yaml内添加新项目的repository信息或删除相关信息**
134 123 
@@ -167,9 +156,9 @@ PMC将通过合并Pull Request的方式来批准您的申请
167请在`/community/sig`文件夹下找到您的sig文件夹，完成sig文件夹内SIG章程的修改156请在`/community/sig`文件夹下找到您的sig文件夹，完成sig文件夹内SIG章程的修改
168 157 
169```158```
170-vi sig-YOURSIGNAME_cn.md159+vi sig_YOURSIGNAME_cn.md
171 160 
172-vi sig-YOURSIGNAME.md161+vi sig_YOURSIGNAME.md
173 162 
174```163```
175 164