lists.openatom.io
Sign In
Sign Up
Sign In
Sign Up
Manage this list
×
Keyboard Shortcuts
Thread View
j
: Next unread message
k
: Previous unread message
j a
: Jump to all threads
j l
: Jump to MailingList overview
2024
May
April
March
February
January
2023
December
November
October
September
August
July
June
May
April
March
February
January
2022
December
November
October
September
August
July
June
May
April
March
February
January
2021
December
November
October
September
August
July
June
May
April
March
February
January
2020
December
November
October
September
List overview
Download
dev
July 2022
----- 2024 -----
May 2024
April 2024
March 2024
February 2024
January 2024
----- 2023 -----
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
----- 2022 -----
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
----- 2021 -----
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
----- 2020 -----
December 2020
November 2020
October 2020
September 2020
dev@openharmony.io
20 participants
42 discussions
Start a n
N
ew thread
[New Committer] Welcoming to become committer of OpenHarmony's wifi related repository : chengguohong
by dongjinguang
Hello chengguohong, The OpenHarmony PMC hereby offers you committer privileges to wifi project. These privileges are offered on the understanding that you'll use them reasonably and with common sense. You have made great contributions to wifi related project. Here are your contributions:
https://gitee.com/openharmony/communication_wifi_lite/pulls/2
https://gitee.com/openharmony/communication_wifi/pulls/7
https://gitee.com/openharmony/communication_wifi/pulls/8
https://gitee.com/openharmony/communication_wifi/pulls/10
https://gitee.com/openharmony/communication_wifi/pulls/13
https://gitee.com/openharmony/communication_wifi/pulls/79
https://gitee.com/openharmony/communication_bluetooth/pulls/6
https://gitee.com/openharmony/communication_bluetooth/pulls/7
https://gitee.com/openharmony/communication_bluetooth/pulls/22
All of them contributed to OpenHarmony and we’re excited to have chengguohong 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 year, 10 months
1
0
0
0
【会议纪要】OpenHarmony 架构SIG纪要20220628
by Yangna (y)
会议主题 Subject OpenHarmony 架构SIG 会议时间 Time 2022-6-28 9:30-11:30(UTC+08:00)Beijing 召集人 Convener 任革林 与会人 Attendees 万承臻;任革林;赵文华;强波;董金光 外部与会人 External Participants dev(a)openharmony.io<mailto:dev@openharmony.io>;minglong@iscas.ac.cn;kelei@iscas.ac.cn 会议议题 Agenda 议题1、新建SIG仓申请:third_party_HDiffPatch 议题2、规范部件仓名和目录申请:语言编译运行时 议题3、规范部件仓名和目录申请:公共基础类库 议题4、Misc子系统下各部件迁移至新子系统的申请 议题5、开发板仓库结构设计及命名规范整改结果汇报 议题6、sig仓孵化毕业:device_soc_amlogic,device_board_unionman,vendor_unionman 议题7、CompileRuntime SIG 建仓申请 议题8、规范部件仓名和目录申请:windowmanager 议题9、扬帆sig仓孵化毕业:device_soc_rockchip,device_board_isoftstone,vendor_isoftstone 议题10、致远sig仓孵化毕业:device_soc_allwinner,device_board_isoftstone,vendor_isoftstone 本次会议主要内容: 议题1、新建SIG仓申请:third_party_HDiffPatch 汇报人:韩锋 1、暂不同意引入该开源软件。 遗留问题: 1、端侧和云侧升级方案需考虑拉通; 2、应用升级方案与OpenHarmony系统层面的升级方案保持一致; 3、PC侧方案需考虑跨平台(支持Windows、Linux、MacOS); 4、HDiffPatch提供的差分能力应该与升级文件格式无关。 议题2、规范部件仓名和目录申请:语言编译运行时 汇报人:李勇彪 会议结论: 1、同意RuntimeCompiler子系统改名为ArkCompiler子系统; 2、同意js_runtime、ts2abc、toolchian、runtime_core(均为修改前名称)部件及其对应仓名和目录名的修改; 3、js_runtime--> ets_runtime,ts2abc-->ets_frontend。 遗留问题: 无。 议题3、规范部件仓名和目录申请:公共基础类库 汇报人:黄慧进 会议结论: 1、同意Utils子系统改名为CommonLibrary; 2、同意native、native_lite、ts_js_lang_library、memory、system_resources(均为修改前名称)部件及其对应仓名和目录名的修改; 3、native-->c_utils,native_lite-->uitls_lite,ts_js_lang_library--> ets_utils。 遗留问题: 无。 议题4、Misc子系统下各部件迁移至新子系统的申请 汇报人:鲍亚永 会议结论: 1、同意迁移Misc子系统下各部件到各个新子系统下。 遗留问题: 1、命名规范,输入法框架子系统修改为输入法子系统,保持统一; 2、锁屏管理服务部件命名同其他部件保持一致,修改为screenlock_fwk; 3、time部件缺乏体现时区的概念,例如:timezone,包含时间、时区、定时器的概念在里面。 议题5、开发板仓库结构设计及命名规范整改结果汇报 汇报人:王少锋 会议结论: 以九联厂家A311D,开发板代号unionpi_tiger为例,建议修改点如下: 1、device_soc_xxx仓 1)device_soc_xxx,其中xxx为soc厂家名称,如amloghic; 2)考虑可能有不同系列soc芯片的情况,建议增加一级区分了系列名称的目录; 3)common:soc系列相关的公共配置; 4)a311d/hardware:主要放置用户态GPU,显示、媒体HDI相关实现的内容,display、ge2d、gpu、isp、media。 2、device_board_xxx仓 1)device_board_xxx,其中xxx为开发板厂家名称,如unionman; 2)unionpi_tiger:开发板目录名称; 3)unionpi_tiger/kernel/driver:原生的linux内核驱动; 4)unionpi_tiger/kernel/logo和unionpi_tiger/bootanimation建议合并至一个资源文件目录; 5)unionpi_tiger/hardware:开发板特有的HDI用户态实现,camera,LCD显示等; 6)unionpi_tiger/bootloader:uboot启动引导相关程序。 3、vendor_xxx仓 1)vendor_xxx,其中xxx为开发板厂家名称,如unionman; 2)unionpi_tiger:建议修改为虚拟产品形态名称,不要和开发板名称重复,并补充针对具体产品的规范。 4、该规范后续根据kernel SIG整改后的策略再刷新后发布。 遗留问题: 无。 议题6、sig仓孵化毕业:device_soc_amlogic,device_board_unionman,vendor_unionman 汇报人:于敏杰 会议结论: 1、同意毕业。 遗留问题: 1、内核patch继续整改,限期七月底前按规范修改完成。 议题7、CompileRuntime SIG 建仓申请 汇报人:彭彪 会议结论: 1、当前业务目标描述不清晰,需要重新修改制定后再评审是否建仓。 遗留问题: 无。 议题8、规范部件仓名和目录申请:windowmanager 汇报人:毛江平 会议结论: 1、同意window_manager部件及其仓名和目录名的修改:仓名由windowmanager 变为window_window_manager,目录名对应变化。 遗留问题: 无。 议题9、扬帆sig仓孵化毕业:device_soc_rockchip,device_board_isoftstone,vendor_isoftstone 汇报人:庞伟 会议结论: 1、同意毕业。 遗留问题: 1、内核patch继续整改,限期七月底前按规范修改完成。 议题10、致远sig仓孵化毕业:device_soc_allwinner,device_board_isoftstone,vendor_isoftstone 汇报人:庞伟 会议结论: 1、同意毕业。 遗留问题: 1、 EULA 如何放置?如何对应具体的二进制文件? 2、 内核patch继续整改,限期七月底前按规范修改完成; 3、继续规范仓库命名,如loader目录名变为bootloader等。
1 year, 10 months
1
0
0
0
← Newer
1
2
3
4
5
Older →
Jump to page:
1
2
3
4
5
Results per page:
10
25
50
100
200