- Infra - mailweb.openeuler.org

28 Mar '20

openEuler基础设施团队的老师，您好。我是中国科学院软件研究所智能软件研究中心的方亚芬，目前参与软件所与华为在openEuler方面的合作，负责openEuler向树莓派的移植部分工作。我们已经申请了树莓派相关的SIG和IRC频道，想在openEuler社区为树莓派申请一个邮箱RaspberryPi@openeuler.org。不知道是不是可以呢？还是只能用现有的邮箱？如果用现有邮箱的话，可以用哪个呢？dev@openeuler.org？谢谢。 -- 祝工作顺利，生活愉快。 ------------------------------------------ 方亚芬中国科学院软件研究所智能软件研究中心邮箱：yafen(a)iscas.ac.cn 地址：北京市海淀区中关村南四街4号5楼

3 2

Re: [Tc] SIG组工作审视
by Fred Li 27 Mar '20

27 Mar '20

Happy to see technical committee members will mentor us. Many thanks in advance. On Fri, Mar 27, 2020 at 7:54 PM myeuler <myeuler(a)163.com> wrote: > > 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是否需要保留或者合并请各位委员给出建议和意见。 > > 谢谢。 > > > > > _______________________________________________ > Tc mailing list -- tc(a)openeuler.org > To unsubscribe send an email to tc-leave(a)openeuler.org -- Regards Fred Li (李永乐)

1 0

[infrastructure][quality]Poor website and blog quality, what should we improve?
by Fred Li 27 Mar '20

27 Mar '20

Hi all, Recently, there happened some bugs in website and blog recently. I list some below: [1] https://gitee.com/openeuler/website/issues/I1CV2L?from=project-issue [2] https://gitee.com/openeuler/website/issues/I1CU4D?from=project-issue [3] https://gitee.com/openeuler/blog/issues/I1AZH8?from=project-issue [4] https://gitee.com/openeuler/blog/pulls/15 The common issue above I can see is that there is not a visible test, especially in blog system. Let's have a discussion on improving the quality. If necessary, it can be one topic for next week's meeting. -- Regards Fred Li (李永乐)

1 0

[infrastructure]Please help to review the guidance to apply for VMs
by Liyongle (Fred) 25 Mar '20

25 Mar '20

Hi infrastructure team and blog team, Virtual machines! Peng Cheng Laboratory donates some virtual machines for openEuler community. To make full use of the resources, I created the following blog to manage, and we infrastructure team will manage it. Please leave your comments here[1]. [1] https://gitee.com/openeuler/blog/pulls/14 Fred 李永乐

1 0

[tc][package]About how to manage and maintain packages/dependencies
by Fred Li 25 Mar '20

25 Mar '20

Hi TC members, Infrastructure team and community members, Recently there are many issues about adding dependencies or new packages [1][2][3]. As a linux operating system, it is extremely critical to manage the dependencies. As we know, Technical committee is managing the packages management policy, however who maintain the new packages is not clear. I have draft idea on this. Please give your advice, opinions on how to maintain the dependencies. - policy. Dependencies are still packages, thus they follow the flow on how to introduce the packages into openEuler community. - Who to maintain: if the packages are new and only dependencies, probably one specific team is an option to do this. - How to automate: Infrastructure should provide a function on getting update from upstream automatically - Dependencies management: an expert should maintain the detailed work on how to choose for ISO and yum for each specific version of release. [1] https://gitee.com/openeuler/community-issue/issues/I1CBYV?from=project-issue [2] https://gitee.com/openeuler/community-issue/issues/I1BHND?from=project-issue [3] https://gitee.com/openeuler/community-issue/issues/I1CBW5?from=project-issue -- Regards Fred Li (李永乐)

2 1

[新SIG提案]申请成立UKUI SIG
by Joey Ma 25 Mar '20

25 Mar '20

Hi Dear TC, We are so pleased to propose to apply a new SIG UKUI, please check it out at PR https://gitee.com/openeuler/community/pulls/291 . Please let me have a brief introduction on UKUI for you. UKUI is designed by KylinSoft Co., Ltd. UKUI is a lightweight desktop environment based on pluggable framework for Linux and other Unix-like Distributions. It provides a simpler and more enjoyable experience for browsing, searching, and managing your computer.It is developed using GTK and Qt. It's comprised of ukui-panel, ukui-sidecar and many other components. Please see the official site http://ukui.org/ for more information. The UKUI SIG will work on making UKUI available to all of openEuler users. Looking forward to hearing from you. Thanks and take care. Regards, Joey

4 6

【Meeting Notice】infrastructure weekly meeting Time: 2020-03-24 17:00-18:00
by Meeting Book 24 Mar '20

