April 2020 - Tc - mailweb.openeuler.org

[讨论]变更当前的SIG申请和repository申请流程
by Huxinwei 11 May '20

11 May '20

大家好：我想在这里发起下“关于TC管理SIG和repository申请流程”的讨论。 [背景] 当前申请新sig时需要在sig目录中创建一个新的子目录，并且在sigs.yaml中增加相应项。而申请新repo时，需要在src-openeuler.yaml, openEuler.yaml以及sigs.yaml增加相应项。由于新增时习惯性会在yaml文件最底部添加，在变更频繁时冲突非常激烈。我们注意到有些PR就是因为这个原因，反复修改来解决冲突，体验非常不好。但，我们也不能简单的对上述文件做拆分，因为gitee提供的机制只能对有限个文件的变化做监控。如果随意拆分，会导致当前社区自动化流程失灵。 [解决方案建议] 1. 保留repositories/src-openeuler.yaml, repositories/openEuler.yaml以及sig/sigs.yaml这三个文件，但是不再接纳TC团队之外发起的任何提交。 2. 将当前repositories/src-openeuler.yaml的内容按首字母拆分到repositories/src-openeuler/$initial_character/$repo_name.yaml中。首字母不区分大小写。 3. 将当前repositories/openeuler.yaml的内容按首字母拆分到repositories/openeuler/$initial_character/$repo_name.yaml中。首字母不区分大小写。 4. 将当前sig/sigs.yaml的内容，按所属SIG，拆分到sig/$sig_name/repositories.yaml中。 5. 新申请SIG时，只需要需要创建相应的SIG目录，填写OWNER，与 repositories.yaml 6. 新增repo时，需要在repositories中相应目录下创建$repo_name.yaml，并在sig/$sig_name/repositories.yaml中新增对应项。 7. 当这些PR被approve之后，TC运行脚本来整合各个分散的yaml文件，提交一个PR来统一修改前述三个yaml文件。 [遗留问题] 1. 由于SIG对自己目录中有完全修改权，所以SIG可以自行修改目录中的repositories.yaml。但是这个修改不会生效。TC在整合各个sig的yaml时，需要做额外的检查。请大家对这个方案建议发表意见。我在随后两天会整合大家意见，发出TC的机器人脚本。谢谢 Poincaré Laboratory Huawei Technologies Co.,Ltd.

6 8

申请添加一个project：oe2cloud
by myeuler 29 Apr '20

29 Apr '20

TC meeting: 申请在openEuler下建立一个新的项目oe2cloud，目的是将openEuler转化为各个公有云的虚拟机镜像。归属dev-utils的SIG组。

1 0

Open Source Promotion Plan - Summer 2020
by Quanyi Ma 29 Apr '20

29 Apr '20

Hi, "Open Source Promotion Plan - Summer 2020"[1] is a summer coding program for university students jointly organized by CAS Software Institute and openEuler community. The project aims to encourage students to take participate in the development and maintenance of open source software and promote the flourishing development of outstanding open source software community in China. The program provides "mini-projects" for the development and maintenance of open source project with the major open source communities to students of universities. Students will be able to apply for projects of their own choice. They will have an allowed to be personally mentored by a senior community maintainer(mentor) of the open source project after being selected. Depending on the difficulty and completion of the project, participants will also receive prizes and trophies for the "Open Source Promotion Plan - Summer 2020" activity. The openEuler community as an organizer will provide mini-projects and mentor. I hope to have a chance to discuss with members of the technologic committee at the next meeting. [1] https://isrc.iscas.ac.cn/summer2020 [2] https://mp.weixin.qq.com/s/ordI9o4gZrO7R4BtzFByTA --- Eli Ma <eli(a)patch.sh>

1 0

Memo//re: refreshments //: Scedule of TC routing meeting of tomorrow
by Xiehong (Cynthia) 22 Apr '20

22 Apr '20

