* Copyright (c) 2013-2019 Huawei Technologies Co., Ltd. All rights reserved.
* Copyright (c) 2020-2021 Huawei Device Co., Ltd. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without modification,
* are permitted provided that the following conditions are met:
*
* 1. Redistributions of source code must retain the above copyright notice, this list of
* conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright notice, this list
* of conditions and the following disclaimer in the documentation and/or other materials
* provided with the distribution.
*
* 3. Neither the name of the copyright holder nor the names of its contributors may be used
* to endorse or promote products derived from this software without specific prior written
* permission.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
* THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
* CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
* EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
* PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
* OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
* OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
* ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/
#ifndef _IT_PTHREAD_TEST_H // 防止头文件被重复包含
#define _IT_PTHREAD_TEST_H
#include "osTest.h" // 包含操作系统测试相关的头文件
#include <sys/resource.h> // 包含资源控制相关的头文件
#include <sys/wait.h> // 包含等待进程结束相关的头文件
#include <time.h> // 包含时间处理的头文件
#define SLEEP_AND_YIELD(tick) usleep((tick)*10 * 1000) // 定义宏，用于睡眠和让出CPU，tick为微秒单位
#include "sys/syscall.h" // 包含系统调用相关的头文件
// 定义一个内联函数，用于执行系统调用
static inline int Syscall(int nbr, int parm1, int parm2, int parm3, int parm4)
{
register int reg7 __asm__("r7") = nbr; // 将系统调用号放入寄存器r7
register int reg3 __asm__("r3") = parm4; // 将第四个参数放入寄存器r3
register int reg2 __asm__("r2") = parm3; // 将第三个参数放入寄存器r2
register int reg1 __asm__("r1") = parm2; // 将第二个参数放入寄存器r1
register int reg0 __asm__("r0") = parm1; // 将第一个参数放入寄存器r0
// 使用svc指令触发系统调用，将结果存回reg0
__asm__ __volatile__("svc 0" : "=r"(reg0) : "r"(reg7), "r"(reg0), "r"(reg1), "r"(reg2), "r"(reg3) : "memory");
return reg0; // 返回系统调用的结果
}
// 声明全局变量，用于存储单元测试的错误码和错误行号
extern INT32 g_iCunitErrCode;
extern INT32 g_iCunitErrLineNo;
// 声明一系列pthread相关的测试函数
extern void ItTestPthread001(void); // pthread测试函数1
extern void ItTestPthread002(void); // pthread测试函数2
extern void ItTestPthread003(void); // pthread测试函数3
extern void ItTestPthread004(void); // pthread测试函数4
extern void ItTestPthread005(void); // pthread测试函数5
extern void ItTestPthread006(void); // pthread测试函数6
extern void ItTestPthread007(void); // pthread测试函数7
extern void ItTestPthread008(void); // pthread测试函数8
extern void ItTestPthread009(void); // pthread测试函数9
extern void ItTestPthread010(void); // pthread测试函数10
extern void ItTestPthread012(void); // 省略了11，可能是个错误或者遗漏
extern void ItTestPthread011(void); // pthread测试函数11
extern void ItTestPthread013(void); // pthread测试函数13
extern void ItTestPthread014(void); // pthread测试函数14
extern void ItTestPthread015(void); // pthread测试函数15
extern void ItTestPthread016(void); // pthread测试函数16
extern void ItTestPthread017(void); // pthread测试函数17
extern void ItTestPthread018(void); // pthread测试函数18
extern void ItTestPthread019(void); // pthread测试函数19
extern void ItTestPthread020(void); // pthread测试函数20
extern void ItTestPthread021(void); // pthread测试函数21
extern void ItTestPthread022(void); // pthread测试函数22
extern void ItTestPthread023(void); // pthread测试函数23
extern void ItTestPthread024(void); // pthread测试函数24
extern void ItTestPthread025(void); // pthread测试函数25
extern void ItTestPthread026(void); // pthread测试函数26
extern void ItTestPthread027(void); // pthread测试函数27
extern void ItTestPthreadAtfork001(void); // pthread atfork测试函数1
extern void ItTestPthreadAtfork002(void); // pthread atfork测试函数2
extern void ItTestPthreadOnce001(void); // pthread once测试函数1
extern void ItTestPthreadCond001(void); // pthread 条件变量测试函数1
extern void ItTestPthreadCond002(void); // pthread 条件变量测试函数2
extern void ItTestPthreadCond003(void); // pthread 条件变量测试函数3
extern void ItTestPthreadCond004(void); // pthread 条件变量测试函数4
#endif // 结束头文件保护
| 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 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/> |
## Project Logo
Please refer to the trademark usage guidelines from [OpenHarmony LOGO](https://www.openharmony.cn/trademark).
The attendance have reached quorum with 16 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
### Review the issues and PRs from the community which need to higlight
1. Opensource community developers are very concerned about the OpenHarmony version evolution roadmap. So each PMC member need to give the planning work of the next phase which and disscuss with each other at the next PMC meeting. -- owner: All PMC member
2. Resolved codestyle check failed issue on the gitee -- owner: dongjinguang
3. Need to clarify the OpenHarmony roadmap timeline -- owner: wangjing
### Open discussion
1. Commit message format request:
- All description should be English
- Commit message format:
- Description:[fix]/[feature]/[workaround] Generally Description
- Bug: Issue number
- Test: Give the detailed test verification procedure
2. To improve development efficiency and reduce maintenance workload, needs to determine internal and external branches sync policy asap. -- owner: dongjinguang & zhangmingxiu
The attendance have reached quorum with 18 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
1. Opensource community developers are very concerned about the OpenHarmony version evolution roadmap. So each PMC member need to give the planning work of the next phase which and disscuss with each other at the next PMC meeting. -- owner: All PMC member
| Provide Dockerfile and Docker image for Developers to compiler and flash image in the same enviroment | Oct | dongjinguang |
| Accepting PR of porting 3rd dev board Application for the Code of L0/L1 Non-HiSilicon Chips | Oct | dongjinguang |
| Provide documents for the above projects | Now | dongjinguang |
| Develop a common driver models such as MTD, MMC, SPI, and I2C ... to facilitate the support of the 3rd-party soc development board. | Need to Confirm | chenfeng |
| Kernel space: trace/debug, file system optimization, and musl interface adaptation of the C library | Need to Confirm | lijiarun |
| User space tool: network TCP dump, memory check | Need to Confirm | lijiarun |
| ACE UI switching effect | Need to Confirm | lubo |
| Globalization capability improvement | Need to Confirm | lubo |
| Optimization redundant code of the public basic library | Need to Confirm | xiaofeng |
| Unify the compile system for HOS L0~L5 | Need to Confirm | wangxing |
| Plug-in platform Hievent (include error code), HiTrace | Need to Confirm | mayaohui |
| Optimize the ring-buffer performance for Hilog | Need to Confirm | mayaohui |
| Upgraded the communication protocol( include IPC ) to solve the problem of intercommunicate between Low wight device with rich Harmony devie. | Need to Confirm | yinyouzhan |
| Need to Provide roadmap | Need to Confirm | lijiarun |
| Need to Provide roadmap | Need to Confirm | futianfu and yangxuan |
| Need to Provide roadmap | Need to Confirm | tanliwen |
| Need to Provide roadmap | Need to Confirm | yuanwenhong |
2. Resolved codestyle check failed issue on the gitee -- owner: dongjinguang
- Have been resolved
3. Need to clarify the OpenHarmony roadmap timeline -- owner: wangjing/zhangmingxiu/panxiaoqun
- Not finished and have been delayed
4. To improve development efficiency and reduce maintenance workload, needs to determine internal and external branches sync policy asap. -- owner: zhangmingxiu/panxiaoquan
### Review the issues and PRs from the community which need to higlight
1. The following compilation requirements are raised by the OpenAtom Foundation's liangkelai for supportting the 3rd-party development board:
- Hope to support each single component compile
- There are many compilation dependency options for new 3rd-party development board configuration file, which depend on the HiSi vendor code.
- Hope to provide the menuconfig mechanism which similar to that of Linux menuconfig mechanism
owner: wangxing
### Open discussion
1. OpenAtom Foundation's Luo Wei proposoal :
- 3rd party development board code repository for PR needs to be specified, which could be placed under the vendor/hisi or device/hisi, need to confirm within this week. owner: chenfeng/wanchengzhen/wenjun/dongjinguang
- Maintainer for 3rd party development board code repository, we sugguest that it is maintained by the contributor and Huawei public at initial stage, and will be gradually transferred the maintainer role to the real contributor.
- For the porting 3rd party development board, there are too many boards and chips, we suggest to maintain one or two board, and provide detailed porting instructions to new 3rd board or chip platform.
The attendance have reached quorum with 19 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
1. Opensource community developers are very concerned about the OpenHarmony version evolution roadmap. So each PMC member need to give the planning work of the next phase which and disscuss with each other at the next PMC meeting. -- owner: All PMC member
| Provide Dockerfile and Docker image for Developers to compiler and flash image in the same enviroment | Oct | dongjinguang |
| Accepting PR of porting 3rd dev board Application for the Code of L0/L1 Non-HiSilicon Chips | Oct | dongjinguang |
| separate ringbuffer managerment from hilog & hievent virtual driver | Oct | stesen |
| read muti-log at one time implement for hilog | Nov | stesen |
| reader session implement for hilog | Nov | stesen |
| Components and animation enhancement | Nov | lubo |
| Page route animation support | Dec | lubo |
| Add some internationalization new APIs | Jan | lubo |
| Percentage relative layout support | Dec | lubo |
| Event bubbling support | Dec | lubo |
| Develop a platform driver models such as GPIO SPI, and I2C ... to facilitate the support of the 3rd-party soc development board. | Nov | Scott |
| Optimization redundant code of the public basic library | Nov | blue.xiaofeng |
| Upgraded the communication (include IPC) to slove the problem of intercommunicate between Low wight device witch rich Harmony device | Dec | yinyouzhan |
| Refactor multimedia foundation and add DRM framework support | Apr 2021 | tanliwen |
| Need to Provide roadmap | Need to Confirm | wangxing |
| Need to Provide roadmap | Need to Confirm | lijiarun |
| Need to Provide roadmap | Need to Confirm | wangzhen |
2. Need to clarify the OpenHarmony roadmap timeline -- owner: aiyongfu/zhangmingxiu/panxiaoqun
- Not finished and have been delayed
3. To improve development efficiency and reduce maintenance workload, needs to determine internal and external branches sync policy asap. -- owner: zhangmingxiu/aiyongfu
4. Hope to provide the menuconfig mechanism which similar to that of Linux menuconfig mechanism. owner: wangxing
5. There are many compilation dependency options for new 3rd-party development board configuration file, which depend on the HiSi vendor code. owern: yuanwenhong、wangxing
6. [Feature Request] Add Light-weight AI framework to OHOS, need to do technical evaluation in TMG of Smart Engineering Dept. Now there is two light-weight AI framework, TinyAI and Mindspore Micro fromwork, we need to decide which Light Weight AI Framework solution to use throught performance comparison test. owner: zhouxinyu 00431241, Vinod Kumar S 70786 and lizhongyuan 00446796
7. Likailong analyzed and designed the solution for third-party development boards. Need to communicate with the Atomic open source foundation contributor and try to accept the corresponding PR. owern: chenfen and Likailong
### Review the issues and PRs from the community which need to higlight
1. [Feature Request] Add Light-weight AI framework to OHOS, need to do technical evaluation in TMG of Smart Engineering Dept. Now there is two light-weight AI framework, TinyAI and Mindspore Micro fromwork, we need to decide which Light Weight AI Framework solution to use throught performance comparison test. owner: zhouxinyu 00431241, Vinod Kumar S 70786 and lizhongyuan 00446796
2. There os only compile detection was integrated on the OpenHarmony CI/CD, and does not have real devices or simulated environments detection, which have raise daily version problem. The CI/CD engineering tool must be deployed asap. owner：wangyiming 00335618
### Open discussion
1. Hope the HiStreamer multimedia system could be integrated to OpenHarmony dev branch ASAP, to support scenario such as drones and motion cameras and so on. owner -- tanliwen
The attendance have reached quorum with 19 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
1. Opensource community developers are very concerned about the OpenHarmony version evolution roadmap. So each PMC member need to give the planning work of the next phase which and disscuss with each other at the next PMC meeting. -- owner: All PMC member
| Provide Dockerfile and Docker image for Developers to compiler and flash image in the same enviroment | Oct | dongjinguang | Close |
| Accepting PR of porting 3rd dev board Application for the Code of L0/L1 Non-HiSilicon Chips | Oct | dongjinguang | Open |
| separate ringbuffer managerment from hilog & hievent virtual driver | Oct | stesen | Open |
| Read muti-log at one time implement for hilog | Nov | stesen | Open |
| Reader session implement for hilog | Nov | stesen | Open |
| Components and animation enhancement | Nov | lubo | Open |
| Page route animation support | Dec | lubo | Open |
| Add some internationalization new APIs | Jan | lubo | Open |
| Percentage relative layout support | Dec | lubo | Open |
| Event bubbling support | Dec | lubo | Open |
| Develop a platform driver models such as GPIO SPI, and I2C ... to facilitate the support of the 3rd-party soc development board. | Nov | Scott | Open |
| Optimization redundant code of the public basic library | Nov | blue.xiaofeng | Open |
| Upgraded the communication (include IPC) to slove the problem of intercommunicate between Low wight device witch rich Harmony device | Dec | yinyouzhan | Open |
| Refactor multimedia foundation and add DRM framework support | Apr 2021 | tanliwen | Open |
| Prepare Linux version, code compliance rectification | Dec | yuanwenhong | Open |
| Communicaton mechaanism between Ability deployed on different devices | Dec 2020 | lijiarun | Open |
| Adjust external compilation dependencies | Dec 2020 | wangxing | Open |
| Supports the installation of multiple HAP packages | Apr 2021 | wangzhen |
| Support transition animation between abilities | Apr 2021 | wangzhen |
2. Need to clarify the OpenHarmony roadmap timeline -- owner: aiyongfu/zhangmingxiu
- Not finished and have been delayed
3. To improve development efficiency and reduce maintenance workload, needs to determine internal and external branches sync policy asap. -- owner: zhangmingxiu/aiyongfu
- Having finished the branch sync policy report on OS STDT meeting and obtain the approval from the PMC leader
4. Hope to provide the menuconfig mechanism which similar to that of Linux menuconfig mechanism. owner: wangxing
- Not finished
5. There are many compilation dependency options for new 3rd-party development board configuration file, which depend on the HiSi vendor code. owern: yuanwenhong、wangxing
- Not finished
6. [Feature Request] Add Light-weight AI framework to OHOS, need to do technical evaluation in TMG of Smart Engineering Dept. Now there is two light-weight AI framework, TinyAI and Mindspore Micro fromwork, we need to decide which Light Weight AI Framework solution to use throught performance comparison test. owner: zhouxinyu 00431241, Vinod Kumar S 70786 and lizhongyuan 00446796
- Not finished
7. Likailong analyzed and designed the solution for third-party development boards. Need to communicate with the Atomic open source foundation contributor and try to accept the corresponding PR. owern: chenfen and Likailong
- Processing
8. Hope the HiStreamer multimedia system could be integrated to OpenHarmony dev branch ASAP, to support scenario such as drones and motion cameras and so on. owner -- tanliwen
- Not finished
### Review the issues and PRs from the community which need to higlight
1. There os only compile detection was integrated on the OpenHarmony CI/CD, and does not have real devices or simulated environments detection, which have raise daily version problem. The CI/CD engineering tool must be deployed asap. owner：wangyiming 00335618
- Real board CI was deployed, missing codestyle and static code check.
The attendance have reached quorum with 12 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
1. Opensource community developers are very concerned about the OpenHarmony version evolution roadmap. So each PMC member need to give the planning work of the next phase which and disscuss with each other at the next PMC meeting. -- owner: All PMC member
| Provide Dockerfile and Docker image for Developers to compiler and flash image in the same enviroment | Oct | dongjinguang | Close |
| Accepting PR of porting 3rd dev board Application for the Code of L0/L1 Non-HiSilicon Chips | Nov 2020 | dongjinguang | Open |
| separate ringbuffer managerment from hilog & hievent virtual driver | Dec 2020 | stesen | Open |
| Read muti-log at one time implement for hilog | Dec 2020 | stesen | Open |
| Reader session implement for hilog | Dec 2020 | stesen | Open |
| Components and animation enhancement | Jan 2021 | Borne | Open |
| Percentage relative layout support | Jan 2021 | Borne | Open |
| Event bubbling support | Jan 2021 | Borne | Open |
| Develop a platform driver models such as GPIO SPI, and I2C ... to facilitate the support of the 3rd-party soc development board. | Nov 2020 | Scott | Close |
| Optimization redundant code of the public basic library | Nov 2020 | blue.xiaofeng | Open |
| Upgraded the communication (include IPC) to slove the problem of intercommunicate between Low wight device witch rich Harmony device | Dec 2020 | yinyouzhan | Open |
| Refactor multimedia foundation and add DRM framework support | Apr 2021 | tanliwen | Open |
| Prepare Linux version, code compliance rectification | Dec 2020 | yuanwenhong | Open |
| Communicaton mechaanism between Ability deployed on different devices | Dec 2020 | lijiarun | Open |
| Adjust external compilation dependencies | Dec 2020 | wangxing | Open |
| Supports the installation of multiple HAP packages | Apr 2021 | wangzhen | Open |
| Support transition animation between abilities | Apr 2021 | wangzhen | Open |
2. Need to clarify the OpenHarmony roadmap timeline -- owner: aiyongfu/zhangmingxiu
- Not finished and have been delayed
3. [Feature Request] Add Light-weight AI framework to OHOS, need to do technical evaluation in TMG of Smart Engineering Dept. Now there is two light-weight AI framework, TinyAI and Mindspore Micro fromwork, we need to decide which Light Weight AI Framework solution to use throught performance comparison test. owner: zhouxinyu 00431241, Vinod Kumar S 70786 and lizhongyuan 00446796
- Processing
4. Likailong analyzed and designed the solution for third-party development boards. Need to communicate with the Atomic open source foundation contributor and try to accept the corresponding PR. owern: chenfen and Likailong
- Processing
5. Hope the HiStreamer multimedia system could be integrated to OpenHarmony dev branch ASAP, to support scenario such as drones and motion cameras and so on. owner -- tanliwen
- Not finished
### Review the issues and PRs from the community which need to higlight
1. There os only compile detection was integrated on the OpenHarmony CI/CD, and does not have real devices or simulated environments detection, which have raise daily version problem. The CI/CD engineering tool must be deployed asap. owner：wangyiming 00335618
The attendance have reached quorum with 16 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
1. Opensource community developers are very concerned about the OpenHarmony version evolution roadmap. So each PMC member need to give the planning work of the next phase which and disscuss with each other at the next PMC meeting. -- owner: All PMC member
| Provide Dockerfile and Docker image for Developers to compiler and flash image in the same enviroment | Oct | dongjinguang | 2020-11-08: https://gitee.com/openharmony/docs/pulls/160 | Close |
| Accepting PR of porting 3rd dev board Application for the Code of L0/L1 Non-HiSilicon Chips | Dec 2020 | dongjinguang | 2020-11-08: Cotex-m refactor https://gitee.com/openharmony/kernel_liteos_m/pulls/5 | Processing |
| separate ringbuffer managerment from hilog & hievent virtual driver | Dec 2020 | stesen | 2020-11-08: Basic functions have been verified and will upstream to mainline. | Open |
| Read muti-log at one time implement for hilog | Dec 2020 | stesen | 2020-11-08: Basic functions have been verified and will upstream to mainline. | Open |
| Reader session implement for hilog | Dec 2020 | stesen | 2020-11-08: Basic functions have been verified and will upstream to mainline. | Open |
| Components and animation enhancement | Jan 2021 | Borne | 2020-11-08: To be completed by end of 2020 | Open |
| Percentage relative layout support | Jan 2021 | Borne | 2020-11-08: To be completed by end of 2020 | Open |
| Event bubbling support | Jan 2021 | Borne | 2020-11-08: To be completed by end of 2020 | Open |
| Develop a platform driver models such as GPIO SPI, and I2C ... to facilitate the support of the 3rd-party soc development board. | Nov 2020 | Scott | 2020-11-08: need to provide the PR link| Close |
| Optimization redundant code of the public basic library | Jan 2021 | blue.xiaofeng | 2020-11-08: Delay to 202101 |Open |
| Upgraded the communication (include IPC) to slove the problem of intercommunicate between Low wight device witch rich Harmony device | Dec 2020 | yinyouzhan | 2020-11-08: No manpower is invested, need to further evaluate the risk of delay | Open |
| Refactor multimedia foundation and add DRM framework support | Apr 2021 | tanliwen | 2020-11-08: Completed the development of basic histreamer functions and planned to be released in March next year. The lite OpenHarmony remains current Arch | Open |
| Prepare Linux version, code compliance rectification | Dec 2020 | yuanwenhong | 2020-11-08: need to provide the release schedule | Open |
| Communicaton mechaanism between Ability deployed on different devices | Dec 2020 | lijiarun | 2020-11-08: Ability deployed on different devices depend on the communication subsystem | Open |
| Adjust external compilation dependencies | Dec 2020 | wangxing | 2020-11-08: need to provide progress | Open |
| Supports the installation of multiple HAP packages | Apr 2021 | wangzhen | 2020-11-08: The business has been switched to application framework team | Open |
| Support transition animation between abilities | Apr 2021 | wangzhen | 2020-11-08: no progress | Open |
2. Need to clarify the OpenHarmony roadmap timeline -- owner: aiyongfu/zhangmingxiu
- Not finished and have been delayed long time
3. [Feature Request] Add Light-weight AI framework to OHOS, will be release initial version on OpenHarmony by end of 2020. owner: :lifu2@huawei.com
- Processing
4. Likailong analyzed and designed the solution for third-party development boards. Need to communicate with the Atomic open source foundation contributor and try to accept the corresponding PR. owern: chenfen and Likailong
- Finished
5. Hope the HiStreamer multimedia system could be integrated to OpenHarmony dev branch ASAP, to support scenario such as drones and motion cameras and so on. owner -- tanliwen
- Not finished
6. [Feature Request] Connectivity capability enhancement for OpenHarmony, have been approved on PMC meeting. Detailed architecture design description and compatibility issues with internal CoAP solutions need to be provided. owner: :nagesh.shamnur@huawei.com
- Open
7. [Feature Request] Python development for OpenHarmony, which have been approved on PMC meeting. In order to be accepted and upstream to the OpenHarmony main-line, there are three items need to be pay attention: 1) Make the module into a component, which could be easily configure through macro definition; 2) Make an assessment of ROM/RAM resource consumption so as to support KB-level devices; 3) For references to third-party open source software( such as micro-python), please archive them in the third_party directory. owner: delphi_tang@dt4sw.com
- Processing
### Review the issues and PRs from the community which need to higlight
1. There os only compile detection was integrated on the OpenHarmony CI/CD, and does not have real devices or simulated environments detection, which have raise daily version problem. The CI/CD engineering tool must be deployed asap. owner：wangyiming 00335618
The attendance have reached quorum with 16 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
1. Opensource community developers are very concerned about the OpenHarmony version evolution roadmap. So each PMC member need to give the planning work of the next phase which and disscuss with each other at the next PMC meeting. -- owner: All PMC member
| Provide Dockerfile and Docker image for Developers to compiler and flash image in the same enviroment | Oct | dongjinguang | 2020-11-08: https://gitee.com/openharmony/docs/pulls/160 | Close |
| Accepting PR of porting 3rd dev board Application for the Code of L0/L1 Non-HiSilicon Chips | Feb 2021 | dongjinguang | 2021-01-04: Cotex-m refactor https://gitee.com/openharmony/kernel_liteos_m/pulls/5 | Processing |
| separate ringbuffer managerment from hilog & hievent virtual driver | Dec 2020 | stesen | 2021-01-04: need to provide progress | Open |
| Reader session implement for hilog | Dec 2020 | stesen | 2021-01-04: need to provide progress | Open |
| Components and animation enhancement | Jan 2021 | Borne | 2021-01-04: Three modules will open-sourced together with component rectification | Open |
| Percentage relative layout support | Jan 2021 | Borne | 2021-01-04: Three modules will open-sourced together with component rectification | Open |
| Event bubbling support | Jan 2021 | Borne | 2021-01-04: Three modules will open-sourced together with component rectification | Open |
| Develop a platform driver models such as GPIO SPI, and I2C ... to facilitate the support of the 3rd-party soc development board. | Nov 2020 | Scott | 2021-01-04: Absent meeting and need to provide the PR link| Close |
| Optimization redundant code of the public basic library | Jan 2021 | blue.xiaofeng | 2020-11-08: Delay to 202102 |Open |
| Upgraded the communication (include IPC) to slove the problem of intercommunicate between Low wight device witch rich Harmony device | Dec 2020 | yinyouzhan | 2021-01-04: Finish user space IPC work, lites os kernel space need to rework | Open |
| Refactor multimedia foundation and add DRM framework support | Apr 2021 | tanliwen | 2020-11-08: Completed the development of basic histreamer functions and planned to be released in March next year. The lite OpenHarmony remains current Arch | Open |
| Prepare Linux version, code compliance rectification | Dec 2020 | yuanwenhong | 2021-01-04: Finished the GPL license rework and need to confirm schedule with PM | Open |
| Communicaton mechaanism between Ability deployed on different devices | Dec 2020 | lijiarun | 2021-01-04: Track the issue in the product requirement, and was not tracked in the open source community. | Close |
| Adjust external compilation dependencies | Dec 2020 | wangxing | 2021-01-04: Absent meeting and need to provide progress | Open |
| Supports the installation of multiple HAP packages | Apr 2021 | wangzhen | 2021-01-04: Tracking the feature in product requirement, not tracked in the open source community | Close |
| Support transition animation between abilities | Apr 2021 | wangzhen | 2021-01-04: Tracking the feature in product requirement, not tracked in the open source community | Close |
2. Need to clarify the OpenHarmony roadmap timeline -- owner: aiyongfu/zhangmingxiu
- Not finished and have been delayed long time
3. [Feature Request] Add Light-weight AI framework to OHOS, will be release initial version on OpenHarmony by end of 2020. owner: :lifu2@huawei.com
- Having finished and will opensource on Jan
4. [Feature Request] Connectivity capability enhancement for OpenHarmony, have been approved on PMC meeting. Detailed architecture design description and compatibility issues with internal CoAP solutions need to be provided. owner: nagesh.shamnur@huawei.com yinyouzhan
- Processing
55555. [Feature Request] SIG for toolchain, OTA, reST/Sphynx doc have been approved by PMC team, but there are some request :
- Toolchain part should focus on clang compiler part, IDE no need be apporved by PMC and should be disscussed on IDE team
- OTA part should firstly focus on L0/L1 device, and try to support commercial case, not just as a toys
- Document part should be support directly edit and sync with website. owner: michael.wangke@huawei.com jianyu.liu@huawei.com
- Processing
### Review the issues and PRs from the community which need to higlight
1. There os only compile detection was integrated on the OpenHarmony CI/CD, and does not have real devices or simulated environments detection, which have raise daily version problem. The CI/CD engineering tool must be deployed asap. owner：wangyiming 00335618
The attendance have reached quorum with 11 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
1. Opensource community developers are very concerned about the OpenHarmony version evolution roadmap. So each PMC member need to give the planning work of the next phase which and disscuss with each other at the next PMC meeting. -- owner: All PMC member
| Provide Dockerfile and Docker image for Developers to compiler and flash image in the same enviroment | Oct | dongjinguang | 2020-11-08: https://gitee.com/openharmony/docs/pulls/160 | Close |
| Accepting PR of porting 3rd dev board Application for the Code of L0/L1 Non-HiSilicon Chips | Feb 2021 | dongjinguang | 2021-01-18: Cotex-m refactor has been finished, and the migration guide document will be released on 2.10 | Processing |
| separate ringbuffer managerment from hilog & hievent virtual driver | Dec 2020 | stesen | 2021-01-18: Tracking the issue in the product requirement, and will not tracked in the open source community | Close |
| Reader session implement for hilog | Dec 2020 | stesen | 2021-01-18: Tracking the issue in the product requirement, and will not tracked in the open source community | Close |
| Components and animation enhancement | Jan 2021 | Borne | 2021-01-18: It will release together with component-based rectification on Feb 28 | Processing |
| Percentage relative layout support | Jan 2021 | Borne | 2021-01-18: It will release together with component-based rectification on Feb 28 | Processing |
| Event bubbling support | Jan 2021 | Borne | 2021-01-18: It will release together with component-based rectification on Feb 28 | Open |
| Develop a platform driver models such as GPIO SPI, and I2C ... to facilitate the support of the 3rd-party soc development board. | Nov 2020 | Scott | 2021-01-18: It will release together with component-based rectification on Feb 28 | Processing |
| Optimization redundant code of the public basic library | Jan 2021 | blue.xiaofeng | 2021-01-18: Absent meeting and delay to 202102 |Open |
| Upgraded the communication (include IPC) to slove the problem of intercommunicate between Low wight device witch rich Harmony device | Dec 2020 | yinyouzhan | 2021-01-18: Tracking the issue in the product requirement, and will not tracked in the open source community | Close |
| Refactor multimedia foundation and add DRM framework support | Apr 2021 | tanliwen | 2021-01-18: Level1 POSIX interfaces are incomplete, the HiStreamer framework needs to be tailored and adapted. | Open |
| Prepare Linux version, code compliance rectification | Dec 2020 | yuanwenhong | 2021-01-18: Media and graphics module still have some problem. Hope it could be finished on February 28 | Open |
| Communicaton mechaanism between Ability deployed on different devices | Dec 2020 | lijiarun | 2021-01-04: Track the issue in the product requirement, and was not tracked in the open source community. | Close |
| Adjust external compilation dependencies | Dec 2020 | wangxing | 2021-01-18: Absent meeting and need to provide progress | Open |
| Supports the installation of multiple HAP packages | Apr 2021 | wangzhen | 2021-01-04: Tracking the feature in product requirement, not tracked in the open source community | Close |
| Support transition animation between abilities | Apr 2021 | wangzhen | 2021-01-04: Tracking the feature in product requirement, not tracked in the open source community | Close |
2. Need to clarify the OpenHarmony roadmap timeline -- owner: aiyongfu/zhangmingxiu
- Not finished and have been delayed long time
3. [Feature Request] Add Light-weight AI framework to OHOS, will be release initial version on OpenHarmony by end of 2020. owner: :lifu2@huawei.com
- Having finished and will opensource on Jan 2021
4. [Feature Request] Connectivity capability enhancement for OpenHarmony, have been approved on PMC meeting. Detailed architecture design description and compatibility issues with internal CoAP solutions need to be provided. owner: nagesh.shamnur@huawei.com yinyouzhan
- Processing
5. [Feature Request] SIG for toolchain, OTA, reST/Sphynx doc have been approved by PMC team, but there are some request :
- Toolchain part should focus on clang compiler part, IDE no need be apporved by PMC and should be disscussed on IDE team
- OTA part should firstly focus on L0/L1 device, and try to support commercial case, not just as a toys
- Document part should be support directly edit and sync with website. owner: michael.wangke@huawei.com jianyu.liu@huawei.com
- Processing
### Review the issues and PRs from the community which need to higlight
1. There os only compile detection was integrated on the OpenHarmony CI/CD, and does not have real devices or simulated environments detection, which have raise daily version problem. The CI/CD engineering tool must be deployed asap. owner：wangyiming 00335618
The attendance have reached quorum with 10 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
1. Opensource community developers are very concerned about the OpenHarmony version evolution roadmap. So each PMC member need to give the planning work of the next phase which and disscuss with each other at the next PMC meeting. -- owner: All PMC member
| Provide Dockerfile and Docker image for Developers to compiler and flash image in the same enviroment | Oct | dongjinguang | 2020-11-08: https://gitee.com/openharmony/docs/pulls/160 | Close |
| Accepting PR of porting 3rd dev board Application for the Code of L0/L1 Non-HiSilicon Chips | Feb 2021 | dongjinguang | 2021-01-18: Cotex-m refactor has been finished, and the migration guide document will be released on 2.10 | Processing |
| Components and animation enhancement | Jan 2021 | Borne | 2021-01-18: It will release together with component-based rectification on Feb 28 | Processing |
| Percentage relative layout support | Jan 2021 | Borne | 2021-01-18: It will release together with component-based rectification on Feb 28 | Processing |
| Event bubbling support | Jan 2021 | Borne | 2021-01-18: It will release together with component-based rectification on Feb 28 | Open |
| Develop a platform driver models such as GPIO SPI, and I2C ... to facilitate the support of the 3rd-party soc development board. | Nov 2020 | Scott | 2021-01-18: It will release together with component-based rectification on Feb 28 | Processing |
| Optimization redundant code of the public basic library | Jan 2021 | blue.xiaofeng | 2021-01-18: Absent meeting and delay to 202102 |Open |
| Refactor multimedia foundation and add DRM framework support | Apr 2021 | tanliwen | 2021-01-18: Level1 POSIX interfaces are incomplete, the HiStreamer framework needs to be tailored and adapted. | Open |
| Prepare Linux version, code compliance rectification | Dec 2020 | yuanwenhong | 2021-01-18: Media and graphics module still have some problem. Hope it could be finished on February 28 | Open |
| Adjust external compilation dependencies | Dec 2020 | wangxing | 2021-01-18: Absent meeting and need to provide progress | Open |
2. [Feature Request] Add Light-weight AI framework to OHOS, will be release initial version on OpenHarmony by end of 2020. owner: :lifu2@huawei.com
- Having finished and will opensource on Feb 2021
3. [XTS CI access controlf for API] OpenHarmony API modification control strategy :
- Conclusion:
(1) Agree to add open-source API modification control policies for code building. Before the implement, we need to know how to ensure the synchronization policy during force upstream (unsolved issue 1).
(2) Agree to requirement that developers must submit XTS test when submitting API modifications.
- Unsolved Issues
(1) How to ensure sync policy that the PMC force upstream new APIs into main branch? Owner: Gao Hanyi
(2) Organize all OpenHarmony PMCs and committers to provide XTS suite development training to guide subsequent XTS development of all subsystem. Owner: Ji Yong
### Review the issues and PRs from the community which need to higlight
The attendance have reached quorum with 6 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
Topic1: Pre-review of the OpenHamony PMC & Committer Community Operation Mechanism and Appointment -- dongjinguang
1. To adapt to OpenHarmony community development, the PMC has 23 SIG groups, which correspond to different subsystems and service domains.
2. For community-based development requirements, the SIG needs to create a requirement list on the Gitee and associate it with the version iteration plan so that ecosystem partners and external developers can understand the evolution roadmap of OpenHarmony.
3. Huawei's attributes should be gradually weakened in subsequent PMC meetings. Tencent meeting/zoom is recommended for the meeting link and OpenAtom Foundation template is recommended for materials.
4. PMCs and committers are regularly elected by voting.
Topic2: [Feature Request] Create Littefs new filesystem, there is no suitable fs for nor flash on m-core chipset -- LiZan
1. Introduce the littlefs third-party file system for the liteos_m core. there are some need to focus on as follows:
(1) Different types of file systems need to be dynamically configured and tailored in different application scenarios.
(2) The lite_m kernel file system uses VFS to design the normalized file system interface.
(3) Establish the ROM and RAM baselines for the littlefs. Need to consider the ROM space consuming for current development board, because there have been reported insufficient free space on Hi3518 board.
2. To solve the problem of insufficient free space on Hi3518, need to sort the ROM/RAM baseline of each subsystem for newly introduced modules.
Topic3: [Feature Request] Create new repository and adjustment hievent kernel driver for OpenHarmony L0-L1 -- MaYaoHui
1. No need to adjustment after evaluation.
Topic4: Issue & PR SLA Requirements for OpenHarmony Community -- XingWenHua
1. OpenSouce Community features need to be created in the Gitee issue and released to the OpenSource community.
2. The handling of community bugs, issues, and mailing lists must meet the SLA requirements.# TensorFlow Special Interest Groups (SIGs)
### Review the issues and PRs from the community which need to higlight
The attendance have reached quorum with 8 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
Topic1: OpenHamony SIG group operation mechanism & community status review
1. The SIG Leader is responsible for defining the scope of work and business objectives of the corresponding SIG, and operate and maintain the corresponding SIG.
2. The SIG Leader is responsible for attracting and developing external committers to participate in project incubation, documentation improvement and community promotion of the corresponding SIG.
3. The SIG leader regularly reports the SIG incubation project and SIG operation progress to the PMC, and makes improvements based on PMC's guidance and suggestions.
4. Responsible for the design, review, and make decisions on software module architectures in the SIG domain, proactively identify, optimize, or reconstruct code in the responsible domain; eliminate technical debts.
5. Serve as OpenHarmony open source technology evangelist to publicize OpenHarmony's value proposition, as the main speech of the technology salon, writing technical articles, etc.
6. There are a total of 107 issues to be created before March 2021, of which 87 have no designated responsible person. The clearing of historical issues is slow.
Topic2: Standardize the use of CMSIS on L0-Provide support for the M core to add other IoT kernel OS
1. 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)
2. Each L0 subsystem is decoupled from the LiteOS and accesses the kernel through the CMSIS interface. Owner: [@wangmihu](https://gitee.com/wangmihu2008)
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)
Topic3: Added KV-database management subsystem:
1. 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.
2. The definition of API interface, repository name, directory name, and architecture should be consistent with those at the L2-L5 level. owner: [@xuchao](https://gitee.com/purple-ding-gags)
4. Due to the lifetime of the NOR flash device, should consider to reduce the frequency of writing on write-back. owner: [@xuchao](https://gitee.com/purple-ding-gags)
Topic4: Writing Component Specification Information to Component README
1. Agree to write specifications and dependent component fields into README, decompose the specifications and dependent information and integrate with the existing README information to form a template to be added to the README and related material writing specifications owner: [@YangNi]https://gitee.com/neeen
2. Push each subsystem to update component specifications based on the template provided in the documentation --- owner: [@mazhanfu](mazhanfu@huawei.com)
3. Component dependencies can be exported and added to the TODO list as a new requirement. owner: [@peitaiyi](https://gitee.com/taiyipei)
Topic5: Building an Open Source Repository for Lightweight Graphics Demo Boards
1. Agree to establish sig-devboard, and sig-devboard will be used to incubate the three-party development board adaptation. Create the device_st and vendor_huawei_minidisplay_demo repositories in the openharmony-sig. The test board with community access control is ready and then open the source. [@lilailong](https://gitee.com/kkup180)
Topic6: Qemu access control test project report
1. Agree to add the QEMU simulator CI test project to improve the efficiency of the pure software CI access control test that does not depend on the hardware development board. owner: [@wangyiming](youthdragon.wangyiming@huawei.com)
### Review the issues and PRs from the community which need to higlight
The attendance have reached quorum with 9 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
Topic 1: Proposal to add DL-Lite and Tiny-TVM components to the AI subsystem
1. The DL-Lite component repository will be under the level 3 directory, which is at the same level as ai_engine.
2. There are some issue need to confirm:
- 2.1 Creat PR to add AI-SIG and add the repository infromation; owner: [@maoyong](maoyong5@huawei.com)
- 2.2 After DL-Lite and Tiny-TVM components upstream to OpenHamrony, need to provide test unit to ensure function correctness; owner: [@niexin](niexin.nie@huawei.com), [@hantongshuai](hantongshuai@huawei.com)
- 2.3 Providing advertorials and introduction to Software Usage for DL-Lite and Tiny-TVMProduct promotion, to ensure that the componment could be used correctly; owner: [@shenbo](shenbo@huawei.com), [@maoyong](maoyong5@huawei.com)
- 2.4 Need to confirm repository address for AI_Engine and DLLite-Micro's document material; owner: [@yangni](https://gitee.com/neeen)
- 2.5 After the conclusion is made at the TMG meeting for component of Tiny-TVM, decided at the next time PMC meeting; owner: [@maoyong](maoyong5@huawei.com), [@Vinod Kumar](vinods.kumar@huawei.com)
Topic 3: Proposal for the construction of the public developer development board incubation pool
1. Agree to create the vendor_oh_fun repository under the sig-devboard to carry and incubate development board with orientation of "interest, low barriers, and sense of achievement".
2. When the incubation project graduates, it enters the OpenHarmony master branch.
Topic 4: Review of OpenHamony security requirements (secure coding specifications, security design specifications, community version network quality requirements)
1. The feasibility of the specifications needs to be considered, for example, how to effectively implement secure coding specifications and security design specifications in actual development. owner: [@yujing](jing.yu@huawei.com)
Topic 5: sig-devboard progress report
1. Agree to the proposal of creating repository stm32l4r9i_disco under sig-devboard; owner: [@likailong](https://gitee.com/kkup180)
2. Ask Liang Kelei and Liu Jianyu to support the development of sig-devboard. owner: [@liangkelei](https://gitee.com/xzmu)
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)
Topic 6: Decision for the proposal of sig-OTA
1. Postponed to the next PMC meeting. owner: [@Jianyu](https://gitee.com/L97229) [@zhangxiaotian](https://gitee.com/handyohos)
# Review the issues and PRs from the community which need to higlight
The attendance have reached quorum with 8 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
Topic1: Review of community security activity specifications and guideline requirements
1. Agree that the community security coding standards and security design standards will be released online;
2. The implementation of the security design specification requires specific requirements and supplementary examples in the relevant templates;
3. Need to confirm with release SIG Leader for network security quality landing; owner: [@mazhanfu](https://gitee.com/fma66169) [@yujing](jing.yu@huawei.com)
4. The principle of community taboo characteristics which is checked on CI in the community needs to confirm with QA-SIG; owner: [@yujing](jing.yu@huawei.com) [@xingwenhua](https://gitee.com/xhuazi)
Topic2: Decision for the proposal OTA sig creating
1. Need to confirm with Basic-Software-Service-SIG leader [@zhangxiaotian](https://gitee.com/handyohos); owner: [@Jianyu Liu](jianyu.liu@huawei.com)
# Review the issues and PRs from the community which need to higlight
The attendance have reached quorum with 8 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
Topic 2: Proposal for OpenBlock SIG
1. The OpenBlock SIG is conducive to the promotion of OpenHarmony in the education field and the development of the developer ecosystem. Agree to establish the OpenBlock sig.
2. The OpenBlock SIG is expected to introduce more foundation members and open community members, and setup planning for openblock roadmap through the repository issue. owner: [dutianwei](https://gitee.com/duzc2)
Topic 3: devboard-sig repository refactoring
1. 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.
2. 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/yuanwhong)
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)
4. The special device/xxx repository should be maintained by the SOC vendor or devboard manufacturer.
Topic 4: Proposal for RISC-V SIG
1. Agree to establish the RISC-V sig, and the owner is yujiageng. [yujiageng](https://gitee.com/yu_jia_geng)
Topic 5: Voting for repository of device_qemu new committer laokz
1. Great thanks to laokz's contributions, The PMC passed the nominating for new committer laokz and who will becomes the new committer of device_qemu. owner: [dongjinguang](https://gitee.com/dongjinguang)
Topic 6: QEMU Project Planning
1. Agree with QEMU's recently roadmap, and create these feature through issues in device_qemu repository. owner:[likailong](https://gitee.com/kkup180)
2. Need to communicate with Huawei's inner source QEMU project to evaluate the feasibility of presenting its achievements in the OpenHarmony open source community. owner:[likailong](https://gitee.com/kkup180)
# Review the issues and PRs from the community which need to higlight
The attendance have reached quorum with 7 participants in the meeting.
### Agenda:
1. Review the actions from last meetings
2. Review the issues and PRs from the community which need to higlight
3. Open discussion
### Review the actions from last meetings:
Topic 1: Commonly used front-end module SIG for application service development
- Will be review on next PMC meeting
Topic 2: ACE application framework PC preview and introduction of tripartite development
- Agree to introduce the glfw third-party software for PC preview
- Need to confirming that the glfw third-party software could be auto added to the open source NOTICE.html through SDK compiling. owner: [wuhaibing](wuhaibin5@huawei.com)
Topic 3: Suggestions on improving the community governance mechanism
- The PMC agrees with the recommendations on improving the community governance mechanism.
- Based on the improvement points, the community development process, SIG specifications and templates could be provide optimization PR. owner: [liuguo](https://gitee.com/guoguoliu)
- The PMC need to organizes the optimization for the 10-minute quick start and proposal template for large feature proposal.
- The User Group team is added to the OpenHarmony community to collect and gain insights into end user requirements, and regularly communicate with the PMC/SIG team owner to close the problem. Need to established the user group team. owner: [liangkelei](https://gitee.com/xzmu)
- The member level is added to the community member category, and try to implement and configure automatic. owner: [huangminglong](https://gitee.com/minglonghuang) [mamingshuai](https://gitee.com/landwind)
Topic 4: Importing nghttp2 protocal for softbus sig
- OpenHarmony will not directly expose the interfaces of third-party open source application components to the system, disagree that nghttp2 is used as an independent three-party component to open a warehouse and merge into openharmony
- If the business is needed, the JS interface to the application must be design. owner: [zhangjian](zhangjian112@huawei.com)
Topic 5: Review the OpenHarmony version test report template
- Agree the content of the test report in the community.
- Archived in the directory of community/release-management/qa. owner: [jiyong](https://gitee.com/jiyong)
- Recommended to simply the inherited features be simplified. owner: [jiyong](https://gitee.com/jiyong)
# Review the issues and PRs from the community which need to higlight
The attendance have reached quorum with 8 participants in the meeting.
### Agenda:
1. Please review list [No20~28](https://shimo.im/sheets/N2A1MZgDZxfbBVAD/MODOC)
### Minute of Meeting:
Topic 1: Easily transport thirdparty dev board task
- 1. Unified HDI interface for graphics, media, and input has been defined.
- 2. Audio, Camera, and Input have provided chip-independent reference implementation codes, which are in the corresponding hal directory.
- 3. Display's corresponding display memory, hardware synthesis and Layer parts have been achived agree with HISI team, and agree to contribute DRM to the open source community, and refactoring is being implemented;
- 4. Codec and format are currently under planning. Recommended to recruit third-party development to provide open source implementations.
- 5. Agree to solution of"Linux Kernel Portability Enhancement Overall Plan", it will be tracked on kernel sig.
Topic 2: OpenHarmony input application development strategy
- 1. Agree that the input appliation developed in open source strategy, and it is recommended to discuss the supporting Chinese with the develop team.
- 2. Agree to postpone the camera application to the 930 LTS plan.
Topic 3: Proposal for creating OLA sig
- 1. Postpone to next time.
Topic 4: Proposal for creating robot os platform sig
- 1. Postpone to next time.
Topic 5: Proposal for creating Taro sig
- 1. Postpone to next time.
Topic 6: Proposal for creating industrial Paas platform SIG
- 1. Agree the proposal
topic 7: Proposal for creating educational information platform SIG
- 1. Agree the proposal
topic 8: Proposal for creating SIG Docs and OpenHarmony community document development process
The attendance have reached quorum with 12 participants in the meeting.
### Agenda:
1. Please review list [No1~3](https://etherpad.openharmony.cn/p/pmc)
### Minute of Meeting:
Topic1: Login easy sig creation
1. Agree to set up sig and introduce Huawei account system committer to join at the same time
Topic2: Special planning for community quality development
1. Agree the proposal of the community quality development planning;
2. For Committer and others quality control issues, need to be quantified and apply into committer/sig/PMC's promotion and withdrawal --owner: [xingwenhua](https://gitee.com/xhuazi)
Topic3: Optimization for OpenHarmony's basic concept
1. For the term names such as FA/PA in Ability, recommended to update the PA name to avoid conflicts between Particle Ability with Page Ability, and it is not recommended to abbreviate for Page Ability. -- owner: [niuhui](niuhui@huawei.com)
2. The problem of service name is too generalization, suggest to keep the current description, and add attributives to clarify the scene when using it. Special for IDE's new project name of service, recomment to change to Atom Service. --owner: [hulin](hulin.hulin@huawei.com)
3. For the inconsistency of OpenHarmony different subsystem, the device names such as Mini, Small, Standard, L0/L1/L2, etc., will unified operating system in three forms: Mini, Small, Standard; components are in two forms: Lite, standard components. --owner: [wanchengzhen](https://gitee.com/wanchengzhen)
4. The Ability name of the drive framework module is under internal rectification, and the code and documentation are to be updated simultaneously. The KAL name in OSAL and system framework is not modified. --owner: [houxuanzhe](https://gitee.com/zianed)
5. Since the bundle of the hpm bundle is a concept of building, it is more appropriate to use package name, and rename it. --owner: [wangyiming](youthdragon.wangyiming@huawei.com)
6. The southbound/northbound interface is a general expression, unified it by adding FAQ description. owner: [yangni] (https://gitee.com/neeen)
# Review the issues and PRs from the community which need to higlight
The attendance have reached quorum with 10 participants in the meeting.
### Agenda:
1. Please review list [No4~6](https://etherpad.openharmony.cn/p/pmc)
### Minute of Meeting:
Topc1: Proposal for creating Smart terminal platform sig
1. Reject, please further decompose the SIG into specific technical directions or join into the existing SIG area
Topic2: Design the graduate standard for devboard sig
1. Combining the demands of the OpenHarmony south ecology developement and devboard sig requirement, sort out the graduate standards forOpenHarmony devboard. owner:[likailong](https://gitee.com/kkup180)
# Review the issues and PRs from the community which need to higlight
The attendance have reached quorum with 12 participants in the meeting.
### Agenda:
1. Please review list [No7~9](https://etherpad.openharmony.cn/p/pmc)
### Minute of Meeting:
Topic1: Proposal for creating logistics robot sig
1. Agree the proposal, SIG's name should be named as common technologies, don't use an company name.
2. It is necessary to analyze the standard ROS, learn from the existing standard foundation of ROS, and make a general industry standard in order to speed up the construction of OpenHarmony's standard for logistics robot.
3. The interface of the cloud service cannot be used as the interface specification of the OS.
Topic2: Proposal for creating print framework SIG
1. Agree the proposal
Topic3: Fast Track Application for Midea Type A Donors
1. Approved by PMC
# Review the issues and PRs from the community which need to higlight
| No71 | devboard sig 开发版官网展示页面提议 | 结论：<br>可以输出到基础设施工作组进行方案设计，之后将初版交于PMC评审。<br>遗留问题<br>1）在展示页中加一项“适配的系统版本”的信息-责任人：基础设施工作组 完成时间：与基础设施工作组进一步沟通后确定<br>2）开发板展示的入口放在哪里?建议放到官网“支持”下拉框下的设备开发的子页中，具体需要基础设施工作组根据官网整体风格和逻辑进行设计--责任人：基础设施工作组 完成时间：与基础设施工作组进一步沟通后确定 <br>3）在官网展示的开发板代码提供的仓地址为OpenHarmony组织下的仓地址--责任人：devboard sig 完成时间：2022年6月20日 <br>4）后期要设计展示下架的机制--责任人：devboard sig 完成时间：2022年6月30日<br>5）展示页面的排序，建议进主干的排在前面--责任人：基础设施工作组 完成时间：与基础设施工作组进一步沟通后确定<br>6）不跳转到其他公司或者三方网站--责任人：devboard sig&基础设施工作组 完成时间：与基础设施工作组进一步沟通后确定<br>7）对于上官网的开发板后期逐渐形成标杆机制（devboard sig可以在例会上讨论）责任人：南向生态拓展团队&devboard sig 完成时间：2022年7月30日<br>8）提供资料给基础设施的法务审核时，尽量突出审核点--责任人：devboard sig 完成时间：2022年6月30日<br>9）未来是否要提供开发版的发行版镜像下载链接？如何提供？可以在devboard sig讨论 责任人：南向生态拓展团队&devboard sig 完成时间：2022年6月30日<br>10）官网展出数据要和gitte做到同源一致，责任人：devboard sig 完成时间：2022年6月30日<br>11）所发布的开发版，需要通过兼容性评测<br>12）所发布的开发版，通过OpenHarmony CI系统，保证一键可用 |
| No78 | OpenHarmony for RISC-V，进展介绍 | 结论：<br>按照当前RISC-VSIG工作目标和PMC专家的建议，继续推进OH for RISC-V工作遗留问题：<br>1）梳理当前OH for RISC-V适配的代码仓（三方库，基础组件），明确各代码仓适配工作的类型（修改编译选项、添加risc-v源码、切换版本等）责任人：邵阳，完成时间：2022年7月。<br>2）明确芯片厂商和软件所等成员单位维护和移植的代码仓。责任人：SIG组成员单位，完成时间：2022年7月<br>3）提前与适配涉及的代码仓owner联系，规划未来合入主线的具体方案。责任人：各代码仓适配负责人，完成时间2022年9月<br>4）RISC-VSIG组需要规划轻量级和小型系统适配工作。责任人：SIG组成员单位，完成时间：2022年10月<br>5）RISC-VSIG组需规划OH IDE的适配工作。责任人：SIG组成员单位，完成时间：2022年11月<br> |
熊卓孜
py6atlu3x
Lvwenxuan
wcr
Mr.NaCl