August 2021 - dev - lists.openatom.io

[SIG-Charter-Proposal-NFC]
by Zhangxiuping (NFC, Device Connectivity Dept) 30 Aug '21

30 Aug '21

1 0

Re: OpenHarmony 架构SIG，时间：2021-08-31 09:10-10:30，地点：线上会议，请您准时与会：）
by minglong 30 Aug '21

30 Aug '21

新增议题：小熊派合仓代码审核 On Aug 30, 2021 10:57，hengting (A)<hengting1(a)huawei.com> wrote：会议主题 Subject OpenHarmony 架构SIG 会议时间 Time 2021-08-31 09:30-10:30(UTC+08:00)Beijing 会议地点 Location 线上会议召集人 Convener 董金光视频会议 Video Meeting 加入会议 : Join (Host) >> Join (Internal) >> Join (External) >> 会议ID : 0215199241 与会人 Attendees 万承臻；任革林；张勇智；强波；董金光外部与会人 External Participants dev(a)openharmony.io 会议议题 Agenda 编号 No. 议题名称 Topic 议题背景介绍 Topic background introduction 时长 Duration 提案人 Proposer 汇报人 Reporter 纪要人 Recorder 议题参与人 Members 1 新增ark_js_runtime,ark_runtime_core,ark_ts2abc,third_party_miniz仓 https://gitee.com/openharmony/ark_js_runtime https://gitee.com/openharmony/ark_runtime_core https://gitee.com/openharmony/ark_ts2abc https://gitee.com/openharmony/third_party_miniz 新增方舟运行时合入社区主线 10 蒋晗蒋晗蒋晗蒋晗(jianghan2(a)huawei.com) 龚俊松(gongjunsong(a)huawei.com) 彭彪(pengbiao1(a)huawei.com) 裴家俊(peijiajun(a)hisilicon.com) 2 新增三个三方开源代码仓： third_party_libsoup:https://gitee.com/openharmony/third_party_libsoup third_party_libpsl:https://gitee.com/openharmony/third_party_libpsl third_party_gettext:https://gitee.com/openharmony/third_party_gettext L2开源媒体子系统新增流媒体播放功能，依赖三方开源软件； 10 朱明亮刘荣亮朱明亮朱明亮（zhumingliang(a)huawei.com) 刘荣亮（liurongliang(a)huawei.com) 蒋文宇（jiangwenyu1(a)huawei.com) 谭利文（tanliwen1(a)huawei.com) 3 内核架构决策内核架构决策 10 吴祚煜吴祚煜吴祚煜吴祚煜（wuzuoyu(a)huawei.com) 余长春（yuchangchun1(a)huawei.com) 董金光（dongjinguang(a)huawei.com)

1 0

OpenHarmony 架构SIG，时间：2021-08-31 09:10-10:30，地点：线上会议，请您准时与会：）
by hengting (A) 30 Aug '21

30 Aug '21