��ˣ� DocoMart Ф��Wang Jianmin ��Houjian �, Zhujianwei �콨ΰ, Liujingang ��, He Xiaowen ��С��,Cai Haomin ��尕F, Ma Quanyi ��ȫһ, Xieqiuqi л��棬myeuler ��ΰ��hanjun ��HailiangZhang �ź��wangxun ��ѫ��shinwell ��ε, Wang Xun ��ѫ, Cynthia л�� ʱ�䣺 2020-4-22 10:00 ~12:00 ��鷽ʽ�� Voice meeting Topic1�� A new SIG named doracms initiated by doramart ---- Xiao Shen //��ۣ� 1. ��doracms-SIG ��ΪCMS-SIG��λ��ݹ��ص�SIG 2. ԭ��doracms��github�ϵ��Ŀ��Ϊ��openEuler�Լ��ɷ�ʽ�� 3. Xiao Shen ��ΪCMS-SIG��owner��ϣ��ҵ�ڸ��CMS��Ȥ��Ͷ�� Topic2�� A new SIG for security_facility---Zhujianwei //��ۣ� 1. ͬ��ר�ŵİ�ȫ��о�SIG 2. ��Ҫmaintainer��ȷ�� µ��㷨��㷨ʵ�֣��Ŀǰֻ��Ĺ��֤�㷨��ʵ�ֿ⣬��ʱͨ��PR�ٵ�TC�� 3. openSSLŲ��SIG Topic 3: A new SIG for RISC-V ---- Zhou Peng //��ۣ� 1. ͬ��RISC-V SIG��zhoupeng��ΪSIG��owner 2. RISC-V ��ڸ��޸�Ҫ�غϵ��ϣ��ܵ��֧��Ҫ��е��ֵ�maintainerЭͬ 3. Ӱ��Ƚϴ��ϸ�Ĺ��ݡ��̡��ʽ��Ҫר��ȷ��ٵ�TC�Ͼ�� Topic 4�� A new SIG for golang ---- Cai Haomin //��ۣ� ͬ�� Topic5�� A new SIG for automation �C Hu Xinwei //��ۣ� 1. ͬ�� 2. ��Ϊ��е��ϵͳ��Կ��ǿ�Դ��SIG Topic 6�� A solution has been provided, to discuss how to divide sigs reasonably. ---- He Xiaowen //�� 1. ͬ��application-SIGɾ�� 2. Programming-language SIG��ʱ��µı��С��𽥰��ȥ��go-SIG��Programming-language SIG��صĲְ��룩 3. Others-SIG��ȷ��һ�� 4. SIG��ԭ��д��һ��PR�ŵ�� Topic 7: ��Ĵ�� --- wangjianmin, houjian //��ۣ� 1. ��еı��֣��ֱ��뵽openEuler�ļ��ɲ֣�src-openeuelr��ϣ��ʱ�Ҳ��SIG�飬��ұ�SIG��󣬻��һ��ʱ��ٿ��ǲ�⣻ 2. ��İ��Ĵ��淶��´�� 3. ��е��ʱ��Ĳ֣�OBS�Ѿ��meta��ʹ��ֱ��issue��߷��ʼ��infra(a)openeuler.org ��: Xiehong (Cynthia) ��ʱ��: 2020��4��21�� 22:25 �ռ��: 'tc(a)openeuler.org' <tc(a)openeuler.org>; 'doramart(a)qq.com' <doramart(a)qq.com>; Hexiaowen (Hex, EulerOS) <hexiaowen(a)huawei.com>; caihaomin <caihaomin(a)huawei.com>; zhujianwei (C) <zhujianwei7(a)huawei.com> ��: refreshments //: Scedule of TC routing meeting of tomorrow Hi ALL Till now, tomorrow topic are here 1. A new SIG named doracms initiated by doramart ---- doramart 2. A new SIG for security_facility---Zhujianwei 3. A new SIG for RISC-V ---- zhoupeng01 4. A solution has been provided, to discuss how to divide sigs reasonably. ---- He Xiaowen 5. A new SIG for golang ---- Cai haomin 6. A new SIG for automation �C Hu Xinwei ��: Xiehong (Cynthia) ��ʱ��: 2020��4��21�� 10:22 �ռ��: tc(a)openeuler.org<mailto:tc@openeuler.org>; 'doramart(a)qq.com' <doramart(a)qq.com<mailto:doramart@qq.com>> ��: Scedule of TC routing meeting of tomorrow Hi ALL Till now, only one topic on the tomorrow meeting 1. Add a new SIG named doracms initiated by doramart Please add the topic if you need Best regards Cynthia Xie

1 0

【Meeting Notice】openEuler TC会议 Time: 2020-04-22 10:00-12:00
by Meeting Book 21 Apr '20

21 Apr '20

1 0

【Meeting Notice】openEuler TC会议 Time: 2020-04-22 10:00-12:00
by Meeting Book 21 Apr '20

21 Apr '20

1 0

refreshments //: Scedule of TC routing meeting of tomorrow
by Xiehong (Cynthia) 21 Apr '20

21 Apr '20

Hi ALL Till now, tomorrow topic are here 1. A new SIG named doracms initiated by doramart ---- doramart 2. A new SIG for security_facility---Zhujianwei 3. A new SIG for RISC-V ---- zhoupeng01 4. A solution has been provided, to discuss how to divide sigs reasonably. ---- He Xiaowen 5. A new SIG for golang ---- Cai haomin 6. A new SIG for automation �C Hu Xinwei ��: Xiehong (Cynthia) ��ʱ��: 2020��4��21�� 10:22 �ռ��: tc(a)openeuler.org; 'doramart(a)qq.com' <doramart(a)qq.com> ��: Scedule of TC routing meeting of tomorrow Hi ALL Till now, only one topic on the tomorrow meeting 1. Add a new SIG named doracms initiated by doramart Please add the topic if you need Best regards Cynthia Xie

1 0

关于申请工具代码开源到社区的申请，谢谢！
by Yangshaohong 21 Apr '20

21 Apr '20

Hi, openEuler-TC：我们这边有一个问答界面的框架代码，能同时支持移动端和PC端的视图，可帮助指导开发者快速开发属于自己的问答服务。目前已经有成功的应用，希望能够进行开源。项目名称： iChat 申请加入SIG分组： dev-utils 谢谢！

2 1

新SIG SIG-security facility 提案
by zhujianwei (C) 21 Apr '20

21 Apr '20

Hi，TC members We wanna set up Security Technology sig. Here is the PR https://gitee.com/openeuler/community/pulls/330

1 0

[tc] 新SIG SIG-Golang 提案
by caihaomin 21 Apr '20

21 Apr '20

Hi~ tc members We wanna set up golang sig~~~ Here is the pr https://gitee.com/openeuler/community/pulls/398 BR~ Haomin

2 1

【Meeting Notice】openEuler TC会议 Time: 2020-04-22 10:00-12:00
by Meeting Book 21 Apr '20

21 Apr '20

2 1

Scedule of TC routing meeting of tomorrow
by Xiehong (Cynthia) 21 Apr '20

21 Apr '20

Hi ALL Till now, only one topic on the tomorrow meeting 1. Add a new SIG named doracms initiated by doramart Please add the topic if you need Best regards Cynthia Xie

1 0

[新SIG提案]https://gitee.com/doramart/community
by DoraCMS 20 Apr '20

20 Apr '20

[新SIG提案]https://gitee.com/doramart/community

3 3

Re: [PATCH 00/22] Add support for Hygon Dhyana Family 18h processor
by Hanjun Guo 18 Apr '20

18 Apr '20

