- Tc - mailweb.openeuler.org

Re: Regarding contributing in Open Euler community
by Liyongle (Fred) 19 Dec '20

19 Dec '20

Hi Sayalee, Thanks. The community infrastructure team is handling the CLA process and will provide feedback in the email thread. Regards Fred 李永乐 From: Sayalee Mankar [mailto:sayalee.mankar@click2cloud.net] Sent: Wednesday, December 16, 2020 3:47 PM To: Liyongle (Fred) <liyongle(a)huawei.com>; Huxinwei via Tc <tc(a)openeuler.org>; community(a)openeuler.org Cc: Shradha Hole <shradha.hole(a)click2cloud.net>; Shivam Methi <shivam.methi(a)click2cloud.net> Subject: RE: Regarding contributing in Open Euler community Hello Fred, Many thanks for your reply. Please find the attachment of agreement. Also, we are more interested to become community TC member, It will be really helpful if you can suggest us what will be the procedure for same. Looking forward for your reply. Thanks, Sayalee From: Liyongle (Fred) <liyongle(a)huawei.com<mailto:liyongle@huawei.com>> Sent: Wednesday, December 16, 2020 12:45 PM To: Sayalee Mankar <sayalee.mankar(a)click2cloud.net<mailto:sayalee.mankar@click2cloud.net>>; Huxinwei via Tc <tc(a)openeuler.org<mailto:tc@openeuler.org>>; community(a)openeuler.org<mailto:community@openeuler.org> Cc: Shradha Hole <shradha.hole(a)click2cloud.net<mailto:shradha.hole@click2cloud.net>> Subject: RE: Regarding contributing in Open Euler community Hi Sayalee, You are more than welcome to join openEuler community. Please follow [1] to sign CLA (sign as corporation) [2], and start selecting SIGs or creating SIGs you want to join. By the way, openEuler summit 2020 [3] will be on Dec. 25th and you are welcome to join the meeting and talk with community TC members, maintainers and other contributors face to face. [1] https://openeuler.org/en/community/contribution/ [2] https://clasign.osinfra.cn/sign/Z2l0ZWUlMkZvcGVuZXVsZXI= [3] https://openeuler.org/en/interaction/summit-list/ Fred 李永乐 From: Sayalee Mankar [mailto:sayalee.mankar@click2cloud.net] Sent: Wednesday, December 16, 2020 1:33 PM To: contact(a)openeuler.org<mailto:contact@openeuler.org> Cc: Shradha Hole <shradha.hole(a)click2cloud.net<mailto:shradha.hole@click2cloud.net>> Subject: [Contact] Regarding contributing in Open Euler community Hello Team, Hope you are doing good. I am Sayalee from Click2Cloud Inc. We are interested to register our CEO, Mr. Prashant Mishra for technical chair in community of Open Euler. It will be really grateful if you can suggest me what will be the procedure of joining the community or can connect me with right point of contact.. Looking forward to hearing from you soon. Thanks, Sayalee

2 1

sig-HA双周会议
by openEuler conference 18 Dec '20

18 Dec '20

1 0

openEuler 20.03 LTS SP1 系统诊断会议 2020-12-17 16:20~17:30
by Hufeng (Solar, Euler) 17 Dec '20

17 Dec '20

openEuler sig-release-management SIG 邀请您参加 2020-12-17 16:20 召开的ZOOM会议会议主题：openEuler 20.03 LTS SP1 系统诊断会议会议链接：https://zoom.us/j/95004019998?pwd=L0NTZXFhRStQVFJIc0RvQmNPRUQyZz09 会议纪要：https://etherpad.openeuler.org/p/openEuler-20.03-LTS-SP1-systemakut 请大家以邮件的方式反馈议题

1 1

【tc议题申报】关于在社区启动 Morphy AI/大数据平台原创项目的讨论
by Hubble_Zhu 16 Dec '20

16 Dec '20

Dear TC: 申请如下议题参与本次 tc 例会讨论/决策： 1、  关于在社区启动 Morphy AI/大数据平台原创项目的讨论。        相关材料会在会上提供 BR

2 2

sig-high-performance-network regular meeting
by openEuler conference 16 Dec '20

