- dev - lists.openatom.io

Re：部分仓在 OpenHarmony GitHub镜像上未公开，导致代码获取失败 | Certain repos are not public on OpenHarmony Github mirror, casuing code fetch failure
by Goldenboy 04 Jan '22

04 Jan '22

请明帅协助看看是什么原因 Original From:"Jianyu Liu via dev"< dev(a)openharmony.io >; Date:2022/1/3 22:33 To:"dev"< dev(a)openharmony.io >; CC:"community(a)openharmony.io"< community(a)openharmony.io >; Subject:[Dev] 部分仓在 OpenHarmony GitHub镜像上未公开，导致代码获取失败 | Certain repos are not public on OpenHarmony Github mirror, casuing code fetch failure 各位新年好，参照获取源码.md中的获取方式4 - 方式二，从OpenHarmony GitHub镜像仓获取代码时，下载会卡在 95% （ Fetching: 95% (264/276) vendor_ohemu）。后会显示错误代码： fatal: Authentication failed for 'https://github.com/openharmony/third_party_egl/' fatal: Authentication failed for 'https://github.com/openharmony/third_party_opengles/' fatal: Authentication failed for 'https://github.com/openharmony-sig/third_party_tinyalsa/' 以上三个仓在Gitee上是开源仓，但在GitHub上则需授权访问。这个问题已有同事在oschina 开源中国的仓下反馈（Issue链接）。因为不确定该在OpenHarmony Gitee的哪个仓下反馈，所以在dev 邮件列表反馈。希望可以尽快修复。谢谢。祝好，刘建宇 Hello guys, happy new year. Followingsourcecode-acquire.md Method 4 – Method 2, to acquire source code from OpenHarmony GitHub mirror, it constantly stuck at 95% (Fetching: 95% (264/276) vendor_ohemu ). Based on the error info: fatal: Authentication failed for 'https://github.com/openharmony/third_party_egl/' fatal: Authentication failed for 'https://github.com/openharmony/third_party_opengles/' fatal: Authentication failed for 'https://github.com/openharmony-sig/third_party_tinyalsa/' It seems like those 3 repos are not public and require access authentication. Yet those same 3 repos are public accessable on OpenHarmony Gitee. This issues is already reported by others under oschina Gitee (Issue link ). Since I’m not sure which OpenHarmony repo this issue should be reported to, hence dev mailing list. Looking forward for the fix. Thanks. Best, Jianyu Liu

2 1

部分仓在 OpenHarmony GitHub镜像上未公开，导致代码获取失败 | Certain repos are not public on OpenHarmony Github mirror, casuing code fetch failure
by Jianyu Liu 03 Jan '22

03 Jan '22

各位新年好，参照获取源码.md<https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/get-code/so…> 中的获取方式4 - 方式二，从OpenHarmony GitHub 镜像仓获取代码时，下载会卡在 95% （ Fetching: 95% (264/276) vendor_ohemu ）。后会显示错误代码： fatal: Authentication failed for 'https://github.com/openharmony/third_party_egl/' fatal: Authentication failed for 'https://github.com/openharmony/third_party_opengles/' fatal: Authentication failed for 'https://github.com/openharmony-sig/third_party_tinyalsa/' 以上三个仓在Gitee上是开源仓，但在GitHub上则需授权访问。这个问题已有同事在 oschina 开源中国的仓下反馈（Issue链接<https://gitee.com/oschina/git-osc/issues/I4P4QE>）。因为不确定该在OpenHarmony Gitee的哪个仓下反馈，所以在 dev 邮件列表反馈。希望可以尽快修复。谢谢。祝好，刘建宇 ________________________________ Hello guys, happy new year. Following sourcecode-acquire.md<https://gitee.com/openharmony/docs/blob/master/en/device-dev/get-code/sourc…> Method 4 – Method 2, to acquire source code from OpenHarmony GitHub mirror, it constantly stuck at 95% ( Fetching: 95% (264/276) vendor_ohemu ). Based on the error info: fatal: Authentication failed for 'https://github.com/openharmony/third_party_egl/' fatal: Authentication failed for 'https://github.com/openharmony/third_party_opengles/' fatal: Authentication failed for 'https://github.com/openharmony-sig/third_party_tinyalsa/' It seems like those 3 repos are not public and require access authentication. Yet those same 3 repos are public accessable on OpenHarmony Gitee. This issues is already reported by others under oschina Gitee ( Issue link<https://gitee.com/oschina/git-osc/issues/I4P4QE> ). Since I’m not sure which OpenHarmony repo this issue should be reported to, hence dev mailing list. Looking forward for the fix. Thanks. Best, Jianyu Liu