Hi Pu Wen, On 2020/3/31 11:20, Pu Wen wrote: > As a new x86 CPU Vendor, Chengdu Haiguang IC Design Co., Ltd (Hygon) > is a Joint Venture between AMD and Haiguang Information Technology Co., > Ltd., and aims at providing high performance x86 processor for China > server market. > > The first generation Hygon's processor(Dhyana) originates from AMD > technology and shares most of the architecture with AMD's family 17h, > but with different CPU Vendor ID("HygonGenuine")/PCIE Device Vendor ID > (0x1D94)/Family series number (Family 18h). > > To enable the support of Linux kernel to Hygon's CPU, we added a new > vendor type (X86_VENDOR_HYGON, with value of 9) in arch/x86/include/ > asm/processor.h, and shared most of kernel support codes with AMD > family 17h. > > As Hygon will negotiate with AMD to make sure that only Hygon will > use family 18h, so try to minimize code modification and share most > codes with AMD under this consideration. > > This patch series have been applied and tested successfully on Hygon > Dhyana SoC silicon. Also tested on AMD EPYC (Family 17h) processor, > it works fine and makes no harm to the existing codes. > > This patch series are created for the current branch openEuler-1.0-LTS. Thanks a lot for your patchset, I took a detail look at this patchset, and it looks good to me, I'm pretty happy that this patchset was backported from mainline kernel and you are the maintainer. For this patchset, Reviewed-by: Hanjun Guo <guohanjun(a)huawei.com> BTW, do we need updates for compiler, glibc and other usersapce package to recognize Hygon processor or performance optimization? if yes, you can send those patches to openEuler as well. And I kindly invite you to create a new SIG for Hygon processor in openEuler [1]. Thanks Hanjun [1]: https://openeuler.org/zh/sig.html > > References: > [1] Linux kernel patches for Hygon Dhyana, merged in 4.20: > https://git.kernel.org/tip/c9661c1e80b609cd038db7c908e061f0535804ef > [2] MSR and CPUID definition: > https://www.amd.com/system/files/TechDocs/54945_PPR_Family_17h_Models_00h-0… > > Pu Wen (22): > x86/cpu: Create Hygon Dhyana architecture support file > x86/cpu: Get cache info and setup cache cpumap for Hygon Dhyana > x86/cpu/mtrr: Support TOP_MEM2 and get MTRR number > x86/smpboot: Do not use BSP INIT delay and MWAIT to idle on Dhyana > x86/events: Add Hygon Dhyana support to PMU infrastructure > x86/alternative: Init ideal_nops for Hygon Dhyana > x86/amd_nb: Check vendor in AMD-only functions > x86/pci, x86/amd_nb: Add Hygon Dhyana support to PCI and northbridge > x86/apic: Add Hygon Dhyana support > x86/bugs: Add Hygon Dhyana to the respective mitigation machinery > x86/mce: Add Hygon Dhyana support to the MCA infrastructure > x86/kvm: Add Hygon Dhyana support to KVM > x86/xen: Add Hygon Dhyana support to Xen > ACPI: Add Hygon Dhyana support > cpufreq: Add Hygon Dhyana support > EDAC, amd64: Add Hygon Dhyana support > tools/cpupower: Add Hygon Dhyana support > hwmon: (k10temp) Add Hygon Dhyana support > x86/CPU/hygon: Fix phys_proc_id calculation logic for multi-die > processors > i2c-piix4: Add Hygon Dhyana SMBus support > x86/amd_nb: Make hygon_nb_misc_ids static > NTB: Add Hygon Device ID > > Documentation/i2c/busses/i2c-piix4 | 2 + > MAINTAINERS | 6 + > arch/x86/Kconfig.cpu | 14 + > arch/x86/events/amd/core.c | 4 + > arch/x86/events/amd/uncore.c | 20 +- > arch/x86/events/core.c | 4 + > arch/x86/include/asm/amd_nb.h | 3 + > arch/x86/include/asm/cacheinfo.h | 1 + > arch/x86/include/asm/kvm_emulate.h | 4 + > arch/x86/include/asm/mce.h | 2 + > arch/x86/include/asm/processor.h | 3 +- > arch/x86/include/asm/virtext.h | 5 +- > arch/x86/kernel/alternative.c | 4 + > arch/x86/kernel/amd_nb.c | 49 ++- > arch/x86/kernel/apic/apic.c | 7 + > arch/x86/kernel/apic/probe_32.c | 1 + > arch/x86/kernel/cpu/Makefile | 1 + > arch/x86/kernel/cpu/bugs.c | 4 +- > arch/x86/kernel/cpu/cacheinfo.c | 31 +- > arch/x86/kernel/cpu/common.c | 4 + > arch/x86/kernel/cpu/cpu.h | 1 + > arch/x86/kernel/cpu/hygon.c | 413 ++++++++++++++++++ > arch/x86/kernel/cpu/mce/core.c | 20 +- > arch/x86/kernel/cpu/mce/severity.c | 3 +- > arch/x86/kernel/cpu/mtrr/cleanup.c | 3 +- > arch/x86/kernel/cpu/mtrr/mtrr.c | 2 +- > arch/x86/kernel/cpu/perfctr-watchdog.c | 2 + > arch/x86/kernel/smpboot.c | 4 +- > arch/x86/kvm/emulate.c | 11 +- > arch/x86/pci/amd_bus.c | 6 +- > arch/x86/xen/pmu.c | 12 +- > drivers/acpi/acpi_pad.c | 1 + > drivers/acpi/processor_idle.c | 1 + > drivers/cpufreq/acpi-cpufreq.c | 5 + > drivers/cpufreq/amd_freq_sensitivity.c | 9 +- > drivers/edac/amd64_edac.c | 10 +- > drivers/edac/mce_amd.c | 4 +- > drivers/hwmon/k10temp.c | 3 +- > drivers/i2c/busses/Kconfig | 1 + > drivers/i2c/busses/i2c-piix4.c | 15 +- > drivers/ntb/hw/amd/ntb_hw_amd.c | 1 + > include/linux/pci_ids.h | 2 + > tools/power/cpupower/utils/cpufreq-info.c | 6 +- > tools/power/cpupower/utils/helpers/amd.c | 4 +- > tools/power/cpupower/utils/helpers/cpuid.c | 8 +- > tools/power/cpupower/utils/helpers/helpers.h | 2 +- > tools/power/cpupower/utils/helpers/misc.c | 2 +- > .../utils/idle_monitor/mperf_monitor.c | 3 +- > 48 files changed, 668 insertions(+), 55 deletions(-) > create mode 100644 arch/x86/kernel/cpu/hygon.c >