24 Mar '20

1 0

Fwd: [Tc] Re: Topics and Schedule RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00
by Fred Li 24 Mar '20

24 Mar '20

There are many new SIGs application in this biweekly TC meeting and please join in if you are interested. ---------- Forwarded message --------- From: Zhanghailiang via Tc <tc(a)openeuler.org> Date: Mon, Mar 23, 2020 at 2:54 PM Subject: [Tc] Re: Topics and Schedule RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 To: Huxinwei <huxinwei(a)huawei.com>, tc(a)openeuler.org <tc(a)openeuler.org> Cc: humin (Q) <humin29(a)huawei.com>, zhaozhijian (A) <zhaozhijian(a)huawei.com> OK~ Updated topics: - Add new sig WukongOS (WebOS for openeuler): related PR is https://gitee.com/openeuler/community/pulls/231 -> zhangpan - Add RaspberryPi SIG: https://gitee.com/openeuler/community/pulls/259 --> 方亚芬 - 1. introduce some development tools packages in openEuler.->myEuler (熊伟） 2. apply to do some clean job in community. refine the organization of the web page. 3. set program language for each package repo https://gitee.com/openeuler/community/issues/I1C1PU - Introduce some big data and ai develop runtime/framework in openEuler: https://gitee.com/openeuler/community/pulls/217 -> zhengxian - Add DPDK SIG: https://gitee.com/openeuler/community/pulls/209 (humin) - Add bounds_checking_function SIG: https://gitee.com/openeuler/community/pulls/274 (zhaozhijian) *From:* Huxinwei *Sent:* Monday, March 23, 2020 11:52 AM *To:* Zhanghailiang <zhang.zhanghailiang(a)huawei.com>; tc(a)openeuler.org *Cc:* humin (Q) <humin29(a)huawei.com>; zhaozhijian (A) < zhaozhijian(a)huawei.com> *Subject:* RE: Topics and Schedule RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 2 additional proposals, One for DPDK SIG, humin29(a)huawei.com https://gitee.com/openeuler/community/pulls/209 One for *bounds_checking_function, zhaozhijian(a)huawei.com <zhaozhijian(a)huawei.com>* https://gitee.com/openeuler/community/pulls/274 Please kindly schedule. Thanks. *From:* Zhanghailiang via Tc [mailto:tc@openeuler.org <tc(a)openeuler.org>] *Sent:* Monday, March 23, 2020 9:34 AM *To:* tc(a)openeuler.org *Cc:* myeuler <myeuler(a)163.com>; 正心 <sinever(a)126.com>; zhangpan (L) < zhangpan26(a)huawei.com>; 方亚芬 <yafen(a)iscas.ac.cn> *Subject:* [Tc] Topics and Schedule RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 Hi All, This is the topics we collected for 3.25 TC meeting: - Add new sig WukongOS (WebOS for openeuler): related PR is https://gitee.com/openeuler/community/pulls/231 -> zhangpan - Add RaspberryPi SIG: https://gitee.com/openeuler/community/pulls/259 --> 方亚芬 - 1. introduce some development tools packages in openEuler.->myEuler (熊伟） 2. apply to do some clean job in community. refine the organization of the web page. 3. set program language for each package repo https://gitee.com/openeuler/community/issues/I1C1PU - introduce some big data and ai develop runtime/framework in openEuler -> zhengxian Please let me know if you would like to add a topic. *From:* Zhanghailiang via Tc [mailto:tc@openeuler.org <tc(a)openeuler.org>] *Sent:* Wednesday, March 11, 2020 2:56 PM *To:* tc(a)openeuler.org *Cc:* zhangpan (L) <zhangpan26(a)huawei.com> *Subject:* [Tc] TC Call for agenda 2020-03-25 RE: 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 Hi Please, send any topic that you are interested in covering. We have already one topic for this call already: 1) Add new sig WukongOS (WebOS for openeuler): related PR is https://gitee.com/openeuler/community/pulls/231 Thanks, Hailiang *From:* Meeting Book via Tc [mailto:tc@openeuler.org <tc(a)openeuler.org>] *Sent:* Wednesday, March 11, 2020 2:37 PM *To:* tc(a)openeuler.org *Subject:* [Tc] 【Meeting Notice】openEuler TC meeting Time: 2020-03-25 10:00-12:00 Topic openEuler TC meeting Time 2020-03-25 10:00-12:00((UTC+08:00)Beijing) Join Conference Join (External) >> <https://welink-meeting.zoom.us/j/627988019> Meeting ID 627 988 019 Convener 张海亮 Tips: Dial the access number to join conference <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 To unsubscribe send an email to tc-leave(a)openeuler.org -- Regards Fred Li (李永乐)