1 0

[New Committer] Welcoming to become committer of OpenHarmony's HDC debug tool related repository : Mayaohui
by dongjinguang 31 Dec '21

31 Dec '21

Hello MaYaohui, The OpenHarmony PMC hereby offers you committer privileges to those HDC debug tools releated project. These privileges are offered on the understanding that you'll use them reasonably and with common sense. You have made great contributions to HDC related project. Below are your PRs: HDC repository: 1. Fixed the server process startup problem: https://gitee.com/openharmony/developtools_hdc_standard/pulls/200 2. Optimized debug log information: https://gitee.com/openharmony/developtools_hdc_standard/pulls/190 3. Help to update the HDC version Number:https://gitee.com/openharmony/developtools_hdc_standard/pulls/197 4. Fixed the file synchronization problem: https://gitee.com/openharmony/developtools_hdc_standard/pulls/175: And MaYaohui also is PMC member for OpenHarmony project and the owner of DFX project. All of them contributed to OpenHarmony and we’re excited to have Yuhao join the project. If you accept, please follow your guidelines: 1. Register an DCO 2. Provide your personal information as following format and sent to email: pmc(a)openharmony.io 3. OpenHarmony Repository: 4. your name: 5. gitee id url: https://www.gitee.com/xxx 6. gitee id associated email:

1 0

[New Committer] Welcoming to become committer of OpenHarmony's softbus related repositories : Yuhao
by dongjinguang 31 Dec '21

31 Dec '21

Hello Yuhao, The OpenHarmony PMC hereby offers you committer privileges to those softbus releated project. These privileges are offered on the understanding that you'll use them reasonably and with common sense. You have made great contributions to softbus related project. Below are your PRs: ipc_lite repository: 1. Add ResetLiteIpc interface: https://gitee.com/openharmony/communication_ipc_lite/pulls/4 2. Review ipc related document: https://gitee.com/openharmony/docs/pulls/173 3. Fix the typo of the LTEPC interface: https://gitee.com/openharmony-retired/communication_interfaces_kits_ipc_lit…. ipc repository: 1. The ipc implements the token ID transfer and query: https://gitee.com/openharmony/communication_ipc/pulls/58. dsoftbus repository: 1. Enhancement ble gat connection capability: https://gitee.com/openharmony/communication_dsoftbus/pulls/426. 2. Added osd capability: https://gitee.com/openharmony/communication_dsoftbus/pulls/286. 3. Issue fixed: https://gitee.com/openharmony/communication_dsoftbus/pulls/520 4. Using hilog for softbus debug information: https://gitee.com/openharmony/communication_dsoftbus/pulls/40. All of them contributed to OpenHarmony and we’re excited to have Yuhao join the project. If you accept, please follow your guidelines: 1. Register an DCO 2. Provide your personal information as following format and sent to email: pmc(a)openharmony.io 3. OpenHarmony Repository: 4. your name: 5. gitee id url: https://www.gitee.com/xxx 6. gitee id associated email:

1 0

[New Committer] Welcoming to become committer of OpenHarmony's ace related repositories : Sunfei
by dongjinguang 30 Dec '21

30 Dec '21