3 3

openEuler 20200415 TC纪要//Re: 【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00
by 瓜-007 17 Apr '20

17 Apr '20

openEuler 20200415 TC纪要   议题一、ROS sig 申请 1、同意申请，但openEuler本身闭源的软件治理还没有梳理清楚，建议先不包括闭源内容。议题二、SDS sig 申请 1、成立分布式存储sig是有必要的，但是当前maintainer未明确，待分布式存储 maintainer 待定后，再进行申请。 2、当前适配的ceph-depoly/ceph-ansible 等工具完成适配后，直接提交PR申请，暂时纳入storage-sig 组进行管理。议题三、Compatible-sig 申请 1、同意在社区成立兼容性sig 组申请。 2、同意在sig组下增加服务器兼容性(OE cert)、并提供相关介绍材料及文档。 3、兼容性清单需要单独在社区呈现。议题四、 1. 软件包在source-openEuler 发布按照现有sig维度发布，网络类软件包归属network sig，系统运维类软件包归属dev-utils sig 2. openEuler上创建一个eBPF-xdp 项目（名称暂定），用于一些创新项目、不成熟软件包的开发、维护工作。遗留问题：原PR需要刷新-luzhihao 议题五：现有 SIG 运作review 1、 需要明确基于一致性检查识别200多软件包的重新归属问题，以及others里面的包重新梳理 2、 不同sig组的重新定位，比如DB和storage 3、 后续例会要例行review 各sig的运作情况遗留问题：梳理清单以及分工-huxinwei 议题六：rpm package命名讨论 1、 先保持命名现状，避免影响升级等问题。后续软件包版本命名一致性规则由xiongwei制定，评审后发布。议题七：Remove PRM包规则 1、建议在LTS版本周期内不能直接删除包，下一个版本要删除的话也要在repo保留。遗留问题：梳理增包，删包流程并发布-huxinwei ---Original--- From: "Meeting Book via Tc"<tc(a)openeuler.org> Date: Wed, Apr 15, 2020 09:21 AM To: "tc"<tc(a)openeuler.org>; Subject: [Tc] 【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00 Topic openEuler TC meeting Time 2020-04-15 10:00-12:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 929 074 130 76   Convener 王勋   Agenda 1. Review on existing SIG work(TC Members) 2. Review the suffix of rpm package (xiongwei) 3.SDS sig （dukaitian） 4.Discuss the package remove policy(TC Members) 5.compatible sig（dukaitian）   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

5 8

【Meeting Notice】openEuler TC会议 Time: 2020-04-22 10:00-12:00
by Meeting Book 16 Apr '20

16 Apr '20

1 0

[ 新SIG提案 ] 申请建立 ROS SIG
by Wei Wu 15 Apr '20

15 Apr '20

Hi openEuler技术委员会，现申请建立 ROS SIG，申请的链接是： https://gitee.com/openeuler/community/pulls/358 ROS是在机器人领域广泛使用的中间件，通过增加对ROS的支持可以让openEuler在机器人领域得到更多的应用。 -- 吴伟中国科学院软件研究所智能软件研究中心 PLCT实验室

4 4

【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00
by Meeting Book 15 Apr '20

15 Apr '20

1 0

【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00
by Meeting Book 15 Apr '20

15 Apr '20

1 0

新SIG提案
by 周鹏 14 Apr '20

14 Apr '20

Hi all, 新兴趣组sig-RISC-V提案，编译构建openEuler兼容RISC-V的版本 PR: https://gitee.com/openeuler/community/pulls/363 Thanks, Best, -- Zhou Peng

1 0

[design summit][governance]Requirements collection for community governance team
by Fred Li 14 Apr '20

14 Apr '20

Hi all, 大家好！openEuler Virtual Summit[1]将于4月17日召开，其中openEuler Community Governance小组将在4月18日（北京时间）9点到10点开会讨论下个阶段的工作任务及优先级。我们这个团队主要为社区提供如下服务： - 组织运作流程设计，比如技术委员会、SIG、打包小组、安全委员会等之间如何协调好。 - 版本开发流程 - 社区价值观（code of conduct) - 其他所有没有团队负责的问题如果您有任何需求或者疑问，请在etherpad[2] 或者 issues[3] 写下来，或者直接回复该邮件。 The team community governance will have the design summit meeting at 9:00 on April 18th [1]. I am glad to collect your requirements to us and please put it in etherpad[2], issues[3], or just reply this email. [1] https://openeuler.org/zh/summit/2020-virtual-summit.html [2] http://etherpad.openeuler.org/p/openeuler-virtual-summit-2020-community-gov… [3] https://gitee.com/openeuler/community/issues -- Regards Fred Li (李永乐)

1 0

Tc meeting topic//Re: 【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00
by 瓜-007 14 Apr '20

14 Apr '20

1. Review on existing SIG work(TC Members) 2. Review the suffix of rpm package (xiongwei) 3.SDS sig  （dukaitian） 4.Discuss the package remove policy(TC Members) ---Original--- From: "Meeting Book via Tc"<tc(a)openeuler.org> Date: Mon, Apr 13, 2020 14:25 PM To: "tc"<tc(a)openeuler.org>; Subject: [Tc] 【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00 Topic openEuler TC meeting Time 2020-04-15 10:00-12:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 929 074 130 76   Convener 王勋   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

3 2

申请ebpf-xdp sig
by newlife_lala＠163.com 14 Apr '20

14 Apr '20

2 1

关于申请成立sig-compatible SIG诉求，望审核批准
by Dukaitian (Dukaitian, Intelligent Computing R&D) 14 Apr '20

14 Apr '20