会议主题 Subject OpenHarmony 架构SIG 会议时间 Time 2021-08-31 09:30-10:30(UTC+08:00)Beijing 会议地点 Location 线上会议召集人 Convener 董金光视频会议 Video Meeting 加入会议 : Join (Host) >><http://imeeting.huawei.com/meeting/startzoom?id=febefee8674c45a5ac377781605…> Join (Internal) >><http://imeeting.huawei.com/meeting/joinzoom?id=0215199241&app=welink> Join (External) >><https://welink.zhumu.com/j/215199241> 会议ID : 0215199241 与会人 Attendees 万承臻；任革林；张勇智；强波；董金光外部与会人 External Participants dev(a)openharmony.io<mailto:dev@openharmony.io> 会议议题 Agenda 编号 No. 议题名称 Topic 议题背景介绍 Topic background introduction 时长 Duration 提案人 Proposer 汇报人 Reporter 纪要人 Recorder 议题参与人 Members 1 新增ark_js_runtime,ark_runtime_core,ark_ts2abc,third_party_miniz仓 https://gitee.com/openharmony/ark_js_runtime https://gitee.com/openharmony/ark_runtime_core https://gitee.com/openharmony/ark_ts2abc https://gitee.com/openharmony/third_party_miniz 新增方舟运行时合入社区主线 10 蒋晗蒋晗蒋晗蒋晗(jianghan2(a)huawei.com<mailto:jianghan2@huawei.com>) 龚俊松(gongjunsong(a)huawei.com<mailto:gongjunsong@huawei.com>) 彭彪(pengbiao1(a)huawei.com<mailto:pengbiao1@huawei.com>) 裴家俊(peijiajun(a)hisilicon.com<mailto:peijiajun@hisilicon.com>) 2 新增三个三方开源代码仓： third_party_libsoup:https://gitee.com/openharmony/third_party_libsoup third_party_libpsl:https://gitee.com/openharmony/third_party_libpsl third_party_gettext:https://gitee.com/openharmony/third_party_gettext L2开源媒体子系统新增流媒体播放功能，依赖三方开源软件； 10 朱明亮刘荣亮朱明亮朱明亮（zhumingliang(a)huawei.com<mailto:zhumingliang@huawei.com>）刘荣亮（liurongliang(a)huawei.com<mailto:liurongliang@huawei.com>）蒋文宇（jiangwenyu1(a)huawei.com<mailto:jiangwenyu1@huawei.com>）谭利文（tanliwen1(a)huawei.com<mailto:tanliwen1@huawei.com>） 3 内核架构决策内核架构决策 10 吴祚煜吴祚煜吴祚煜吴祚煜（wuzuoyu(a)huawei.com<mailto:wuzuoyu@huawei.com>）余长春（yuchangchun1(a)huawei.com<mailto:yuchangchun1@huawei.com>）董金光（dongjinguang(a)huawei.com<mailto:dongjinguang@huawei.com>）

1 0

鸿蒙驱动适配咨询
by Issac Renton 29 Aug '21

29 Aug '21

你好！我是一名嵌入式开发工程师。现对鸿蒙刚开始了解不多。碰到了一些比较笼统的疑问，尤其是3518平台相关，如：鸿蒙给出的例程中， 1. 默认的摄像头sensor驱动，内置了imx307、f23等型号如果因为成本等因素考量，需要更换其他型号的sensor（而且该sensor我已适配于较早版本的liteos，可运行），该如何开展？有无相关例程、流程？同样， 2. 默认使用的WIFI芯片是3881，如果因为某些因素的考量，使用非3881WIFI芯片，该如何适配？ 3. 如何优雅的（鸿蒙风格）驱动第三方传感器？如使用I2C接口的一些测距传感器祝国产越来越好！

1 0

[New Committer] Welcoming to become committer of OpenHarmony's multimedia_camera_standard repository : Muralid
by dongjinguang 28 Aug '21

28 Aug '21

Hello Muralid , The OpenHarmony PMC hereby offers you committer privileges to the multimedia_camera_standard project. These privileges are offered on the understanding that you'll use them reasonably and with common sense<https://gitee.com/openharmony/community/blob/master/zh/guidelines_role_grou…>. You have made great contributions to multimedia camera. Below are your PRs: 1. Reviewer of camera, audio & medialibrary ~300+ review comments in camera_standard, audio_standard & media_standard https://gitee.com/openharmony/multimedia_camera_standard/pulls/3 https://gitee.com/openharmony/multimedia_camera_standard/pulls/5 https://gitee.com/openharmony/multimedia_camera_standard/pulls/7 https://gitee.com/openharmony/multimedia_camera_standard/pulls/6 https://gitee.com/openharmony/multimedia_camera_standard/pulls/17 https://gitee.com/openharmony/multimedia_camera_standard/pulls/28 2. Design Contribution : - Designed audio framework & pulseaudio interfaces - Contributed to MediaLibrary design We’re excited to have Muralid join the project. If you accept, please follow your guidelines: 1. Register an DCO<https://dco.openharmony.io/sign/Z2l0ZWUlMkZPcGVuQXRvbQ==> 2. Provide your personal information as following format and sent to email: pmc(a)openharmony.io<mailto:pmc@openharmony.io> 3. OpenHarmony Repository: 4. your name: 5. gitee id url: https://www.gitee.com/xxx 6. gitee id associated email: Best Regards OpenHarmony PMC

