- Tc - mailweb.openeuler.org

[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

[Infra]Has the sychronization for SIG infor between gitee and website been implemented?
by Fred Li 31 Mar '20

31 Mar '20

Hi infra, I remembered I did submit an issue to request sychronization for SIG information between gitee.com/community/sig/sigs.yaml and website, but I couldn't find it. I check the current status but stil not sure it is done or not. Could anyone help to check? -- Regards Fred Li (李永乐)

1 0

about TC meeting topics
by myeuler 30 Mar '20

30 Mar '20

Hi, TC members, For the reason that more and more topics are added in meeting. I think we should do a ranking work. I propose we should arrange SIG apply topic in high priority in meeting. What about you guys?

2 1

申请增加HA SIG组
by 侯健 30 Mar '20

30 Mar '20

3 2

add to the list
by hxp 29 Mar '20

29 Mar '20

1 0

SIG组工作审视
by myeuler 27 Mar '20

27 Mar '20

Hi, All tc members, Please do the SIG work review according to this list: 1. xinwei hu : Virt, system-tool, storage, sig-kernel, sig-community 2. hong xie : sig-bounds_checking_function, sig-ai-bigdata, security-committee, Runtime, Programming-language 3. hanjun guo : Private, Packaging, oVirt, Others, Networking, 4. xiuqi Xie : Kernel, kae, iSulad, Infrastructure, doc 5. hailiang Zhang : Desktop, DB, Container, Computing 6. Xun Wang : Compiler, Base-service, A-Tune, atune 7 Wei Xiong : dev-util, Application, sig-template, sig-mate-desktop 请各位委员按照上述的分组对SIG组进行审视，审视的内容包含： 1. SIG组是否正常运作。是否有明确的负责人。 2. 相关的项目是否已经有输出，相关软件是否已经进入gitee仓。 3. 相关SIG的主页面是否有明确的介绍信息和完善的说明。下次TC meeting我们审视一下这些SIG的运作，一些SIG是否需要保留或者合并请各位委员给出建议和意见。谢谢。

2 1

Re: 新增RaspberryPi提案
by Hanjun Guo 27 Mar '20

27 Mar '20

谢谢，我初步看了代码，确实改动非常多（不仅仅是代码行数，还有改动的文件也非常多），没想到RaspberryPi有这么多代码没进主线。有几个问题想确认下： 1. 所有的RaspberryPi板子都要支持吗？我看有arm32的板子，目前openEuler不支持arm32，也没有相关的构建； 2. 里面有非常多的驱动，我们能否选一些关键的驱动先做支持？谢谢，郭寒军 On 2020/3/25 12:11, 方亚芬 wrote: > Here is our kernel source of RaspberryPi for openEuler : > https://gitee.com/eulixos/kernel/tree/openEuler1.0-base-raspi/ > > Yafen > >> -----原始邮件----- >> 发件人: "Hanjun Guo" <guohanjun(a)huawei.com> >> 发送时间: 2020-03-25 10:53:23 (星期三) >> 收件人: "方亚芬" <yafen(a)iscas.ac.cn>, tc(a)openeuler.org >> 抄送: "Xie XiuQi" <xiexiuqi(a)huawei.com> >> 主题: Re: [Tc] 新增RaspberryPi提案 >> >> +Cc Xiuqi >> >> Hi Yafen, >> >> Could you please provide the diff statistics for >> the RaspberryPi support? using "git diff --stat" or >> "git log --stat your_raspberrypi_commits" to get the data. >> >> I don't have email address from Jianmin, so did't cc >> him, sorry for that, please cc him if needed. >> >> Thanks >> Hanjun >> >> On 2020/3/13 20:44, 方亚芬 via Tc wrote: >>> openEuler技术委员会的老师，您好。我是中国科学院软件研究所智能软件研究中心的方亚芬，目前参与软件所与华为在openEuler方面的合作，负责openEuler向树莓派的移植部分工作。 >>> 申请在openEuler社区开通SIG：RaspberryPi，PR链接为：https://gitee.com/openeuler/community… 。 >>> >>> 烦请处理，谢谢。 >>> >>> >>> -- >>> 祝工作顺利，生活愉快。 >>> >>> ------------------------------------------ >>> 方亚芬 >>> 中国科学院软件研究所智能软件研究中心 >>> 邮箱：yafen(a)iscas.ac.cn <mailto:jiran@iscas.ac.cn> >>> 地址：北京市海淀区中关村南四街4号5楼 >>> >>> >>> _______________________________________________ >>> Tc mailing list -- tc(a)openeuler.org >>> To unsubscribe send an email to tc-leave(a)openeuler.org >>> > > > -- > 祝工作顺利，生活愉快。 > > > ------------------------------------------ > 方亚芬 > 中国科学院软件研究所智能软件研究中心 > 邮箱：yafen(a)iscas.ac.cn > 地址：北京市海淀区中关村南四街4号5楼 >

3 4