hi,openEuler TC: 目前我在做操作系统与硬件兼容性及与应用软件兼容性相关工作，我提议在openEuler下建一个sig组，主要用来完善openEuler 硬件/软件兼容性清单及相关支撑工具项目。 SIG名称 sig-compatible SIG组工作目标和范围 1、与硬件服务器、主板兼容性，成立相关兼容性测试项目，进行操作系统与服务器(驱动、bios、bmc等)兼容性的相关方面探索活动 2、操作系统与应用程序兼容性清单范围识别及版本配套审查。 3、识别POSIX/lsb等组织对于兼容性的定义及规范性满足度审查。项目名字 - oecert -待补充组织会议公开的会议时间：北京时间，双周五下午，2点~3点会议可通过现场或者远程视频进行，会提前提醒通知会议，如遇时间冲突，可根据实际情况调整。成员 Maintainer列表 jimmy_hero walkingwalk Committer列表 lutianxiong air9 eric14chan 项目清单: 服务器兼容性检查工具服务器与操作系统兼容性清单服务器与应用软件兼容性清单项目名称： - oscert repository地址：

1 0

【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00
by Meeting Book 14 Apr '20

14 Apr '20

1 0

Re: [Infra] 树莓派SIG-CI咨询
by Huxinwei 13 Apr '20

13 Apr '20

这个问题我明白了，不过当前应该是没有现成的CI流程支持。我理解这里是需要定制新的流程。是不是可以申请个VM来做这个过程的自动化？我会拉相关的人也讨论下;) Regards Xinwei From: Jianmin Wang [mailto:jianmin@iscas.ac.cn] Sent: Monday, April 13, 2020 10:20 AM To: Huxinwei <huxinwei(a)huawei.com> Cc: infra(a)openeuler.org; yafen(a)iscas.ac.cn; dongjian (D) <dongjian13(a)huawei.com> Subject: Re: [Infra] 树莓派SIG-CI咨询 Hi, Xinwei, 嗯，这个构建方式我理解是针对 RPM 包的构建。不过，树莓派这个其实是构建一个镜像版本（img）？而不是一个单独的 rpm 包。目前两个仓库分别是用来构建内核 img，和构建生成树莓派刷机镜像的脚本。构建生成树莓派刷机镜像的脚本会使用内核 img + 上游 firmeware 仓库 + openEuler 软件源仓库的包，来构建生成最终可以刷写在 sd 卡启动的树莓派镜像。不知道构建版本这块有没有通用的 CI 流程？ ——王建民 On 9 Apr 2020, at 3:55 PM, Huxinwei via Infra <infra(a)openeuler.org<mailto:infra@openeuler.org>> wrote: 我咨询了下相关同事，回复如下。他也在抄送中，有进一步问题可以邮件咨询。您好：当前openEuler社区的src-openeuler下的仓库会触发CI构建，openeuler下的仓库存放源码，均不会触发CI构建。如果需要提交代码之后自动构建、测试，可以在src-openeuler下建立同名仓库。流程如下： 1. 修改https://gitee.com/openeuler/community/blob/master/repository/src-openeule…<https://gitee.com/openeuler/community/blob/master/repository/src-openeuler.…>中新建仓库。例如新增raspberrypi仓库： - name: raspberrypi description: "" protected_branches: - master type: public 2. 提交pr，待合入之后，gitee会自动触发在src-openeuler下新建raspberrypi仓库。 3. 将源码和spec文件提交到raspberrypi仓库，则会自动触发构建。并且在http://117.78.1.88/project/show/openEuler:Mainline下会有该仓库，可以下载到该软件包编译生成的二进制包<http://117.78.1.88/project/show/openEuler:Mainline%E4%B8%8B%E4%BC%9A%E6%9C%…>。 From: 方亚芬 via Infra [mailto:infra@openeuler.org] Sent: Wednesday, April 8, 2020 10:48 PM To: infra(a)openeuler.org<mailto:infra@openeuler.org> Subject: [Infra] 树莓派SIG-CI咨询 openEuler基础设施团队的老师，您好。我是中国科学院软件研究所智能软件研究中心的方亚芬，目前参与软件所与华为在openEuler方面的合作，负责openEuler向树莓派的移植部分工作。我们在openEuler社区申请了sig-RaspberryPi，同时在申请到的两个repo（openeuler/raspberrypi，openeuler/raspberrypi-kernel）上传了代码。现在想咨询一下CI组，如何在openEuler社区建立CI，提交代码后自动构建镜像并测试。希望借鉴一下openEuler社区的经验。谢谢。 ________________________________ 祝工作顺利，生活愉快。 ------------------------------------------ 方亚芬中国科学院软件研究所智能软件研究中心邮箱：yafen(a)iscas.ac.cn<mailto:jiran@iscas.ac.cn> 地址：北京市海淀区中关村南四街4号5楼 _______________________________________________ Infra mailing list -- infra(a)openeuler.org<mailto:infra@openeuler.org> To unsubscribe send an email to infra-leave(a)openeuler.org<mailto:infra-leave@openeuler.org>

2 1

Tc meeting topic//Re: 【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00
by 瓜-007 13 Apr '20

13 Apr '20

1. Review on existing SIG work(TC Members) 2. Review the suffix of rpm package (xiongwei) 3.SDS sig  （dukaitian） add more... ---Original--- From: "Meeting Book via Tc"<tc(a)openeuler.org> Date: Mon, Apr 13, 2020 14:25 PM To: "tc"<tc(a)openeuler.org>; Subject: [Tc] 【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00 Topic openEuler TC meeting Time 2020-04-15 10:00-12:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 929 074 130 76   Convener 王勋   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

2 1

[summit]openEuler Virtual Summit 2020 will be held on Apr. 17th and 18th
by Fred Li 13 Apr '20

13 Apr '20