Hello Sunfei, The OpenHarmony PMC hereby offers you committer privileges to those ace_ace_engine, ace_napi, third_party_flutter project. These privileges are offered on the understanding that you'll use them reasonably and with common sense. You have made great contributions to ACE related project. Below are your PRs: Ace related repository contribution: 1. https://gitee.com/openharmony/ace_ace_engine/pulls/13 2. https://gitee.com/openharmony/ace_ace_engine/pulls/15 3. https://gitee.com/openharmony/ace_ace_engine/pulls/226 4. https://gitee.com/openharmony/ace_ace_engine/pulls/232 5. https://gitee.com/openharmony/ace_ace_engine/pulls/285 6. https://gitee.com/openharmony/ace_ace_engine/pulls/291 7. https://gitee.com/openharmony/ace_ace_engine/pulls/316 8. https://gitee.com/openharmony/ace_ace_engine/pulls/345 9. https://gitee.com/openharmony/ace_ace_engine/pulls/398 10. https://gitee.com/openharmony/ace_napi/pulls/64 11. https://gitee.com/openharmony/ace_napi/pulls/97 12. https://gitee.com/openharmony/third_party_flutter/pulls/16 13. https://gitee.com/openharmony/third_party_flutter/pulls/30 All of them contributed to OpenHarmony and we’re excited to have Sunfei join the project. If you accept, please follow your guidelines: 1. Register an DCO 2. Provide your personal information as following format and sent to email: pmc(a)openharmony.io 3. OpenHarmony Repository: 4. your name: 5. gitee id url: https://www.gitee.com/xxx 6. gitee id associated email:

1 0

[New Committer] Welcoming to become committer of OpenHarmony's multimedia related repositories : sharpshooter_t
by dongjinguang 29 Dec '21

29 Dec '21

Hello taojun, The OpenHarmony PMC hereby offers you committer privileges to those multimedia_media_standard, third_party_gstreamer project. These privileges are offered on the understanding that you'll use them reasonably and with common sense. You have made great contributions to multimedia related project. Below are your PRs: 1. https://gitee.com/openharmony/multimedia_media_standard/pulls/5 2. https://gitee.com/openharmony/multimedia_media_standard/pulls/39 3. https://gitee.com/openharmony/multimedia_media_standard/pulls/40 4. https://gitee.com/openharmony/multimedia_media_standard/pulls/42 5. https://gitee.com/openharmony/multimedia_media_standard/pulls/53 6. https://gitee.com/openharmony/multimedia_media_standard/pulls/54 7. https://gitee.com/openharmony/multimedia_media_standard/pulls/55 9. https://gitee.com/openharmony/multimedia_media_standard/pulls/66 10. https://gitee.com/openharmony/multimedia_media_standard/pulls/72 11. https://gitee.com/openharmony/multimedia_media_standard/pulls/74 12. https://gitee.com/openharmony/multimedia_media_standard/pulls/80 13. https://gitee.com/openharmony/multimedia_media_standard/pulls/89 All of them contributed to OpenHarmony and we’re excited to have taojun join the project. If you accept, please follow your guidelines: 1. Register an DCO 2. Provide your personal information as following format and sent to email: pmc(a)openharmony.io 3. OpenHarmony Repository: 4. your name: 5. gitee id url: https://www.gitee.com/xxx 6. gitee id associated email:

1 0

[New Committer] Welcoming to become committer of OpenHarmony's little kernel related repositories : JerryH
by dongjinguang 29 Dec '21

29 Dec '21

