Merge branch 'master' of https://bdgit.educoder.net/py6atlu3x/openharmonydocs
commit
1e81313cb2
@ -0,0 +1,21 @@
|
||||
name: 需求建议
|
||||
description: 您需要反馈一个需求建议时，使用此模板反馈
|
||||
title: "[需求建议]: "
|
||||
labels: ["enhancement"]
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: |
|
||||
感谢提出建议，我们将仔细考虑！
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: 您需要什么功能？
|
||||
description: 请描述下您需要的功能是什么？社区会综合考虑是否支持您提出的需求。
|
||||
validations:
|
||||
required: true
|
||||
- type: textarea
|
||||
attributes:
|
||||
label: 为什么需要该功能？
|
||||
description: 请描述下该需求的价值，应用场景等。
|
||||
validations:
|
||||
required: true
|
||||
@ -0,0 +1,177 @@
|
||||
|
||||
Apache License
|
||||
Version 2.0, January 2004
|
||||
http://www.apache.org/licenses/
|
||||
|
||||
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
||||
|
||||
1. Definitions.
|
||||
|
||||
"License" shall mean the terms and conditions for use, reproduction,
|
||||
and distribution as defined by Sections 1 through 9 of this document.
|
||||
|
||||
"Licensor" shall mean the copyright owner or entity authorized by
|
||||
the copyright owner that is granting the License.
|
||||
|
||||
"Legal Entity" shall mean the union of the acting entity and all
|
||||
other entities that control, are controlled by, or are under common
|
||||
control with that entity. For the purposes of this definition,
|
||||
"control" means (i) the power, direct or indirect, to cause the
|
||||
direction or management of such entity, whether by contract or
|
||||
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
||||
outstanding shares, or (iii) beneficial ownership of such entity.
|
||||
|
||||
"You" (or "Your") shall mean an individual or Legal Entity
|
||||
exercising permissions granted by this License.
|
||||
|
||||
"Source" form shall mean the preferred form for making modifications,
|
||||
including but not limited to software source code, documentation
|
||||
source, and configuration files.
|
||||
|
||||
"Object" form shall mean any form resulting from mechanical
|
||||
transformation or translation of a Source form, including but
|
||||
not limited to compiled object code, generated documentation,
|
||||
and conversions to other media types.
|
||||
|
||||
"Work" shall mean the work of authorship, whether in Source or
|
||||
Object form, made available under the License, as indicated by a
|
||||
copyright notice that is included in or attached to the work
|
||||
(an example is provided in the Appendix below).
|
||||
|
||||
"Derivative Works" shall mean any work, whether in Source or Object
|
||||
form, that is based on (or derived from) the Work and for which the
|
||||
editorial revisions, annotations, elaborations, or other modifications
|
||||
represent, as a whole, an original work of authorship. For the purposes
|
||||
of this License, Derivative Works shall not include works that remain
|
||||
separable from, or merely link (or bind by name) to the interfaces of,
|
||||
the Work and Derivative Works thereof.
|
||||
|
||||
"Contribution" shall mean any work of authorship, including
|
||||
the original version of the Work and any modifications or additions
|
||||
to that Work or Derivative Works thereof, that is intentionally
|
||||
submitted to Licensor for inclusion in the Work by the copyright owner
|
||||
or by an individual or Legal Entity authorized to submit on behalf of
|
||||
the copyright owner. For the purposes of this definition, "submitted"
|
||||
means any form of electronic, verbal, or written communication sent
|
||||
to the Licensor or its representatives, including but not limited to
|
||||
communication on electronic mailing lists, source code control systems,
|
||||
and issue tracking systems that are managed by, or on behalf of, the
|
||||
Licensor for the purpose of discussing and improving the Work, but
|
||||
excluding communication that is conspicuously marked or otherwise
|
||||
designated in writing by the copyright owner as "Not a Contribution."
|
||||
|
||||
"Contributor" shall mean Licensor and any individual or Legal Entity
|
||||
on behalf of whom a Contribution has been received by Licensor and
|
||||
subsequently incorporated within the Work.
|
||||
|
||||
2. Grant of Copyright License. Subject to the terms and conditions of
|
||||
this License, each Contributor hereby grants to You a perpetual,
|
||||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
||||
copyright license to reproduce, prepare Derivative Works of,
|
||||
publicly display, publicly perform, sublicense, and distribute the
|
||||
Work and such Derivative Works in Source or Object form.
|
||||
|
||||
3. Grant of Patent License. Subject to the terms and conditions of
|
||||
this License, each Contributor hereby grants to You a perpetual,
|
||||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
||||
(except as stated in this section) patent license to make, have made,
|
||||
use, offer to sell, sell, import, and otherwise transfer the Work,
|
||||
where such license applies only to those patent claims licensable
|
||||
by such Contributor that are necessarily infringed by their
|
||||
Contribution(s) alone or by combination of their Contribution(s)
|
||||
with the Work to which such Contribution(s) was submitted. If You
|
||||
institute patent litigation against any entity (including a
|
||||
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
||||
or a Contribution incorporated within the Work constitutes direct
|
||||
or contributory patent infringement, then any patent licenses
|
||||
granted to You under this License for that Work shall terminate
|
||||
as of the date such litigation is filed.
|
||||
|
||||
4. Redistribution. You may reproduce and distribute copies of the
|
||||
Work or Derivative Works thereof in any medium, with or without
|
||||
modifications, and in Source or Object form, provided that You
|
||||
meet the following conditions:
|
||||
|
||||
(a) You must give any other recipients of the Work or
|
||||
Derivative Works a copy of this License; and
|
||||
|
||||
(b) You must cause any modified files to carry prominent notices
|
||||
stating that You changed the files; and
|
||||
|
||||
(c) You must retain, in the Source form of any Derivative Works
|
||||
that You distribute, all copyright, patent, trademark, and
|
||||
attribution notices from the Source form of the Work,
|
||||
excluding those notices that do not pertain to any part of
|
||||
the Derivative Works; and
|
||||
|
||||
(d) If the Work includes a "NOTICE" text file as part of its
|
||||
distribution, then any Derivative Works that You distribute must
|
||||
include a readable copy of the attribution notices contained
|
||||
within such NOTICE file, excluding those notices that do not
|
||||
pertain to any part of the Derivative Works, in at least one
|
||||
of the following places: within a NOTICE text file distributed
|
||||
as part of the Derivative Works; within the Source form or
|
||||
documentation, if provided along with the Derivative Works; or,
|
||||
within a display generated by the Derivative Works, if and
|
||||
wherever such third-party notices normally appear. The contents
|
||||
of the NOTICE file are for informational purposes only and
|
||||
do not modify the License. You may add Your own attribution
|
||||
notices within Derivative Works that You distribute, alongside
|
||||
or as an addendum to the NOTICE text from the Work, provided
|
||||
that such additional attribution notices cannot be construed
|
||||
as modifying the License.
|
||||
|
||||
You may add Your own copyright statement to Your modifications and
|
||||
may provide additional or different license terms and conditions
|
||||
for use, reproduction, or distribution of Your modifications, or
|
||||
for any such Derivative Works as a whole, provided Your use,
|
||||
reproduction, and distribution of the Work otherwise complies with
|
||||
the conditions stated in this License.
|
||||
|
||||
5. Submission of Contributions. Unless You explicitly state otherwise,
|
||||
any Contribution intentionally submitted for inclusion in the Work
|
||||
by You to the Licensor shall be under the terms and conditions of
|
||||
this License, without any additional terms or conditions.
|
||||
Notwithstanding the above, nothing herein shall supersede or modify
|
||||
the terms of any separate license agreement you may have executed
|
||||
with Licensor regarding such Contributions.
|
||||
|
||||
6. Trademarks. This License does not grant permission to use the trade
|
||||
names, trademarks, service marks, or product names of the Licensor,
|
||||
except as required for reasonable and customary use in describing the
|
||||
origin of the Work and reproducing the content of the NOTICE file.
|
||||
|
||||
7. Disclaimer of Warranty. Unless required by applicable law or
|
||||
agreed to in writing, Licensor provides the Work (and each
|
||||
Contributor provides its Contributions) on an "AS IS" BASIS,
|
||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
||||
implied, including, without limitation, any warranties or conditions
|
||||
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
||||
PARTICULAR PURPOSE. You are solely responsible for determining the
|
||||
appropriateness of using or redistributing the Work and assume any
|
||||
risks associated with Your exercise of permissions under this License.
|
||||
|
||||
8. Limitation of Liability. In no event and under no legal theory,
|
||||
whether in tort (including negligence), contract, or otherwise,
|
||||
unless required by applicable law (such as deliberate and grossly
|
||||
negligent acts) or agreed to in writing, shall any Contributor be
|
||||
liable to You for damages, including any direct, indirect, special,
|
||||
incidental, or consequential damages of any character arising as a
|
||||
result of this License or out of the use or inability to use the
|
||||
Work (including but not limited to damages for loss of goodwill,
|
||||
work stoppage, computer failure or malfunction, or any and all
|
||||
other commercial damages or losses), even if such Contributor
|
||||
has been advised of the possibility of such damages.
|
||||
|
||||
9. Accepting Warranty or Additional Liability. While redistributing
|
||||
the Work or Derivative Works thereof, You may choose to offer,
|
||||
and charge a fee for, acceptance of support, warranty, indemnity,
|
||||
or other liability obligations and/or rights consistent with this
|
||||
License. However, in accepting such obligations, You may act only
|
||||
on Your own behalf and on Your sole responsibility, not on behalf
|
||||
of any other Contributor, and only if You agree to indemnify,
|
||||
defend, and hold each Contributor harmless for any liability
|
||||
incurred by, or claims asserted against, such Contributor by reason
|
||||
of your accepting any such warranty or additional liability.
|
||||
|
||||
END OF TERMS AND CONDITIONS
|
||||
@ -0,0 +1,46 @@
|
||||
# OpenHarmony Community
|
||||
Welcome to the OpenHarmony community.
|
||||
|
||||
English | [简体中文](./README.md)
|
||||
|
||||
## Introduction
|
||||
The **community** repository stores the following content:
|
||||
|
||||
- Community Governance Organizational Structure
|
||||
- [Project Management Committee](/zh/pmc.md)
|
||||
- [Contributing to the Community](https://gitee.com/openharmony/docs/blob/master/en/contribute/Readme-EN.md)
|
||||
- [Contributor Agreement for Contributing to the Community](https://dco.openharmony.io/sign/Z2l0ZWUlMkZPcGVuQXRvbQ==)
|
||||
- [Communications in the Community](https://gitee.com/openharmony/docs/blob/master/en/contribute/communication-in-community.md)
|
||||
- [Responses to Security Issues](https://gitee.com/openharmony/security)
|
||||
- [Project Logo](https://gitee.com/openharmony/community/blob/master/README_EN.md#project-logo)
|
||||
|
||||
## Community Governance Organizational Structure
|
||||
|
||||
The [Project Management Committee](/zh/pmc.md) (PMC) manages the OpenHarmony community.
|
||||
|
||||
## Contributing to the Community
|
||||
|
||||
See [How to Contribute to the OpenHarmony Community](https://gitee.com/openharmony/docs/blob/master/en/contribute/Readme-EN.md).
|
||||
|
||||
## Signing the Developer Certificate of Origin
|
||||
|
||||
You must sign the Developer Certificate of Origin (DCO) before you can contribute to the community.
|
||||
|
||||
[Sign the DCO and check the signing status](https://dco.openharmony.io/sign/Z2l0ZWUlMkZvcGVuX2hhcm1vbnk=).
|
||||
|
||||
## Communications in the Community
|
||||
|
||||
### OpenHarmony Mailing List
|
||||
| Address | Introduction | Description |
|
||||
| ---------------------------------------|---------- | ------------------------------------------------------------ |
|
||||
| contact@openharmony.io <img width=150/> | Public mailing list <img width=100/> | Public mailing list of the OpenHarmony community. You can send a signed CLA to this mailing list. <img width=200/> |
|
||||
| dev@openharmony.io <img width=150/>| Development mailing list <img width=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. <img width=200/> |
|
||||
| cicd@openharmony.io <img width=150/> | CI mailing list <img width=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. <img width=200/> |
|
||||
| pmc@openharmony.io <img width=150/>| PMC mailing list <img width=100/> | Mailing list for PMC discussion. PMC members can [subscribe to](https://lists.openatom.io/postorius/lists/pmc.openharmony.io/) this mailing list. <img width=200/> |
|
||||
| scy@openharmony.io <img width=150/> | Mailing list for security issues <img width=100/> | Mailing list for reporting OpenHarmony security issues. <img width=200/> |
|
||||
| scy-priv@openharmony.io <img width=150/>| Security group mailing list <img width=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. <img width=200/> |
|
||||
|
||||
|
||||
## Project Logo
|
||||
|
||||
Please refer to the trademark usage guidelines from [OpenHarmony LOGO](https://www.openharmony.cn/trademark).
|
||||
@ -0,0 +1,33 @@
|
||||
# Project Management Committee Meeting 2020-09-14
|
||||
|
||||
### Attendance:
|
||||
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
|
||||
|
||||
|
||||
@ -0,0 +1,56 @@
|
||||
# Project Management Committee Meeting 2020-09-28
|
||||
|
||||
### Attendance:
|
||||
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
|
||||
|
||||
| Plan | Period | Proposer |
|
||||
|--------------|:--------------:|:--------------:|
|
||||
| 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.
|
||||
@ -0,0 +1,44 @@
|
||||
# Project Management Committee Meeting 2021-02-01
|
||||
|
||||
### Attendance:
|
||||
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
|
||||
|
||||
| Plan | Period | Proposer | Progress | Status |
|
||||
|--------------|:--------------:|:--------------:|:--------------:|:--------------:|
|
||||
| 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
|
||||
|
||||
|
||||
### Open discussion
|
||||
@ -0,0 +1,37 @@
|
||||
# Project Management Committee Meeting 2021-03-29
|
||||
|
||||
### Attendance:
|
||||
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
|
||||
|
||||
|
||||
### Open discussion
|
||||
@ -0,0 +1,61 @@
|
||||
# Project Management Committee Meeting 2021-04-13
|
||||
|
||||
### Attendance:
|
||||
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.
|
||||
TOP projects:
|
||||
sig-kernel [@wangmihu](https://gitee.com/wangmihu2008)
|
||||
sig-Test [@gaohanyi](https://gitee.com/gaohanyi1982)
|
||||
sig-Compiler-and-build [@wangxing](https://gitee.com/wangxing-hw)
|
||||
sig-hisi-vendor [@yuanwenhong](https://gitee.com/yuanwhong)
|
||||
sig-softbus [@xuyongpan](https://gitee.com/Xuyongpan)
|
||||
7. A total of 75 issues will be created after March 2021, of which 57 have not designated responsible persons;
|
||||
TOP projects:
|
||||
sig-kernel [@wangmihu](https://gitee.com/wangmihu2008),
|
||||
sig-graphic [@lizhiqi](https://gitee.com/pssea)
|
||||
sig-ACE [@lubo](https://gitee.com/borne)
|
||||
sig-Test [@gaohanyi](https://gitee.com/gaohanyi1982)
|
||||
|
||||
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
|
||||
|
||||
|
||||
### Open discussion
|
||||
@ -0,0 +1,43 @@
|
||||
# Project Management Committee Meeting 2021-04-26
|
||||
|
||||
### Attendance:
|
||||
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
|
||||
|
||||
|
||||
### Open discussion
|
||||
@ -0,0 +1,31 @@
|
||||
# Project Management Committee Meeting 2021-05-10
|
||||
|
||||
### Attendance:
|
||||
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
|
||||
|
||||
|
||||
### Open discussion
|
||||
@ -0,0 +1,43 @@
|
||||
# Project Management Committee Meeting 2021-05-26
|
||||
|
||||
### Attendance:
|
||||
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)
|
||||
device_hisilicon_third_party_uboot -> third_party_uboot
|
||||
device_hisilicon_third_party_ffmpeg -> third_party_ffmpeg
|
||||
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
|
||||
|
||||
|
||||
### Open discussion
|
||||
@ -0,0 +1,42 @@
|
||||
# Project Management Committee Meeting 2021-06-28
|
||||
|
||||
### Attendance:
|
||||
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
|
||||
|
||||
|
||||
### Open discussion
|
||||
@ -0,0 +1,46 @@
|
||||
# Project Management Committee Meeting 2021-07-22
|
||||
|
||||
### Attendance:
|
||||
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: Proposal for solution-component
|
||||
- 1. The basic OS capability has not been incorporated into the openharmony project, should be embeded in the form of vendor repository.
|
||||
|
||||
Topic 2: QEMU Progress Report
|
||||
- 1. Agree to the repository of vendor_ohemu will be accepted into OpenHarmony project.
|
||||
|
||||
Topic 3: Proposal the ark toolchain and runtime as a default runtime of OpenHarmony
|
||||
- 1. Agree the proposal
|
||||
|
||||
Topic 4: Proposal for creating blockchain sig
|
||||
- 1. As a part of project of security sig
|
||||
|
||||
Topic 5: Proposal for creating Python SIG
|
||||
- 1. The code of the SIG group has been refactored and will setup in OpenHarmony SIG group.
|
||||
|
||||
|
||||
Topic 6: Proposal for creating CICD SIG
|
||||
- 1. Suggest to rename as infrastructure SIG and will setup in OpenHarmony SIG group.
|
||||
|
||||
|
||||
topic 7: Porting thirdparty devboard requirements for OpenHarmony
|
||||
- 1. It is tracked by some special issue.
|
||||
|
||||
topic 8: Proposal for creating Linkboy sig
|
||||
- 1. Agree the proposal and establish education sig.
|
||||
|
||||
|
||||
# Review the issues and PRs from the community which need to higlight
|
||||
|
||||
|
||||
### Open discussion
|
||||
|
||||
@ -0,0 +1,51 @@
|
||||
# Project Management Committee Meeting 2021-08-19
|
||||
|
||||
### Attendance:
|
||||
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
|
||||
- 1. Agree the proposal.
|
||||
|
||||
topic 9: Creating OpenHarmony Github mirror repository
|
||||
- 1. Agree the proposal.
|
||||
|
||||
# Review the issues and PRs from the community which need to higlight
|
||||
|
||||
|
||||
### Open discussion
|
||||
@ -0,0 +1,32 @@
|
||||
# Project Management Committee Meeting 2021-09-30
|
||||
|
||||
### Attendance:
|
||||
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
|
||||
|
||||
|
||||
### Open discussion
|
||||
@ -0,0 +1,25 @@
|
||||
# Project Management Committee Meeting 2021-10-14
|
||||
|
||||
### Attendance:
|
||||
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
|
||||
|
||||
|
||||
### Open discussion
|
||||
@ -0,0 +1,29 @@
|
||||
# Project Management Committee Meeting 2021-10-28
|
||||
|
||||
### Attendance:
|
||||
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
|
||||
|
||||
|
||||
### Open discussion
|
||||
@ -0,0 +1,31 @@
|
||||
# PMC 例会 2021-12-23
|
||||
|
||||
## 参会人员 (Attendance):
|
||||
| 姓名 | 账号 |
|
||||
| :----: | :----: |
|
||||
| 董金光 |[@dongjinguang](https://gitee.com/dongjinguang) |
|
||||
| 任革林 | [@im-off-this-week](https://gitee.com/im-off-this-week) |
|
||||
| 强波 | [@huawei_qiangbo](https://gitee.com/huawei_qiangbo) |
|
||||
| 余枝强 | [@yuzhiqiang101](https://gitee.com/yuzhiqiang101) |
|
||||
| 梁克雷 | [@xzmu](https://gitee.com/xzmu) |
|
||||
| 黄明龙 | [@minglonghuang](https://gitee.com/minglonghuang) |
|
||||
| 李家欣 | [@ninalijiaxin](https://gitee.com/ninalijiaxin) |
|
||||
| 邢文华 | [@xhuazi](https://gitee.com/xhuazi) |
|
||||
| 高涵一 | [@gaohanyi1982](https://gitee.com/gaohanyi1982) |
|
||||
| 议题相关人员 | 议题相关人员|
|
||||
|
||||
|
||||
## 议题(Agenda):
|
||||
|
||||
1. PMC etherpad 议题列表 [No24~28](https://etherpad.openharmony.cn/p/pmc)
|
||||
|
||||
|
||||
## 会议纪要(Minute of Meeting):
|
||||
|
||||
| 议题编号 | 议题名称 |会议纪要 |
|
||||
| :----: | :----: | :----: |
|
||||
| No24 | 申请创建OpenHarmony迁移助手SIG | 会议结论:1. 需要验证在OpenHarmony设备上是否可以运行 <br> 2. 鉴于工作目标一致,建议与crossplatform-ui SIG归一|
|
||||
| No25| OpenHarmony 64位软件编程规范评审发布| review问题闭环并评审通过,同意发布 |
|
||||
| No26 | OpenHarmony HDF驱动编程规范评审发布 | 同意作为初始版本发布 |
|
||||
| No27 | OpenHarmony 日志打印规范评审发布 | 评审通过,同意发布 |
|
||||
| No28 | OpenHarmony主仓代码贡献度量规则评审 | 同意 |
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in new issue