Hi all, I am exited to announce that openEuler Virtual Summit is coming! Due to COVID-19, we have to hold the first summit virtually, and I believe this is good to all the members' health. Please stay healthy and strong. Please visit https://openeuler.org/zh/summit/2020-virtual-summit.html (Chinese) or https://openeuler.org/en/summit/2020-virtual-summit.html (English) for details. As you can find on the page, there are several pases: 1. From now on to April 9th, it is call for speakers. To emphasize, this is only for Design summit, and please developers to start planning your design summit. 2. From Apr. 10th to 15th, it is open for registration. 3. The summit will be on Apr. 17th and 18th. There will be 2 parts. The first one is summit, and the second one is design summit. On Design summit, the contributors will have a virtual face to face meeting to discuss what we will develop for next release, which is openEuler 20.09 here. openEuler SIGs maintainers, please start to plan the design summit for your SIG with your team. Please note that you will have 2 hours for the meeting. Once confirmed, please send the following information to marketing(a)openeuler.org. Make sure you have subscribed [1]. - group name (SIG name): - chair: - BIO of the chair: - Brief introduction to the meeting: [1] https://mailweb.openeuler.org/postorius/lists/marketing@openeuler.org/ -- Regards Fred Li (李永乐)

8 13

Tc meeting topic//Re: 【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00
by 瓜-007 13 Apr '20

13 Apr '20

1. Review on existing SIG work(TC Members) 2. Review the suffix of rpm package (xiongwei) 3.SDS sig  （dukaitian） add more... ---Original--- From: "Meeting Book via Tc"<tc(a)openeuler.org> Date: Mon, Apr 13, 2020 14:25 PM To: "tc"<tc(a)openeuler.org>; Subject: [Tc] 【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00 Topic openEuler TC meeting Time 2020-04-15 10:00-12:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 929 074 130 76   Convener 王勋   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

1 0

【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00
by 瓜-007 13 Apr '20

13 Apr '20

Topic openEuler TC meeting Time 2020-04-15 10:00-12:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 929 074 130 76   Convener 王勋   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载Zoom客户端入会，并升级Zoom最新版本。 Please click the conference link and download the Zoom to join the conference, and upgrade to the latest version of Zoom.

1 0

【Meeting Notice】openEuler TC meeting Time: 2020-04-15 10:00-12:00
by Meeting Book 13 Apr '20

13 Apr '20

1 0

openEuler峰会议题-RaspberryPi
by 方亚芬 11 Apr '20

11 Apr '20

老师，您好。以下是 RaspberryPi SIG 组参与的议题。烦请查收，谢谢。- 组名：树莓派 - 主持人：方亚芬 - 主持人简介：树莓派 SIG 组负责人 - 会议议程简介：本次会议主要介绍如下内容： 1、RaspberryPi SIG 组的背景介绍 2、RaspberryPi SIG 组的当前工作进展包括 openEuler 移植到树莓派的方法、当前存在问题及解决方案 3、后续发展规划 - group name (SIG name): RaspberryPi - chair: YaFen Fang - BIO of the chair: RaspberryPI SIG maintainer. - Brief introduction to the meeting: 1. Background of RaspberryPi SIG group. 2. Current progress of RaspberryPi SIG Include how to migrate openEuler to Raspberry Pi, and how to tackle current problems. 3. Future plan 祝工作顺利，生活愉快。 ------------------------------------------ 方亚芬中国科学院软件研究所智能软件研究中心邮箱：yafen(a)iscas.ac.cn 地址：北京市海淀区中关村南四街4号5楼

2 1

关于优化社区文档的阅读体验，欢迎您的反馈/Optimized the reading experience of document in the community document.Your feedback is welcome
by Junqi?Xie 10 Apr '20

10 Apr '20

关于优化社区文档的阅读体验，欢迎您的反馈： https://gitee.com/openeuler/website/issues/I1E208?from=project-issue issue内容如下：关于文档阅读体验，有如下issue反馈： 1、https://gitee.com/openeuler/docs/issues/I1CTZ8?from=project-issue 2、https://gitee.com/openeuler/docs/issues/I1CPWY?from=project-issue 3、https://gitee.com/openeuler/docs/issues/I1CPXV?from=project-issue 主要问题点在于： 1、目录结构不易展开 2、文档内容不连续，层级太多且无法顺畅翻页阅读。每次都需要在左侧导航切换希望提供pdf、single page、multi page不同阅读体验 sigle page：一个页面显示一个章节的所有内容，且能够提供页内的索引、目录或者浮动目录 multi page：一个页面内显示一个手册的所有内容。针对这些问题，请大家体验下mindspore资料阅读方式，如果大家认可该方式，openEuler社区文档就按照该框架优化资料阅读内容： https://www.mindspore.cn/tutorial/zh-CN/master/index.html 您是否认可mindspore的阅读体验？或者有更好的建议参考? 【English】 The following issues have been reported regarding document reading experience: 1.https://gitee.com/openeuler/docs/issues/I1CTZ8?from=project-issue 2.https://gitee.com/openeuler/docs/issues/I1CPWY?from=project-issue 3.https://gitee.com/openeuler/docs/issues/I1CPXV?from=project-issue The main problems are as follows: 1.The directory structure is difficult to expand. 2.The document content is not continuous. There are too many layers and pages cannot be turned smoothly. You need to switch between the navigation tree on the left each time. Different reading experience for PDF, single page, and multi page. sigle page: All contents of a chapter are displayed on a page. In addition, indexes, directories, or floating directories can be provided on the page. multi page: displays all contents of a manual on a page. To solve these problems, please experience the MindSpore documentation reading mode. If you agree with this mode or have made improvements based on this mode, the documentation of the OpenEuler community will be optimized based on this mode. **https://www.mindspore.cn/tutorial/zh-CN/master/index.html ** Do you recognize mindspore's reading experience? Or do you have any better suggestions?

1 0

新增repository提案
by wang.jing 08 Apr '20

08 Apr '20

技术委员会：          您们好           我司是普华基础软件股份有限公司，           提交申请[新增repository提案]，项目名称为mate-desktop           PR链接地址：https://gitee.com/openeuler/community/pulls/338

2 1

【Meeting Notice】openEuler TC meeting Time: 2020-04-08 10:00-12:00
by Meeting Book 08 Apr '20

08 Apr '20

3 7

关于申请成立分布式存储sig的申请
by Dukaitian (Dukaitian, Intelligent Computing R&D) 08 Apr '20

08 Apr '20