Hello JerryH, The OpenHarmony PMC hereby offers you committer privileges to those drivers_liteos, kernel_liteos_a, kernel_liteos_m, third_party_FatFs, third_party_FreeBSD, third_party_Linux_Kernel, third_party_NuttX, third_party_cmsis, third_party_mksh, third_party_mtd_utils, third_party_musl, third_party_optimized_routines, third_party_rt_thread, third_party_toybox, third_party_littlefs project. These privileges are offered on the understanding that you'll use them reasonably and with common sense. You have made great contributions to little kernel related project. Below are your PRs: kernel_liteos_m repository: 1. TrustZone for the TEE solution with Cortex-m33: https://gitee.com/openharmony/kernel_liteos_m/pulls/118 2. Modified the kernel CMSIS interface and abnormal commissioning: https://gitee.com/openharmony/kernel_liteos_m/pulls/24 3. The MPU-based task stack protection mechanism is added: https://gitee.com/openharmony/kernel_liteos_m/pulls/46 4. Add the backtrace component: https://gitee.com/openharmony/kernel_liteos_m/pulls/135 5. Add the arm9 architecture: https://gitee.com/openharmony/kernel_liteos_m/pulls/205 6. Optimized scheduling and interrupt assembly logic: https://gitee.com/openharmony/kernel_liteos_m/pulls/222 7. The mechanism for deleting software timers is optimized: https://gitee.com/openharmony/kernel_liteos_m/pulls/446. 8. Fixed issues: https://gitee.com/openharmony/kernel_liteos_m/pulls/455 kernel_liteos_a repository: 1. The VM module supports small-sized tailoring: https://gitee.com/openharmony/kernel_liteos_a/pulls/105 2. Multi-core boot and memory mapping decoupling simplify third-party chip adaptation: https://gitee.com/openharmony/kernel_liteos_a/pulls/487 3. Solving the deadlock problem of the SHM shared memory interface: https://gitee.com/openharmony/kernel_liteos_a/pulls/438. 4. Troubleshooting the Memory Leakage Mechanism: https://gitee.com/openharmony/kernel_liteos_a/pulls/242 5. Solving the image code segment tampered vulnerability: https://gitee.com/openharmony/kernel_liteos_a/pulls/112 Contribution to code review: 1. Low memory resource reclamation: https://gitee.com/openharmony/kernel_liteos_m/pulls/434#diff_note_7812600 2. LMS lightweight address disinfection: https://gitee.com/openharmony/kernel_liteos_a/pulls/708#diff_note_7539548 3. Low power consumption: https://gitee.com/openharmony/kernel_liteos_m/pulls/298#diff_note_6666918 4. A stack error occurs when a new chip is transplanted in the community: https://gitee.com/openharmony/docs/issues/I4852F#note_6507406. 5. Memory size collected by task: https://gitee.com/openharmony/kernel_liteos_m/pulls/285#diff_note_6415610 6. The heap memory algorithm supports multiple discontinuous memory segments: https://gitee.com/openharmony/kernel_liteos_m/pulls/249#diff_note_6250867 All of them contributed to OpenHarmony and we’re excited to have JerryH join the project. If you accept, please follow your guidelines: 1. Register an DCO 2. Provide your personal information as following format and sent to email: pmc(a)openharmony.io 3. OpenHarmony Repository: 4. your name: 5. gitee id url: https://www.gitee.com/xxx 6. gitee id associated email:

1 0

[SIG-Charter-Proposal-Lua] 申请成立SIG_Lua
by 乔楚|HonestQia 27 Dec '21

27 Dec '21

各位PMC负责人及社区专家：现申请成立SIG_Lua，申请材料请见附件，敬请各位审阅和提出建议，谢谢！顺祝工作顺利！ -------------------------------------- 乔楚|HonestQiao 手机：13581882013 微信：HonestQiao 邮箱：honestqiao(a)163.com

1 0

请点击链接反馈SIG会议纪要，后续上会评审后请尽快反馈纪要//FW: 【会议通知】OpenHarmony 架构SIG，时间：2021-12-21 09:30-10:30，地点：线上会议，请您准时与会：）
by hengting (A) 27 Dec '21

27 Dec '21