16 Dec '20

1 0

为什么你一定要参加 openEuler Summit 的 TC、Maintainer、SIG 组工作会议
by public openEuler 16 Dec '20

16 Dec '20

嗨，各位 openEuler 社区的开发者：很高兴能够向你们汇报 openEuler Summit 的会议进度。对于各位来说，本周最重要的事情是 TC、Maintainer和SIG 组开放工作会议的议程已经上线了。 *为什么你一定要参与 TC、Maintainer、SIG组开放工作会议？* 1. 你可以清楚的了解 openEuler 社区的运作模式 2. 你可以和 TC、Maintainer、SIG 的成员共同探讨openEuler 社区的下一个版本的计划和技术路线 3. 可以跟社区里的技术大佬进行面对面交流。 4. 更好的规划自己在社区中的成长路线 *会议时间和房间号：* TC 开放工作会议 Maintainer 开放工作会议 SIG 组开放工作会议时间 12/24 13:00-14:30 12/24 15:00-17:00 12/25 13:00-15:30 房间号悦府6和悦府7 悦府6和悦府7 大宴会厅B *TC **开放工作会议议程：* 1. 讨论 openEuler 支持 App Stream 机制 2. 申请成立智能运维 SIG 3. 讨论从 Gitee issue 整体切换到bugzilla 4. 讨论2021年 TC 合作的开展方式 5. …… *Maintainer **开放工作会议议程* 1. 开场 & 颁发 Maintainer 纪念徽章 2. openEuler 社区运作分析 3. 我在 openEuler 社区担任 Maintainer 的那些事儿 4. 自由问答 5. 总结 *参与本次 SIG 组开放工作会议的 SIG 组：* 1. sig-DDE 2. sig-UKUI 3. sig-Ha 4. sig-arrch32 5. A-Tune 6. iSulad & Container 7. sig-ai-bitdata 8. sig-security-facility 9. sig-confidential-computing 10. Compiler 11. Doc 12. Infrastructure 13. security-committee 14. sig-Compatibility-Infra 15. sig-QA 16. sig-release-management 17. Kernel 18. Virt *openEuler Summit **专属伴手礼：* [image: image.png] *openEuler **卫衣* [image: image.png] *openEuler Maintainer **纪念徽章* *欢迎通过openEuler 社区开发者专属的报名渠道报名：* https://etherpad.openeuler.org/p/openEuler-Summit-2020 openEuler Summit 官网： https://openeuler.org/zh/interaction/summit-list/

1 0

Re: Regarding contributing in Open Euler community
by Liyongle (Fred) 16 Dec '20

16 Dec '20

Hi Sayalee, You are more than welcome to join openEuler community. Please follow [1] to sign CLA (sign as corporation) [2], and start selecting SIGs or creating SIGs you want to join. By the way, openEuler summit 2020 [3] will be on Dec. 25th and you are welcome to join the meeting and talk with community TC members, maintainers and other contributors face to face. [1] https://openeuler.org/en/community/contribution/ [2] https://clasign.osinfra.cn/sign/Z2l0ZWUlMkZvcGVuZXVsZXI= [3] https://openeuler.org/en/interaction/summit-list/ Fred 李永乐 From: Sayalee Mankar [mailto:sayalee.mankar@click2cloud.net] Sent: Wednesday, December 16, 2020 1:33 PM To: contact(a)openeuler.org Cc: Shradha Hole <shradha.hole(a)click2cloud.net> Subject: [Contact] Regarding contributing in Open Euler community Hello Team, Hope you are doing good. I am Sayalee from Click2Cloud Inc. We are interested to register our CEO, Mr. Prashant Mishra for technical chair in community of Open Euler. It will be really grateful if you can suggest me what will be the procedure of joining the community or can connect me with right point of contact.. Looking forward to hearing from you soon. Thanks, Sayalee

1 0

申报议题
by xiasenlin 16 Dec '20

16 Dec '20