Hi,openEuler-TC: 目前我在做ceph相关项目验证工作，发现有些分布式存储开源软件指定了支持发行版信息，未在发行版清单的内容无法使用部署工具来部署ceph，建议后续成立分布式存储sig，提升对分布式存储部署易用性及分布式存储组合方案探索。 SIG名称 sig-distributed-storage SIG组工作目标和范围分布式存储一般采用分布式的系统结构，利用多个服务器节点实现存储负荷分担，它大大提高了系统的可靠性、可用性，避免单点故障导致生产系统不可用，还支持存储容量动态扩容，支撑业务场景对海量数据的存储诉求，当前分布式存储有多种实现技术，如Ceph、Glusterfs等，希望在社区引入分布式sig，主要对如下功能进行探索： 1、针对ceph-deploy/ceph-ansible 等相关部署特性修订，支持在多个Linux开发版本中使用及适配。 2、开展DPDK、SPDK 适配工作。组织会议公开的会议时间：北京时间，双周四下午，2点~3点会议可通过现场或者远程视频进行，会提前提醒通知会议，如遇时间冲突，可根据实际情况调整。成员 Maintainer列表 Committer列表项目清单: 项目名称：ceph/glusterfs repository地址： https://github.com/ceph https://github.com/gluster/glusterfs

2 1

[新sig提案]申请成立openEuler包管理委员会
by 杨丽 08 Apr '20

08 Apr '20

hi all This time, we specially applied to TC for establishing the "Package-Committee" on 8 April Meeting. The responsibilities of the Package-Committee are as follows: [1]. Release and maintain the packaging specifications, packaging principles and dependency specifications of the community. [2]. Implement the package introduction and exit mechanism of the TC, and preview the application of releasing the software package in community. [3]. Coordinate the division of software, and dependency conflict [4]. Work with the release manager and sig-QA team to support the release process of the community release [5]. Establish and maintain the Package Management TOOL solution to support automation and traceability of package management PR application link : https://gitee.com/openeuler/community/pulls/132 Thank you for your opinions. | | 杨丽软件工程师 | | 华为技术有限公司 rainbow1981(a)163.com | 签名由网易邮箱大师定制

4 5

[openEuler 20.09]How to release Desktop Environment
by 风 08 Apr '20

08 Apr '20

[1]openEuler iso contains  Desktop Environment(gnome,kde or others)    redhat desktop environment is gnome,but centos 8.1 don't contain gnome package [2]openEuler iso contains Customed Destop Environment(ukui,mate or others) [3]openEuler iso doesn't contain desktop,Desktop Environment release in EPOL repo（gnome,kde,ukui，mate or others） I recommend solution 2

3 2

议题申报
by zhujianwei (C) 07 Apr '20

07 Apr '20

申请sig-security-facility兴趣组https://gitee.com/openeuler/community/pulls/330#<https://gitee.com/openeuler/community/pulls/330>

1 0

Invitation: Re: topic update // Re: 【Meeting Notice】openEuler TC meeting Time: 2020-04-08 10:00-12:00
by Xie XiuQi 07 Apr '20

07 Apr '20

Xie XiuQi <xiexiuqi(a)huawei.com> has invited you to [Tc] Re: topic update // Re: 【Meeting Notice】openEuler TC meeting Time: 2020-04-08 10:00-12:00

2 1

Invitation: Re: topic update // Re: 【Meeting Notice】openEuler TC meeting Time: 2020-04-08 10:00-12:00
by Xiexiuqi 07 Apr '20

07 Apr '20

1. Review on ebpf-xdp sig: https://gitee.com/openeuler/community/pulls/292 (Zheng Xian) 2. Review on HA sig: https://gitee.com/openeuler/community/pulls/311 (Hou Jie) 3. Review on Kubernetes sig: https://gitee.com/openeuler/community/pulls/312 (FeynmanZhou) 4. Review on existing SIG work (TC Members) 5. Review the suffix of rpm package. (xiongwei) 目前我们的rpm的后缀是oe1，比如GConf2-3.2.6-24.oe1.x86_64.rpm 这个和我们定的20.03 LTS没有办法对应。我们需要讨论一下这个是继续保持，这样，还是在SP1的时候修正掉 6. Review on mpam sig. (PR need update) (xiexiuqi, wangshaobo) Join Conference Join (External) >> <https://welink-meeting.zoom.us/j/582485837><https://welink-meeting.zoom.us/j/582485837> Meeting ID 582 485 837 On 2020/3/30 17:10, Xie XiuQi via Tc wrote: 1. Review on ebpf-xdp sig: https://gitee.com/openeuler/community/pulls/292 (Zheng Xian) 2. Review on HA sig: https://gitee.com/openeuler/community/pulls/311 (Hou Jie) 3. Review on Kubernetes sig: https://gitee.com/openeuler/community/pulls/312 (FeynmanZhou) 4. Review on existing SIG work (TC Members) On 2020/3/30 10:41, Xie XiuQi via Tc wrote: 1. Add ebpf-xdp sig: https://gitee.com/openeuler/community/pulls/292 (zhengxian) 2. Add ha sig: https://gitee.com/openeuler/community/pulls/311 (侯健) 3. SIG work review （tc members) On 2020/3/25 14:27, Meeting Book via Tc wrote: Topic openEuler TC meeting Time 2020-04-08 10:00-12:00((UTC+08:00)Beijing) Join Conference Join (External) >> <https://welink-meeting.zoom.us/j/582485837><https://welink-meeting.zoom.us/j/582485837> Meeting ID 582 485 837 Convener 谢秀奇 Tips: Dial the access number to join conference <http://app.huawei.com/eshare/voiceMeetings><http://app.huawei.com/eshare/voiceMeetings> 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 请点击会议链接按照提示下载ZOOM客户端入会。 Please click the conference link and download the ZOOM to join the conference. Huawei and all its affiliates respect your privacy and are committed to protecting it. When inviting you to join a video meeting, we will collect and use your personal information, including your name, device type, IP address, network type, microphone, speaker, camera, joining time, and leaving time. For more information about Huawei’s privacy policy, visit https://www.huawei.com/en/privacy-policy _______________________________________________ Tc mailing list -- tc(a)openeuler.org<mailto:tc@openeuler.org> To unsubscribe send an email to tc-leave(a)openeuler.org<mailto:tc-leave@openeuler.org> _______________________________________________ Tc mailing list -- tc(a)openeuler.org<mailto:tc@openeuler.org> To unsubscribe send an email to tc-leave(a)openeuler.org<mailto:tc-leave@openeuler.org> _______________________________________________ Tc mailing list -- tc(a)openeuler.org<mailto:tc@openeuler.org> To unsubscribe send an email to tc-leave(a)openeuler.org<mailto:tc-leave@openeuler.org> _______________________________________________ Tc mailing list -- tc(a)openeuler.org<mailto:tc@openeuler.org> To unsubscribe send an email to tc-leave(a)openeuler.org<mailto:tc-leave@openeuler.org>