1 0

[New Committer] Welcoming to become committer of OpenHarmony's multimedia_audio_standard repository : Anurup
by dongjinguang 28 Aug '21

28 Aug '21

Hello Anurup, The OpenHarmony PMC hereby offers you committer privileges to the multimedia_audio_standard project. These privileges are offered on the understanding that you'll use them reasonably and with common sense<https://gitee.com/openharmony/community/blob/master/zh/guidelines_role_grou…>. You have made great contributions to multimedia audio. Below are your PRs: 1. audio_standard in OpenHarmony https://gitee.com/openharmony/multimedia_audio_standard/commit/899ce4a2c0b5… https://gitee.com/openharmony/multimedia_audio_standard/commit/4fe82b86f4e6… https://gitee.com/openharmony/multimedia_audio_standard/commit/ccfb2e856b88… https://gitee.com/openharmony/multimedia_audio_standard/commit/aaba390e14dd… 2. Some bug fixes in weston+wayland opensouce https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/519 https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/522 https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/530 https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/526 We’re excited to have Anurup join the project. If you accept, please follow your guidelines: 1. Register an DCO<https://dco.openharmony.io/sign/Z2l0ZWUlMkZPcGVuQXRvbQ==> 2. Provide your personal information as following format and sent to email: pmc(a)openharmony.io<mailto:pmc@openharmony.io> 3. OpenHarmony Repository: 4. your name: 5. gitee id url: https://www.gitee.com/xxx 6. gitee id associated email: Best Regards OpenHarmony PMC

1 0

订阅测试
by 戴东东 27 Aug '21

27 Aug '21

您好！测试是否订阅成功！谢谢！

1 0

Re: openharmony的文档上应用开发到底按照哪个来进行？
by minglong 27 Aug '21

27 Aug '21

感谢提醒。今晚刷新文档。 On Aug 27, 2021 10:45，zhaiqi163@163.com<zhaiqi163(a)163.com> wrote：这个网页，https://www.openharmony.cn/pages/0f194b/下面按照这个开发准备，直接跳转到HarmonyOS的开发界面，然后在下面的页面中又说：到底应该按照哪种描述来开发Openharmony的应用？？ Openharmony的文档和工程能否同HarmonyOS完全分离？本身这两个概念就让大众比较混乱了，连文档都混乱，那大家就更不知道什么是Openharmony，什么是HarmonyOS了 zhaiqi163(a)163.com

1 0

openharmony的文档上应用开发到底按照哪个来进行？
by zhaiqi163＠163.com 27 Aug '21

27 Aug '21

这个网页，https://www.openharmony.cn/pages/0f194b/下面按照这个开发准备，直接跳转到HarmonyOS的开发界面，然后在下面的页面中又说：到底应该按照哪种描述来开发Openharmony的应用？？ Openharmony的文档和工程能否同HarmonyOS完全分离？本身这两个概念就让大众比较混乱了，连文档都混乱，那大家就更不知道什么是Openharmony，什么是HarmonyOS了 zhaiqi163(a)163.com

2 1

关于输入法的一点想法
by 962030＠qq.com 26 Aug '21

26 Aug '21

各位，因为目前的版本里没有WIFI配网的界面，所以社区里面有一个兄弟开发了一个WIFI配网的APP，详情如下： https://harmonyos.51cto.com/posts/6290 代码在这里： https://gitee.com/panda-coder/open-harmony-apps/tree/master/Wifi 因为要输入WIFI密码，所以就要做个输入法，我看做的已经相对完善了，如下图：之前PMC会议讨论过输入法的问题，我建议，把这件事在社区里推动起来，没必要等华为的兄弟开发一个类似的东西了。是不是可以考虑怎样把这样一个APP，变成所有APP可以共享的输入法。我们应该更多依赖社区的力量，用开源而不是“满足需求”的思路去解决一些特性的缺失。 962030(a)qq.com

2 1