反馈纪要链接：https://etherpad.openharmony.cn/p/sig-architecture From: hengting (A) Sent: Monday, December 20, 2021 4:39 PM To: Rengelin <rengelin(a)huawei.com>; wanchengzhen <wanchengzhen(a)huawei.com>; Qiangbo(Paul,OpenHarmony) <qiangbo2(a)huawei.com>; dongjinguang <dongjinguang(a)huawei.com>; Zhaowenhua <zhaowenhua(a)huawei.com>; fangzhongcan <fangzhongcan(a)huawei.com>; 毛思平 <maosiping(a)huawei.com>; Jiayanhong <jiayanhong(a)huawei.com>; zhanghaifeng (K) <zhanghaifeng11(a)huawei.com>; Zhangxiaobo (Tony) <tony.zhangxiaobo(a)huawei.com>; Tangchengkai <tangchengkai(a)huawei.com>; renxiang (E) <renxiang11(a)huawei.com>; zhaizhiqiang <zhaizhiqiang(a)huawei.com>; guochaosheng <guochaosheng(a)huawei.com>; Xudaqing <xudaqing(a)huawei.com> Subject: 【会议通知】OpenHarmony 架构SIG，时间：2021-12-21 09:30-10:30，地点：线上会议，请您准时与会：）会议主题 Subject OpenHarmony 架构SIG 会议时间 Time 2021-12-21 09:30-10:30(UTC+08:00)Beijing 会议地点 Location 线上会议召集人 Convener 任革林视频会议 Video Meeting 加入会议： Join (Host) <http://imeeting.huawei.com/meeting/startzoom?id=bc2483726ec1475daeff49d2b0f…> Join (Internal) <http://imeeting.huawei.com/meeting/joinzoom?id=0171006113&app=welink> Join (External) <https://welink.zhumu.com/j/171006113> 地点：线上会议ID： 0171006113 与会人 Attendees 万承臻；任革林；赵文华；强波；董金光外部与会人 External Participants dev(a)openharmony.io<mailto:dev@openharmony.io>;minglong@iscas.ac.cn；kelei@iscas.ac.cn 会议议题 Agenda 编号 No. 议题名称 Topic 议题背景介绍 Topic background introduction 时长 Duration 提案人 Proposer 汇报人 Reporter 纪要人 Recorder 议题参与人 Members 1 新增杂散子系统开源仓 10 10 赵超、方忠灿赵超、方忠灿赵超、方忠灿赵超、方忠灿 2 新增仓communication_netmanager_base和communication_netmanager_ext 基础网络连接管理：提供基础网络连接管理和对应的native和ACE JS API接口，包括不同网络连接优先级管理，网络连通性检查、网络连接质量评估、网络连接信息查询、网络连接状态变化等；网络管理扩展：提供网络热点共享、VPN、加密DNS等附加网络管理能力和对应的native和ACE JS API接口 10 毛思平、贾艳红、张海丰毛思平、贾艳红、张海丰毛思平、贾艳红、张海丰毛思平、贾艳红、张海丰 3 新增开源仓libexif 图片Exif相关功能需求依赖开源仓引入 10 张晓波张晓波张晓波李昕，朱明亮，程成 4 新建全局资源调度子系统sig仓 OpenHarmony上新建5个仓，用于子系统仓代码提交和开源。修改两个仓名 10 唐城开唐城开唐城开王文利、曾广珠、陈明 5 新增开源仓auxiliary_tools OpenHarmony上新建OH辅助工具SIG代码仓auxiliary_tools 10 赵军霞赵军霞赵军霞张亮亮、李祥志、陈迅 6 测试子系统开源仓third_party_benchmark孵化毕业评审测试子系统C++ benchmark测试开源 10 任翔任翔任翔任翔 7 新增AI子系统(MindSpore)开源仓 AI引擎MindSpore Lite作为OHOS内置AI引擎 10 翟智强翟智强翟智强翟智强、柴俊、张海波、孙锁东 8 新增PPG功能框架开源仓sensors_health PPG模块HDI&HDF适配 10 郭超胜武和波武和波武和波、穆凡、郭超胜 9 新增开源仓data_share_ability OpenHarmony上新建数据分享SIG代码仓data_share_ability 10 徐大庆徐大庆徐大庆徐大庆

1 0

[SIG-Charter-Proposal-HuaweiCloud_IoT] 申请新建 SIG_HuaweiCloud_IoT
by Suzhen(Max,IoT) 24 Dec '21

24 Dec '21

您好，申请新建 SIG_HuaweiCloud_IoT（申请材料见附件）。谢谢！ [cid:image002.jpg@01D7F8BC.D1251F10]

1 0