1．评审议题：sleuthkit oss-fuzz 堆缓冲溢出责任人：凌笙问题进展：问题2经过分析发现可能是误报，申请评审。经过gdb调试发现堆空间分配大小实际不是1字节，而是分配了attrFile.nodeSize大小字节，gdb调试打印attrFile.nodeSize值为2570。强制类型转换指针为结构体指针后，访问结构体成员type，oss-fuzz认为此时发生堆缓冲溢出，实际type成员地址仍在堆分配内存中，不存在溢出现象。 typedef struct { uint8_t flink[4]; /* node num of next node of same type */ uint8_t blink[4]; /* node num of prev node of same type */ int8_t type; /* type of this node */ uint8_t height; /* level in B-tree (0 for root, 1 for leaf) */ uint8_t num_rec[2]; /* number of records this node */ uint8_t res[2]; /* reserved */ } hfs_btree_node; 2．议题：gdm重启报错责任人：孙国帅问题分析：初步判定为gdm的bug，kill掉gdm的主进程之后，虽然gdm服务会重新启动，但是不会恢复当前的gdm界面，导致用户无法使用当前界面登录。规避方案：（1）重启后即可正常登录（2）使用Ctrl-Alt-（F2-F6）切换到其它consloe登录发件人: Hufeng (Solar, Euler) [mailto:solar.hu@huawei.com] 发送时间: 2020年12月15日 15:09 收件人: tc(a)openeuler.org; dev(a)openeuler.org; release(a)openeuler.org; qa(a)openeuler.org; sa-announce(a)openeuler.org 主题: [Dev] 12/15会议冲突取消【会议时间】 openEuler 20.03 LTS SP1 系统诊断会议 2020-12-16 16:00~17:30 12/15会议冲突取消(对大家工作造成影响深表歉意)，以下为明天会议通知，请大家以邮件方式上报议题。 openEuler sig-release-management SIG 邀请您参加 2020-12-16 16:00 召开的ZOOM会议会议主题：openEuler 20.03 LTS SP1 系统诊断会议会议链接：https://zoom.us/j/97394171115?pwd=QklPL3I1M1JaQzd5UVN2U2dYR014QT09 会议纪要：https://etherpad.openeuler.org/p/openEuler-20.03-LTS-SP1-systemakut 请大家以邮件的方式反馈议题

2 1

申报议题
by xiasenlin 16 Dec '20

16 Dec '20

