April 2020 - Tc - mailweb.openeuler.org

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