1 0

[Infra]Meeting for help-wanted tasks
by Liyongle (Fred) 20 Mar '20

20 Mar '20

Hi all, On Tuesday we failed to have the meeting with welink for unknown reasons as some of us cannot dial in, and on the meeting we agreed to have another short meeting to check the welink availability. There are some tasks we want to check and review, let have a short meeting to review the tasks on wiki[1]? [1] https://gitee.com/openeuler/infrastructure/wikis/help-wanted%20tasks?sort_i… -- Topic [WeLink Meeting] [Infrastructure] Meeting for help wanted tasks Time 2020-03-20 17:00-18:00 ((UTC+08:00)Beijing) Join Conference Join (Host) >><http://imeeting.huawei.com/meeting/startzoom?id=4028852f70d3f8360170f6951b9…> Join (Internal) >><http://imeeting.huawei.com/meeting/joinzoom?id=832110922&app=welink> Join (External) >><https://welink-meeting.zoom.us/j/832110922> Meeting ID 832 110 922

2 1

Introduction to the new commentable and rename_from features supported in ci-bot
by joey 20 Mar '20

20 Mar '20

Hi all: I’m Joey and from infrastructure team of openEuler. So glad to see you guys and hope everybody is doing well. I’m writing here to have a brief introduction to the new features provided by ci-bot. We believe they would be helpful for your repository management. As it’s known to us, ci-bot is an automation system to handle lots of infrastructure stuff, such as gitee web hook events, repository management, owner management and etc. For more details about our lovely ci-bot, please refer to https://gitee.com/openeuler/ci-bot <https://gitee.com/openeuler/ci-bot>. For now, please let me elaborate how you can make use of the two features to ease the repository management. 1. Add commentable property for repository definition in openeuler.yaml or src-openeuler.yaml under openeuler/community. PR is: https://gitee.com/openeuler/ci-bot/pulls/26 <https://gitee.com/openeuler/ci-bot/pulls/26> . > Previously users could leave a comment at the index page of the project, which is a great feature provided by Gitee. While as we all know, the more conventional way is posting an issue request for questions/bugs/features. So after discussion, we finally consider to disable the comment-to-repository feature for all repositories. So here comes to this functionality, which adds an extra commentable property. If it’s not specified, the default value is false of boolean type. > Actually, you DO NOT need to pay any attention to this new property since non-commentable repository is strongly recommended. Just think it never exists. The example is shown as below, ```yaml community: openeuler repositories: - name: A-Tune description: "" type: public commentable: false # User CAN NOT see or leave comment to repository - name: ci-bot description: "" type: public commentable: true # Users CAN see and leave comment to repository - name: community description: "" type: public # User CAN NOT see or leave comment to repository ``` 2. Add rename_from property for repository definition in openeuler.yaml or src-openeuler.yaml under openeuler/community. PR is: https://gitee.com/openeuler/ci-bot/pulls/27 <https://gitee.com/openeuler/ci-bot/pulls/27> . > Please let me take a real case for example. In PR https://gitee.com/openeuler/community/pulls/128 <https://gitee.com/openeuler/community/pulls/128>, iSulad team wants to change the names of three repositories: iSulad-kit ===> iSulad-img iSulad-lxcfs-toolkit ===> lxcfs-tools iSulad-tools ===> syscontainer-tools > As the PR is shown to us, the code diff is as below, which leaded ci-bot to completely remove the old repository and create a new empty one with the new name, causing loss of all the existing issues and PRs. ```diff - - name: iSulad-kit + - name: iSulad-img description: "" - - name: iSulad-lxcfs-toolkit + - name: lxcfs-toolkit description: "" - - name: iSulad-tools + - name: syscontainer-tools description: "" ``` > While after the PR has been merged, the diff would be like the following. This could make use of the newly supported renaming-repository Gitee OpenAPI to keep all the issues and PRs unchanged. ```diff - - name: iSulad-kit + - name: iSulad-img description: "" + rename_from: iSulad-kit - - name: iSulad-lxcfs-toolkit + - name: lxcfs-toolkit description: "" + rename_from: iSulad-lxcfs-toolkit - - name: iSulad-tools + - name: syscontainer-tools description: "" + rename_from: iSulad-tools ``` > While it should noted that rename_from is not declarative but imperative cause it will take effect only for once and not stored in DB. So if we remove it from repository definition after renaming operation has been finished, nothing will happen. Hopefully I have explained clear enough. Currently the new functionalities are not in production yet and your feedback is rather important to us. So please reply this email for further discussion as soon as you have any doubt. Looking forward to your feedback. Take care! Best regards, Joey

3 2