3．议题：atotrace包社区无人维护，CVE无解决方案的问题，鉴于该包也已经不符合软件包引入要求，申请移除。责任人：王歌 autotrace是一个将位图转换为矢量图的工具。该包最后一次发布版本是2002年，之后就无人维护。近期收到了该包的50个安全漏洞，由于社区无人维护，这些CVE也都无解决方案。（1）移除autotrace对其他包的影响排查autotrace包的系统依赖，可以得出结论，只有fontforge包受到影响。 autotrace是fontforge的安装依赖（2）在fontforge中去除autotrace安装依赖，验证fontforge的功能 fontforge解除autotrace依赖后，其他功能都可以正常使用，但做位图转换的autotrace插件功能消失。（3）使用potrace可以代替autotrace提供的功能，为fontforge提供位图转换功能（4）epol仓不存在对autotrace的依赖（5）SP1分支引入potrace不需新增依赖关系（6）其他厂商autotrace包信息 openSUSE 代码版本：0.31.1 与openEuler的差异：源码包版本相同，缺少6个补丁 fedora (f33) 代码版本：0.31.1 与openEuler的差异：无 centOS(8.3) 代码版本：0.31.1 与openEuler的差异：无发件人: xiasenlin 发送时间: 2020年12月16日 14:22 收件人: 'Hufeng (Solar, Euler)' <solar.hu(a)huawei.com>; tc(a)openeuler.org; dev(a)openeuler.org; release(a)openeuler.org; qa(a)openeuler.org; sa-announce(a)openeuler.org 主题: 申报议题 1．评审议题：sleuthkit oss-fuzz 堆缓冲溢出责任人：凌笙问题进展：问题2经过分析发现可能是误报，申请评审。经过gdb调试发现堆空间分配大小实际不是1字节，而是分配了attrFile.nodeSize大小字节，gdb调试打印attrFile.nodeSize值为2570。强制类型转换指针为结构体指针后，访问结构体成员type，oss-fuzz认为此时发生堆缓冲溢出，实际type成员地址仍在堆分配内存中，不存在溢出现象。 typedef struct { uint8_t flink[4]; /* node num of next node of same type */ uint8_t blink[4]; /* node num of prev node of same type */ int8_t type; /* type of this node */ uint8_t height; /* level in B-tree (0 for root, 1 for leaf) */ uint8_t num_rec[2]; /* number of records this node */ uint8_t res[2]; /* reserved */ } hfs_btree_node; 2．议题：gdm重启报错责任人：孙国帅问题分析：初步判定为gdm的bug，kill掉gdm的主进程之后，虽然gdm服务会重新启动，但是不会恢复当前的gdm界面，导致用户无法使用当前界面登录。规避方案：（1）重启后即可正常登录（2）使用Ctrl-Alt-（F2-F6）切换到其它consloe登录发件人: Hufeng (Solar, Euler) [mailto:solar.hu@huawei.com] 发送时间: 2020年12月15日 15:09 收件人: tc(a)openeuler.org<mailto:tc@openeuler.org>; dev(a)openeuler.org<mailto:dev@openeuler.org>; release(a)openeuler.org<mailto:release@openeuler.org>; qa(a)openeuler.org<mailto:qa@openeuler.org>; sa-announce(a)openeuler.org<mailto:sa-announce@openeuler.org> 主题: [Dev] 12/15会议冲突取消【会议时间】 openEuler 20.03 LTS SP1 系统诊断会议 2020-12-16 16:00~17:30 12/15会议冲突取消(对大家工作造成影响深表歉意)，以下为明天会议通知，请大家以邮件方式上报议题。 openEuler sig-release-management SIG 邀请您参加 2020-12-16 16:00 召开的ZOOM会议会议主题：openEuler 20.03 LTS SP1 系统诊断会议会议链接：https://zoom.us/j/97394171115?pwd=QklPL3I1M1JaQzd5UVN2U2dYR014QT09 会议纪要：https://etherpad.openeuler.org/p/openEuler-20.03-LTS-SP1-systemakut 请大家以邮件的方式反馈议题

1 0

【Notice/通告】 openEuler 21.03 创新版本需求收集提醒，请各maintainer及时提交需求PR，多谢
by Jiangyumin (Jimmy) 15 Dec '20

15 Dec '20

各位maintainer，大家好 openEuler 21.03 创新版本需求收集计划及已反馈的需求请见如下链接，如果还有新需要进入21.03版本，请尽快提交PR到下面的仓库，多谢 https://gitee.com/openeuler/release-management/blob/master/openEuler-21.03/… Feedback feture list no fetur status sig owner 1 openEuler 21.03 support openStack<https://gitee.com/openeuler/release-management/issues/I25Y6B?from=project-i…> discussion sig-openstack @joec88<https://gitee.com/joec88> @liksh<https://gitee.com/liksh> 2 openEuler 21.03 support virtualization live migration pro<https://gitee.com/openeuler/release-management/issues/I25ZB1?from=project-i…> discussion sig-virt @alexchen<https://gitee.com/alexchen> 3 openEuler 21.03 support StratoVirt function enhancement<https://gitee.com/openeuler/release-management/issues/I25ZH0?from=project-i…> discussion sig-virt @alexchen<https://gitee.com/alexchen> 4 openEuler 21.03 support Risc-v virt live migration<https://gitee.com/openeuler/release-management/issues/I25ZF1?from=project-i…> discussion sig-virt @alexchen<https://gitee.com/alexchen> 5 openEuler 21.03 support DDE<https://gitee.com/openeuler/release-management/issues/I27TT4?from=project-i…> discussion sig-DDE @panchenbo<https://gitee.com/panchenbo> 6 openEuler 21.03 kernel update to version 5.10<https://gitee.com/openeuler/release-management/issues/I27YGU?from=project-i…> discussion sig-kernel @XieXiuQi<https://gitee.com/xiexiuqi> 7 openEuler 21.03 remove python 2 from release<https://gitee.com/openeuler/release-management/issues/I29EV9?from=project-i…> discussion sig-python-modules @yaqiangchen<https://gitee.com/yaqiangchen>

1 0