2 1

TC议题申请：Application to create ReleaseManager SIG
by Maliang (Marlon, IT) 07 Apr '20

07 Apr '20

序号时间段议题类别议题名称决策建议/议题背景时长 min 提案人汇报人汇报地点纪要人相关与会人 1 　决策类 Application to create ReleaseManager SIG ReleaseManager will plan the release schedule of the openEuler and track the development status (updates or feature updates) during the development/test cycle. 10 MarlonMa B/R Thanks 马亮

1 0

Re: [Dev] Re: Chinese Fedora packager is here
by Fred Li 03 Apr '20

03 Apr '20

+ tc(a)openeuler.org and community(a)openeuler.org In case some members have not subscribed to dev(a)openeuler.org. On Fri, Apr 3, 2020 at 8:28 PM Fred Li <yongle.li(a)gmail.com> wrote: > > I am not the right person to reply this, as UKUI team uses the same > email list and let's wait for them to reply. > > On Fri, Apr 3, 2020 at 7:06 PM myeuler <myeuler(a)163.com> wrote: > > > > I think we can work with fedora community together to make the both community to go well together. ;-) > > for example, share the packages or something like that. > > > > > > > > At 2020-04-03 18:12:39, "Robin Lee" <robinlee.sysu(a)gmail.com> wrote: > > >Hi, all > > > > > >I learned about openeuler is packaging Ukui from news. > > > > > >Any chance we can also submit the packages to Fedora? > > > > > >Or any openeuler packager also want to be Fedora packager? I can help > > >if anyone is interested. > > > > > >-robin > > >_______________________________________________ > > >Dev mailing list -- dev(a)openeuler.org > > >To unsubscribe send an email to dev-leave(a)openeuler.org > > > > > > > > > > > > _______________________________________________ > > Dev mailing list -- dev(a)openeuler.org > > To unsubscribe send an email to dev-leave(a)openeuler.org > > > > -- > Regards > Fred Li (李永乐) -- Regards Fred Li (李永乐)

1 0

[new SIG proposal] Apply for establish QA SIG
by liyongqiang (H) 03 Apr '20

03 Apr '20

Hi Dear TC, We are so pleased to propose to apply for a new SIG QA on 8 Apr meeting, please check it out with PR: https://gitee.com/openeuler/community/pulls/320 Now let me introduce QA SIG for you. 1. Open current test capability to developers in the community. 2. Test openEuler release and evaluate its quality. 3. Distribute the issues to the corresponding teams and track the issues continuously. 4. Draft, release, and maintain release criteria. 5. Develop and maintain test tools which promote code develop and execute efficiency Looking forward to hearing from you, thanks BR, Charlie

2 1

[new SIG proposal] Apply for establish QA SIG
by liyongqiang (H) 03 Apr '20

03 Apr '20

Hi Dear TC, We are so pleased to propose to apply for a new SIG QA on 8 Apr meeting, please check it out with PR: https://gitee.com/openeuler/community/pulls/320 Now let me introduce QA SIG for you. 1. Open current test capability to developers in the community. 2. Test openEuler release and evaluate its quality. 3. Distribute the issues to the corresponding teams and track the issues continuously. 4. Draft, release, and maintain release criteria. 5. Develop and maintain test tools which promote code develop and execute efficiency Looking forward to hearing from you, thanks BR, Charlie

1 0

[Docs]Please check the 2 PRs for the same(perhaps) purpose
by Fred Li 03 Apr '20

03 Apr '20

Hi Docs team, community, To add one committer to Docs team, @amyMaYun submitted [1], and I put -1 comment with reason, but I haven't got any reply so far. @Rudy_Tan submitted another one [2], and it got approved immediately. I am not against the nominated committer himself/herself, but I am against the process. I propos to revert [2] if there is not a reasonalbe explanation. [1] https://gitee.com/openeuler/community/pulls/321 [2] https://gitee.com/openeuler/community/pulls/300 -- Regards Fred Li (李永乐)

3 4

有谁有普华mate-desktop负责人的联系方式
by myeuler 02 Apr '20

02 Apr '20

有的话请帮忙把联系方式发给我 myeuler(a)163.com

1 0

[governance]Do we need to define who should approve for the PRs?
by Liyongle (Fred) 02 Apr '20

02 Apr '20

Hi all, One colleague pinged me to discuss the process about review and approve. What he said was “PR的approve我们的流程是不是需要固定一下，好像感觉没有明确谁最终approve，大家都在看”. In English, it seems that many committers may have reviewed but no one approves usually, should we define who should approve? For your information, currently, one PR will not be merged until both /lgtm and /approve are labeled. Only committers/maintainers can /lgtm and /approve. In my opinion, it is up to each SIG to decide whether they need identify who should do /approve. In my team, we committers follow the non-written rule: 1. the PR should be reviewed, and all the comments should be handled and replied. If not, /lgtm will not be given. 2. if one committer gives the first /lgtm, the committer doesn’t give /approve usually, unless the PR is obviously an easy one. In other word, 2 committers to agree on the PR are a must. What is your opinion or suggestion? Regards Fred 李永乐

4 3